- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2025 10:47 AM
Hi Team,
We are using import function in project to load MPP files, But after importing currently we are seeing below hierarchy:
Top Project -> Project Task -> Sub-Task - Child Tasks ....
really we wanted is to create in below order:
Top Project - Sub-Projects - Tasks - Child Tasks
How to change this configuration, please suggest
Thanks,
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2025 11:23 AM
Hi @maneesh3 ,
If my answer is useful, please indicate its helpfulness by selecting " Accept as Solution" This action benefits for others as well.
Thanks,
Pratik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2025 11:13 AM
Hi @maneesh3 ,
- Option 1: Pre-process the MPP file or convert to XML and parse manually
Best suited for complex projects with multiple embedded sub-projects. - Convert your MPP file to XML format using MS Project (Save As > XML).
- Use a custom import transform map to:
- Identify rows that represent sub-projects (often marked in MPP as Summary Tasks)
- Create a new Project record (pm_project) for each
- Link tasks to their corresponding sub-project
- The top-level project will act as a "Program" or parent container for sub-projects.
- You can create a script in your Transform Map > Script to dynamically:
- Insert new pm_project records
- Use parent field to maintain project > sub-project hierarchy
- Populate project field in pm_project_task records accordingly
Option 2: Split your MPP file into multiple files (1 per sub-project)
Quick fix approach:
- Save each sub-project as a separate .mpp file
- Import each one as a separate project into ServiceNow
- Link them manually or via automation as Related Projects or under a Program
- This gives you cleaner control but adds overhead in maintaining files.
- Option 3: Modify Import Set logic to create Sub-Projects dynamically
You can customize the import logic (via script or Flow Designer) to: - Read the indentation/outline level in the MPP import
- Use Outline Level 1 for sub-project names and create pm_project records
- Assign tasks with outline level >1 under the right project/task
- Check if your import set table has a field like outline_level or summary that could be used as a logic flag.
Area What to Do
Import Set Table | Check how your MPP import maps data — see if outline levels or summary flags exist |
Transform Map | Add scripts to differentiate between projects, summary tasks, and actual tasks |
Business Rules / Script Includes | Use them to handle dynamic project/task creation |
Program Management Module | Consider leveraging it if this is truly a program-sub-project model |
- Final Tip
If this hierarchy is business-critical and frequent, it may be worth creating a custom MPP Import Parser that can: - Detect project structure
- Create/update records in the correct tables
- Maintain cross-links
If my response helped, please hit the 👍Thumb Icon and accept the solution so that it benefits future readers.
Regards,
Pratik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2025 11:23 AM
Hi @maneesh3 ,
If my answer is useful, please indicate its helpfulness by selecting " Accept as Solution" This action benefits for others as well.
Thanks,
Pratik