Yokohama version displays date field in Portal in strange format

YamaT
Tera Contributor

Please excuse the automatic translation.

 

Today, we upgraded from Washington to Yokohama.
As a result, the behavior of the Date-type field in the Catalog Item became abnormal.

 

Assumption: The “glide.sys.date_format” property is set to “yyyy/M/d”.

YamaT_0-1744178455063.png

 

Problem behavior:

 When entering “2024/12/31” in the Date-type field "Birthdate", it automatically changes to “2024/12/366”.

YamaT_1-1744178473317.png

If I enter 2024/12/31, I want 2024/12/31 to be displayed.

 

Please lend us your wisdom on this issue.

 

ーーー以下、原文ーーー

本日、WashingtonからYokohamaにバージョンアップしました。
すると、Catalog Itemで作った「Date」型の項目の挙動がおかしくなりました。

 

【前提】

Propertiesの「glide.sys.date_format」は「yyyy/M/d」です。

 

【問題の挙動】

Date型の項目「生年月日」に「2024/12/31」を入力すると、自動で「2024/12/366」に置き換わります。

 

2024/12/31を入力したら、そのまま2024/12/31が表示されるようにしたいです。

どうかみなさまのお知恵をお貸しください。

1 件の受理された解決策

@YamaT 

then it's not working as expected and seems to be a platform bug.

If you are sure no script etc is running on that date field which is changing it, then raise a Case with ServiceNow.

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

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

元の投稿で解決策を見る

7件の返信7

@YamaT 

are you saying if you select 2024/12/31 in portal, it's changing it to 2024/12/366?

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

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

@Ankur Bawiskar 


are you saying if you select 2024/12/31 in portal, it's changing it to 2024/12/366?


Yes, that's correct.

@YamaT 

then it's not working as expected and seems to be a platform bug.

If you are sure no script etc is running on that date field which is changing it, then raise a Case with ServiceNow.

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

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader