Unanswered

Not seeing all objects when exporting and importing solution from non-prod to prod environment

(0) Share

Report

Posted on by nguyen-tr-ea-89

I followed this Microsoft tutorial to set up a deployment pipeline from my non-prod environment to prod environment.

Everything works fine and I'm able to export as an unmanaged solution from non-prod, store it in Github, then import the solution as managed into prod.

However, when I create my app in non-prod, the owner is me. But when I run the Github Actions workflows, the owner changes to my Service Principal (I use the SP as my authentication method to access the environments)

Therefore, when I go to prod and go to the managed solution, I don't see the app because the owner is the SP and not me.

here's what the admin sees in prod env, of course, they can see objects owned by different accounts

I can only see "Business Unit" and "Solution Health Hub" in prod env, and not the other three objects that I created in non-prod env because, after the import, those are now owned by my SP rglns-n-ENYInsight-2335-sp.

here's what I can only see in prod env, from my account

How do I go around this? Because from a PowerApps developer's perspective, I need to be able to see the app in order to click the three dots and share the app to my users.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

v-xiaochen-msft on at

Like (0)

Report

Hi @nguyen-tr-ea-89 ,

I haven't used the github import solution, but I think there are two ways to solve the problem.

1\ Use your credential instead of service principal credential in github yml file. Therefore, the owner of the created application will be you instead of sp.

2\ Elevate your environment permissions. For example, you can contact your administrator and ask him to assign you a 'System Customizer' security role. Now even if the owner of the application is someone else, you can still see it in the solution.

Best Regards,

Wearsky

Was this reply helpful? Yes No
nguyen-tr-ea-89 on at

Like (0)

Report

Hi @v-xiaochen-msft, thank you for the response.

I want to set the deployment so that every developer in the environments can move their solutions from non-prod to prod. So, I don't think I want to use my credential in the github yml file.

About asking for the a 'System Customizer' security role, then every Power Apps developer will need to ask for this, and this seems excessive so I doubt the admin will give this, but I can certainly ask. Currently, our developers are assigned "Environment Maker" role. So, they need to have all the privileges in "Environment Maker" and somehow be able to distribute the apps they build while using GitHub Actions to move solutions from non-prod to prod environment (which is the issue of this post).

I see that there's an option to create a custom security role. Is there a way for the admin to customize a role to fulfill the requirements for our developers as mentioned? I imagine a custom role that's able to see everything the SP owns and able to share its apps?

Was this reply helpful? Yes No
nguyen-tr-ea-89 on at

Like (0)

Report

I see that for Azure DevOps, there's an action to create a solution deployment settings file that can configure solution component ownership in target deployment environments. Can I do that in Github Actions? The idea is to have the action add a developer as a co-owner to the components/apps in the solution that the SP imports into prod env.

Was this reply helpful? Yes No