Date Posted: 2018-04-04
Product: TIBCO Spotfire®
Product: TIBCO Spotfire®
Migrating analysis from one library to another fails with warning: "Unresolved dependencies found during import. Item '...' is missing"
When importing items from one environment (e.g. TEST/DEV) to another (e.g. PRODUCTION), you may get the following warning:
Handling dependencies. Unresolved dependencies found during import. Item '4a778ca4-ce8d-41b8-a063-aaaaaaaaaaaa' ('null') is missing. Required by 1 items. Item '10c5b763-93ec-443d-9459-bbbbbbbbbbbb' ('Column required by this query') is missing. Required by 2 items. Item '18c231e8-76aa-47d8-a88e-cccccccccccc' ('Column required by this query') is missing. Required by 1 items. Item '17b0b361-90e8-4ce2-8bab-dddddddddddd' ('Column required by this query') is missing. Required by 1 items.The warning "Unresolved dependencies found during import. Item '...' is missing" usually suggests that there are some elements, like data source, information links, joins, filters, or column elements, which are required by the analysis file which are missing in the destination environment (or not included in the content being imported). You can verify that the element does not exist in the destination environment by opening the Information Designer and searching for the missing item's GUID with syntax like: id::4a778ca4-ce8d-41b8-a063-aaaaaaaaaaaa
To resolve the issue, there are a couple options depending on your library content and what is missing.
The best option is to migrate the content again. Export the content from the originating environment and make sure to have all required information model objects required by that analysis included in the library export. Then when importing to the destination environment, ensure that the import settings are set to "If an imported item has the same name or GUID as an existing item: Replace existing item". This will ensure that the imported element has the same GUID as the originating environment, and will overwrite any existing objects which are already present in that exact same path (thus updating the GUID). Note: It is recommended to backup library content in the destination environment before importing new content since a library import may have modify objects being used elsewhere in the destination environment.
Additionally, you can re-create the missing item in the destination environment but this is normally more complicated if there are many missing objects and since any new items will have a different GUID, which means that all references to that previous object must be manually updated to use the new object (which has the new GUID). For example, if a column object is missing and a new column object is created, an information link which references that column would need to get updated to have that new column object used instead. Doc: Importing to Library
Article is closed for comments.