Problem of a not found ID used for updating MObjects | Community
Skip to main content
July 14, 2014
Solved

Problem of a not found ID used for updating MObjects

  • July 14, 2014
  • 3 replies
  • 1319 views
Hi all,

I'm coding integration with SOAP APIs.
When updating data into Opportunity with a record whose ID coule not be found, I think the server send me a result with an error message "not found" and a null id. (ID being null, -1, 0, or the specified invalid value would all make sense.)
But in the SOAP API, the id property is required in result. So I could not get the exact result message but an exception of deserializing XML string.

I think it is better to make the id property being allowed to be null or empty, or to set a valid number with special meaning to the id property of result.
Could you please show me whom could I send this issue to? And how long it would cost for me to get the support?

Thanks,
Biao
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by

It works now after version 2_7

3 replies

July 14, 2014
That is more an enhancement than a bug as such. I would suggest to submit an "Idea".

July 14, 2014
OK, thank you very much.
I'll move it to "Idea".
Accepted solution
September 10, 2015

It works now after version 2_7