pm_project >> pm_project_task

[ggg]

Issue: import project and tasks and populate the Project(project) field on the pm_project_task table.

pm_project_task appears to reference pm_project through the composite field Project(project)

I do not see a sys_id on pm_project_task referencing pm_project (as I would expect).

If I create a task through the UI the Project field on the Task record shows the project short description and below it the project number as a clickable link.

I want to do the same thing through an import.

I have an input excel file with project tasks.

I have the project name (project.short_description which is loaded first)

I want to populate the pm_project_task.project field so that it appears the same as if I did this through the UI.

The pm_project_task.project field is a composite field >> short_description + number.

I have a scripted transform map that is not working.

My return value is short_description + number (ex. project1PRJ11111) I log this so I know this is the value I am returning.

but it does not appear on the pm_project_task list view.

I am populating the Project(project) field on  pm_project_task.

var rv = '';

var gr = new GlideRecord('pm_project');

gr.addQuery('short_description', source.getValue('u_projectname');

gr.query();

if (gr.next()){

    rv = gr.short_description + gr.number;

}

return rv;

There is another table, pm_project_task_link, but if i do a pm_project_task_link.list, there are no records.

any help appreciated!!

[ggg · Accepted solution]

you can import the .mpp file directly into servicenow.

there is a module in the Project application that does this already!

[DrewW]

Just for clarity the Project field on the project task table is a composite field which means it is automatically calculated based on the project tasks parent.  So when importing data into the project task table you want to use the parent field to connect the project task to the project.  The Project field will then automatically populate properly.

[ggg]

just for clarity the Project field on the project task table is a composite field which means it is automatically calculated based on the project tasks parent.  So when importing data into the project task table you want to use the parent field to connect the project task to the project.  The Project field will then automatically populate properly.

the following map made the project field on task populate:

input project name   to   Project(sub_tree_root)