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

Field values are not being displayed in RD column filter

SA-28274

Summary



Field values are not picked up in a report definition (RD) column filter. 

The field values are visible in the report itself if the RD runs standalone.

If the RD gets embedded in a repeat grid, when the column filter is clicked at runtime, the actual values are displayed not the ones defined via Rule-Field-Values.


Error Messages

Not applicable


Steps to Reproduce

  1. Create an RD with pyStatusWork.
  2. Put this RD in a repeat grid in a section. 
  3. Save pyStatusWork into the framework layer. 
  4. Create several pyStatus field values to hold string translations. 
  5. Create a Multi-step flow and add the pyStatus created in step three to different shapes. 
  6. Run the flow to create several work items. 
  7. Run the RD created in step one standalone and click filter of pyStatusWork field. 
  8. Run the section and choose to filter on the pyStatusWork field.
  9. Observe that the field value results are not displayed for the pyStatusWork values in the filter field.
 

Root Cause



The localized values are not displayed in the filter popover for a static grid.

Resolution



Either of following local changes will address the concern :
  • Use the control GetLocalizedValue for the columns of static grid.
  • Configure the RD in a dynamic grid, and check the 'Create Dynamic' check box.

Published October 6, 2016 - Updated October 8, 2020

Was this useful?

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.

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