View Categories

Date Field storing slightly delayed values for the in Lead Details | Multi-TimeZone User base

< 1 min read

Issue
– Date Formatting varies from what has been captured on the lead(via form submission) vs. that which has been posted on the UI.

Associated Issues
– Birthdays stored in the DB are reflecting 1 day less or more, considering they remain constant irrespective of timezones. 
Eg: If my birthday is on 6 Feb. 2024, 4 AM IST, my birthday will not be 5 Feb. 2024 3.30 PM PST, rather should be the same time across the globe. 
– Eg. of the concern at hand; 
Preview

Root Cause Analysis
– The date-time view on LS is set to dynamic within the platform so that the timestamp changes with the user profile. Now, on request, some fields remain static so that Datetime fields such as Birthday remain intact irrespective of timezone differences. Hence the time displayed is purely a cosmetic error and will not affect any workflows.

Solution
– There is a fix deployed on a tenant-field level basis based on the customer by the platform team. The below query is pushed into the DB to modify the DateTime field to be static. 
– INSERT INTO `Setting_Base`
(`SettingId`,
`Name`,
`Value`,
`Category`,
`Description`)
VALUES (UUID(), ‘IsDateTypeRenderFixEnabled’, ‘1’, ‘Portal’, ‘Setting to Render only Date Field’)
ON DUPLICATE KEY UPDATE `VALUE` = ‘1’;

Hope this helps 🙂
Scroll to Top