DropDown Component is not updating with Default Value when new selectRows is done.
DropDown Default Value is: {{ sw_multipe_items.value ? '' : list_items.selectedRow.StatusID }}
Form data key: blank
I have Table listing information from our SQL DataBase
Table source: Get_Task
I have a dropdown listing statuses from out SQL database
Mappet with: Get_Status
I have a button (update)
trigger:
Post_Status
Get_Task (update table data after update / change)
If user Select status Finish then press Update button and then select next row in the table.
The Status Dropdown is showing "Finish" and not updated with Default Value for the new Selected Row. It looks like it then is stuck on last selected status "Finish" in the DropDown for any selected rows in Table.
Is this a Bug that the DropDown selected value is not refresh. how can I solve this so DropDown list always shows the value for selected row?
After updating the selected row in the table, could you try resetting the Dropdown component so it reverts to its default value?
Also, could you please share screenshots of your Retool table’s inspector settings, the Dropdown component’s inspector, and the related queries you’re using? That would help us get a clearer picture of your setup.
I will tray to explain the process and added some screenshots:
I'm not sure how to reset the dropdown value to default after Update button is pressed.
I'm not any good with JS. I do not know if this will work as a event on the update button?
If the selected row has a status, it will be shown.
If the status is missing (null or undefined), the Select will show a fallback value — for example, the first option in the list (self.data[0].value) or a custom string like "Pending".
this is a tricky one to troubleshoot without the data. If you are ok with sending me a DM with the data included I can try to reproduce it and see if there is a better solution or if there is a Retool bug.
To export the app with data, click the debug console & then the download button:
Otherwise, I'd be curious if the users experiencing this have seen any patterns (maybe a specific row that is often wrong, does it resolve on page refresh, does it happen in an incognito window, etc)