Solved: Re: ALM virtual connector provider

JacoDeRooij · ‎06-01-2022

Hi All,

I don't exactly know if this is the correct forum, but we use the virtual connector provider to use SQL data in Dataverse, and this works fine. the only thing we do not succeed in doing is to transfer these virtual tables to another environment. The documentation says the following
"Application lifecycle management (ALM) is supported for virtual tables created with the virtual connector provider. Virtual tables must be part of the managed solution together with the connection reference to distribute the solution. The solution may have other components, such as a model-driven app that uses virtual tables." Create virtual tables using virtual connectors (Microsoft Dataverse) - Power Apps | Microsoft Docs

However when I have a solution containing the virtual tables and the connection reference I get a message on import that a dependency of the virtual tables is missing, the 'Virtual Table Data Source'. If I add this 'Virtual Table Data Source' to the solution and try to import again it will import, but data will not appear. In the virtual table data source the connection reference cannot be found because the ID is different. Besides that if you select the right Connection reference you get the message

ErrorCode: 0x80040265
Message: Error authorizing the Virtual Connector Provider first-party app

Kind regards,

Jaco

EricRegnier · ‎06-10-2022

Hi @JacoDeRooij,

It should work fine exporting and importing the virtual table along with it's connection reference (conn ref) and Virtual Table Data Source in a unmanaged or managed solution. The only thing is you'll have to setup the connection (not the conn ref) in the target environment before or after solution import. Once the connection is established and the solution is imported, bind the conn ref to the connection. After that further solution imports should work seemlessly. Unfortunately it's that 1st time setup where you'll need to create the connection and associate to the conn ref. Hope this helps!

View solution in original post

rfarri2000 · ‎06-10-2022

I'm running into the same issue just trying to create a new virtual table.

EricRegnier · ‎06-10-2022

Hi @JacoDeRooij,

It should work fine exporting and importing the virtual table along with it's connection reference (conn ref) and Virtual Table Data Source in a unmanaged or managed solution. The only thing is you'll have to setup the connection (not the conn ref) in the target environment before or after solution import. Once the connection is established and the solution is imported, bind the conn ref to the connection. After that further solution imports should work seemlessly. Unfortunately it's that 1st time setup where you'll need to create the connection and associate to the conn ref. Hope this helps!

JacoDeRooij · ‎06-14-2022

Hi @EricRegnier,

Thank you for your reaction and objects to include.

I'm still running in to the following issue.

If a setup the solution as you mentioned with:

- Virtual table

- Connection Reference

- Virtual Table Data source

- Canvas app (a app that works shows the contents of the tables)

On import it will return the following

But the Virtual Connection Data Provider I haven't to include right?

Thanks in advance,

Kind regards,

Jaco

EricRegnier · ‎08-03-2022

Hi @JacoDeRooij, sorry for my late reply. Did you get this working after all? Correct, you don't have to include the Virtual Connection Data Provider since that should come out of the box with Database. You can install it here: https://appsource.microsoft.com/product/dynamics-365/mscrm.connector_provider if not already installed. More info here.
Hope this helps!