Hello All ,
we have a database view , using that we created a record ( disable data sync) as Appian record is not allowing view with enable sync option.
facing performance issues with this Appian record picker, please can someone help with the following questions :
Question 1 : how can we implement a minimum character requirement for the search input in the record picker (pickerFieldRecords) to reduce the number of database queries ?
Question 2 : how can we limit the initial load to a smaller subset (i.e. only load 20 result based on user filter) of records to prevent performance bottlenecks ?
Question 3 : is there a way to implement Appian caches record data in memory with disabled data sync record type ?
Thanks!
Discussion posts and replies are publicly visible
That said, it’s important to note that the current approach (using a non-synced record type based on a view) is not inherently wrong. In fact, if the view performs well and the volume of data is manageable, this solution is perfectly acceptable.
However, if you're experiencing performance issues now — or anticipate scalability concerns in the future — the synced approach via Integration offers more control and flexibility.
Ultimately, the key is to base the decision on a clear understanding of the performance profile of the current view and its expected usage