SCO 2012 – Attention! Use correct order of params in Invoke Web Services XML Payload!


Are you experiencing problems when using advanced SOAP XML payloads in “Invoke Web Services”?

I did! it seems to work properly, but some parameters did not get filled correctly.

After some testing i discovered that the parameters in the XML payload has to be in the correct order!!

If not, the parameters “in between” will be filled by NULL, and then later it will ignore or skip the rest of the parameters if they appear in the wrong order!!

The reason is that it is using the DataContractSerializer.

thanks to by colleague Claus for finding this forum thread there they discuss the challenge:

By | 2013-10-15T15:11:04+00:00 October 15th, 2013|Automation|1 Comment

About the Author:

Jakob Gottlieb Svendsen

Twitter: @JakobGSvendsen

Jakob Gottlieb Svendsen is a Microsoft Cloud and Data Center Management MVP (, Working as Global Lead Developer, Senior Consultant and Trainer at CTGlobal, where he is one of the driving forces in keeping CTGlobal a System Center Gold Partner and member of the System Center Alliance.

Since he started at Coretech in 2007, he has focused on Scripting and Development, primarily developing tools, extensions and scripts for the System Center Suite. His main area is Automation (including OMS/Azure Automation, Service Management Automation, PowerShell and Orchestrator). Another area is Windows Azure Pack / Azure Stack, where he does implementation, development, workshops and presentations. He is a world-wide renowned voice in the Automation field.

He is passionately devoted to the community, to which he contributes by being a moderator at TechNet and sharing his knowledge at

  • Co-founder: PowerShell User Group Denmark
  • Speaker at MMS 2016, Minneapolis (
  • SCU Europe 2014, 2015, 2016 (
  • Microsoft TechEd North America 2014, Houston
  • NIC 2012,2013,2014,2015, Oslo (
  • Microsoft CampusDays 2011, 2013, Copenhagen
  • Microsoft TechDays 2015, Sweden (
  • Microsoft Partner Event: New in SC2012 SP1
  • User group meetings (PSUG.DK , SCUG.DK/BE/NO, AZMUG + more)
  • Microsoft Certified Trainer.
  • Microsoft Scripting Guys Forum Moderator

Main working areas:

  • Automation (Azure Automation, SMA, SCO)
  • Windows Azure Pack / Azure Stack
  • System CenterVisual Studio Team Services / Team Foundation Server
  • Development:C#.Net, VB.NET, VBScript, PowerShell, Service Manager, OpsMgr, ConfigMgr
  • Orchestrator
  • Windows Azure Pack / Azure Stack


  • Azure Automation
  • Service Management Automation
  • System Center Orchestrator
  • PowerShell, VBScript, C#.Net, VB.Net
  • Windows Azure Pack / Azure Stack Development Workshops

One Comment

  1. AMK April 11, 2018 at 14:32 - Reply


    I reached your blog searching for SCOM integration with ServiceNow. I am using WSDL method and trying to configure Orchestrator Runbook, but failing to pull dynamic values into incident, the incident is being created by runbook but only hardcoded values appear. Need your help to fix this mess.

    Here is how my Request Payload looks:

    $String$String{Name from “Monitor Alert”}$StringStringStringStringStringString{Description from “Monitor Alert”}String

Leave A Comment