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 filter displays Function Alias name instead of value



User has a report definition with the below filter configuration.

The highlighted section is a custom Function Alias, but could also reference an out of the box Function Alias).

When the user runs the report definition, they see the name of the Function Alias that is, DateToYearMonth instead of the actual value.

This does not change even if they click on the filter hyperlink, bring up the filter modal popup, select values and submit the popup.

Error Messages

Not Applicable

Steps to Reproduce

1. Create a Report Definition and specify filters in the 'Edit Filters' section of Query tab.
2. Make use of a Function Alias as highlighted in the screenshot above.
3. Also configure a custom section to display the filters at runtime.
4. Run the report definition and look at the Filter section.

Root Cause

If the scenario used a top-level property reference or a constant/static value, it would return a raw value that could be displayed.

But in this case, with a Function Alias, the value is not always not a static value.

For example, if the function alias took one of the properties as a parameter, it's output will probably be different for each record.

Hence it is expected behavior to see the name of the Function Alias in the filter section rather than the actual value.


It is expected behavior to see the name of the Function Alias in the filter section rather than the actual value.

To control what's displayed, use a filter caption that is descriptive of it's intent.

Published May 9, 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