Configure the Ext.nd.Profile document problem (demo database and other database)
both for b2r1 and b2r2 release (thank you jratcliff for send me this new release),
i have some problems in the profiles document during the configuration of the demo.nsf database (or other my personal application using the Ext.nd UI b2r1 and b2r2)
i need to configure the document as indicated in the embedded image.
in particular if put in the field Ext.nd Version the value Ext.nd 2x the Ui interface will be not loaded.
so, i have changed the field Ext.nd Version with value Ext.nd 3x and Save Profile button but still not work... so, with some check and some try i have notice that the hidden fields extUrl and extndUrl are not updated by the QuerySave event formula, so i have put this fields editable and change manually...
finally, the demo.nsf database (b2r1 and b2r1) works correctly with the configurations with Ext.nd 3x parameters, but not working if i put the Ext.nd 2x parameters... what is the differences from 2x and 3x ?
see this image to show the configuration for my demo.nsf database in order to load and work correctly
Sencha - Services Team
Thanks for reporting the bug. I thought that we had fixed the profile doc to work from the Notes Client so I'll double check it. Oh, and Beta 2r2 doesn't include the 2x code since the zip file was then so large that it couldn't be emailed to several people. So if you choose the 2x and point to the 2r2 db, it won't find any code to load.
Download of b2r2?
Hi all, is there a download of b2r2 with ext3 support or is it still only available by email please?
Demo database profile configuration
The database Ext.nd tasks sample app, is missing the two agents : ExtND\Edit ExtND Profile Doc and ExtND\Sign DB and the form Ext.nd.Profile wich need to be copied from database Ext.nd demo
In the form Ext.nd.Profile the WebQuerySave formula should not contains @SetProfileField because the profile document is already being modified, the formula @SetProfileField should be replaced by simple @SetField
This bug may cause the need to edit save the configuration document two times to work