- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-09-2017 03:05 AM
Can I link an approved Demand to an existing project rather than creating a new one? I have bucket projects that will take the work from multiple demands.
Solved! Go to Solution.
- Labels:
-
Demand Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2017 04:19 AM
Hello Neil,
May i know the status of this thread?
Let me know if that answered your question. If so, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.
How To Mark Answers Correct From Community Inbox
ServiceNow Commnunity MVP -2018 class.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-11-2021 10:05 PM
I probably think that you would need to create a new project using the Create Project Link on the demand form to associate and have a relation between demand and project. With the above-said approach, you may see the project record but there won't be any association created.
Hope this helps...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-28-2021 12:44 PM
Without the sys_id association then there is not really a linkage. So looking for a better, more correct way to add Demand to an existing Project.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2022 11:32 AM
same issue here. Found any resolve for this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2022 07:18 AM
customer support provided this background script. I'm wondering about if theres a way to incorporate this into a flow or import set transform script.
i did attempt using Import set to update Project with Demand number and that does work however it doesnt trigger the automation (BR's, scripts etc) that on the Demand record would cause Project field to display and show the associated demand - so it almost works but doesnt provide the output that you'd have if you create a PROJ from the DMND.
the background script method does better in that it will show the proj# on the demand record.
here's the background script:
background script for associating DEMAND to a PROJECT
var demandId = '<insert SYSID of Demand>';
var projectId = '<insert SYSID of PROJECT>';
var gr = new GlideRecord('dmn_demand');
gr.get(demandId);
gr.setWorkflow(false);
gr.setValue('project', projectId);
gr.update();
var gr1 = new GlideRecord('pm_project');
gr1.get(projectId);
gr1.setWorkflow(false);
gr1.setValue('demand', demandId);
gr1.update();