cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ZePowerDiver
Level 8

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

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 !!

 

2019-02-06_12-16-55.jpgHTTP REQUEST2019-02-06_12-18-45.jpgHTTP 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!

 

2019-02-06_12-20-07.jpgADD RESPONSE IN FLOW2019-02-06_12-20-31.jpgBADGATEWAY!!!!

help appreciated!

2 ACCEPTED SOLUTIONS

Accepted Solutions
ZePowerDiver
Level 8

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

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 🙂

 

2019-02-06_12-33-27.jpg

 

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

 

2019-02-06_12-40-32.jpg

 

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

 

2019-02-06_12-39-59.jpg

 

Case closed!

View solution in original post

NicolasK
Level: Powered On

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

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.

View solution in original post

2 REPLIES 2
ZePowerDiver
Level 8

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

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 🙂

 

2019-02-06_12-33-27.jpg

 

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

 

2019-02-06_12-40-32.jpg

 

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

 

2019-02-06_12-39-59.jpg

 

Case closed!

View solution in original post

NicolasK
Level: Powered On

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

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.

View solution in original post

Helpful resources

Announcements
firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

firstImage

Incoming: New and improved badges!

We've given our badges an overhaul and also added some brand new ones!

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

sixthImage

Power Platform World Tour

Find out where you can attend!

seventhimage

Webinars & Video Gallery

Watch & learn from the Power Automate Community Video Gallery!

Top Kudoed Authors (Last 30 Days)
Users online (4,146)