Copilot Studio Agent with SharePoint Knowledge (Dataverse-based): Connection References and Dataverse Tables No Longer Added to Solution

Question

Copilot Studio Agent with SharePoint Knowledge (Dataverse-based): Connection References and Dataverse Tables No Longer Added to Solution

Sohna Sukumaran Hemalatha 0

Agent scenario

I have a Copilot Studio agent that uses SharePoint knowledge sources configured using the Dataverse storage method.

I had no issues adding this agent to a solution before in my Dev environment. When the agent was added, all required connection references and associated Dataverse tables/records for the knowledge sources were automatically included, allowing the solution to pass Solution Checker, and smooth deployment with pipeline.

Issue

A few days ago, while preparing for a fresh production deployment, I created a new solution in Dev and added the same agent. Since then, I have encountered the following behaviour:-

Connection references and Dataverse table dependencies were not added into the solution in Dev.
When attempting to export the solution, it showed an error and prompted for only 1 (of the 2) Dataverse entries associated with the SharePoint knowledge sources is included.

So now my solution is not correct, it is missing one full chunk of knowledge and I cannot deploy it to QA.

What I've already tried

Used Add Required Objects on the agent component.
Recreated knowledge sources in the agent
Created a brand-new solution and repeated the process.
Verified that both SharePoint knowledge sources are configured using the Dataverse method and are working correctly within the agent in Dev.
I also see the records inside DVTableSearch table in Dev.

0 comments

1 answer

Your answer

Answer 1

Prasad-MSFT 10,541 Microsoft External Staff Moderator

This looks less like an agent configuration issue and more like a solution dependency/ALM issue with the Dataverse-backed SharePoint knowledge sources. Since both knowledge sources work correctly in Dev and their records exist in DVTableSearch, the key issue appears to be that only one of the two underlying Dataverse knowledge/search records is being picked up by the solution dependency tree.

Check the PowerAIExtensions version in Dev/QA and make sure it's current.
Identify the two DVTableSearch records and determine which one is actually included in the solution.
Compare the dependencies/relationships of the included vs. missing record.
Check the agent's solution dependencies, rather than relying only on Add Required Objects.
If possible, explicitly add the missing Dataverse knowledge/search component and test the export again.

Please do not manually copy/recreate the DVTableSearch records in QA, as these are system-managed knowledge/search metadata.

The fact that this worked previously but now fails with a newly created solution also makes a recent Copilot Studio/Power Platform ALM change or regression worth considering.

If you can share the exact solution export error (especially the part showing the 1-of-2 Dataverse entries), we can pinpoint which dependency is missing.

Sohna Sukumaran Hemalatha 0 Reputation points

2026-08-21T11:32:13.7633333+00:00
Thank you for taking a look at this and for the suggestions, @Prasad-MSFT ! :)

After solution export flagged the missing components (see screenshot below),

I followed the action to add them. As a result of that, both connection references and 1 (of the 2 DVTableSearch objects) were automatically added into the solution.

Solution Checker doesn't give any errors

Checking for solution dependencies doesn't highlight the missing dataverse entry

Checked the two DVTableSearch records and confirmed that only one was included in the solution

It is not possible for me to add the 2nd Dataverse component into the solution as what is missing is a record from DVTableSearch not the full table.

There is nothing special about the 2nd Dataverse component - this comes from a SharePoint Knowledge which is set up exactly like the other one - it points to a different folder in the same Document Library. I've already verified that the permissions of the library including the folders are all correct & nothing has changed. I also tried to remove the Knowledge and add it back to the agent. That also did not add the component into the solution.

What is strange is that the connection references and dataverse entries are not getting added into the solution automatically when I add the agent into the solution. This was the behavior always until two days ago when I started getting this error. Could this be some changes related to solution design from Microsoft related to dataverse tables?

✅ I've taken a note of the below and won't be going in that direction

No manual copy of DVTableSearch records in QA