We are using a tool (SAP PI using Advantco's CRM Adapter) to update the Account record based on the values in our ERP system. We are using an Upsert xml via SOAP.
We can successfully modify all fields with the exception of one. The Name field when we attempt to modify on the Account record throws an error stating Expected Non-Empty GUID. - the AccountId is not empty - the ID is not empty. The only thing modified was the text of the string field name. I have tried removing AccountId from the attribute list - changing the ID to a FetchXML query. All fail if we reference the name field.
<?xml version="1.0" encoding="UTF-8"?>
<DFCUDAccountRequest>
<RequestName>Upsert</RequestName>
<Parameters>
<Entity>
<LogicalName>account</LogicalName>
<Id>23b1cc0a-6a9c-e711-80e7-0050569b0dd7</Id>
<Attributes>
<AccountId>23b1cc0a-6a9c-e711-80e7-0050569b0dd7</AccountId>
<Name>DianeTest</Name>
<AccountNumber>99988877</AccountNumber>
<spirit_SAPAcctType>100000000</spirit_SAPAcctType>
</Attributes>
</Entity>
</Parameters>
</DFCUDAccountRequest>
Are there some limitations on the Name field? Our system of record has the ability to modify the name field (as there is an account number field that makes it unique) so we must keep the two systems in sync.
Can workflows update the name field? Do we have to come up with an alternative field for the system of record to update and then a workflow fires to modify the name field?
Thank you for your time,
Diane
Suggestions? Reasons we are hitting this error?
*This post is locked for comments
I have the same question (0)
