Strange behaviour with a date field within a catalog item (date variable not visible)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2024 11:36 PM
Hi,
I have a strange behaviour with a date field within a catalog item set as "public".
On a Cat-Item form a variable "birthdate" is placed.
If you look at the cat item as a logged in user, you can see the variable in the form.
As a non-logged-in user, you only see the label of the variable.
Now the strange behaviour:
If you place a second date variable on the cat item form, both fields are displayed correctly as public (non-logged-user ) in the portal.
There are no Ui Policies or Catalog Client Scripts activated which could trigger the hiding of the variables.
P.S.:
The catalog item has worked for years.
We suspect that the behaviour has changed since the UTAH patch6-hotfix1.
Does anyone have similar symptoms or possible bugfixes without having to create a second date variable on the cat item.
Greetings
Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2024 12:36 AM
Did you try removing and adding the variable again?
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2024 12:52 AM
Yes, i've tried removing and adding the variable again, but unfortunately no effect.
I have also noticed that the strange behaviour occurs in all Catalog items that contain a date variable

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2024 10:30 PM
I have also discovered that the date variable is only visible if the language "English" is selected.
If another language (German) is selected, the variable is not visible.
Could this be related to PRB1651362 (Date fields do not display on the Portal when a non-OOTB language is being used), which was mentioned in the release notes https://docs.servicenow.com/bundle/utah-release-notes/page/release-notes/quality/utah-patch-3.html ?
How can this be fixed?
We are currently on version UTAH Patch 10.