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 Definition JOIN does not return expected results



User joins two classes via  a report definition: Assign-WorkBasket and Work table.

When this "JOIN" is performed by comparing pzInsKey and pxRefObjectInsName, the results returned on two environments are identical.  

However when the JOIN is performed by comparing  pyID (text property) and pxRefObjectInsName the results returned vary between these environments.

Error Messages

Not applicable

Steps to Reproduce

1. Create a Report in Assign-Workbasket class.
2. Join with Work class with pyID and pxRefObjectInsName.

Root Cause

User is using MS-SQL server on one environment and PostGres on another.

MS-SQL does a case-insensitive search by default and PostGres does a case sensitive search.  

User is using a mix of upper and lower case for his work object prefix.  

This is reflected in the resulting pyID. Due to this the JOIN comparison yields different results across databases.


User is advised to assume case sensitive search to keep results consistent across databases. In the current scenario user can try the following :

1. Change the collation sequence:  This sequence determines whether the comparison is case sensitive or not. This  is an advanced database developer / administrator task and should be done with care.

2. Fix the Work object prefix : Ensure that work object prefix is of one case only. Though this will work for new work objects, user may need to write an utility to fix older work objects.

3. Create sub-reports :  Use a sub-report to fetch data and apply pxUppercase function alias.  This can then be used to apply JOIN.
Suggest Edit

Published December 21, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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