All: I am new to Alpha Anywhere and while I love the power of the tool, I have to admit that I'm getting very frustrated with it! This week alone, I have been through roughly 480 threads on the forum and watched many videos, but I still cannot find how to do something with initializing list component on a UX. I realize that this is probably very easy to do, but I am struggling here.
I am building a library look-up mobile application which contains two panels: the first contains search criteria (search value, search type, item class, and item type and a search button) and the second panel contains the search results which is only displayed once the end-user enters search criteria clicks the search button on the first panel. The "search" button works well with all of the search criteria being correctly processed and returning the correct records on the search results panel.
Unfortunately, my problem is that the list obtains all records in SQL statement (which is not filtered) when the UX is initially rendered (and with over 100K records, it is taking a while for the UX to display). It doesn't make sense to have the SQL statement execute until the end-user enters search criteria and clicks the search button.
Everything that I've read pertaining to the list control starts out with a pre-populated list which is then furthered filtered based on end-user provided search critiera. Can anyone please provide direction to this me on how to make the list behave dormant until the end-user clicks the "search" button in the UX?
Any assistance you can provide to me is greatly appreciated!
I am building a library look-up mobile application which contains two panels: the first contains search criteria (search value, search type, item class, and item type and a search button) and the second panel contains the search results which is only displayed once the end-user enters search criteria clicks the search button on the first panel. The "search" button works well with all of the search criteria being correctly processed and returning the correct records on the search results panel.
Unfortunately, my problem is that the list obtains all records in SQL statement (which is not filtered) when the UX is initially rendered (and with over 100K records, it is taking a while for the UX to display). It doesn't make sense to have the SQL statement execute until the end-user enters search criteria and clicks the search button.
Everything that I've read pertaining to the list control starts out with a pre-populated list which is then furthered filtered based on end-user provided search critiera. Can anyone please provide direction to this me on how to make the list behave dormant until the end-user clicks the "search" button in the UX?
Any assistance you can provide to me is greatly appreciated!
Comment