• Salesbot
  • NEWBIE
  • 0 Points
  • Member since 2017

  • Chatter
    Feed
  • 0
    Best Answers
  • 1
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 0
    Replies
After updating Enterprise WSDL from v40 to v41, LeadConvert seems to require accountRecord, contactRecord, opportunityRecord, bypassAccountDedupeCheck, and bypassContactDedupeCheck.

I'm looking through the SOAP API documentation (LeadConvert Arguments): https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_calls_convertlead.htm. The fields above don't appear anywhere.

Does anyone know where these fields come from? Is the documentation incomplete? Is there a way to ignore them? I was happy with v40 api behavior.
After updating Enterprise WSDL from v40 to v41, LeadConvert seems to require accountRecord, contactRecord, opportunityRecord, bypassAccountDedupeCheck, and bypassContactDedupeCheck.

I'm looking through the SOAP API documentation (LeadConvert Arguments): https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_calls_convertlead.htm. The fields above don't appear anywhere.

Does anyone know where these fields come from? Is the documentation incomplete? Is there a way to ignore them? I was happy with v40 api behavior.