![]() It is when the onScriptInit for the whole app (NOT the search onScriptInit) that the values are added to the WHERE. Then the grid processes the search, which really does nothing as far the ‘fake’ fields are concerned. When I click advanced search button, I can put anything I want in those fields. 2.a) Select type field works fine executing code for the AJAX events onClick, onFocus, onChange. You can create some rules, like to save the searches by user login. It works as a preparation for the application, where it is possible, among other things, to manipulate variables, perform validations and change the connection with the scchangeconnection macro. This feature allows the end-user to save his searches in a profile. For information about the timing of events execution or other information, access the documentation of the desired event. When the app loads the 2 fake search fields are empty by default. It is the first event executed in the application, being fired even before the SQL and HTML assembly. The title_search is a global OUT I use in the layout header. (I had to do this because the encryption SQL code that works elsewhere in the app caused errors in search code. ![]() In the grid’s event onScriptInit (NOT the search onScriptInit) - searchname and searchaddress are ‘fake’ fields I created in advanced search…No corresponding fields in DB. Yes unfortunately, the macros in thr search events do not seem to add anything to WHERE, so this is what I did (SC bug?). So I also needed to create some ‘fake’ fields in the advanced search, and intercept the values, then slip those in the special WHERE using the AES_DECRYPT). (I use AES_DECRYPT in the SQL Select and preparation boxes and other events to do it FYI, but that is another post LOL). On a grid app I am using aes_encryption, so I am not able to directly use the advanced search (or any search) for those fields. You and I always seem to be trying the same things LOL. ![]() Next, we will go to the option 'Fields', because we will change the type of the field 'customerid' to 'Select' and activate the option 'Use Select2'. I know this is a year old post - but I figured out something just today on same thing. We created the first application of the type Search using the table 'customers', and we will select only the field 'customerid' to be used in the application. My friend! Sorry I haven’t skyped in like forever. This event occurs after form validation (onValidate and onValidateSuccess), when clicking the Save button, and before executing the SQL command to Update the record in the database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |