Hello everyone, I have had a problem with the use of the DropdownList component when working with tuples, for some strange reason the value to which the component is bound is changing by the first value of the data list.
This problem does not happen to me with other components that use another type of value only with this one of the tuples.
I have tried to handle this bug with ItemTemplate or ValueTemplate, without having the desired result.
I don't want the value to change on its own.
Thanks for any help or comment.
In this example, the selected record is the one with the value: "Value4" but when you enter the section to update the record, in "Status" the value of the record is changed by itself by the first value of the data list .
Hi All,
We are validating the requirement. We will update the further details in two business days(27th June 2022).
Regards,
Udhaya Kumar D
Update:
I have been working on the problem in a separate template and I am sharing it so that you better understand the context.
I have put two messages in the console to see the behavior of the binding and if it is modified by itself.
As you can see in the capture that I share, the value at a certain moment changes by itself, it does not usually happen with the other component that binds a "string" in which the value remains
From what I can identify, it is as if the bound tuple is not matching any of the records in the list and it is changed to a default value.
Attached is the ".razor" file of the example.
Thanks for any help.
Hi Mxuavl,
From our end, we can reproduce the reported issue of “when component initialized with tuple shorthand definitions the preselect value does not update to the component" in two business days, we'll provide further information regarding the issue (June 29th,2022).
Regards,
Udhaya Kumar D
Thank you, I will be waiting for your response.
Hi Mxuavl,
We have confirmed the reported issue is an issue at our end and this fix will be included in our upcoming patch release, which is expected to be rolled out on July 20th,2022.
You can track the status of this issue from the below feedback.
Feedback: https://www.syncfusion.com/feedback/35987
Disclaimer: Inclusion of this solution in
the weekly release may change due to other factors including but not limited to
QA checks and works reprioritization
Regards,
Udhaya Kumar D
Hi Mxuavl,
We have fixed your reported issue from our end in the latest 20.2.39 version (Release Notes). So, we suggest you upgrade to our latest version to resolve the current issue.
Regards,
Udhaya Kumar D