Possibility to Merging Multiple Demands into a Single Demand
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
In Strategic Portfolio Management, can we merge multiple demands into one single demand? For example, if we have 10 demands, is it possible to bring them all together into one, along with their tasks, cost plans, resources, and other related data ?, Right now, we can add demands as child records or group them under a program, but that doesn’t really combine everything in the financial section. We can also set dependencies at the portfolio level, but still need to track each demand separately. Is there a way to fully merge them into one?
- Labels:
-
Demand Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @makmishra ,
In ServiceNow SPM, there isn't any OOB feature to merge multiple demands into a single demand record. You need to build your own custom solutions.....
Create a UI Action that enables users to select multiple demand records.
Merge Data: In the UI Action script, aggregate the necessary data (such as tasks, cost plans, resources) from the selected demands.
Create a New Demand Record: Generate a new demand record that consolidates the aggregated data.
Update Relationships: Set the new demand record as the parent of the original selected demands.
Data Migration: Ensure that all related records (tasks, cost plans, resources) are appropriately linked to the new consolidated demand record...
If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.
Kaushal Kumar Jha - ServiceNow Consultant - Lets connect on Linkedin: https://www.linkedin.com/in/kaushalkrjha/

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @makmishra ,
Thank you for taking suggestions from the community.
There are two ways to address your query:
1. Can multiple demands be merged into one? - @kaushal_snow has shared the thoughts on this point.
2. Should multiple demands be merged into one?
I would focus on point #2 i.e. Should demands be merged into one?
ServiceNow SPM does not natively support merging demands in a way that automatically consolidates all tasks, resources, and financial information - and you have also mentioned this point.
In my humble opinion merging demands decision should be first considered as a concept. In other words what would be the impact if demands are merged because technically it is possible as mentioned above by @kaushal_snow.
Now though you can merge the demands but attempting to do so manually or through custom scripts is not recommended. Following are some of the reasons that I can mention :
Loss of Traceability
-
Each demand has its own lifecycle and approvals. Merging could make it hard to track:
-
Original requesters
-
Individual benefit realizations
-
Delivery timelines
-
Data Integrity Issues
-
Duplicate or conflicting data: Different demands may have overlapping tasks, dependencies, or resource assignments. On merging, you may lose the original information.
-
Financial aggregation: Cost plans and budgets may not sum cleanly if different currencies, cost models, or timelines are involved.
-
Audit trails: Merging may break the historical record of individual demand approvals, updates, or changes.
Maintenance Overhead:
- Now as we understand that custom scripts can make this merge but please do note that this will increases maintenance overhead.
Now that I have shared the reasons, let me also share the Best Practices for this scenario:
Instead of trying to merge demands, the recommended best practices are:
a. Use Programs / Initiatives
-
Group related demands under a Program or Initiative.
-
This allows:
-
Roll-up of high-level financials and KPIs
-
Dependency tracking at a consolidated level
-
Portfolio-level reporting without losing individual demand details
-
b. Financial Aggregation via Reports or Roll-ups
-
Instead of merging, use reports, dashboards, or calculated roll-ups to consolidate costs and resources.
-
This maintains data integrity while giving a single “view” of multiple demands.
c. Align with Portfolio Hierarchy
-
For example:
-
Portfolio > Program > Demands
-
-
Use dependency links and milestones to track cross-demand relationships.
Happy SPM Learning!!
Thank You!
Namita Mishra

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @makmishra ,
Glad that you liked the response.
If you feel this is correct then please mark it as correct. This will help me and other community members.
Have a Great Week Ahead !!
Thank You!
Namita Mishra