Microsoft Dynamics 365 | Integration, Dataverse...

Error deploying after deleting virtual table

(0) Share

Report

Posted on by AH-04121610-0

My solution uses a virtual table to SharePoint. In my latest version of the model drivel app, I'm retiring the virtual table and moving to a standard table.

I deleted the table, the connection reference, and the VDS.

The deployment from dev to test keeps failing with the error message: "Entity 'connectionreference' With Id = 061e92ea-13dc-f011-8544-6045bd13c440 Does Not Exist"

I cannot find a connection reference with that ID in dev or test so I believe that is the connection reference I deleted - as it is no longer required. Since it's no longer required, I'm struggling to understand why it's causing the import to fail. The export seems to be working fine.

Categories:

Dynamics 365 general

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

11manish 1,309 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!
Don't recreate the Connection Reference and don't keep retrying the same export.
Your migration from:
SharePoint Virtual Table → Standard Dataverse Table
has left a stale dependency somewhere in the solution or in the managed layers of Test.
I would:
Search the exported solution ZIP for the exact GUID.
If found, identify and remove the component referencing it.
Check the model-driven app for the retired virtual table.
Check solution-aware flows for the old SharePoint Connection Reference.
Check Show Dependencies / Missing Dependencies.
In Test, inspect the managed solution and solution layers.
Publish all customizations.
Increment the solution version.
Export again.
Import as a managed solution upgrade if this is your normal Dev → Test ALM process.
That is the cleanest approach because the goal isn't to satisfy the missing GUID—it is to remove the dependency on that GUID completely. Microsoft explicitly recommends removing the dependency when the missing component is no longer required rather than restoring an obsolete component.
Refer :
https://learn.microsoft.com/en-us/troubleshoot/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import

Was this reply helpful? Yes No
Suggested answer

rajeshjamrodh 50 on at

Like (0)

Report
Copy link

Link copied!

Hi …..Virtual Tables in Dataverse are generally used when we need to expose and work with data that resides in an external system without physically storing that data in Dataverse.
The Virtual Table provides a Dataverse table-like interface to the external data source, while the actual data remains in the external system.
In an integration scenario, D365 CE can use the Virtual Table to retrieve, view, and, where the provider supports it, create/update/delete data in the external system. The actual persistence is handled by the external application rather than Dataverse.
Therefore, if we remove a Virtual Table from a solution, we must verify all dependencies and integration components before deployment. Forms, views, lookups, relationships, Power Automate flows, plugins, Custom APIs, JavaScript, PCF controls, model-driven apps, and virtual-table provider/data-source configuration may still reference the Virtual Table.
The deployment should therefore be handled through the proper solution/ALM process, rather than manually deleting the Virtual Table in higher environments.

Was this reply helpful? Yes No