HTTP 400 and/or BadGateway (http request to Dynamics CRM)

[ZePowerDiver]

I'm trying to build a flow that will eventually return data from CRM based on a user query. All works well in my browser, but when I try to integrate in a Flow it fails. So I dropped the filter out of the equation and only went to select data from a OOB entity (accounts in this case).

When I test it, I get an error http 400 !!

HTTP REQUESTHTTP RETURN CODE 400!!!

So, I added my next step right away, which is to provide a response back to the calling app of the body obtained in the first step..

If I test this, the flow doesn't even execute as I get a Bad Gateway error at the run popup window!

ADD RESPONSE IN FLOWBADGATEWAY!!!!

help appreciated!

[ZePowerDiver · Accepted solution]

It's funny how you end up finding a solution to an issue.. just when you dropped the towel and sent out the question in the world!!

I ended up going in the run history to see if I could see details about the bad gateway.. and that's where I fumbled the following details regarding the error 🙂

Bottom line, in the connection definition I had used the "CRM" site address and in the http request I used the API call URL

when in fact I had to make sure the resource URI was/is the API one!!

Case closed!

[NicolasK · Accepted solution]

Glad you found a solution, but your analysis is not completly correct. 

The important thing is that each URL is the same. It does not matter if it is the API url or the main one, as long as they are identical.

So you can have https://xxxx.crm.dynamics.com in both connection definition and action URL, and it will work perfectly too.