Executing Imports

Warning: The import process is performed either in the working version (if it is selected in the Dashboard) or the working fix of the version currently selected on the workspace.

In order to upload an export file holding project data previously exported using the “Manage Exports” process, proceed as follows:

[In the menu toolbar]
- Click on the upload function
[In the popup]
- Browse to the export file and click “OK”.
  - The import table is updated and a line is created for the export file. The “workspaces” column indicates every workspace used in the export file.

In order to detect conflicts for a to-be-imported file, proceed as follows:

[In the import table]
- Select a line corresponding to the export file to be imported.
[In the menu toolbar]
- Execute the Check for conflicts function
[In the popup]
- For each workspace found in the export file, provide the target workspace in which the corresponding objects need to be imported
- Click “OK”
- The conflict detection process starts.

In order to import the file, proceed as follows:

[In the import table]
- Select a line corresponding to the export file to be imported.
[In the menu toolbar]
- Execute the start function
[In the popup]
- Select the Import mode
  When conflicts arise during the import process, they have to be managed. There are 2 policies that can be applied in order to resolve conflicts:

Keep local

In case of a conflict during the import of an object in the working fix/version, the “Keep local” policy will reject the to-be-imported object and keep the object already in the working version.

Override

The “Override” policy will reject the object in the working version and update it with the information coming from the to-be-imported version.

Clean
- The ‘Clean’ mode has to be used with caution. It should only be launched when you want to start from scratch on a specific version (e.g. if 2 databases have been de-synchronized). The process permanently removes all items of the working version (or working fix) whatever their workspace.
- [In the popup – (XML format only)]
  - For each workspace found in the export file, provide the target workspace in which the corresponding objects need to be imported
  - Click “OK”
  - The import process starts.

In order to delete a previously uploaded/imported file, proceed as follows:

[In the import table]
- Select a line corresponding to the export file to be deleted.
[In the menu toolbar]
- Execute the delete function
[In the popup]
- Click “OK”.

The table presented in this step will hold all imported files (unless you’ve specifically deleted them). For each line, you will be able to:

Delete it, by checking the line and clicking on the Delete function in the menu toolbar.
Look at the log of the import execution, by clicking on the status indication.
Download the imported file by clicking on the file link.
Tip: The physical location of the imported file on the server is determined by
the modeling.api.distributionFolder parameter in the cameleon.properties configuration file.

If you just want to detect conflicts for an uploaded file, without actually importing it: proceed as follows:

[In the import table]
Select the line corresponding to the version you would like to import.
[In the menu toolbar]
Execute the detect conflicts function

Once the conflict detection has finished, a popup will enable you to:

Download the log file, indicating all objects that will be added, removed or updated
Download the source conflict file, containing the XML representation of all conflicting objects from the source export file
Download the destination conflict file, containing the XML representation of all conflicting objects in the working version

Imports Limitations

Warning: Importing a file results in fields being created in the CPQ Database. Database columns have a maximum allowed size in bits.

Our database uses UTF8 encoding. A single character in your import file may take several bits in the database. Please refer to the most frequent limitations below.

Once and Import is started the process cannot be stopped.

For Description, Long Text, and List Business Properties the maximum size is 4000 bits. Please note that for Business Properties of type Object, the complete PK of the object is stored.

For Text Business Properties value the maximum value is 80 bits.

Trademarks

All other brands and their products are trademarks or registered trademarks of their respective holders and should be noted as such. This product includes software developed by the Apache Software Foundation https://www.apache.org/

Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Executing Imports