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

Format error in Report Definition Output



Try modifying the width of a column on a Report Definition output which has a control as the Format value, error is thrown “saying incorrect format value”.

Error Messages

pyPropertyName:** This is an invalid format. Click the Down arrow key and select a valid format.

Steps to Reproduce

  1. Generate Report using a Report Definition in which enter format value on any of the column as Date/Integer.
  2. After the Report gets generated, try to modify the width of the column for which you kept a format value.
  3. Hit “Apply” and the issue will be replicated.

Note:-If “Date” control is used, the property used by us was of “DateTime” type. And when we used Integer control, the property used in Report Definition was of “text” Type


The reported behavior is not a bug and is working as expected the validation is called to check if the type of the property and the format (control ) is matching if not it throws the error.

When we try to modify the column width on a Report Definition output and hit “Apply” ac activity- pzPostReportEditColConfig is being called, which further calls another activity- pzValidateFormatField.
The activity pzValidateFormatField has a java step which checks for the Data Type of the property used in Report Definition, if it is DateTime and it is not equal to the Data Type of the HTML property then it should throw an error saying "This is an invalid format. Click the Down arrow key and select a valid format” which we observe on the screen.


This issue was corrected in was corrected in later releases.
Suggest Edit

Published June 16, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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