Unanswered

As of today, my Users can't see environments other than the default environment when using a browser

(0) Share

Report

Posted on by UB400

356

I have created several environments, which were until today visible to Users I had shared apps with. As of today, the Users can only see the default environment when they log in using a browser.

I've not assigned any specific permissions in the environments. The Users can access the apps in their respective environments while using the Windows PowerApps Studio, but can't access them when using a browser.

I initially thought it may be a licencing issue and have subsequently purchased licences and assigned them to the Users.

We're using CDS.

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

Sort by

carlosag Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Did you have them contributor access? If not they would need to run the apps from the "consumption" portal. Can you ask then to go to https://home.dynamics.com/ and see if they can run them from there?

Web.powerapps.com is more intended for be application maker for them to manage apps, create new ones or share and manage other resources like cds, flow or connections, hence if they don't have contributor access hey will not see them there.

Was this reply helpful? Yes No
UB400 356 on at

Like
a
(0)

Report
Copy link

Link copied!

@carlosag thanks for the super quick response, I really appreciate it. I tried as you suggested and that works. Is this a new change, because as of last use on Friday 28th April, the Users were able to select the environment to connect to.

Also a related question, when the App is displayed in the Dynamics site, it does not show the logo I had used for the App, instead I only see the PowerApps logo, any way of changing this?

Was this reply helpful? Yes No
carlosag Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

From a PowerApps perspective that has not changed, the environments that are shown are either 1) Environments that the user has Maker permission (this can be added in https://admin.powerapps.com/) or 2) Environments where the user has at least one application where he/she are a contributor.
What could have happened is if someone removed them from the maker permission, or if someone removed (or unshared) an app where they were makers.

In regards to the logo, that should not be the case, the logo should show the same logo you have configured for your application. If you have never been to that site, maybe give it an hour and see if it starts showing since it may be a caching issue.

Was this reply helpful? Yes No
UB400 356 on at

Like
a
(0)

Report
Copy link

Link copied!

@carlosag thanks. There were no changes made as far permissions go, the Users have always had User permissions. The experience so far has been as follows: first time the User logged in, they were shown the "default" environment. The User then had to select the environment where the App had been published. The only change was made to some formulas inside of the App around 16 hours ago.

I'll wait to see if the logo appears, in the test I just did with a "User" account, was the first time logging in to the dynamics site.

As for the logo, this is what shows at the top of the App

Was this reply helpful? Yes No
abdullahilyas 2 on at

Like
a
(0)

Report
Copy link

Link copied!

None of this worked for my users, however I did found a workaround:
The steps below, while initially worked for me, did not work for users.
1) using edge browser go to https://make.powerautomate.com
2) from upper right hand corner, click on Environment, & then select "the desired environment"
3) from within make.powerautomate.com site, lower left hand side menu, select option for Power Platform,
4) from pop up window select Power Apps, this will bring him to "lets build an app" title page in "make.powerapps.com",
5) from within this page, under section your apps, select "Apps under the Desired Environment" , now you should be able to Edit
the app

the work around is using static URL to make.powerapps.com replace the default environment part listed before /home with the desired environment ID:
example: https://make.powerautomate.com/environments/Default-whatever/home to https://make.powerautomate.com/environments/desired_environementID/home

Was this reply helpful? Yes No