Export and Import of Copilot Solution Between Power Envs Issue

(4) Share

Report

Posted on by Mithoon

I'm facing the following issues while exporting and importing a Copilot solution between two Power Platform environments (from our dev environment to prod). The Copilot was created with topics and knowledge sources (PDFs) in the dev environment, and we exported it as a managed solution using PowerApps. However, upon importing into the prod environment, I'm encountering these issues:

Topics issue: The topics section displays the following message: “Because this topic is managed and non-customizable, it can't be modified.” Furthermore, within the custom topics, the "Create Generative Answers" node under Data Sources is showing the error: "Cannot reference variable from component 'XXX'." These issues are preventing modifications to the topics and impacting the functionality of the Copilot in production.
Knowledge Source issue: The knowledge source PDFs were not imported, resulting in the Copilot not being able to provide responses from the knowledge source in the production environment.

Could you kindly advise if I need to export and import the solution with unmanaged settings and manually configure the knowledge PDFs, topics, and nodes in the new environment? Additionally, if there’s a best practice or alternative approach to resolving these issues while moving Copilot solutions between environments, I would greatly appreciate your guidance.

Thank you in advance for your assistance.

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (0)

EL-05111634-0 3 on at

Like (0)

Report

I have the same problem with documents upload, Knowledge base is exported and i can download files, but they seem lost connection with embedded/vectorized data/search, so their status is "unknown" and i can not search them as knowledge-base.

Was this reply helpful? Yes No
Suggested answer

Vinoth Selvam 1,590 Super User 2025 Season 2 on at

Like (0)

Report

Hi Mithoon ,

For migration purposes, use an unmanaged solution to move your Copilot configuration from dev to prod. This will allow you to make necessary adjustments after import, especially for topics and nodes.

PDF knowledge sources do not automatically transfer with solution imports/exports. Knowledge sources such as PDFs need to be manually added to each environment, as the links are specific to the environment where they were initially uploaded.

Thanks.

Was this reply helpful? Yes No
Suggested answer

Vinoth Selvam 1,590 Super User 2025 Season 2 on at

Like (0)

Report

Hi Mithoon ,

You can checkout this video from Dewain.

https://www.youtube.com/watch?app=desktop&v=6sLGlCoypTI

Hope this will help you.

Thanks.

Was this reply helpful? Yes No
MM-20031533-0 2 on at

Like (0)

Report

@Vinoth Selvam
I'm also facing the same issue. I used website links as a knowledge source and moved the solution as unmanaged to another environment. However, all the knowledge sources were missing, and in the Generative Answer action within the topic, the knowledge source links caused an error.

I manually added and linked them back, but after re-importing a new version of the solution, the same issue occurred again at the topic level, where the links to the knowledge source failed.

How should we handle this situation? Does this mean we always need to modify the topics and update the knowledge source in the Generative Answer action after each import?

What if we have multiple knowledge sources linked to different topics? Do we need to perform this task manually after every import? Is there no smarter solution available to handle this efficiently?

Was this reply helpful? Yes No
advillacorta 29 on at

Like (0)

Report

@Mithoon,

Yesterday I had the same problem as you mention. To solve it, I did the following steps:

1. Go to the solution where your agent is created.

2. Click on the 3 dots.

3. Select Advanced > Add required objects

4. Wait until the process ends.

5. Check the Agent components tab and you will see all the files, knowledge previously configured for your agent.

In that way, when you export and then import your solution in another environment, all references will keep the same without problem.

Hope it helps,

Thanks,

2 people found this reply helpful.

Was this reply helpful? Yes No