Answered

Importing canvas app to another tenant goes wrong

(0) Share

Report

Posted on by Ousselg

I exported a powerapp from a dev tenant I don't have anymore, when I requested a new dev tenant I tried importing the app.

It keeps failing when importing the flow part.

Is there a way to edit the json file to skip that step or take the whole flow part out of the import?

I deleted the flow folder but that didn't do the trick.

This is the error I get:

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (1)

BCLS776 8,994 Moderator on at

Like (0)

Report
Copy link

Link copied!

If the app has an associated flow, are you exporting/importing a Solution or just the app on its own? A Solution would work much better.

Bryan

Was this reply helpful? Yes No
Ousselg 53 on at

Like (0)

Report
Copy link

Link copied!

It's a app not a solution. I don't have access anymore to the tenant so is there a way to skip the flow part or change the json file?

Was this reply helpful? Yes No
BCLS776 8,994 Moderator on at

Like (1)

Report
Copy link

Link copied!

Well, I think there's a way around this, but haven't done it myself. Ready for an adventure?

We can directly edit the json files for the app using VS Code. You'll start by downloading that IDE plus the extensions for Power Apps. Then, import your app so we can look at the raw files.

I am also calling in some help to see if they can provide some advice: @RandyHayes , @StalinPonnusamy , @ChrisPiasecki

Fellas, this Maker has an app with a dependent flow (not in a Solution) that is failing on import, probably due to the non-existent flow reference in their target environment. Other than editing the source files, can you think of another way around this? If we have to edit source files, do you know which fields this Maker will need to edit to get something that will import? In the end, they will need to recreate/reconnect the SharePoint List and flow too.

Bryan

Was this reply helpful? Yes No
Verified answer

RandyHayes 76,299 Super User 2024 Season 1 on at

Like (2)

Report
Copy link

Link copied!

@BCLS776

The export will produce a zip file in it. In that zip file will be a manifest.json file. Although I have never had a need to modify it, it would seem feasible to remove the dependency to the flow.

You'd need to scroll through that file and find the record for the flow and remove it and then make sure you take note of the guid for that flow and remove that from the dependency list.

If you just want the app itself, in that zip file you will find a Microsoft.PowerApps folder. In that is an apps folder. In that folder you will find some long number folder, and in that folder you will eventually find a GUID named file with an MSAPP extension. That is the app!

If you pull that out and then open it (not import it, but open) in the designer...that will be the app. You will have bunches of errors because none of the dependencies will have been brought in, but you will have the app.

I hope this is helpful for you.

Was this reply helpful? Yes No
Ousselg 53 on at

Like (0)

Report
Copy link

Link copied!

This worked, thanks for the help!

Was this reply helpful? Yes No