This article is for providing the syntax usage to define an input for "ArrayOf_tns3_ResourceIdentityInfo"
NCM 10.1.X
The ArrayOf_tns3_ResourceIdentityInfo" is an array of ResourceIdentityInfo i.e, ResourceIdentityInfo[].
Reference: Following is a sample of its implementation to auditDevices using the API sample.
This sample has input of two devicesIDs.
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="Urn:ApiService" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<soapenv:Header/>
<soapenv:Body>
<urn:auditDevices soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<in0 xsi:type="urn:ArrayOf_tns3_ResourceIdentityInfo" soapenc:arrayType="api:ResourceIdentityInfo[]" xmlns:api="http://api.common.configmgr.powerup.com">
<item xsi:type="api:ResourceIdentityInfo" xmlns:api="http://api.common.configmgr.powerup.com">
<resourceKey xsi:type="soapenc:string">0a50421a96a0df3f7fed80f98d010000</resourceKey>
<resourceName xsi:type="soapenc:string">NCM-Dev-1</resourceName>
<resourceType xsi:type="soapenc:string">DEVICE</resourceType>
</item>
<item xsi:type="api:ResourceIdentityInfo" xmlns:api="http://api.common.configmgr.powerup.com">
<resourceKey xsi:type="soapenc:string">0a50421ae004d03fc9cecc578f010000</resourceKey>
<resourceName xsi:type="soapenc:string">NCM-Dev-2</resourceName>
<resourceType xsi:type="soapenc:string">DEVICE</resourceType>
</item>
</in0>
<in1 xsi:type="api:ResourceIdentityInfo" xmlns:api="http://api.common.configmgr.powerup.com">
<resourceKey xsi:type="soapenc:string">0a50421ac554d03f05c185588f010000</resourceKey>
<resourceName xsi:type="soapenc:string">std</resourceName>
<resourceType xsi:type="soapenc:string">CASTANDARD</resourceType>
</in1>
</urn:auditDevices>
</soapenv:Body>
</soapenv:Envelope>
NOTE: The above is an example for implementation of the ArrayOf_tns3_ResourceIdentityInfo and not a standard.
Support does not engage with assistance with APIs, and hence the example should be modified/implemented based on user requirements accordingly.