Finance | Project Operations, Human Resources, ...

Virtual Entity error preventing a solution import to Dataverse (CE)

(2) Share

Report

Posted on by Sophs@4Sight

We are trying to import a solution into Dataverse for CE. However it keeps failing with the following error. "Failure to sync entity metadata for entity "VRMVENDORENTITY". Exception details:Could not find an entity with specified entity logicalname: msdyn_globalvendor.

No entity exists in Dataverse called msdyn_globalvendor.

I have found the following Virtual Entity in Dynamics 365 FnO VRMVENDORENTITY with the following failure message.

Could not find an entity with specified entity logicalname: msdyn_globalvendor\r\nTimeStamp: 2025-08-13T11:11:14.5545206Z\r\n--\r\nException details: \r\nErrorCode: 0x80048D0B\r\nMessage: Could not find an entity with specified entity logicalname: msdyn_globalvendor\r\nTimeStamp: 2025-08-13T11:11:14.5545206Z\r\n--\r\n)."

I also found the virtual entity in Dataverse VRMVENDORENTITY under the Available finance and operations entities

How do I solve this error. I can not delete the Virtual entity.

On further investigation I have found on FnO Virtual entity metadata sync status another Failure message on VRMCONTACTPERSONENTITY. With the failure message Entity Key 'msdyn_contactpartykey' of referenced entity 'contact' of relationship 'mserp_FK_VRMContactPersonEntity_ContactRel' does not exist.\r\nTimeStamp: 2025-09-04T02:29:45.9006584Z\r\n--\r\nException details: \r\nErrorCode: 0x80048D0B\r\nMessage: Entity Key 'msdyn_contactpartykey' of referenced entity 'contact' of relationship 'mserp_FK_VRMContactPersonEntity_ContactRel' does not exist.\r\nTimeStamp: 2025-09-04T02:29:45.9006584Z\r\n--\r\n)."

How do I solve this.

Any assistance will be greatly appreciated

Categories:

Dynamics 365 Finance

All responses (9)

Answers (0)

Sohaib Cheema on at

Like (0)

Report

Virtual Entity error preventing a solution import to Dataverse (CE)

Have you enabled this entity as Virtual Entity? If not, enable it first as a virtual entity and then retry importing your solution in the CE/Dataverse.
Suggested answer

Sagar121 on at

Like (1)

Report

Virtual Entity error preventing a solution import to Dataverse (CE)

Hi,

If you don't need this entity then exclude this object from solution and try import again & if this is needed then you a re-build of this entity from CE.
Suggested answer

André Arnaud de Cal... on at

Like (0)

Report

Virtual Entity error preventing a solution import to Dataverse (CE)

Hi Sophs,

The VRM elements do belong to a new module which is currently in private preview. In case someone created a solution based on the latest version of Dynamics 365 while you are importing it in an older environment where the VRM elements are not present, you will get the errors as encountered. Either the solution needs to be created from a lower base version or it should be deployed to the same versions (or higher) from which the solution was created.
Sophs@4Sight on at

Like (0)

Report

Virtual Entity error preventing a solution import to Dataverse (CE)

Thank you all for your replies however it is still not solved. Here my responses to your advice

@Andre : The old dataverse version 9.2.25082.158 the new version is 9.2.25083.168. In both these versions we can see the VRMVENDORENTITY virtual entity but we can not find the msdyn_globalvendor. Do you know what the name is of the new module, that is in Preview. Or where can we see to which table does the virtual entity relate.

@Sagar121 We have tried to find where in the solution this is being referenced but can not find it. Note there are a number of apps enabled but can not find the table msdyn_globalvendor anywhere in the old environment or in the new environment.

@Soihab We initially had the virtual entity VRMVENDORENTITY enabled and then disabled it and tried again. Still find the same error.
André Arnaud de Cal... on at

Like (0)

Report

Virtual Entity error preventing a solution import to Dataverse (CE)

The prefix triggered me about the new module. VRM stands for Vendor Relationship Management.

The msdyn_globalvendor is a Dataverse table. That means that your environment does not have this solution. Probably the environment where the solution was initiated from does have it.
Sophs@4Sight on at

Like (0)

Report

Virtual Entity error preventing a solution import to Dataverse (CE)

Thank you for your responses. I have found the VRMVENDORENTITY  virtual entity in F&O and in Dataverse.

But can not find the msdyn_globalvendor  in dataverse. Where in Dataverse would this link between the virtual entity and the table be set up or how should I go about finding it, where this VRMVENDORENTITY  references the msdyn_globalvendor.

In F&O VRMVendorEntity is linked to a config key for Vendor Portal. Will it make a difference in the CE solution if I disable this Config key. I was thinking maybe it will then exclude the virtual entity from dataverse (Available F&O entities)?

We tried enabling the VRMVendorEntity in the source solution by making it visible but get error.

Error Logs from CE.

Exception Message: This operation failed because we couldn't connect to the server. Please try again later.

ErrorCode: -2146881533
HexErrorCode: 0x80093003
Call Stack: Error: request failed with timeout
    at v._logErrorAndRejectPromise (https://content.powerapps.com/resource/uci-infra-web/scripts/44.90ab9b65f93d3c1231ebc678236e5600.js:4:473220)
    at https://content.powerapps.com/resource/uci-infra-web/scripts/44.90ab9b65f93d3c1231ebc678236e5600.js:4:473038

Activity Id: f6ae15b7-d9a6-451f-8967-620043d9cf74
Exception Message: PluginSqlLockManager failed to acquire lock

ErrorCode: -2147187695
HexErrorCode: 0x80048411

ErrorDetails:
            ApiExceptionSourceKey: Plugin/Microsoft.Dynamics.FOVirtualEntityGeneration.Plugins.GenerateVirtualEntityPlugin
            ApiStepKey: 03171a39-aa4d-401e-ad73-637a5408b32d
            ApiDepthKey: 1
            ApiActivityIdKey: 3852a1a0-3ba0-44b3-ade8-1cc806b3f4c5
            ApiPluginSolutionNameKey: MicrosoftOperationsVESupport
            ApiStepSolutionNameKey: MicrosoftOperationsVESupport
            ApiExceptionCategory: ClientError
            ApiExceptionMessageName: FailedToAquireLock
            ApiExceptionHttpStatusCode: 400
HelpLink: http://go.microsoft.com/fwlink/?LinkID=398563&error=Microsoft.Crm.CrmException%3a80048411&client=platform
TraceText: [Microsoft.Dynamics.FOVirtualEntityGeneration.Plugins: Microsoft.Dynamics.FOVirtualEntityGeneration.Plugins.GenerateVirtualEntityPlugin] [03171a39-aa4d-401e-ad73-637a5408b32d: Microsoft.Dynamics.FOVirtualEntityGeneration.Plugins.GenerateVirtualEntityPlugin: Update of mserp_financeandoperationsentity]

Activity Id: 9a34ee35-0f99-49da-a269-00e0e742922d

Kind regards
Sohaib Cheema on at

Like (1)

Report

Virtual Entity error preventing a solution import to Dataverse (CE)

Hi,

msdyn_ tables com from Microsoft (usually) with installation of standard/managed solutions.

I cannot find this msdyn_globalvendor in any of my preview environments.

it appears you would need t get in touch with Microsoft to be part of preview program (Supplier Engagement) or ask Microsoft to make this entity available for you by somehow.

Also it appears flight for this feature is enabled in one of your environments and not in other enevironments.
Sohaib Cheema on at

Like (0)

Report

Virtual Entity error preventing a solution import to Dataverse (CE)

Some further digging of code and online docs, shows that it is this feature named Supplier Engagement, that has it's own Model Driven Power Apps, to which this table belongs: https://learn.microsoft.com/en-us/dynamics365/release-plan/2025wave2/enterprise-resource-planning/dynamics365-supply-chain-management/manage-supplier-relationships-improve-collaboration
Suggested answer

BJ-06102300-0 on at

Like (1)

Report

Virtual Entity error preventing a solution import to Dataverse (CE)

Hopefully this issue isn't still affecting you Sophia, but I've just experienced this same issue for the second time and raised a ticket to Microsoft.

They have advised that it is a known issue and a fix has been made available via FO update. Further info: Details for issue 1044527