We have an On Premise install of Dynamics CRM 2011 as we haven't gotten around to migrating to Dynamics 365 yet. How can I connect a Power App to the CRM 2011 web services?
We have a data gateway configured that we've successfully used for PowerBI and we have our on premise AD synchronized with Azure AD.
Hi @sparkymark75 ,
When your app loads or click on the button, use the Power Automate to search all items on the Dynamics CRM 2011.
And in your Power Automate, you connect with the Data gateway and respond to Power Apps.
In the Power Apps, you read the result and set it in a new collection.
Items property --> Set(Results, 'MyFlow.Run()')
If you like this reply, please give kudos. And if this solves your problem, please accept this reply as the solution.
Ok, I've created a flow which calls the CRM web service and parses the returned json. However when I run it, it just sits and runs for minutes and I eventually have to cancel it. If I check the Flow, the "Invoke an HTTP request" has a Bad Gateway message but keeps running.
I cancel it after its been running for around 5 or 6 minutes. If I take the URL and paste it into a browser window, it returns results within 2 or 3 seconds.
If I look at the error attached to the button I'm using to run the Flow from Power Apps it shows the following....
It's not even reaching the Response action yet so I'm not worried about that until I can get it to actually connect to the CRM web service and retrieve data.
They claim these tools are easy to use, but that's only the case when you're using the latest Microsoft products!
I've changed it to an HTTP action but now can't get the URI to be accepted!
Insert an action before the Http request called "Compose", insert the url on there and in the URI (Http action), insert the Output the Compose method.
The errors are common when we are configuring the difficult process. 🙂
Thanks. Getting somewhere now. It's still failing but with an authorization error because the CRM web service will be expecting AD authentication (which is why I was using the HTTP with Azure AD action). I now need to figure out how to get past this!