Support Article

Export to Excel does not localize field values of report



When you Export a Report Definition (RD) to Excel, non-localized property values are exported instead of the localized field values. This issue does not occur with Export to PDF of the report.

Export to PDF compared to Export to Excel

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a Report Definition with pyStatusWork as the source of one column.
  2. Create localized field values for pyStatusWork.
  3. Run the report.
  4. From the report's Actions menu, click Export to Excel.
    The Excel spreadsheet does not display the localized field values. Instead it displays non-localized property values.

Root Cause

A defect in Pegasystems’ code or rules

Rule-Utility-Functions (RUFs) used by Export to Excel do not consider pxObjclass when exporting field values because of a missing context page.


Perform the following local-change:
  1. Do a private check out of the report.
  2. Edit the report to change the columns with localized field values to use the control GetLocalizedValue:
    a. Click the gear icon next to the column.
    b. In Edit Column Options, the Column Format field, specify GetLocalizedValue.
    c. Click Submit.
Edit Column Options to specify Column Format GetLocalizedValue

Related Content
If you are using Pega 7.1.8, see SA-20204,

Published March 3, 2017 - Updated September 14, 2017

100% found this useful

Have a question? Get answers now.

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