Oracle Web Services On Demand Guide > Web Services On Demand API Calls > Web Services v2.0 API Calls >

The Field-level Replace Operation

For the Web Services v2.0 Update and Execute method calls you can specify the operation attribute with the value "replace" on reference ID fields. Requests that include this attribute remove the existing association between the parent and the referenced record and create a new association with a specified record. An example of such a request is as follows:

<CampaignUpdate_Input xmlns="urn:crmondemand/ws/ecbs/Campaign/">

<ListOfCampaign>

<Campaign>

<Id>1-FRW01</Id>

<CustomObject1Id operation="replace">1QA2-LVL4X</CustomObject1Id>

</Campaign>

</ListOfCampaign>

</CampaignUpdate_Input>

In this example, the existing association between the campaign parent and the custom object child record is replaced with an association between the campaign parent and the custom object record with the ID: 1QA2-LVL4X.

The list of objects and reference ID fields that support the replace operation in the current release is shown in Table 30.

Changes to WSDL Files

To enable the field-level replace operation, the data types for many elements in WSDL files were changed from the string to OperationData data type in Oracle CRM On Demand Release 26.

For example, in the Web services v2.0 WSDL file for Service Request in Release 25:

<xsd:element name="CustomObject1Id" maxOccurs="1" minOccurs="0" type="xsd:string" />

and for the WSDL for Service Request in Release 26 and later:

<xsd:element name="CustomObject1Id" maxOccurs="1" minOccurs="0" type="xsdLocal1:OperationData" />

The definition of the OperationData type is as follows:

<xsd:complexType name="OperationData">

<xsd:simpleContent>

<xsd:extension base="xsd:string">

<xsd:attribute name="operation" type="xsd:string" />

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

This change will not regress existing proxy classes and integrations generated using WSDL files from before Release 26. However, if you are planning to generate fresh proxy classes from WSDL files from Release 26 and later, you must enhance your integration to use the OperationData data type.

Also, note that upgraded Release 26 proxies and updated integrations will be able to consume the OperationData data type value against a Release 25 environment only if the replace functionality is not used. In other words, you cannot use the operation attribute against an environment based on an older release than Release 26.