While using UTC date with "MarkedDataCreate" to set Begin and End Timestamps. In smartClient the end Timestamps is displayed as LocaleDate.

MIP
, , , ,
1

Is this behaviour caused by a setting in XProtect ?

Is the End Date always in Local Time ?

2

Yes. It is possible to make the Smart Client run in UTC time, you can do so in Setiings (gear icon in the upper right of the Smart Client) on the Advanced tab.

The usual way to use the system is however that the internal representation in the server is UTC and all clients convert it to local time. This scheme works even if you have a system stretching multiple time zones.

Usually, if you develop something working with bookmarks you should use to UTC when you ask for data in the server and convert to local time when you show the data in the client.

3

Thank you Bo for this answer,

The thing is SmartClient displays mixed information :
[cid:image004.png@01D6610C.12E0C2F0]

This evidence has been locked using ServerCommandService.markedDataCreate with timeStart and timeEnd in UTC. However, SmartClient displays the evidence with Start in UTC and End in Locale Time.
Is it a display problem ? Is there something we could check to investigate further ?
Could this be coming from the markedDataCreate function ?

4

Please try again to show/upload the picture, I think the picture is a good idea for me to see to understand..

Also:

Do you see the same issue if you use the SDK sample? (While testing you might want to comment out the delete part.)

https://doc.developer.milestonesys.com/html/index.html?base=samples/bookmarkcreator_component.html&tree=tree_2.html

or

https://doc.developer.milestonesys.com/html/index.html?base=samples/scbookmark.html&tree=tree_1.html

If the sample does not cause the same issue please compare your code to that of the sample..