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 save Access group



You observe errors, regarding pyUserRoles and pyPortals not being valid records, when attempting to save an access group after changing major version on the application ruleset.

Error Messages

pyUserRoles:Pega:SmartDisputeExceptionProcessingVP is not a Valid Record for use by this

Steps to Reproduce

Save the access group after changing the major version of the ruleset associated to the user roles and portals.

Root Cause

The root cause of this problem is a defect in customer application code/rules. The rules being referrenced are from a prior major revision and rule resolution doesn't cross major revision boundries.

Illustrated root cause: perform save-as on an invalid record reference to the new major release and observe specific rule error is removed - and as documented in


The explanation for this behavior is as follows:

AYour access group rule is trying to reference rules that exist in a prior major version of a ruleset. To bring forward rules to the next major version the recommended method is skimming. Process: (
Suggest Edit

Published April 1, 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