I'm working on a low code app that includes a chart filtered by a dropdown. The dropdown is filled using a query that retrieves all elements using a specific protocol, are active, and match an ID stored in a DOM instance. This DOM instance is listed in a table on a separate configuration page.
Problem:
The dropdown and table only exist on a configuration page for now. However, the chart on the main page (which uses the dropdown value to filter data) only works after I visit the configuration page. If I open the main page directly, the dropdown doesn’t populate, and the chart remains empty.
It seems like the dropdown query only refreshes after the configuration page is loaded.
What I’ve tried:
-
On the main page, I added an event action to:
-
Execute “Fetch the data”
-
Execute “Select Item” on both the dropdown and the table
But this had no effect.
-
Expected behavior:
The main page should populate the dropdown automatically and show the filtered chart, without requiring the configuration page to be opened first.
Question:
How can I make the dropdown and table data initialize properly on the main page without needing to open the configuration page first? Is there a way to trigger the DOM instance and the dropdown query loading from the main page?