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

Report exported file name is appending with _ in all scenarios

SA-37879

Summary



When user create a report say Test:1 Daily Report and export this to Excel, the generated file name would be Test_1_Daily_Report.

User requirement is to have hyphen (-) instead of underscore (_) in the place of colon (:)

Every space in the file name is getting converted to underscore (_). This was working fine (Test_1 Daily Report) in earlier versions of Pega and not in Pega 7.2.2.


Error Messages



Not Applicable

Steps to Reproduce



1. Create a report say Test:1 Daily Report.
2. Export this to Excel. The generated file name would be Test_1_Daily_Report.


Root Cause



This is working as designed.


Resolution



Here's an explanation for the behavior:

Question 1. Requirement is to have hyphen(-) instead of underscore(_) in the place of colon(:)

Explanation:
Underscores are used as a convention for spaces within the file name (such as between the title of the report and the date/time).

Hyphens are already in use for the dates or times.

Example: Test_1_Daily_Report_2017-05-20_12-20-43.xlsx

Question 2. Every space in the file name is getting converted to underscore(_). This was working fine in earlier versions of Pega and not in Pega 7.2.2.

Explanation: Spaces being replaced with underscores was done to resolve an issue with UTF-8 characters. Going forward, the spaces will be replaced with underscore.

Published July 18, 2017 - 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