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

Cannot checkin BIX Extract rule containing page group data

SA-104941

Summary



Pega Platform 8.2.2 is updated to  Pega Platform 8.2.5. 
Post the update, when performing Business Intelligence Exchange (BIX) Extract to a database, unable to checkin the BIX Extract rule containing a page group and page list data.


Error Messages



Property name—'To Table' field length of "PromiseList" cannot be more than 30 characters
Property name—'To Table' field length of "PaymentPlanPage" cannot be more than 30 characters



Steps to Reproduce

  1. Create an Extract rule in which the class has a page group and page list data.
  2. Perform the BIX Extract as a database extract.
  3. Save the rule.
  4. Check in the same rule.


Root Cause



When extracting to a database, BIX automatically normalized the data; and stored the top-level properties of a class in one table, and the data embedded page lists and page groups in separate tables.
The default generation of the table name for an embedded page list or page group property is a combination based on the class name and the property name.
This is an existing issue, which is corrected in Pega 8.2.4. However, after the Pega update, the user had not imported the latest BIX rulesets Zip. Hence, the previous rule is retrieved from where the issue is present.


Resolution



Perform the following local-change:

Import the BIX ruleset Zip provided in the media files in the Addition Products > BIX > rulesets.
Suggest Edit

Published December 2, 2021

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