Support Article
Export to Excel does not localize field values of report
SA-34501
Summary
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.
Error Messages
Not Applicable
Steps to Reproduce
- Create a Report Definition with pyStatusWork as the source of one column.
- Create localized field values for pyStatusWork.
- Run the report.
- 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.
Resolution
Perform the following local-change:
- Do a private check out of the report.
- 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.
Related Content
If you are using Pega 7.1.8, see SA-20204, https://pdn.pega.com/support-articles/export-report-excel-does-not-localize-value.
Published September 14, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.