Code and Resource Field Length
If the code/resource field exceeds the 59 character limit that Open Plan can accept, it may rename it to fit.
For example, DEMO2-3.SHIP_XXXXXXXXXXXXXXX.ENGE_YYYYYYYYYYYYYYY.MULT_ZZZZZZZZZZZZZZZ, which contains 70 characters, would be truncated to DEMO2-3.SHIP_XXXXXXXXXXXXXXX.ENG~.MULT_ZZZZZZZZZZZZZZZ, which contains 54 characters.
Open Plan always tries to preserve the full local ID (lowest level child part of the ID). If Open Plan determines that the ID must be shortened, the system starts by shortening the closest parent, if the parent contains over 4 characters, to 3 characters followed by a tilde (~). Note that you will need to know which P6 code/resource the truncated version represents when you are viewing the codes/resources in Open Plan.
To avoid truncation, there are two options:
- Consider using numbers or short text strings instead of more verbose IDs. Remember that you can store explanatory text in the P6 Name field (OP code Description field or Resource code Description field).
- Ask your IT department to increase the size of the Open Plan code/resource ID field and its corresponding data dictionary entry so that the longest P6 path will fit in the resized Open Plan code/resource field. Contact Deltek Customer Care if you need assistance with this.
When you perform a web export, since Open Plan keeps track of each unique code/resource ID, if the codes/resources do get renamed, they are still matched up to the correct code/resource when they are exported back to P6. When you perform an XER export, renamed WBS elements or resource descriptions are considered new objects in P6.
Before you start integrating your P6 data with Open Plan, Deltek suggests that you plan your field lengths and hierarchy levels to limit codes/resources being truncated in Open Plan.