I have a solution that I can't export/import to a new environment as long as it has virtual tables. The error is below and I've checked normal stuff: I have admin privileges, no issue with the virtual tables in the source environment.
Solution contains a Canvas app, model driven app, flows, virtual tables and custom tables. If I remove all of the virtual tables, solution seems to import fine. The only only commonality that I can see is that all of the virtual tables use the same virtual table data source (which makes sense as they all live on the same SQL server).
Solution "XXXXXXX" failed to import: Failed to create entity with logical name cr0d1_client_episode_visit_with_notes and object type code 11167. Exception: Microsoft.Crm.BusinessEntities.CrmObjectNotFoundException: Cannot add EntityDataSource with id (fe48cbbb-a046-ee11-be6d-000d3a3707cb) to solution (743888ae-6f0a-4ba3-bd20-8642ff6ea973) because it does not exist at Microsoft.Crm.ObjectModel.SolutionComponentService.VerifyComponentExists(IBusinessEntity entity, ExecutionContext context) at Microsoft.Crm.ObjectModel.SolutionComponentService.AddSolutionComponent(Guid componentId, Int32 componentType, Guid solutionId, Boolean addRequiredComponents, Boolean doNotIncludeSubcomponents, String[] includedComponentSettingsValues, ExecutionContext context) at Microsoft.Crm.ObjectModel.SolutionComponentService.AddSolutionComponent(Guid componentId, Int32 componentType, Guid solutionId, Boolean addRequiredComponents, ExecutionContext context) at Microsoft.Crm.MetadataService.VirtualEntity.VirtualConnectorProviderService.AddDatasourceAndConnectionReferenceToSolution(Guid entityDataSourceId, Guid solutionId, ExecutionContext executionContext) at Microsoft.Crm.MetadataService.VirtualEntity.VirtualConnectorProviderService.PostProcessVirtualTableSyncCore(IEntityInfo entityInfo, ExecutionContext executionContext) at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute(ILogger logger, EventId eventId, ActivityType activityType, Action action, IEnumerable`1 additionalCustomProperties) at Microsoft.Crm.MetadataService.VirtualEntity.VirtualConnectorProviderService.PostProcessVirtualTableSync(IEntityInfo entityInfo, ExecutionContext executionContext) at Microsoft.Crm.Metadata.EntityService.PostProcessVirtualConnectorProviderEntity(ExecutionContext context, EntityCreateInfo entityInfo, Boolean isInSolutionImportMode) at Microsoft.Crm.Metadata.EntityService.CreateInternalHelper(EntityCreateInfo entityInfo, MetadataHelper metadataHelper, Boolean shouldCreateOnlyFromReserve, ExecutionContext context)
I received the error too. Once I uploaded the full solution it goes away.
Does any of you got a warning message :
"Solution "ALM with Virtual Tables-VirtualTableDataSourse" imported successfully with warnings: Data Source secrets are not included in solutions. You'll need to edit your data sources to add secrets back following solution import."
after a managed package with Virtual Table Data Source and Connection Reference imported ?
Genius! Thank you!
Now, explain why the solution import will create everything but the virtual table data source? Think it's a bug?
do not include the Virtual table in the smaller solution, just the Virtual Table Data Source and the Connection Reference
No. Same error as on the larger solution. This small test solution (with just one virtual table) is the error message I pasted above. If I remove virtual tables, it's fine. And I can create the same virtual tables in the target environment without issue. So I know it's not a permission issue. For time's sake, I wish I could just recreate the virtual tables in the target environment, remove them from my solution in source, and import the rest of the solution. But that didn't work either.
and this solution importing ok to the target environment?
One is there, but I can't see a name or GUID. But in the table properties, I see the data source and that data source is added to the solution:
customizations.xml
click on 'dependencies' on your virtual table, and click on the 'required object' tab... verify that the Virtual Entity Data Source listed there is in the new/temporary solution you created
I only see one VTD source in the solution.
mmbr1606
22
Super User 2025 Season 1
stampcoin
19
Michael E. Gernaey
15
Super User 2025 Season 1