List Picker Pagination - Feature Request

[tylerm007]

ALS will automatically generate a list picker on the Home and Detail pages for any relationship defined as manytoone. If the parent table has a large number of rows - these will not be displayed in the ListPicker and the lookup value will fail showing a red alert box on the field.

1. Can this widget use the passed in value to do a query to lookup the value?
2. Can this widget support pagination so that thousands of rows can be used?
3. Can this widget support a query like lookup (partial search)?

I have put a patch in to lookup 999 rows - but this is a performance issue which works for demo only.

[patricia-martinez-imatia]

Can you give more information? When you refer to 'the parent table has a large number of rows' , do you mean that the table to which the query is made has a large number of rows?
For example a gif animation to see the use case

[tylerm007]

List Picker Feature I have an order entry system with 1,000's of products. I want to create a List Picker on my OrderItem.ProductID - but show the Product.Name instead of the ProductID (Product table is parent to OrderItem). I am trying to use the ListPicker but the API Bridge will limit the number of rows to a default value (e.g. 20 or 99 or 999) - 1. the ListPicker should always display the requested row display value (search?) using the primary key 2. In s NEW screen - the ListPicker should be able to paginate (first, next, previous, last) 3. The ListPicker should be able to do search by entered fields (select * from Product where "Name" like '%A%") I may be old school here - how does Imatia/Ontimize design UX to support selection from a large table (e.g >1,000 rows)? NOTE: JSON API has a neat feature to include the parent table in the Query (this will eliminate the need for a 2nd request) (http:// ...../OrderItem/100?include=Product&fields[OrderItem]=ProductID,....) Tyler

…

On Tue, Oct 22, 2024 at 4:54 AM Patricia Martinez ***@***.***> wrote: Can you give more information? When you refer to 'the parent table has a large number of rows' , do you mean that the table to which the query is made has a large number of rows? For example a gif animation to see the use case — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABV34VS4EFF4B4VCI56UEDDZ4YHEJAVCNFSM6AAAAABNUJBJKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRYGY3TGMRQGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[patricia-martinez-imatia]

hi @tylerm007,

When the result is more than 1000 values, they are displayed with virtual scrolling and local pagination and the frontend is not overloaded.

Even so, we have considered making the list selector pageable like other components we have and filter in server instead of in local