Sometimes I don't have access to the MSP schedule my client wants me to put into P6, therefore I can't import. I've set up a fill-in USER DEFINED FIELD that Emily refers to as the "line numbers' column in P6. That let's me have both an activity id in P6 and reference the same User ID from MSP. It also allows me to fill in the Unique ID if that is available... That way they'll recognize the activities as they are in P6, even if I've used a different WBS structure than they did.
Personally I'm not keen on Line Numbers at all. Rows are automatically renumbered during data manipulation. So any time you remove an activity, add one, move one, change the WBS, apply a filter, or even when data is expanded or collapsed, the numbers are assigned to different items.
Also, if these numbers are being used in communications, you run the risk of confusion down the line whereby an item is referenced one day with a Line Number which is then assigned to something completely different the next. Dangerous for other users with different layouts, or even the same user who may be unaware. Why take the risk?
Activity ID is a unique reference number and, unless changed manually through poor control, will always refer users to the same item. Sure the numbers might be a little longer, but they're much more reliable than Line Numbers in my opinion.
I'm sure there are occasions when people find it useful but I'd always recommend sticking with Activity ID.
Member for
21 years 8 monthsSometimes I don't have access
Sometimes I don't have access to the MSP schedule my client wants me to put into P6, therefore I can't import. I've set up a fill-in USER DEFINED FIELD that Emily refers to as the "line numbers' column in P6. That let's me have both an activity id in P6 and reference the same User ID from MSP. It also allows me to fill in the Unique ID if that is available... That way they'll recognize the activities as they are in P6, even if I've used a different WBS structure than they did.
Member for
9 years 5 monthsHi David,Very true. They
Hi David,
Very true. They do have the Unique ID column as well, but most MSP users I've dealt with don't seem to use it......
Member for
21 yearsYou are correct of course,
You are correct of course, Robert, but we do need to help the walking wounded who are escaping from Microsoft Project......
Member for
9 years 5 monthsPersonally I'm not keen on
Personally I'm not keen on Line Numbers at all. Rows are automatically renumbered during data manipulation. So any time you remove an activity, add one, move one, change the WBS, apply a filter, or even when data is expanded or collapsed, the numbers are assigned to different items.
Also, if these numbers are being used in communications, you run the risk of confusion down the line whereby an item is referenced one day with a Line Number which is then assigned to something completely different the next. Dangerous for other users with different layouts, or even the same user who may be unaware. Why take the risk?
Activity ID is a unique reference number and, unless changed manually through poor control, will always refer users to the same item. Sure the numbers might be a little longer, but they're much more reliable than Line Numbers in my opinion.
I'm sure there are occasions when people find it useful but I'd always recommend sticking with Activity ID.