I'm trying the following: Exporting an App from one tenant (Export Package) - importing the App on a different one (import package).
App components:
- 1 SQL Connection
- 4 Flows
- 1 Outlook connection
After importing and creating/updating the connection everything seems to be fine (the message says everything was imported correctly) but if I try to modify the app I get the error "Error opening file - there was an error opening the file".
Modify error
if I try to USE the imported App, then I got a different error: "The app didn't start correctly. Try refreshing your browser. Session ID: e7dd68d2-b300-468e-a61d-87490feb9206"
Checks already done:
- I tried importing on different tenants with different accounts
- I tried importing using different browsers in-private
- Checked the "unblock" flag on the .zip package
- All the connections and the flows are up and running
- I tried to import in "creation mode" and then in "update mode" with two different packages.
Details:
App ID
e65ddae9-43aa-4df3-a2a8-47a654522d24
thanks
Ali
Solved! Go to Solution.
Hi @AliAdamu
Have you tried to do the export again?
You could also try to just save the app locally, and then open it on the new tenant while in the studio, and then save it to the new tenant.
If you can't access it in the original tenant then we can try to get the PowerApp out of the zip export, and then try to open it in the studio.
Please also keep in mind that if your other tenant was in a preview environment, the versions would not be compatible.
Let me know if you don't come right.
Dawid van Heerden
Follow on Twitter: @davestechtips
Subscribe to YouTube: https://www.youtube.com/davestechtips?sub_confirmation=1
**If you found this reply helpful, please mark this as the answer to close the topic and make it easier to find for other people with similar questions. AND we get points for it 😉
Hi @AliAdamu
Have you tried to do the export again?
You could also try to just save the app locally, and then open it on the new tenant while in the studio, and then save it to the new tenant.
If you can't access it in the original tenant then we can try to get the PowerApp out of the zip export, and then try to open it in the studio.
Please also keep in mind that if your other tenant was in a preview environment, the versions would not be compatible.
Let me know if you don't come right.
Dawid van Heerden
Follow on Twitter: @davestechtips
Subscribe to YouTube: https://www.youtube.com/davestechtips?sub_confirmation=1
**If you found this reply helpful, please mark this as the answer to close the topic and make it easier to find for other people with similar questions. AND we get points for it 😉
And that was it... a single drop-down list in the preview version was the cause of the mess.
once removed all the things worked as expected.
Strangely, I created again the drop-down list and retried. Everything was fine even then. Probably that version of the DD list was created and updated in a short period of time letting the one I had in the application not compatible anymore. It's only a guess but makes sense in the preview’s logics.
Thanks for putting me in the right direction.
Ali
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
User | Count |
---|---|
203 | |
45 | |
45 | |
45 | |
39 |
User | Count |
---|---|
279 | |
81 | |
79 | |
79 | |
69 |