How to manage virtual tables and solutions?

[ArneVlietinck]

Hi,

We have a solution with:

• 1 model-driven app
• 25+ Power Automate Flows
• 6 dataverse tables
• 9 connection references
• ....

This solution is available in following environments:

• DEV - unmanaged solution
• UAT - managed solution
• PRD - managed solution

We would like to add a virtual table to our model-driven app. However virtual tables come with their own solutions installed in the environment. We would like to know how to handle our own solution together with the virtual table. Can we include it in our own solution. We want to make sure our ALM process still works. Microsoft documentation points out it should work.

Our first tests were not successful it looks like we need to recreate the virtual table in the other environment, however since our custom solution is managed we cannot include the table in our app.

Please advice on how to handle this.

[Jondoesflow]

Hey

go to each of your environments in https://aka.ms/ppac and click on Dynamics 365 apps on the right hand side, and ensure this solution is installed in each of the target environments:

---------------------------------------------------------------------------


If I have helped you with an answer, please accept this post as a solution and thumbs up my reply. Thanks !

Blog - JonDoesFlow
Twitter - JonDoesFlow
YouTube - JonDoesFlow

[ArneVlietinck]

Hi, thanks for your message. I know a lot has changed in the meantime on Virtual Tables. My problem is more with making sure that the virtual table points to the right datasources. For example:

• DEV: point to SQL server 1
• UAT: point to SQL server 2
• PRD: point to SQL server 3

For other datasources you can use environment variables to manage this in many cases. But for virtual tables it isn't clear to me.

[Marcin_Roger]

I had a big headache with virtual tables recently  (Importing a Solution with Virtual Tables Fails ).

Long story short:

• You need to create a separate solution containing Virtual Table Data Source and the table's Connection Reference.
• You have to import this into the UAT/Prod ahead of Solution that contains the virtual table. 
• Make sure that Virtual Table Data Source and the table's Connection Reference had been removed from solution that contains Virtual Table. 
• During importing a solution containing Virtual Table Data Source and the table's Connection Reference, you will be prompted for a connection. This connection defines a data source for you virtual table.

Let me know if you need more information.