Please, let us know version where you are facing this issue.
Could you check if the shared object is added when exporting the mapping?
It would make sense you lose the links to that shared object in that case.
In the source environment, do you have those shared objects in a shared folder, and shortcuts pointing to those objects in the mapping?
If that's the case, you should be able to see warnings/errors like "Object referenced by the shortcut does not exist in the original folder, object will be imported under the current folder" in the mapping's import logs (i.e. target environment). If you see those messages and your shared folder is in the target environment, maybe it's just a matter of making sure the folder is "shared."
If you don't see anything like this in the import logs, then I'd say such relationship (i.e. via shortcuts) hasn't been defined in the source environment either.
Another question: what's the PowerCenter version of the source and target repositories of the XML export/import? They have to (almost exactly) match.
Also please confirm which tool you are using to import ? Designer /Repository manager .
Repository manager is usually the better tool for all these export imports.
Also, for verification, you should always open 'Powercenter Designer' tool. If you want to verify; then under one Database Source (DBD) only one unique source name should be visible. If you see more than one source under one DBD then it is an indication of repository metadata corruption and INFA-Support should be called for.
1 of 1 people found this helpful
Are you using same version of PowerCenter for Import/Export? Just ensure, you should have same version of PowerCenter
3 of 3 people found this helpful
Can you please confirm the Informatica version that you are using? Also are facing this issue while importing a specific workflow or all the workflows?