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

BIX - Save an Extract rule fails with table name error



When doing a Save on an Extract rule that has the output format of Database Schema, it fails with the below error.   

Error Messages

Several in the form of:
.pyName: ** 'To Table’ field length of "TestPeriodRangeValues" cannot be more than 30 characters

Steps to Reproduce

Try to save an Extract rule.

Root Cause

This issue was determined to be a product enhancement request.

The product is behaving as designed and an edit of the table names generated must be done.  

When extracting to a database, Business Intelligence Exchange (BIX) automatically normalizes the data, storing the top-level properties of a class in one table and 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 of the based on class name and the property name.

In this example, the based on class for this extract is PegaSampleTest and TestPeriodRangeValues is a page list property.  

The default generated table name is PegaSampleTest_TestPeriodRangeValues which is greater than the 30 character limit for the database table name.


An enhancement request, FDBK-17848, has been created for consideration by Pega Product Management. 
The request is to generate default names that comply with the 30 character limit.



Published January 11, 2017 - 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