Salesforce Response mapping generating 405 error intermittently | XM Community
Skip to main content
Solved

Salesforce Response mapping generating 405 error intermittently

  • August 29, 2018
  • 6 replies
  • 341 views

Howdy We have a survey which is mapping back to the Contact object in Salesforce, it works most of the time but occasionally we get the following debug email and nothing gets updated back on Contact: StatusCodeError: 405 - [{"errorCode":"METHOD_NOT_ALLOWED","message":"HTTP Method 'PATCH' not allowed. Allowed are HEAD,GET,POST"}] Any ideas?? Sorry if this in the wrong category. Regards Cain

Best answer by LaurenK

Hey @Cain! If you have not yet already, feel free to reach out to our Support Team and ask for an Integrations specialist so they can further troubleshoot this with you!

6 replies

MohammedAli_Rajapkar
QPN Level 5 ●●●●●
Forum|alt.badge.img+20
Is it possible to share the response mapping window screen-shot? it will help to look into it further Also, are you performing the response mapping through "Action" tab or "Tools"?

LaurenK
Former XM Community Team Member
Forum|alt.badge.img+13
  • Former XM Community Team Member
  • Answer
  • September 4, 2018
Hey @Cain! If you have not yet already, feel free to reach out to our Support Team and ask for an Integrations specialist so they can further troubleshoot this with you!

Mohammedali_Rajapakar_Ugam LaurenK
Hi, was this ever resolved? I am having the same problem almost constantly.


KevinMcNamara
Level 1 ●
Forum|alt.badge.img+2
  • Level 1 ●
  • October 13, 2020

I am having the same problem with all Salesforce updates on recently modified actions. I submitted a ticket with Qualtrics. I will update here if I learn anything.


LaurenK
Former XM Community Team Member
Forum|alt.badge.img+13
  • Former XM Community Team Member
  • October 13, 2020

Hi rebecca_reed - if you have not yet already, you'll want to follow what KevinMcNamara did here and submit a ticket with our Support team, as they are best equipped to help troubleshoot and look into this for you!


KevinMcNamara
Level 1 ●
Forum|alt.badge.img+2
  • Level 1 ●
  • October 13, 2020

rebecca_reed I ended up figuring out my mistake. I had changed my task conditions slightly but it was "any" instead of "all" true. This made it fire on records that were missing the "Id" column to match on. Without an Id you can do an insert but not an update. My own silly mistake. Hope that helps some.