When trying to set a DateTime Parameter on a Low Code App through the "Parameter Page" component, it seems to be oddly tied to the timezone that the DMA is set to.
For example, the DMA is set to the timezone EST. If the computer I'm running the Low Code App on is also on the EST timezone, then it works as expected. If I set it to "29 / 05 / 2024 13:00", then it saves to the parameter as "5/29/2024 1:00:00 PM" (Note that this is the common US datetime format of MM/DD/YYYY HH:MM:SS)
However, if the computer I'm running the Low Code App on is on the PST timezone, then it instead sets 3 hours ahead of the value that I put. If I set it to "29 / 05 / 2024 13:00", then it saves the parameter as "5/29/2024 4:00:00 PM".
When I set the parameter on DataMiner Cube, it doesn't matter what the timezone of my local computer is and sets it to the exact value I input.
This parameter shouldn't be setting the datetime based on the timezone. Is there a way to fix this on Low Code App?
Low-Code Apps (and all our web apps) run by default in the timezone of the end-user, while Cube always uses the same timezone as the DMA.
The default timezone of the web apps can be configured. If you prefer using a fixed timezone, which could be equal to the timezone of the DMA, then this can be configured in the clientsettings.json.
To explain the behavior you're currently seeing: when setting "29 / 05 / 2024 13:00" on a device in PST, while the DMA is in EST, then this value gets converted to the timezone of the DMA (1pm PST is 4pm EST). The displayed parameter values are generated on the DMA using the timezone of the DMA, which is confusing for users in another timezone, this should get fixed. But the raw value set on the parameter is correct.
Parameters values that are dates did not take the time zone into account within Dashboards and Low-Code Apps. This has been resolved as of 10.4.8.
Hi Wim! Thank you for the response! I’ll try this solution