CLI Reference > Configuration Management Commands > si importsandbox
si importsandbox
imports an existing sandbox
si importsandbox [--[no]openView] [--importFiles=[none|members|all]] [--[no|confirm]overwriteExistingFile] [--targetSandboxDir=value] [--hostname=server] [--port=number] [--password=password] [--user=name] [(-?|--usage)] [(-F file|--selectionFile=file)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd=directory] [--forceConfirm=[yes|no]] [(-g|--gui)] [--quiet] [--settingsUI=[gui|default]] [--status=[none|gui|default]] file...
si importsandbox imports an existing Sandbox and registers it as a new Sandbox on the Windchill RV&S client. For example,
si importsandbox c:/Aurora_Program/bin/Libra/project.pjx
To import a Sandbox, the project identified by the Sandbox must exist on the Windchill RV&S server. However, if the Sandbox being imported is a build Sandbox, the project does not need to be currently registered as visible on that server.
The si importsandbox command can import two types of sandboxes:
Sandboxes that have a file extension of .pj. Those are Sandboxes that were created using Integrity 10.7 or earlier, but not opened in 10.8 or later.
Sandbox files with the extension .pjx that were exported using the si exportsandbox command.
This command takes the universal options available to all si commands, as well as some general options. See the options reference page for descriptions.
specifies the files to include when importing the Sandbox. This option is only relevant when specifying a .pjx file for import.
specifies not to import working files in the Sandbox import operation. Working files can be obtained after import by resynchronzing the Sandbox.
specifies to only include working files that correspond to members. Note that former members and deferred operations are also included.
specifies to import all working files in the Sandbox. Note that non-member files are not added as members to the project, but the files are copied to the corresponding Sandbox directory.
specifies whether or not to overwrite an existing file in the target Sandbox directory. This option is only relevant when specifying a .pjx file for import.
specifies the location where the Sandbox will be located after it is imported. This option is only relevant when specifying a .pjx file for import.
controls whether to open the Sandbox view after this Sandbox is imported and registered on the client. If --noopenView is used, the Sandbox view does not open.
identifies an existing Sandbox file on the Windchill RV&S client system to be imported. The command accepts the following file types: .pj and .pjx. The command also accepts a comma separated list of files.
See the diagnostics reference page for possible exit status values.
Using si setprefs or si viewprefs, you are able to set or view the preference keys for this command.
See Also
Commands: , si createsandbox, si exportsandbox, si dropsandbox, si sandboxes, si viewsandbox
Miscellaneous: ACL, diagnostics, options, preferences