Hi everyone,
I’m using the AdvancedDropdownServerSide widget with on-scroll pagination. Everything works fine initially — items load in batches as I scroll.
However, when I later refresh the dropdown data (for example, after a search or filter reset), the API returns 100 items and my list variable correctly holds all 100, but the dropdown only renders 2 items in the UI.
Here’s what I’ve tried so far:
Cleared and reassigned the list using ListClear + ListAppendAll.
Rebuilt the list in a loop.
Confirmed that the variable has all 100 items.
It looks like the widget keeps some internal pagination state after the on-scroll action and doesn’t fully refresh even though the list is updated.
Has anyone faced this issue before? Is there a way to force the dropdown to re-render or reset its internal cache when refreshing data?
Dou you have a sample OML file?
Hi @Akhil Nazim KT
Since Initial scrolling works, API returns 100 records, List variable contains 100 records but only after a refresh you see 2 records, the most likely issue is that the Advanced Dropdown's internal Select2 pagination cache is not being reset. Forcing the widget to be destroyed and recreated (via a changing WidgetId/Key) is usually the first thing that can be tried.
The exact component name and version will help identify whether there's a known bug and the correct reset action.