Changing Project Import Fields

[drewgordan]

How can I change the import from MSP into SN to look at the Resource Initials field instead of the Resource Name field?   I have mapped the Resource Initials in MSP to mirror the user names in SN and need to change the import map/process.

[chrisvan1]

Kelly,  I know this is old post but we are experiencing the same issue.  Exporting to excel and making the changes could work but it's not really a feasible work around in some cases.  We are migrating approx. 200 project over from PS to SN PPM.  We would have to open up each project schedule that was exported from PS and make those changes and then import back into PS and then export back out so that the fields would map properly in SN.  Also, if you change the Resource Names in Project it will lose some of the time keeping information.  There really needs to be a way to customize the resource name/assigned to name during the import.  Also, there is a lot of other information in Project Server that is not captured by the import function that would be nice to include.  The Project Server Pages, documents, and status comments are some of the information we are having to create multiple import sets to get everything from Project Server into PPM.  Just wanted to add some to the thread in hopes it can be improved in future.

[MIKE CHEN]

I'm trying to import my project, but seems there are only 7 columns (Task mode, Task name, Duration, Start, Finish, Predecessors, Resource name) available. same for export, even there are more fields available inside ServiceNow. Is it the case? If yes, we do hope your enhancement can be available asap. You see, there is no mass updating function there like MS Project. Look forward to it.

[Ashutosh36]

Hi,  Are there any recent updates on this, and the ability to customize in the current Kingston version?

[Uncle Rob]

Upvote on this!  Especially since the Project Importer doesn't work as well as it did in previous versions, and not as advertised on Docs.

[ITSMgal]

Hi Robert, 

What do you mean by "it doesn't work as well as it did in previous versions"? and what doesn't work as advertised in Docs?

I will get the feedback to Product Management