Support Article

Data Table conversion fails and unable to use Edit in Excel



After upgrading from PRPC 6.3 to Pega 7.2.1, an error occurred when trying to convert data tables to local storage. Once converted, the Data Type records could not be edited using Excel.

Error Messages

** Optimization cannot be performed for classes in this hierachy because of one or more of the following reasons : they are abstract or in a Pega shipped ruleset or mapped to either pr_other or an external table

Steps to Reproduce

Open the data table and click the Convert button.

Root Cause

An issue in the custom application code or rules. The database table mapped to the data table did not have the BLOB column pzPvStream.


To resolve the error when converting the data table, manually create the BLOB column pzPvStream in the database table as noted in the below Support Article.

Once the data table is converted to local storage, the Data Type rule can be delegated to an access group and users will have the option to export and import records as a csv file. When rules are delegated to an access group, a System-User-MyRules instance is created and will contain a list of all the rules that are delegated to that access group. The delegation can be removed by deleting the entry from the System-User-MyRules instance.

Here is a link to a video that provides an overview of the new Manage Change features that were introduced in Pega 7.

Additional rule types were added to the new delegation model in Pega 7.2. Here is the list of rules that can be delegated using this model.
  • Map values
  • Correspondence rules
  • Paragraphs
  • Decision tables
  • Data types

Published February 3, 2017 - Updated February 4, 2017

Have a question? Get answers now.

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