Unanswered

Azure SQL virtual table and ALM

(0) Share

Report

Posted on by tomsaudrins

We have created an application based on an Azure SQL as a data storage, and virtualized it (Dataverse Virtual Tables), and it works great. When moving the solution (manual, as we needed to set up the connection), we are able to create the SQL connection and access the data, but can not define new server/database to connect to, as we would like to match our environment strategy in SQL (Dev -> Dev, UAT -> UAT, Prod -> Prod).

So far based on the preliminary research it seems that I might need to modify the virtual data source dataset value on UAT and Prod, but that does not seem like a proper practice, so I wanted to see if one of you have had experience with this. Thank you in advance!

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (7)

Answers (1)

Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@tomsaudrins

I haven't been deeply into this but I would say you need to configure the connection on each server and then you would need to add the virtual data source as a solution component ,while moving your solution you need to bind your connection reference to your connection.Hope this gives you an idea!

Was this reply helpful? Yes No
tomsaudrins 74 on at

Like (0)

Report

Thanks for the reply.

Could you please clarify the "configure the connection on each server" part?
The solution currently already contains a connection reference and the virtual data source (generated automatically with the new/preview experience).

When moving the solution, a new connection is created and linked to the connection reference, and that works great, but that still does not resolve the issue of pointing it to the corresponding UAT server/db. As far as I can see, that is defined on the virtual data source itself, where the connection reference is referred to, together with the server and DB name.

It might be also possible that I had misunderstood your reply 🙂

Was this reply helpful? Yes No
Verified answer

tomsaudrins 74 on at

Like (1)

Report

Update: Will extract the Data Source to a separate solution, remove it from our pipeline and overwrite the value in UAT and Prod, as dataset value after changing is pointing to the correct server/db 🙂

Was this reply helpful? Yes No
Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@tomsaudrins

That's sounds great

Was this reply helpful? Yes No
devothunder 23 on at

Like (0)

Report

Hi @tomsaudrins, could you elaborate a bit more on your solution? I'm trying to do exactly what you mentioned in your original post but I don't quite follow your solution path.

Was this reply helpful? Yes No
devothunder 23 on at

Like (0)

Report

Oh, I see! Nevermind @tomsaudrins.

I have to switch to the classic view and look at the virtual entity data sources. From there I can see the connection reference and the dataset value pointing to the server and database. I'll just switch it from there. Thank you for pointing me in the right direction. I'll break it out into its own solution as well 🙂

Was this reply helpful? Yes No
tomsaudrins 74 on at

Like (1)

Report

No worries, glad it works for you. But yes, ended up with virtual entity data source as a separate solution that I just imported and never touched it again. 😊

Was this reply helpful? Yes No