Support Article
Data does not get populated for exposed column from the page
SA-7515
Summary
User has configured the database table mapped to work class with few additional columns. The work class has a page property defined on a data class. The database table columns are mapped to page level properties under 'External Mappings' tab of class definition. User opens the report browser to create a new report in this report. In the report configuration window, when the page level properties are included the data is not fetched and shown. When the same report report is opened in 'Designer Studio', it is observed that page level properties do not have page name reference, i.e. value in column is specified as '.memberID' instead of '.Member.memberID'.
Error Messages
No error messages.
Steps to Reproduce
1. Create a work class.
2. Add a page property in this class that should be mapped to a data class.
3. Configure the table mapped to work class to have few additional columns in the database.
4. Open class definition rule. Under "External Mappings" tab of this rule, map newly created columns to page level properties.
5. Open the report browser and create a new report.
6. Include the page level properties in the report definition. The column gets included but data is not shown for this column.
7. Data is present in the database table column corresponding to that page property.
Root Cause
Out of the box activity pzCreateColumnPage performs the job of mapping the field name with the property reference. "pyFieldName" is set to Param.FieldName always. In case of page property, pyFieldName should be set to 'PropertyPath':
Resolution
The changes made to activity pzCreateColumnPage are packaged in HFix-21047.
Published January 31, 2016 - 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.