Objective

Record the follow-up diagnostic from Sam's screenshot: Beginning Date/Time shows 10:30 AM while Beginning Hour and Beginning Minute show 14 and 30, making the page appear internally inconsistent.

Live finding

• Record checked: a4RUV000004KMV72AO.
• Beginning_Date_Time__c = 2026-04-29T14:30:00.000+0000.
• Salesforce Lightning renders that datetime in Sam's local timezone as 4/29/2026, 10:30 AM.
• Beginning_Time__c = 14:30:00.000Z.
• Beginning_Hour__c formula is HOUR(Beginning_Time__c), so it returns 14.
• Beginning_Minute__c formula is MINUTE(Beginning_Time__c), so it returns 30.
• The top field is local Eastern display; the bottom formula fields are UTC-derived display values. The page is showing two time representations for the same start time.

Related issue

• Ending_Date_Time__c is blank for this record and many recent partial-day records.
• Ending_Date__c and Ending_Time__c are populated, but Ending_Date_Time__c is not.
• Length_Minutes__c stays blank when Beginning_Date_Time__c exists and Ending_Date_Time__c is null.

Recommended fix

1. Remove Beginning_Hour__c, Beginning_Minute__c, and probably Length_Minutes__c from the visible record layout unless they are needed for admin debugging.
2. Keep user-facing start/end display on Beginning_Date_Time__c and Ending_Date_Time__c, once Ending_Date_Time__c is populated.
3. Fix active New_Time_Off_Request so it writes Ending_Date_Time__c for partial-day requests.
4. Backfill recent partial-day records with blank Ending_Date_Time__c from their populated ending date/time components.
5. If hour/minute helper fields must remain for integration, relabel them as UTC helper fields and move them out of the main user-facing section.