I have a multi-domain environment and am working on exporting applications from one SCCM environment to another. Both are ConfigMgr 2012 R2 CU5. And I've already done several export/imports without a problem. The error that I get when I import one of the applications is;

Error: Dependency unresolved, please assign a substitute for object SMS_Application.ModelName='ScopeID21A0F29F-833B-4D13-B763-75D5B28635F6/Application_a499118f-c9df-4a29-8e30-f1d4ecccb01b',CIVersion=9. If this object is being migrated, ensure Data Gathering has run on each site since SMS_Application.ModelName='ScopeID21A0F29F-833B-4D13-B763-75D5B28635F6/Application_a499118f-c9df-4a29-8e30-f1d4ecccb01b',CIVersion=9 was modified.

This error references another application. When I import that application I get the same error except that it references the first application. There is a deployment type in the first application that has a dependency that includes the second application and the second application has a deployment type that has a dependency that includes the first application though it's a different deployment type so the references aren't circular. The application installs without a problem. Has anyone come across this kind of error?

Well this is not a problem it`s by design you are trying to import application that have dependency and they are not found in the current SCCM.

If app1 as a part of it that require app2 and app2 as a part of it that require app1  SCCM only look at it this way and tell you can't do it.

if you don't want to recreate them you could do a migration and migrate both of them in the same job.

 

I went ahead and did the applications as an object migration and got the same error. I also tried to create the app manually using all the same settings in the other environment but when I tried another app that has that one as a dependency it didn't recognize it as the same one and wanted to create a new app which then failed as the ones before it. What does the import look at to determine if the app already exists. I've checked the CI Unique ID and it creates a new one for all the imports I've made so far so it doesn't seem to be that one.

When you did the export of the original application did you have the export all application dependencies ?

Yes. and none of the dependencies imported when the import failed. I have worked backwards to import anything that was a dependency that didn't have any dependencies. Those worked OK but anything that had the failing apps as dependencies failed.

Sorry i could not be more help with the migration i never add issue migrating application with the dependency.

You could try to do the export/import using powershell 

Try this http://liammatthewsit.com/2015/01/16/sccm-2012-r2-exporting-an-application-with-powershell-2/

Hope it work for you because am out of idea.

I'm having the same issue migrating between two environments but with a task sequence. All depencenies are successful migrated but the core (the ts fails) Not sure how to solve it.

Will follow your post for hopefully more info and solution.