object locked error while importing application

One option is to delete these data types and then run the import. Before deleting, make sure you understand all impacted objects and get these imported as well in a subsequent package.

1. First of all you need to make sure while creating the patch or packages no object should be open by any other user if it is already created
2. Try to deploy the CDT first

It seems to be an issue with CDT version mismatch, which relates to the version difference between the CDT that is currently there in the target environment and what is getting deployed with the build package.
Am I right folk ?

Hi Roshan, Did u resolved the issue? if yes could you please tell us how u resolved the Issue?
Does your exported file contains CDT and corresponding Process Models ?

Hi All,

we can not delete the CDT's on client server. We are importing CDT's and DS only first time and facing the below issue. Please suggest.

Hello Roshan,

As per my understanding, the child CDT definition in the parent CDT which you are importing in the target environment has different version than the packaged child CDT definition. So, i suggest you try deleting the child CDT in the target environment and deploy the package which contains both parent and child CDT's and update the references.

Hope this should work and let us your exercise.

Thanks

Hi Roshan, You may try these general debugging steps.

1. How the inspection has gone? was it good?
2. Do you have right access (admin) for these objects (CDT and DS) to deploy?
3. Have you gone through the import logs and system logs after this error for detailed observations of what dependent objects have been referred to these CDT's and other objects?
4. If it is on premise, try to run the scritps for clear the cache memory and try inspect the package. If it is cloud, open a support ticket with Appian for more clarity on the issue.

Thanks

Is your CDT mapped with the DS, if not then create a patch only for CDTs. Deleting the CDT will not create any issue however for the safer side take the XSD file or create the patch of existing CDT and then delete and redeploy it.

Hi,

We have also faced the similar issue and in our case there was some lock on the table in database corresponding to the CDT so please verify that there should not be any lock on the tables from database end.

Generally the lock expires after one hour if you try to update that data type again and it worked fine.

Thanks