Power Platform Community Forum Thread Details

Hi, it appears the export Power App option retains some auth and other sensitive info within with the intent that package will be imported in a familiar environment.

Does anyone know of a method to export a Power App with supporting Flows while removing all sensitive info in the supporting .json files? I'd like to create a template for anyone to reuse publicly. Again, the existing export option retains sensitive info with the supporting files, I also noticed export doesn't capture all supporting Flows either....

Categories:

Building Power Apps

@cbernier12

If you mean the original environment info like the usernames and email addresses of the original Connectors, etc. showing up in the JSON files, here is what comes to mind right away, but note that we did not test it, so you may want to check it:

you could go ahead and make a new dummy Azure / Office 365 tenant with non-sensitive info all over it which is used solely for this purpose only, import the stuff that you feel like contains "sensitive" information into there, hook it there, then re-export it, then the information will only reference about the info from dummy tenant and does not matter at all then.

Check if above helps @cbernier12

Also in case it helps (but the above may fit much more closely with your requirement):

There is also a method to export a Power App in the msapp format by itself, independent of data sources, etc. - you go into the Power Apps Editor and you press F12 and then click on the "Download' button, in order to download an msapp copy.

Then for someone to import it they follow these steps:

Navigate with your browser manually to this URL (or just click the following link): https://us.create.powerapps.com/studio/
Then, Click "Open" on the left side
Next, Click "Browse" on the right side
Finally, select the msapp file from the window when prompted.
Done

See if any of the above helps.