I have a screen with 2 dropdowns; Commodity and Variety. Variety depends on commodity. Variety can have duplicate names, belonging to different commodities.
I have set this up as normal, fetching the full variety list, binding it to the selected commodity via the ParentBinding configuration.
Everything has been working fine, the dropdown only shows the varieties for the selected commodity.
However, when a user types in the field and lets the option auto-complete, sometimes a variety is selected that is not in the dropdown list. This is only possible when the name matches a variety that is available in the list.
This happens sometimes and results in that a variety with the correct name but belonging to a different commodity is selected. This is undesirable and as a result fails the validations we have set up.
Is there a workaround for this, or any fixes on our end?
Thanks in advance
P.S. I should mention that the variety fetch is set up, so that for each parent commodity, there is an empty variety option. This is to ensure the user can select an empty variety, regardless of which commodity they have selected as this field is not mandatory.
Screenshot of the (partial) result of the GetVarieties data action, empty values are inserted for all parent commodities. Note the duplicate Durum, belonging to different parent commodities.
Hello @Fred Derks
To make this more efficient and collaborative for the community, please share a sample OML where that issue can be reproduced. That way, someone from the community can take a look without investing more time in implementing the use case.
Cheers,GM
Hello @Gonçalo Martins
No problem, I have created a small demo application with instructions to reproduce the bug
All the best, Fred
First of all, great work on the reproduction scenario - I hoped everyone did this since it would be so much easier for everyone 💪🏻
I replicated the issue, and it seems to be something on Wijmo's Flexgrid side, so I created a task under ROU-11823 (future reference on release notes) so we can try to find and fix the issue in the next release.