Task Name Unavailable in MS Project Import Wizard Mapping Options

Anonymous
2025-01-03T18:28:59+00:00

Hello,

I have an existing MS Project mpp file.

I have an Excel Spreadsheet with task durations that I want to import into the existing mpp file.

I have both the Task Name and Work field names in the Excel file matching those (native) defaults in the mpp file.

When I try to use the MS Project Import Wizard, I select New Map and then "Merge the data into the active project" since I want to keep everything in the mpp file as is except for updating the Work fields.

I then select Tasks as the type of data for import and specify the import includes headers.

In the Import Wizard Task Mapping dialog I then select the desired worksheet.

Everything in the "From: Excel Field" shows up correctly.

When I scroll down, I can see that the wizard correctly mapped "Work" in the Excel file to "Work" in the mpp.

However, it does not map the Excel "Task Name" to anything.

This should be mapped to "Task Name" in the mpp.

When I try to manually select "Task Name" in the "To: Microsoft Project Field" the option for "Task Name" is not present.

So, I cannot map the Task Name and hence can't Set Merge Key to Task Name.

What am I doing wrong here?

Thank you in advance!

Chris

Microsoft 365 and Office | Project | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
John Project 49,720 Reputation points Volunteer Moderator
2025-01-03T18:46:20+00:00

Chris Minerva,

What you are doing wrong is looking for a field called Task Name. The field you want is simply "Name", the "task" is assumed by Project since you are mapping into a task based view.

I'll caution you on something though. In Project all time related data is in minutes, so you will need to express duration and work as minutes in Excel in order for Project to accept your Excel data as intended.

Hope this helps.

John

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

6 additional answers

Sort by: Newest
  1. John Project 49,720 Reputation points Volunteer Moderator
    2025-01-13T15:14:53+00:00

    Chris,

    You're welcome and thanks for the feedback.

    John

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-01-13T02:18:28+00:00

    OK, that makes sense. Thank you for the detailed explanation, John. I'm just coming back to using Project again after many years and this is the first time I'm trying to setup a workflow that exports from Excel to Project. *sweat* :-)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-01-13T02:16:26+00:00

    Ahhh... OK. Thank you, Trevor!

    Was this answer helpful?

    0 comments No comments
  4. John Project 49,720 Reputation points Volunteer Moderator
    2025-01-08T16:29:49+00:00

    Chris,

    Nomenclature in Project can be quite confusing. As Trevor notes, each column header in a view has two or three elements. There is a field name, a column title, and in some cases, a friendly name.

    There is no field called "Task Name". What you see is the column title. For most built-in fields, by default, the title is also the field name (see the view entry table). The Name field is a special case. For task based views (e.g. Gantt Chart, Task Usage), the Name field is titled "Task Name". For Resource views (e.g. Resource Sheet, Resource Usage), the Name field is titled "Resource Name". For extra fields (e.g. Text1, Number1, etc.), the field name is still the same (e.g. Text1, Number2, etc), but extra fields can also be renamed with what is called a friendly name. So for example, if the Text1 field is used to identify a "phase", the field might be renamed "Phase 1". Or the title of the column could be "Phase 1". However, if that custom field is being used in a custom field formula, it must be referenced by its field name (or friendly field name), not by its column title.

    Is your head spinning yet?

    So, when using an import map, the Name field for task elements will be the task name and for resource elements will be the resource name.

    With regard to minutes to hours translation, you are correct, the import will interpret the value per the Project option settings. However, internally Project stores all time based data in minutes.

    John

    Was this answer helpful?

    0 comments No comments