Resource ID in the database is defined as unique. If you import a project and P6 does find an existing resource, the rules you defined for import will be used: Keep Existing or Insert New (one of the previous you used), Update or Don’t Import. May be a warning from P6 would be appropriate.
To avoid this effect, you’ll have to check for duplicates before. This is from the "Help"-function: "If duplicate resource IDs are encountered during the import process, you can choose how to resolve each conflict by modifying the import configurations in the Import wizard." (End of P6 Help)
Did you read the paragraph under "Import a P3 project" under "Help" already?
Member for
18 years 9 monthsRE: IMPORT P3 TO P6 - RESOURCE DICTIONARY UPDATES
Suresh
Resource ID in the database is defined as unique. If you import a project and P6 does find an existing resource, the rules you defined for import will be used: Keep Existing or Insert New (one of the previous you used), Update or Don’t Import. May be a warning from P6 would be appropriate.
To avoid this effect, you’ll have to check for duplicates before. This is from the "Help"-function: "If duplicate resource IDs are encountered during the import process, you can choose how to resolve each conflict by modifying the import configurations in the Import wizard." (End of P6 Help)
Did you read the paragraph under "Import a P3 project" under "Help" already?
Regards
Dieter