Hello @Nitesh_Jha ,
Welcome to the Retool Community!
The issue with disappearing drop-down options might arise from how the data is bound and managed in Retool. Ensure you correctly reference the optionsList. For example:
This ensures that you handle undefined or null values gracefully while filtering out duplicates based on linkedinId and providing a clear structure for the id and label values.
Thanks for you code snippet but we already handle that in our js data source. I feel something is wrong with trigger, data state.
When I go to the option list and click on data source then it starts giving me options. After refresh it get backs to the original problem.
Apologies for the delay in responding. This issue may be a bug, but I tested it in my app and encountered the same problem. However, I have a solution for you:
You can set your query to run on page load and configure the dropdown option list accordingly. Please refer to the screenshots for guidance.
Unfortunately this isn't currently supported by the Tags or Tag column type. The Tags and Tag column types only allows for a single selection of options that will be available for every row in the table. It's not possible to configure distinct options for each row.
Are we using a separate Select/Multiselect component to list the options on row selection? Or did this approach work for the options to render independently on each row?
I have a table with a column service_completed. I want this to be a tag with an option list. The data for the option list is in the column services.
The value in services is different per row and is structured like this:
Hi @Shawn_Optipath, this is a current limitation of the table component. I merged your post here so we can update you when there's progress on the request.