microsoft / microsoft/powerplatform-actions
Not seeing all objects when exporting and importing solution from non-prod to prod environment
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 301
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
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.
For example, here's what the admin sees in the managed solution in prod env, of course, they can see all objects owned by different accounts:
here's what I can only see in prod env, from my account:
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.
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Microsoft Power Platform ALM tutorial and the repository's GitHub Actions deployment workflow. Reproduce the non-prod export and managed import with the service principal, then investigate how ownership affects object visibility in prod; done means the ownership or access behavior is explained and a supported resolution is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100