Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

DateTime format is incorrect when operator locale is ja



In a report definition, on setting the DateTime format as 'MMM/dd/yyyy HH:mm z', the DateTime format is incorrect when the Operator’s locale is set to Japan (ja).
That is, the month format (MMM) displays of '4月' or '3月' in Japanese Locale instead of Apr or Mar.

The DateTime Format is correct when the Operator’s locale setting is not Japan (ja). That is, the format of month is 'MMM' (MMM displays 'Apr' or 'Mar').

Error Messages

Not Applicable

Steps to Reproduce

  1. Set the DateTime Format as 'MMM/dd/yyyy HH:mm z' in the report definition. 
  2. Set the Operator locale to 'ja'.

Root Cause

This behavior is as per Pega product design. The months display as Apr or May for Japanese localization.


Here's the explanation for the reported behavior:

When the custom format for month is configured as 'MM', the month displays in a number format (for example, 01,02,03...). However, if the month is configured as 'MMM' or 'MMMM...', the number format is converted to text and is displayed as Jan or January.

According to the custom format, 'MMM/dd/yyyy HH:mm z', when the Operator’s locale setting is not Japan then the format of month displays correctly as MMM (such as Apr or Mar). However, when the Operator’s locale setting is Japan (ja), the English characters are not displayed in the Japanese localized application. Hence, actual Japanese month in text format is displayed (for example, 1月、2月、3月).

Update the format to 'MM/dd/yyyy HH:mm z' to display the same format or text for both Japanese and non-Japanese localized versions.


Published September 12, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us