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

DB instances do not get imported correctly on a tenant level



When you import a Data-Admin-DB-Table instance associated with a database view, the name of the table is changed from the original.
For example, History_foo_summary is changed to History_foo_Summ_001.

Error Messages

Not Applicable

Steps to Reproduce

 Import a Data-Admin-DB-Table instance associated with a database view.

Root Cause

This is working as designed in Pega 7.1.6. When importing a Data-Admin-DB-Table instance into a tenant layer, the table name is modified to an identifier that corresponds to the tenant. 


This issue is scheduled to be resolved in Pega 7.1.9. 

Published August 10, 2015 - 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