We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date
close icon

SfNumericUpDown Value is always 0

hi,
can you check why since last release value property is always 0?
thanks

7 Replies

LU Luca April 8, 2019 12:09 PM UTC

tested the prev version and it is ok, so the bug is just in the last release


BK Bharathiraja K Syncfusion Team April 9, 2019 11:53 AM UTC

Hi Alberto, 
 
Greetings from Syncfusion. We have tried to replicate the reported issue at our end by created a sample with the provided information that you mention on your last update, we are afraid that, we are not able to reproduce the issue at our end. 
 
Please find the tested sample below.  
 
 
We are not able to reproduce this issue at our end, so can you please revert us by modifying the sample based on your application along with replication procedure. This will be helpful for us to investigate further and provide you a better solution at the earliest. 
 
Regards, 
Bharathi. 



LU Luca April 10, 2019 10:32 PM UTC

i mean that at code level  property value is always 0 even if the control shows a number.
can you try?
works just till version 16.4.0.54
thanks


BK Bharathiraja K Syncfusion Team April 11, 2019 10:16 AM UTC

Hi Alberto, 
  
Sorry for the inconvenience caused.  
 
We were able to reproduce the reported "Public Value property not updated properly" issue at our end and logged a defect report. 
 
 
We will fix this issue and include in our weekly NuGet which is scheduled to be release on 23rd April 2019.  
  
Regards, 
Bharathi. 



LU Luca April 12, 2019 10:53 AM UTC

thank you.
guys your library are amazing but (my 2 cents) you should improve your test process because often happpen that a new release breaks something.
of course it can happen, but please improve your test phase ;)


IM Iyyappan Mani Syncfusion Team April 16, 2019 01:17 PM UTC

Hi Alberto, 
 
We deeply regret the inconvenience. 
  
We used to test our controls manually and through automation before every release to make sure there are no breaks in the existing behavior. 
  
However, in this particular case, we have made some architectural changes for the stability of SfNumericUpDown control and it lead to this break in the behavior. We are continuously working on to ensure seamless upgrade for our updates and we will make sure these kind of issues are avoided in future. 
 
Regards, 
Iyyappan M. 




IM Iyyappan Mani Syncfusion Team April 23, 2019 02:55 PM UTC

Hi Alberto, 
  
Thanks for your patience.  

We couldn’t able to move this fix in the promised weekly nuget and hence we have fixed and provided the patch for the reported “Public Value property not updated properly“ issue and it can be downloaded from the below link.  

Please find the patch setup from the below location.  

or  
  
Please find the patch assemblies from the below location.  

or  
  
Please find the NuGet from the below location.  

Assembly Version: 17.1.0.38  
   
Disclaimer:  
Please note that we have created this patch for version 17.1.0.38 specifically to resolve the issue reported in the forum 143841. If you have received other patches for the same version for other products, please apply all patches in the order received. This fix will be included in our next weekly NuGet release which is scheduled to be rolled out on April 30th  2019. We appreciate your patience until  

Note: 
Could you please follow the below steps before applying the patch clear the Nuget cache in your machine and check.  

 
Regards, 
Iyyappan M. 


Loader.
Live Chat Icon For mobile
Up arrow icon