Rules for the Package Import Utility
Importing follows these rules to resolve conflicts during import:
• If an imported resource does not exist prior to import, it is created. The user performing the import is given all privileges of the original creator (such as READ|WRITE for a folder or READ|WRITE|EXECUTE for a procedure) unless the ‑includeaccess option is specified.
If an administrative user who has the Modify All Users right imports a resource using the ‑includeaccess option, the original owner of the resource is set as the owner and any pre-existing privileges in the import package are also set for the newly imported resource.
• If a resource is imported to a nonexistent folder, the folder and any parent folders that do not yet exist are created with the importing user being granted READ|WRITE privileges and ownership of the folders.
Note: Auto-creation of folders is not supported in the Data Services folder in the resource tree.
• If an imported resource already exists, the old version is overwritten (assuming you have the WRITE privilege), except that:
— The owner is not changed. The original owner retains ownership.
— Privileges for users that are not explicitly changed by the import are left intact. For example, if Abe has READ|WRITE and Bob has READ|WRITE, and the import lists Abe as READ but does not mention Bob, Abe’s privileges are updated but Bob’s are left intact.
— If the resource is a folder or data source, its child resources are not removed.