Support Article

Modified data instances are not getting reimported



The user is trying to import the data instances with the modified values in one of the columns. It is expected to get JAR file imported and database (DB) column to reflect the modified values. However, it is being observed that upon importing a JAR with modification in a column value, the system is not able to identify the change in the column values between the existing and the newly modified instances. Instead, on UI, the following message is getting displayed:

"There is nothing to import -- the rules contained in this archive are already present in the database."

Error Messages

Not Applicable

Steps to Reproduce

Import jar using (Designer studio--> Application-->Distribution-->Import)

Root Cause

A defect or configuration issue in the operating environment: As the last updated date is same in the destination DB and the exported data in the jar, system is not recognizing it as a change and hence it skips to import anything and column is not getting populated.


Perform the following local-change:

Use column populator utility. T
he utility can populate values for a newly exposed column and expose values that were previously stored only in the Storage Stream (BLOB) column.

Published April 24, 2017 - Updated May 5, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.