Hi PowerApps Communtiy,
I'm struggling right now with adding a Flow which uses the Common Data Service (Current Environment) connector to my Canvas app. I have determined that the current environment connector is the issue because when I removed the connector and just used the regular CDS connector, the flow was successfully added to my app. However I need the current environment connector because I need to run a query using fetchxml (odata doesn't have the type of joins we need unfortunately) and then return the result set to the Canvas app which then puts the data into a collection.
What is really strange is that I already have flows added to my app which use the Current Environment connector and successfully execute fetchxml queries and return the data to the Canvas app and it successfully converts the JSON to a collection, but these flows have been in my app for some time now (a few weeks). It seems that something changed recently which broke Canvas App's ability to add Flows with the current environment connector.
I'm having a similar issue. I have several instant Flow built and previously has no issue. Now if I want to add flow into the Canvas app I'm building, it displays nothing and says I don't have any flow built.
Hi @frustrateduser9 ,
Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned.
Please consider take a try to move the CDS action in your flow from the "If/yes" branch of the nested Condition to above the Condition action, then save your app, try your app again, check if the issue is solved.
Also please consider re-create a new app based on your data source, then add a new connection to the flow from your app, then check if the issue still exists.
I have the same issue. Even with a brand new app. just add a button and get error on all flows recently created. the flows aren't even doing anything, just tests that initialize a variable.
Nothing I try works, if I ask PowerApps for a variable the flow cannot be attached to the button.
If I had not done this many times I would assume that I was doing something wrong but clearly something is very broken.
I'm having the same issue. What I did is I temporarily removed the CDS (current environment) action from my flow, add the flow to the canvas app (this time it will be successfully added), then re-add the CDS action to my flow.
This is a quick work around, however, where to trying to achieve a seamless managed deployment which does not involved the steps above whenever we deploy to a different environment. This will not be possible with the current issue
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.
Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.
Featuring samples like Return to the Workplace and Emergency Response Applications
Features releasing from October 2020 through March 2021