Can a List Workflow Start a Demand Management Workflow? RRS feed

  • Question

  • 2010 Project Server / Nintex driven workflows. 

    I have a very simple list driven workflow that contains a Start Workflow action for the intention of turning my list item into a new enterprise project.  The selected “workflow to start”  is a demand management workflow associated to an Enterprise Project Type (with required fields) that we’ve used in this environment for years.  However I’m unable to get the new workflow to actually create, with most of my confusion being around the passing of data to the new project type.  I am currently unsuccessful in using the update project properties action where the Project Name is set to the new ‘workflow instance ID’ (provided by the Start Workflow action), which is also configured to update each of the required fields in the EPT from the list.

    The demand management workflow history error reads “Failed to start workflow. Value cannot be null.  Parameter name: contextObject” while the list workflow history error reads “Error updating project properties. Project server error code: ProjectDoesNotExist. projGuid: xxxxxxxxxxxxxxxxxx”.  Advice is appreciated.  But ultimately: is this even possible in the 2010 environment?  

    Additional Data: Just to confirm, I am passing data to the system required fields too, including PROJ_NAME and ProjectOwnerID. <o:p></o:p>

    • Edited by L.e.s.l.i.e Thursday, October 30, 2014 7:30 PM
    Thursday, October 30, 2014 7:27 PM

All replies

  • L.e.s.l.i.e,

    Have you looked at this excellent blog post from Alex?:


    Prasanna Adavi, Project MVP

    Blog:   Podcast:    Twitter:    LinkedIn:   

    Thursday, October 30, 2014 8:31 PM
  • Thank you – a great article for sure but moving forward I see a discrepancy and I’m not really sure how to handle it. The blog states “For the list workflow to create a project automatically, it is essential to make sure this EPT is set as the ‘default’ and that a Project schedule template has been uploaded and associated with the EPT” while Project Server reads “Choose whether this is the default Enterprise Project Type for Project creation. If no type is specified during Project Creation, the default Enterprise Project Type will be used.  Note: Making this default will automatically unselect all the departments. The default Enterprise Project Type cannot have a Project Plan Template associated with it.  Any ideas on how to manage this or am I interpreting it wrong?

    I tried posting directly to that site but was unable.

    Friday, October 31, 2014 4:14 PM