Date Posted:
Product: TIBCO Spotfire®
Product: TIBCO Spotfire®
Problem:
Error/Warning while library import " (") is missing" and " 'Column required by this query' is missing. Required by 1 item".
Solution:
When importing library content from one Spotfire environment to another environment, you may get "(“) is missing" and " 'Column required by this query' is missing. Required by 1 items" warning in front of many or all items. For example:
While this warning may be seen if there are indeed missing library objects (for example, a Column object is not included which is needed for the imported Information Link), you may also get this warning depending on the order in which you do import.
If you are certain that the entire Information Model is included in the library export file, then this warning is caused due to the order of import. The solution is to first verify if the analysis file or Information Links can be opened successfully after import.
Also, verify it is possible to open and expand the Data Source in the Information Designer. Note that if you are importing from one environment to another, you will need to update the password for all data sources in Information Designer. Enter the password for data sources and re-save.
If you run into further issues opening the analysis file or Information Link, verify you have included all required objects of the information model in your library export, then verify if you have any objects in the destination environment that may have the same library path or GUID that may be interfering with the library import. Contact Technical Support for further assistance if the issue persists.
Also, verify it is possible to open and expand the Data Source in the Information Designer. Note that if you are importing from one environment to another, you will need to update the password for all data sources in Information Designer. Enter the password for data sources and re-save.
If you run into further issues opening the analysis file or Information Link, verify you have included all required objects of the information model in your library export, then verify if you have any objects in the destination environment that may have the same library path or GUID that may be interfering with the library import. Contact Technical Support for further assistance if the issue persists.
Comments
0 comments
Article is closed for comments.