Lesson learned during Dataverse integration: Namemapping = ‘Logical’ was not found in the MetadataCache.

Yesterday I was working on integrating a custom entity using the box connector for Dataverse in Microsoft Dynamics 365 Business Central. After completing all the changes and deploying the app to a sandbox environment, I tried to open the custom entity table through its list page. Unexpectedly I ran into below dialogue box.

The entity with a name = 'xxxxxxxxx' with namemapping = 'Logical' was not found in the MetadataCache. MeradataCacheDetails: ProviderType=Dynamic, StandardCache=True, IsLoadedInStagedContext = False, Timestamp=4684909, MinActiveRowVersion=4684909, MeradataInstanceID=42066757, LastUpdated=2021-09-01 01:13:43:839

After investigating this issue with another colleague we identified the root cause of the issue.

We identified that the “ExternalName” property of the CDS table in Business Central is causing the above-mentioned error. Even though I used the PS script to generate the CDS table schema, while saving it in AL, one of my scripts running in the background in VS Code has changed the “ExternalName” property value to a different value.

How the ExternalName was while trying to open the page
How the ExternalName should be

Once I set the original “ExternalName”, the error went away and we manage to successfully open the Dataverse entity in Business Central.

The lesson to learn is once you generate the CDS table schema through the Powershell script, never go and change any properties.

Thank you and Regards,
Tharanga Chandrasekara

Click on a star to rate it!

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?