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. If you want help with something specific and could use community support, post on the GitLab. Fixed issue in Filter search with negative values. If you didnt find what you were looking for, search the docs.
Before that, the event was only created in the first 10 records.
#Scriptcase search onvalidate full#
Fixed issue in ajax events of the Grid when using full pagination. When I click advanced search button, I can put anything I want in those fields. Fixed issue when saving theme in Charts, in Scriptcase versions that were installed with MySQL. When the app loads the 2 fake search fields are empty by default. also if user in Indonesia login, so user in indonesia so can read only customer record in Indonesia. If user in Brazil login to this application, so this user only can read customer reord in brasil. The title_search is a global OUT I use in the layout header. I try to make a web aplication using scriptcase, this aplication have login page and showing customer database record where depend who login user.
#Scriptcase search onvalidate code#
(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. Error: Expected payload to be a plain object. Yes unfortunately, the macros in thr search events do not seem to add anything to WHERE, so this is what I did (SC bug?). Write a JavaScript function to find the difference of two arrays. Leave the description of the lable-field empty.
Add a new field of type ‘Label’ and place it at the right position on the form. There are projects, where it is necessary to place a ‘save’ button not on the top or the bottom toolbar of a form but within a form, i.e. 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). Add new save button anywhere within a Scriptcase form. (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. I know this is a year old post - but I figured out something just today on same thing.
My friend! Sorry I haven’t skyped in like forever.
0 kommentar(er)
