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

After export/import different precision for NUMBER columns

SA-31404

Summary



User packaged an export of ruleschema 1 and imported this in ruleschema 2  using Pega's export/import functionality (pega-import-migrate).

In table PR4_RULE the 2 number columns were different
----------------------------------------
The NUMBER columns in the source schema have a precision of 22.
The NUMBER columns in the target schema do not have a precision.
The two columns are
PYACCESSIBILITYLEVEL
PYBROWSERSUPPORTLEVEL

Error Messages



Not applicable

Steps to Reproduce



Not applicable

Root Cause



Columns pyAccessibilityLevel and pyBrowserSupportLevel do not have any precision out of the box.

There might have been some customization performed at user's end in the source environment.


 

Resolution

User is requested to verify their source environment, since these columns without precision is as per product design and is an Out-of-the-box (OOTB) expected behaviour.

Suggest Edit

Published December 22, 2016 - Updated October 8, 2020

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