When migrating an application package, we have noticed that Appian does not auto

When migrating an application package, we have noticed that Appian does not automatically migrate items in order of their dependencies. Specifically, if a package contains CDTs, Process Models, and Reports, and is being imported in a destination that has none of the objects already, Appian does not migrate them with CDTs first, Process Models second, and Reports third.

I am not sure whether the order the objects are migrated simply has to do with the order they were added to the package, but we have had problems when trying to migrate something with the above scenario. What we need to do is create a separate migration package for CDTs, Process Models, and Reports (3 packages in this case).

Is it possible to avoid having to migrate all 3 packages in order? Is it possible to create one release package for everything?...

OriginalPostID-110436

OriginalPostID-110436

  Discussion posts and replies are publicly visible

Parents
  • Eduardo, I have had the same difficulties when importing a package which contains some new query rules and an existing Data Store with new entities. On the first import, it will not identify the new entities within the Data Store and it will throw errors indicating that the entities in the DS can not be found. This means Appian does not resolve this kind of dependency and I would have to import the application twice. Do you have any resolution to this?
Reply
  • Eduardo, I have had the same difficulties when importing a package which contains some new query rules and an existing Data Store with new entities. On the first import, it will not identify the new entities within the Data Store and it will throw errors indicating that the entities in the DS can not be found. This means Appian does not resolve this kind of dependency and I would have to import the application twice. Do you have any resolution to this?
Children
No Data