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 PageList table mapping

SA-22968

Summary



When mapping same table in the 'to table' for a pagelist in the Business Intelligence Exchange (BIX) extract rule form, a warning is being thrown stating that same table may not be provided for two different pagelists.
But in the earlier version of BIX that is BIX 6.3, there are no such limitations. See the use case below.

Usecase: User has a parent cover case that initiates two child sub cases having the different data and gets merged into the parent case after the child case is closed. These two data pages is merged into the parent page list separately but mapped to the same table in the BIX as the variables are same.


Error Messages



Not Applicable.


Steps to Reproduce



1. Create an extract rule.
2. Map two pagelists on the rule.
3. Try to define the same 'to table' to different pagelists.


Root Cause



A validation has been introduced in BIX 7.1 to restrict users in providing one table to multiple pagelists.

Resolution



As a same table name cannot be used with different pagelists, follow the below steps:

1. Create a synonym or alias for the original table.
2. Repalce the synonym / alias in the To_Table field in the pagelist mapping.


After the above change, data gets inserted into the same table, as a synonym would point to the same table in the database as the original table.

 

Published May 12, 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