Using Periods in ID Fields
Deltek recommends that you refrain from using periods in the "local" segments of the P6 ID (such as PRJ.OR.USR.001).
For example, you see the local part of the code name in the P6 WBS Code field box on the projects WBS tab.
When a field with a period is imported into Open Plan, Open Plan changes the period to an underscore (for example, PRJ_OR_USR_001).
If you then export the data back to P6, you may have issues:
- When you import the field back into P6 from an XER project, the XER file requires an exact match with the ID. Since the field no longer matches up to the original value in P6, it is created as a new object (activity, WBS, resource description, and so on).
- When you import the field back into P6 through the web, the changed ID won't cause an issue because Open Plan keeps track of most P6 objects using a numeric key instead of a character-based ID. As long as the unique ID matches, the objects match.
Related Topic
Parent Topic: Best Practices for P6 Integration