Apex Code Development You need to sign in to do that
Don't have an account?
MDXHiker Extra attribute in Outbound Message
I use outbound messages to kick off a process which does further downstream processing. I have an integration which is running for the past 6 months
Over this last weekend, I noticed that extra attribute was being sent over which my schema did not account for. Hence it starting erroring out.
Now the outbound message and the workflow rule in Salesforce was not modified whatsoever.
I am puzzled that this was being inserted.
<notifications>
<OrganizationId>00D0000000XXXXXXX</OrganizationId>
<ActionId>04k000000004CA1AAM</ActionId>
<SessionId xsi:nil="true"/>
To resolve this I wrote a script to strip out the namespace, and then it worked fine
<notifications>
<OrganizationId>00D00000000XXXXXX</OrganizationId>
<ActionId>04k000000004CA1AAM</ActionId>
<SessionId/>
My question is how was attribute added over hte weekend and what do I do to prevent future changes like these?
Thanks
Message Edited by MDXHiker on 06-09-2008 03:08 PM
Over this last weekend, I noticed that extra attribute was being sent over which my schema did not account for. Hence it starting erroring out.
Now the outbound message and the workflow rule in Salesforce was not modified whatsoever.
I am puzzled that this was being inserted.
<notifications>
<OrganizationId>00D0000000XXXXXXX</OrganizationId>
<ActionId>04k000000004CA1AAM</ActionId>
<SessionId xsi:nil="true"/>
To resolve this I wrote a script to strip out the namespace, and then it worked fine
<notifications>
<OrganizationId>00D00000000XXXXXX</OrganizationId>
<ActionId>04k000000004CA1AAM</ActionId>
<SessionId/>
My question is how was attribute added over hte weekend and what do I do to prevent future changes like these?
Thanks
Message Edited by MDXHiker on 06-09-2008 03:08 PM