E
eganeva
Guest
Hi Lino, I was able to reproduce the issue that you mentioned and I believe that it is caused because our property service always returns the values of the properties serialized to string. Therefore if your int field has value 5, the service will return it as “5” and the angular number field can’t process it. I tested the same scenario with older versions of Sitefinity (going back to 10.0) but I observed the same behavior there just like in latest 12.0. Could you provide me with more info in which version this worked for you, and if possible please attach your sample widgets so we can be sure that we are looking into the same scenario? Thanks in advance. Regards, Elena
Continue reading...
Continue reading...