Power Automate process will not run from Power App in QA Environment

(0) Share

Report

Posted on by iskguy

402

We are using pipeline to deploy solutions from DEV to QA (then to PROD). This has been successful with one app that does not use a power automate process. We have another that I published into QA and it does have a power automate process in the solution. The process saves uploaded attachments to a sharepoint library. In DEV this works for anyone who is testing. However, in QA I have users that get this error. I have deleted the solution from QA and republished, I have checked connections and environment variables. Not sure what else to check. Thanks for any help and advice.

Categories:

Building Power Apps

All responses (4)

Answers (0)

Sort by

Suggested answer

Pstork1 69,665 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Check the environment settings for the QA environment in the Power Platform Admin center. I suspect the QA environment is secured with a group and some of the people testing aren't members of the security group in QA.
iskguy 402 on at

Like
a
(0)

Report
Copy link

Link copied!

I checked the environments. We have DEV, QA, and PROD environments. The only difference I see is that QA is under a "Developer" environment whereas the other two are production. Possibly that could be the reason. I did also see this when looking at the settings in QA.
Pstork1 69,665 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Unless you specifically add users to the Developer environment they are restricted to the user who owns the environment. Normally you would use a Developer environment for Dev, but a Sandbox for QA. I suspect that is the problem. I would switch it out to a different environment. That limitation is documented here: About the Power Apps Developer Plan - Power Platform | Microsoft Learn
Suggested answer

iskguy 402 on at

Like
a
(0)

Report
Copy link

Link copied!

I did notice in one error message when I tried to add a security group that due to the environment being set up as a "developer"-type environment that security groups were not allowed to be added. That is the whole issue. It is too bad the environment itself could not be edited to be a production-type environment. But what we did is disable the QA environment and set up a new TEST environment and it seems to be working.