In DM 9.6 We recently noticed that when running the Cube on a PC with a different time zone as the DMA all our trend graphs in our custom old style dashboards the time looks to be shifting the time to the time zone of the Cube client PC but all other trend plots created in trend groups and individual parameter trending selections use the time zone of the DMA. In other words, when running cube on pc with same time zone of DMA all trend plots, dashboards and trend groups, look the same with the same times, but in the above scenario the plots from dashboards do not match the other plots.
I saw this post and assume it is related to this behavior in the old style dashboards, is this correct? “Dashboard App – Client Date & Time – DataMiner Dojo”
Question: Is there a way to have it use the timezone being used on the DMA instead of having to specifically tell it what actual time zone to use?
Thanks
The default timezone is indeed different:
- Dashboards shows everything in the local timezone of the client pc
- Cube shows everything in the timezone of the DMA server
If you want to override this default, then you have to configure a fixed timezone in the ClientSettings.json. This way you can make the web apps use the same timezone as the DMA.
Understood and thanks. So there is no way just to tell DM to use the DMA’s timezone, you must actually figure out how to get the desired timezone string and enter it into the ClientSettings file? This is not very convenient for end customers to figure out how to do this. Is there somewhere on the DMS in a config file that this string can simply be copied?
Thanks again
Correct, there’s no other way at the moment. This should become a configurable setting in the UI of Cube and/or web, but it isn’t there yet. In the help there is a PowerShell example of how you can get the string. If you run that on the DMA server, it will be for the time zone of the DMA.
Ok, so I have tested this by changing both the file at the global lever and at the Client lever restarting DM both time and it is not making any difference. Here is what I have added to both files:
{
“Name”: “commonServer.ui.DefaultTimeZone”,
“Value”: “US Mountain Standard Time;-420;(UTC-07:00) Arizona;US Mountain Standard Time;US Mountain Daylight Time;;”,
“VersionNumber”: 0,
“Mode”: 0,
“InVisible”: false
}
Client connected from EST time computer dashboards are still showing time as Arizona.
As this question has been inactive for a long time, we will now close it. If you want further assistance, could you post a new question with the problems you are still facing?