Import .mpp to server-mapping custom fields

[LPW]

I am using import wizard to bring .mpp files to Project server. I have
mapped local data fields to enterprise fields:

CAM (text1) to Enterprise CAM(text1)

Once import is complete, all appears correct. Close the plan, open the plan
from server the following gray window appears " This project contains outline
code and/or custom fiels which have the same field name as in enterprise
global. Each outline code or custom field w/a matching name will be offered
for renamin in the project...."

I thought the point of mapping it in the import was so this would not
happen. Am I missing something?

Thank you!

 

[Gary L. Chefetz [MVP]]

LPW:

When you import the project, the plan retains its local field definitions,
regardless of whether you've mapped the values to another field. The
resolution is simple: Make sure that the field names aren't identical. Put
an 'x' or an 'l' for local in the filed names in the to-be-imported plan and
the problem disappears.

 

[LPW]

Thank you, that is what I was thinking...wish the local fields would become
enterprise so one would not have to do all the prior to import.

 

[LPW]

After you rename, where is the local definition stored and would it impact
performance?

 

[Gary L. Chefetz [MVP]]

LPW:

Assuming that you mean rename the local field, it's stored in the project
file and it shouldn't impact performance.

 

[Dale Howard [MVP]]

LPW --

After you import the project, click Tools - Organizer, click the Fields tab,
select the custom local Task field from the list on the right, and then
delete it. Because the values were transferred to the custom enterprise
Task field when you imported the project, you no longer need the local
field. Hope this helps.