1 day behind on chart

Radzen Studio Angular
1

I thought the chart should display whatever the value supposed to be but not for a date. It seems to display 1 day behind.

image
image.png801×445 16.4 KB

image
image.png1155×227 59.1 KB

2

This looks as a timezone conversion problem. Does it happen for all dates or just the ones highlighted? Can you please check how those dates look in the JSON response? You can get that from the Network tab of your browser.

3

This happen to all the date. The JSON response is display correctly, but when it display on the chart, it display one day behind.

4

I need to see the actual JSON in order to troubleshoot. Can you paste it here?

5

image
image.png743×335 9.08 KB

6

Would it be too much to ask for a text version instead of a screenshot?

7

Not at all.
{
"value": [
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZlN2hnPSc="",
"DateWorked": "2019-10-02T00:00:00Z",
"HoursWorked": 8.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZlN2lJPSc="",
"DateWorked": "2019-10-03T00:00:00Z",
"HoursWorked": 8.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZlN2ljPSc="",
"DateWorked": "2019-10-04T00:00:00Z",
"HoursWorked": 4.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ0SmNNPSc="",
"DateWorked": "2019-10-07T00:00:00Z",
"HoursWorked": 8.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ0SmRNPSc="",
"DateWorked": "2019-10-08T00:00:00Z",
"HoursWorked": 8.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ0SmJvPSc="",
"DateWorked": "2019-10-08T00:00:00Z",
"HoursWorked": 1.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ0SmM0PSc="",
"DateWorked": "2019-10-09T00:00:00Z",
"HoursWorked": 9.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ0SmNBPSc="",
"DateWorked": "2019-10-10T00:00:00Z",
"HoursWorked": 8.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ0SmNrPSc="",
"DateWorked": "2019-10-11T00:00:00Z",
"HoursWorked": 8.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ0L2E0PSc="",
"DateWorked": "2019-10-14T00:00:00Z",
"HoursWorked": 8.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ0L2FRPSc="",
"DateWorked": "2019-10-15T00:00:00Z",
"HoursWorked": 8.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ0L2FrPSc="",
"DateWorked": "2019-10-16T00:00:00Z",
"HoursWorked": 8.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ0L1o4PSc="",
"DateWorked": "2019-10-17T00:00:00Z",
"HoursWorked": 8.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ1RlVjPSc="",
"DateWorked": "2019-10-17T00:00:00Z",
"HoursWorked": 1.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ0L2JNPSc="",
"DateWorked": "2019-10-18T00:00:00Z",
"HoursWorked": 8.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ1Rmg4PSc="",
"DateWorked": "2019-10-18T00:00:00Z",
"HoursWorked": 2.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ1Z2pnPSc="",
"DateWorked": "2019-10-23T00:00:00Z",
"HoursWorked": 12.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ1Z2o0PSc="",
"DateWorked": "2019-10-24T00:00:00Z",
"HoursWorked": 15.0
},
{
"@odata.etag": "W/"YmluYXJ5J0FBQUFBQUZ1Z2lFPSc="",
"DateWorked": "2019-10-25T00:00:00Z",
"HoursWorked": 8.0
}
]
}

8

Thanks @HotRice! I confirm there is an issue with displaying dates in some timezones. We will look for a way to fix that.

1 Like