Closed CooperZhao1998 closed 1 month ago
Hi @CooperZhao1998
Thanks for reporting. It looks like this is caused by the update in 14.4 that made it so that when you have chained Select components, when you change the first Select, then the second Select should only contain values based on the updated data(options).
In your scenario, it appears that you are updating the value of the second Select before the data(options) are updated, so the value is removed.
You could probably solve this by updating both the values and the data when you add the second Select component.
Hi @AnnMarieW
Thanks for your prompt answer!
So you mean I should combine the two callback together, so the data(options) should will be update when there is record_select
been added?
Also I wondering why this will work both in 0.12 and 0.14.2, but not in 0.14.4?
I didn't dive into the code to see if there was a simpler way to do this - maybe with a different type of pattern matching callback? But yes, combining the callbacks is the first thing I'd try.
It doesn't work in 14.4 because there was a change made to verify that the value was valid based on the options data. This step was missing in previous versions.
Got it! Thanks!
I am creating an app that can add/remove records while preserving the selected value. And the data of the records are depends on the value selected from the topic dropdown. The issue is after I select the topic value, I am not able to select the record value, it will always set to none no matter which value I select.
This issue only happed in 0.14.4. And the code works fine in 0.12 and 0.14.2.