Problems importing (via "Open") an Excel spreadsheet into MS Proje

[Victor Schwartz]

I am attempting to import records from an Excel spreadsheet into my MS
Project file. I have followed the clear instructions to create a MAP of the
columns in Excel to columns in Project.

There are about 20 columns I wish to import, and after I complete all the
steps I find that about 11 or 12 of the columns are correctly imported, but
the other 8 or 9 columns are left BLANK in Project.

I have examined the MAP many times, and repeated the import operation many
times, always with the same result. I cannot see any pattern in the
specification for the successful columns or the failed columns.

Does anyone have any suggestions as to what the problem might be, or a way
to further investigate it?

Thanks, Victor Schwartz
(e-mail address removed)

 

[John]

I am attempting to import records from an Excel spreadsheet into my MS
Project file. I have followed the clear instructions to create a MAP of the
columns in Excel to columns in Project.

There are about 20 columns I wish to import, and after I complete all the
steps I find that about 11 or 12 of the columns are correctly imported, but
the other 8 or 9 columns are left BLANK in Project.

I have examined the MAP many times, and repeated the import operation many
times, always with the same result. I cannot see any pattern in the
specification for the successful columns or the failed columns.

Does anyone have any suggestions as to what the problem might be, or a way
to further investigate it?

Thanks, Victor Schwartz
(e-mail address removed)

Victor,
I haven't done much work with import maps but I do know the Excel
spreadsheet needs to be in a particular row and column format. Also, it
would help to know what fields seem to be working and what fields do not
import. So, a little more detail would help us help you.

John
Project MVP

 

[Victor Schwartz]

John,

Thanks for your reply. Let's see if this provides enough information to
help someone offer a hypothesis. (If you provide your e-mail address I could
send you a collapsed version of the 2 files in question to provide even more
detail.

Here is the header and 1 row of the Excel spreadsheet:

Control No Date Req Internal Due Date External Due Date Date Dlv IS
Estimated Delivery Date Requesting Department Internal Customer Requestors
Priority Requestors Status External Customer Item Est Hours to
Complete Actual Hours to Complete Request Type (later - REMOVE this
column) Status % Complete IS Priority Queue Assigned To System Type Task Docs
(see mhnet-02/~Shared Workspace\Projects\TaskDocs\<Control#> Comments
20061027003 10/27/2006 39020 Claims John Doe Customer1 EOB Claims
Denial template for Windsor Beth mhnet-02/~Shared
Workspace\Projects\TaskDocs\20061027003

The fields that come through successfully are: Item, Control No, Date Req,
Internal Due Date, External Due Date, Date Dlv, IS Estimated Delivery Date,
Requestor Priority, Actual Hours to Complete, %complete, IS Priority Queue

Fields that do NOT come through are: Requesting Dept, Internal Customer,
Requestor Status, External Customer, Est Hours to Complete, Request Type,
Status, Assigned To, System, Type, Task Docs, Comments

 

[John]

John,

Thanks for your reply. Let's see if this provides enough information to
help someone offer a hypothesis. (If you provide your e-mail address I could
send you a collapsed version of the 2 files in question to provide even more
detail.

Here is the header and 1 row of the Excel spreadsheet:

Control No Date Req Internal Due Date External Due Date Date Dlv IS
Estimated Delivery Date Requesting Department Internal Customer Requestors
Priority Requestors Status External Customer Item Est Hours to
Complete Actual Hours to Complete Request Type (later - REMOVE this
column) Status % Complete IS Priority Queue Assigned To System Type Task Docs
(see mhnet-02/~Shared Workspace\Projects\TaskDocs\<Control#> Comments
20061027003 10/27/2006 39020 Claims John Doe Customer1 EOB Claims
Denial template for Windsor Beth mhnet-02/~Shared
Workspace\Projects\TaskDocs\20061027003

The fields that come through successfully are: Item, Control No, Date Req,
Internal Due Date, External Due Date, Date Dlv, IS Estimated Delivery Date,
Requestor Priority, Actual Hours to Complete, %complete, IS Priority Queue

Fields that do NOT come through are: Requesting Dept, Internal Customer,
Requestor Status, External Customer, Est Hours to Complete, Request Type,
Status, Assigned To, System, Type, Task Docs, Comments

Victor,
OK, let me explain something. Of all the "fields" you mention, both
those that import and those that do not, only one or two are actual
fields. Project has a defined set of fields, things like: Task Name,
Start, Finish, % Complete, Duration, Task Text1, etc. All of Project's
fields can be renamed by the user but the underlying identifier is still
the basic field name. Obviously you have renamed many fields but that
doesn't give me a clue as to which actual Project fields you are
referring to and that's the information I was looking for.

You are welcome to send me your Excel spreadsheet and the resulting
Project file (I would need both) and when I get some time, I will take a
look at them. It is likely I will also have a lot of questions.

John
Project MVP
jensenj6atatcomcastdotdotnet
(remove obvious redundancies)