Loading...

The magical option to refresh virtual table relationships in Dataverse

The magical option to refresh virtual table relationships in Dataverse

My goal in this blog post will be to provide you with steps that will help you to auto-refresh Virtual table relationships when changes are made to the Data entity relationships in Dynamics 365 FO.

Business scenario:

Consider the scenario where you have modified & developed several standard and custom data entities and defined the relationships required by the business.

As a result of the discussion with the business SME, it was discovered that Power Apps or Dynamics 365 CE require a few additional relationships between the data fields.

Lets deep dive and understand the steps

I have chosen **PurchPurchaseOrderHeaderV2Entity (**Public Collection Name: PurchaseOrderHeadersV2) as an example.

Assumption: PurchPurchaseOrderHeaderV2Entity is already enabled as a Virtual table in the Dataverse.

In some situations, it is not necessary to enable all data entities as virtual tables within the main entity relationship.

As part of my scenario, I have enabled two existing relationships between data entities.

Do you know? A relationship on a data entity is primarily used to automate lookups in Power Apps or Dynamics 365 CE. Isnt a cool low code option. 😎

Refer to my YouTube videos if you would like to learn more about virtual entities and Dynamics 365 Cross apps.

Cross Apps Learning

The standard data entity of PurchPurchaseOrderHeaderV2Entity has two relationships (DimensionDimensionSet & Project), and the view Dataverse shows the same relationship, as indicated in the snapshot below.

Based on the business scenario, I will add new relationships on Vendor Account Number and perform the steps to enable the same in Dataverse with a single button click.

1. Navigate to Visual Studio and head over to Solution and create an extension of OOB PurchPurchaseOrderHeaderV2Entity

2. Build the VS solution

3. Navigate to System Administration module -> select Data management workspace -> Framework parameters -> Entity settings tab -> Refresh entity list

4. Depending on your Tier-1 box configuration, step 3 may take longer to complete, please wait until it does

5. Navigate to the Advanced setting option in the maker portal of Power Apps (https://make.powerapps.com/)

6. Select the Advanced settings and lookup for the PurchPurchaseOrderHeaderV2Entity virtual table using advanced filter option

7. Select the magical "Refresh" option to restore Data entity relationships of PurchPurchaseOrderHeaderV2Entity in the Virtual table of Dataverse

8. Click on Save or Save & Close option

9. Navigate to the Power Apps maker portal and select your Dataverse environment

10. From the Left pane, select Dataverse and then Tables

11. To filter the virtual entities, choose "mserp" as the prefix and select All to show all virtual and physical tables

12. The selected Virtual tables were automatically created as part of the virtual table's "Visible" option. Please refer to the assumption section.

13. Navigate to the relationships schema to validate the newly created Data entity relationships

Conclusion

Developers and code reviewers can benefit greatly from even the simplest observations.

I hope this article was a good read for you. Do share it with your friends and other peers.

Thank you so much!

Thank you for Reading - Let's Connect!

Enjoy my blog? For more such awesome blog articles - follow, subscribe and let's connect on LinkedIn, Twitter, YouTube

Stay tuned!

Published on:

Learn more
Rakesh Darge's Blog
Rakesh Darge's Blog

Rakesh Darge's Blog

Share post:

Related posts

Microsoft 365 & Power Platform Call (Microsoft Speakers) – May 7th, 2024 – Screenshot Summary

Call Highlights Β  SharePoint Quicklinks: Primary PnP Website: https://aka.ms/m365pnp Documentation & Guidance SharePoint Dev Videos Issues...

1 hour ago

We need to talk about... Dynamics 365... Dataverse

In this blog post, the author sheds light on an important feature that appears in Microsoft's release waves update for 2024 - Dynamics 365 Dat...

6 hours ago

Fixed – The latitude or longitude for the User record associated with this resource is invalid – Dynamics 365 Field Service /Dataverse

If you're facing the error message "The latitude or longitude for the User record associated with this resource is invalid" while trying to se...

18 hours ago

Use uploaded documents for generative answers with Copilot Studio | Power Platform Shorts

Learn how to leverage the power of Copilot Studio to generate answers from uploaded documents in this latest video from the Power Platform "Wh...

1 day ago

Dataverse | Restore deleted table records (preview)

If you accidentally delete a table record in Dataverse, there is now a way to restore it with the new preview feature - Recycle bin. This opti...

1 day ago

Dataverse – Convert UTC Time to User Timezone in Plugin

In this post, you'll learn how to convert UTC time to the user's local timezone settings in the Plugin in Dataverse. The article covers the lo...

3 days ago

Restore delete records in Dataverse table – Quick Review

Have you or your team accidentally deleted important records in your Model Driven Apps? Don't worry, this blog post has got you covered. In th...

3 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy