Date/Time Fields not displaying in Workspace

[Sabrina Ethridg]

We have a weird issue where a date/time field will not display in the HR Agent Workspace if it has a value.   This is happening for the Opened (opened_at) and Due Date (due_date) fields.   When I try to manually enter a value in the Due Date field, it won't accept it - I've tried both typing the a date/time in the correct format and using the date picker. 

It leaves an empty space where the field should be.    I've checked client scripts and ui policies to make sure that nothing is hiding the fields.   We do have a HI ticket open with SN, but wanted to post here in case anyone else has seen the issue and knows how to resolve it.

Workspace: 

Backend 

[GlideFather]

Hi @Sabrina Ethridg,

due to the blank space it indicates that the field is hidden, check the ACL and/or client scripts on that table that might have hid the Opened field.

Let me know how it goes

[Sabrina Ethridg]

We've done that and no luck.  There are no acls or ui policies on the opened field that would prevent anyone from seeing it on the form

[GlideFather]

Some of quick ideas:

• Ensure the field is really added to the Workspace form and to the correct view,
• If the field is added to the form but is not visible, please try to remove the field, save the layout and add it back again.
• Before and even after that, erase the cache or use the incognito regime,
• Check in a different browser,
• Was the form updated in UI Builder?
• Is it related to one environment or more?

Good luck! 🤞

[Ankur Bawiskar]

@Sabrina Ethridg 

Things to check

1) is this happening for admins and non-admins both?

2) those fields are present in workspace view

3) any client script or UI policy on your HR Case Child table is hiding? Also check any client script or UI policy running on parent HR Case is running on your child table

4) any field level READ ACL is hiding?

5) clear instance cache using cache.do and then logout and login again

6) check with different browsers

7) did you recently upgrade and this issue started coming post upgrade?

If my response helped please mark it correct and close the thread so that it benefits future readers.