Hi Experts,
We have the requirement to show only the date part for the plan_start_dttm field of task (on the web client). We tried to achieve this by adding a DATEONLY mask type on the custom metadata level.
So, now we got it to show this
instead of this
This worked well from the UI p.o.v as well, because the user no longer has to select a time when setting this date (which is what they expected)
But then we ran into an issue with time zone differences. The customer time zone is UTC+10. Whenever a task was created before 10 a.m, the field returns the date part of the UTC time (without any timezone conversions), resulting in showing the previous date on the client.
Example,
with DATEONLY mask for the plan_start_dttm
- If a task is created on the web client at 8.00 a.m (on brisbane timezone/utc+10), with the plan start date set to 23/10/2023 and saved, soon after saving the plan start date shows 22/10/2023.
- If a task is created on the web client at 11.00 a.m (on brisbane timezone), with the plan start date set to 23/10/2023 and saved, it correctly shows 23/10/2023 .
with DATETIME mask for the plan_start_dttm
If a task is created on the web client at 8.00 a.m (on brisbane timezone), with the plan start date set to 23/10/2023 and saved, the client shows the date & time converted to the timezone as
23/10/2023 08:00. This is accurate in terms of the data, but not the desired UI look.
So, is this a limitation/bug? Can this be achieved without having to go for a code customization?
