This is just one of the many scenarios where I wasted my time on understanding certain behaviour of Scriptcase, or trying to locate certain settings. This may or may not be Scriptcase bug, but in any case, the error message is not helpful at all here. If these errors are later corrected, the display fields will be populated again with the correct entries but the search field list still remains empty, causing the error Search fields undefined.
Once errors are detected in the SQL query, the display fields will not be populated and will be filled with some default values while the search field list will be emptied.
Another few hours of my development time has just been wasted on a trivial issue ….īut why would the search field list suddenly become empty for this grid? I guess it is because Scriptcase always tries to re-populate the display/search fields in the grid settings when the SQL query changes. So the solution is to simply go to the grid search settings and re-configure the fields to be searched. Although these fields are usually auto-generated, a quick check revealed that the search field configuration for this grid was indeed empty: Apparently for every Scriptcase grid, several sets of fields to be shown in list view mode (from the Grid > Edit Fields menu), in record detail view mode (from the Grid > Details > Setting menu), and in search mode (from the Search > Advanced Search/Quick Search/Dynamic Search > Select Fields menu) need to be defined. Where exactly is the Fields Positioning option and what was the cause of the error message in the first place?Īfter several more hours of trial and errors I found the solution.
Or perhaps it was meant for an older version of Scriptcase. So what is the issue? A Google search on the error message returned this thread as the only result containing a hint The solution: grid_customers…Left:Search…Fields Positioning…middle:the ‘valami’ push right !!!. In other words, there seemed to be no problems with the grid.
0 kommentar(er)
