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

Unable to use keyword 'Primary' in Pega 7.1.6 report definition



User has migrated their custom application to Pega 7.1.6. They have been using the keyword 'Primary' to refer to pyWorkPage in their Report Definitions. After the migration, Primary is no longer taken in as a keyword. PRPC now assumes that Primary is a physical page name that it should look for. User needs confirmation whether he should use a physical page name, e.g. pyWorkPage instead of Primary for Report Definitions.

Error Messages


Steps to Reproduce

In a Report Definition, in the Classes & Pages tab set Primary to point to a class e.g. ClassX
Refer a property by using Primary.Property1 in parts of the report definition, for example for the report definition's filter.
Observe PRPC assumes that Primary is a physical page name that it should look for in Pega 7.1.16. While in previous versions this was refering to pyWorkPage.

Root Cause

Primary keyword has not been supported even in PRPC prior to Pega 7.1.6.


The behavior is expected. PRPC help does not list Primary as a supported keyword. This has been confirmed in 6.3 SP1 and 7.1.6 help document.

Published January 31, 2016 - 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