Answered

Dataverse Solution deploy - SQL Connection issue

(0) Share

Report

Posted on by dignus93reply

Hello there!

I have a test environment in dataverse called TEST-ICC.
In this place I login with my test user test-user-icc@outlook.com.

I create an unmanaged solution called ICC-SOL.

I create some virtual table that read a sql db called SQL-TEST-ICC (that stay in a test server called SQL-TEST-ICC-SERVER).
In this environment I also create a ModelDriven app that use the virtual tables.

Now I want to deploy in PROD.

There I have an environment called PROD-ICC.
I also have a sql prod db called SQL-PROD-ICC (that stay in a test server called SQL-PROD-ICC-SERVER).

I will use a user prod-user-icc@outlook.com.

I successfully deploy the solution ICC-SOL as managed.

When I deploy the solution I choose to create the sql connection reference with the prod user prod-user-icc@outlook.com.
Of course now my virtual table are pointing to the sql db SQL-TEST-ICC.

Is there a way to edit the connection reference in a managed solution, so I can read a different sql server and db?
Do you have any suggestion?
Regards,
dignus

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (1)

PowerThomas 277 on at

Like (0)

Report
Copy link

Link copied!

@dignus93reply Go to Solutions -> find "Default Solution" -> Find your connection reference and edit it's properties from here.

Was this reply helpful? Yes No
Verified answer

dignus93reply 87 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the reply @PowerThomas !

You can change some property in the default solution but it's not what I need.
As you can see from the screenshot above, if you edit the connection reference in the Default Solution you can change the displayname and choose the connection.

If I try to go in the connection section and edit the relative connection i see this:
But I cannot edit the server and db name. Probably because the login is Azure AD Integrated

For now I close this thread because I recreate the solution from scratch, the virtual table and the model driven.
Maybe I am not using the virtual table in the correct way.
I will update this thread if I have a new workaraound.

Regards,
dignus

Was this reply helpful? Yes No