Secure Codes
If you have the suitable permissions, you can control how secure codes are imported from Primavera XML files into your database. The information here assumes that the person importing the data has the add/delete, edit, assign, and view permissions for secure codes.
Unlike UDFs and calendars, for codes, the Action setting on the Advanced tab of the import tab controls only the security status of a code, that is, whether or not the code is secure. In situations where the security status of a code is the same in the import file as in the database, the code and its values are imported according to the import action selected on the basic tab for the data type and the action selected on the advanced tab for each code.
However if the security status of a code is different in the import file from the code in the database, further rules are applied.
Mismatch of Secure or Unsecured Status
When the security status of a code differs between the import file and your database, the rules used for importing depend on the import action for the data type and the action for the code.
Note: Importing a file will never change a secure code into an unsecured code.
When the import action for the data type is Insert New, Keep Existing, or Do Not import, neither the code's security status, nor other attributes of the code are imported, even if you have set the action for the code to Keep. This is because the rule used where a match is found in your database for Insert New, Keep Existing, and Do Not Import is not to update the matching data.
However, when the import action for the data type is Update Existing, the action you choose for each code determines how that code in your database will be updated. The table below summarizes the rules.
Status in Import File | Status in Database | Action | Update Code to Secure? | Update Other Attributes? |
|---|---|---|---|---|
Unsecured | Secure | Do Not Import | No | No |
Secure | Unsecured | No | Yes | |
Unsecured | Secure | Keep | No | Yes |
Secure | Unsecured | Yes | Yes |
Note: It is important to be aware that if the code is secure in the import file but is unsecured in the database, choosing Do Not Import for the code will allow the definition of the code, except its security status, to be updated.
Therefore, depending on what aspects of a secure code you want to update, you should set the action for the code as follows:
If you want to update the security status of the code, use Keep. Keep allows P6 to update the code in your database from the import file.
If you want to update the definition of the code, but you do not want to change its security status in your database:
- If the code is unsecured in your database, use Do Not Import.
Do Not Import prevents the security status of the code in your database from being changed. Therefore, because the code is not secure in your database, using Do Not Import retains that unsecured status and the code and other aspects of the code are updated according to the Update Existing rules applied to the data type.
- If the code is secure in your database, use Keep.
Importing a code cannot change the code in your database from secure to unsecured. Selecting Keep allows P6 to update other aspects of the code in your database from the import file.
Related Topics
About Importing and Exporting Data
Last Published Tuesday, April 1, 2025