I am having this issue as well. I tried the above solution but it did not fix the issue. This happens to me on two separate pages, an Add page as well as the Edit page. I am not storing the data as a UTC, it is simply a date field in SQL not datetime. I tried to simply uncheck UTC and the control then operates correctly (does not subtract a day), but it will not save the record. I get at 400 bad request with the error stating " The Input was not valid"
By the way there was an issue with the datepicker which has been fixed. Just in case make sure there isn't a client\node_modules directory in your application. If there is delete it and restart the application.
Also if the issue can be reproduced in the files that you have sent us over email before - do tell us what page that is.
Yes it can be reproduced. It is on the Add Deal page and the Edit Deal New page. The field is BL_Date. I have updated to the most current version. I do see a node_modules directory while the application is running but looks to be a shortcut. When I stop debug it is gone. I have made several changes to the app since I sent it but nothing to this field I believe.
I have pulled the code out on the Add Deal page and left the UTC checkbox not checked and now the control is not losing a day. The Edit page on the other hand is still not working even when I uncheck or recheck the UTC box. This issue is very confusing lol.
I may have found the cause of this but need more time to find a fix.
If you can move everything in the same TemplateForm you can probably use a workaround. Instead of setting the Deal parameter of the updateDeal method to ${formData} use ${event} (in the TemplateForm's Submit event handler). Leave the Utc property set to true otherwise the wrong date will end up in the database.
Update: this workaround will not work.
All those date issues are caused by a nasty JavaScript quirk. Browser dates are always in the local timezone however when sending them over the wire to the server they are converted to UTC format. The server also returns dates in UTC format. If we don't do anything all dates will appear in the future or in the past (depending on your timezone). Radzen tries to mitigate that by treating all dates as UTC. Unfortunately the DatePicker doesn't handle this case properly and we have to fix it.
I have an edit page that uses a Template Form with a date value called BL_Date. It is not a UTC date format.
On screen load I am invoking the getDealByID data source method and setting the property "formData" to ${result}. The BL Date field value is set to ${formData.BL_Date}.
The add form version of this form works fine and is also a template form.
I see a date parameter passed to a page but it shows a day behind as you can see the URL has 10/01/2019 but on the page it shows 9/30/19, can you please let me know?