Date Picker does not work using Catalog UI Policy

[Nick29]

In the Service Portal, we have a catalog item that uses a catalog ui policy to show a date field contingent on another field selection.

When the date field becomes visible, clicking the calendar button does not generate the calendar pop-up. The catalog ui policy has "read_only=false, mandatory=true, and visible=true". There are no other rules or scripts that affect this date field. I have also attempted to inactive this catalog ui policy and use an onChange policy to hide on load, then toggle the above values if true or not, also to no avail.

Prior to upgrading to Utah, this was working as expected. Searching message boards, I have not seen any other people with the same issue.

Any suggestions?

[SanjivMeher]

Can you make the read only to 'Leave alone' and try?

[Nick29]

Thank you for the suggestion. It was the original setting, but I tried read only = no, to ensure it was explicitly not causing an issue. I reverted it back to "Leave Alone", but still behaves the same way.

[Tai Vu · Accepted solution]

Hi @Nick29 

Have you checked the console for any error messages?

Additionally, if there have been customizations to the portal theme in your instance, the date picker might still be present but in a different location. Please refer to the following threads for more information:

KB0952715 - Calendar type fields are not working properly in catalog forms in service portal

Datepicker is not working on Service Portal

Cheers,

Tai Vu

[Nick29]

Support has found someone put an custom angular provider for a specific catalog item to show date in a certain format. After system updates, that broke and affect multiple catalog items. Disabling the custom code corrected the date picker.