This document describes the import of .car files in Cisco Information Server (CIS) Studio.
Why should you import a package-level .car file into the root of the Studio's resource tree?
Sometimes for organizational purposes, you might want to import a .car file into a folder you specifically created to contain the contents of that .car file. For simple cases such as a .car file that contain a single view and a datasource, that will be fine.
In more complex cases where a .car file contains a multi-level hierarchy of resources where some objects have the same name but exist on different levels of the hiearchy (resource tree path), this can result in various parser or other runtime errors if the .car file was imported into a single folder.
When you import it into a user-defined folder, all the objects will end up in the same path in that single folder. Any duplicate name conflicts will result in a loss of those resources, and thus the resulting errors.
To avoid this, you must import the .car file into the root of the Studio's resource tree.
This is the node labeled as Desktop (<username>).
The import will then retain its original pathing as it was on the source server, hence it preserves all paths and resource objects.
If you want to see where the resources ends up, the Preview button of the import User Interface (UI) will list the destination of the objects.