BoldDeskWe are launching BoldDesk on Product Hunt soon. Learn more & follow us.
I attach an example to show this problem.
When I set the Minimum property and then I try to set it on XAML code or even in the C# event handler code, the Value property is setted to the Minimum.
Is this a normal way to work or I must to do something diferent?
Thanks.
I found a way to set Null value:
NumericUpDown.ClearValue(SfNumericUpDown.ValueProperty);
Any way I can't do it on XAML, and I can't set it on the consctructor.
Hi Asier,
We were able to reproduce the reported issue “Null value was not applied when AllowNull and Minimum properties were set.” and have confirmed this as a bug and logged a defect report. You can track the status of the bug from the below link.
We will provide a patch for this issue on March 9, 2023. We appreciate your patience until then.
Note: The provided feedback link is private, and you need to log in to view this feedback.
If you have more specifications/precise replication procedures or a scenario to be tested, you can add them as a comment in the portal.
Regards,
Vijayakumar V
I'm not hurry because I could solve using a simple code form my project and can wait to the solution without problems.
Thanks you.
P.S.:
I had opened this morning an Feedback post with this same problem, because I believe that it is a bug like you confirm me now:
Hi Asier,
Thank you for your response.
As stated earlier, we will be sharing the fix for this issue on March 9, 2023. We sincerely appreciate your patience and understanding while we work on resolving this issue.
Hi Asier,
We have fixed the reported issue "Null value was not applied when AllowNull and Minimum properties were set". Please find the fixed assemblies and NuGet using the below link.
This fix will be included in our upcoming weekly release in the last week of March/2023. We appreciate your patience until then.
Assembly version: 20.4.0.48
Disclaimer:
Please note that we have created this patch for version 20.4.0.48 specifically, to resolve the issue reported in this incident. If you have received other patches for the same version for other products, please apply all patches in the order received.
Note: Please refer to the below link to apply the custom assembly
Note: Please clear the NuGet cache, before using the latest one.
Hi Asiar,
Thanks for your patience.
We are unable to release it along with this weekly release due to some technical reasons. Currently, the patch will generate in the volume 1 release version. Below are the patch and assemblies links,
Assembly version: 21.1.35
Assembly Link: https://syncfusion.com/Installs/support/patch/21.1.35/1531272/F180623/SyncfusionPatch_21.1.35_1531272_4032023092001981_F180623.zip
Nuget:
Disclaimer:
Please note that we have created this patch for version 21.1.35 specifically, to resolve the issue reported in this incident. If you have received other patches for the same version for other products, please apply all patches in the order received.
Note: Please refer to the below link to apply the custom assembly
Note: Please clear the NuGet cache, before using the latest one.
https://www.syncfusion.com/kb/6987/how-to-clear-nuget-cache
This fix will be included in the April 11th weekly release. We appreciate your patience until then.
Regards,
Arunachalam K
Hi Asier,
Thanks for your patience.
We have included the fix in our latest Weekly NuGet release 21.1.39 which is available for download ( https://www.nuget.org/ ). We thank you for your support and appreciate your patience in waiting for this update. Please get in touch with us if you require any further assistance.
Regards,
Arunachalam K