Support Article
Summary view join with work class throws error
SA-7809
Summary
User created a summary view report in 'Assign-Worklist' class and configures a join with a work class.
When the report is run, following error opens:
Error Messages
** There was a problem getting a list: code: 4104 SQLState: S0001 Message: The multi-part identifier "WK.pxObjClass" could not be bound.
Steps to Reproduce
- Create a report in "Assign-Worklist' class.
- Perform a join with a work class.
- Use 'getContentAgeInCalculatedOrder' as the source of the report source.
- Run the report.
Root Cause
The 'getContentAgeInCalculatedOrder' activity is created specifically for some Out-of-the-Box (OOTB) reports under "AssignmentMonitoring" category and does not support all features of summary view SQL.
It is recommended to use OOTB 'getContent' activity. When user configured 'getContent' activity as report source, it throws another error:
This error opens as the table mapped to work class is in a different database than core PegaRules tables.
When executed the SQL statement on PegaRules database manually the same error message displays.
Resolution
As per product design, if the work class database and the assign-worklist database are different then we cannot perform a join directly.
For a solution you can define a synonym for the PegaRULES database.
The synonym must point to the work class table in the PegaRules database instance.
Ensure that the Data-Admin-DB-Table instance for the work class is changed to use the synonym name and PegaRULES as the database name.
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.