Migrating solution to target environment (standard data model portal)

(0) Share

Report

Posted on by MartiK

132

Hi everyone,

I am currently working with the old power portal (and all related objects) migration to a new tenant's environment.

However, when I am trying to import the solution package (all canvas, model-driven apps, tables, portal configuration app, flows, processes, etc), I am getting the below error:

However, no link is provided (Some of these dependent solutions are part of an application, which can be installed or updated to the latest version by clicking through the Power Platform Admin Center link provided.) and the solutions are managed, thus I cannot export them from my source environment to target environment.

Any ideas or thoughts on that would be very appreciated! 🙂

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (1)

Jcook 7,781 Most Valuable Professional on at

Like (0)

Report

Hello @MartiK

What I normally do is create a blank Power Pages site in the target env, this will get all the necessary solutions and dependencies for the portal.

Was this reply helpful? Yes No
remandlo 2 on at

Like (0)

Report

I am getting an error when exporting (unmanaged) power page solutions and importing (unmanaged) to a different environment using the DevOps Pipelines. I am using the Power Platform tools and I am getting the following error messages:
failed: info: bolt.Session[0] Product Version: 1.30.5+g0bf9504; File Version: 1.30.5 info: bolt.Session[0] Start new session. (sessionId: 251736c1-0052-4ecd-9862-851cf6bff8a7; operationId: f24fa54d62cc78ed432546e9e223dbce; userId: bff2c9cb-0041-4faa-a583-216b1dce13a8; nonInteractiveMode: False) info: bolt.cli.CommandProcessor[0] StartExecutingVerb (Verbs: ["solution","export"]) info: bolt.cli.Verb[0] Executing verb 'solution export' with arguments --name,--path,--overwrite,--managed,--async,--max-async-wait-time.

Was this reply helpful? Yes No
Verified answer

MartiK 132 on at

Like (0)

Report

The problem was solved by switching the data model to standard (from enhanced), because old Power Portals was build on standard data model

Was this reply helpful? Yes No