Unanswered

SQL data source environment variable - What released version ?

(1) Share

Report

Posted on by FredericForest

303

Does anyone know what release version is necessairy to use the newly announced generally available SQL Server Data Source?

At the moment, when I use a SQL data source variable, the doesn't seem to be a link established between the app and the variable (no dependencies shown) and when I import it, it doesn't update the connexion with the value in the variable. I'm hoping I simply didn't recieve the update yet... rather than a broken GA.

I was so excited about this feature... ^^

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (2)

Answers (0)

iAm_ManCat 18,228 Most Valuable Professional on at

Like (0)

Report

Hi!

Might be a silly question, but are you editing an App that is within a solution?

If you try add SQl in app that's not in solution:

If you try add SQL in app that's within solution:

Select Advanced and then choose the environment variable:

Cheers,

Sancho

Was this reply helpful? Yes No
FredericForest 303 on at

Like (0)

Report

Hey Sancho,

Thanks for the reply. Yeah, everything is in solution. It's actually all backed by custom devops pipelines. But even manual import/exports don't work at the moment, so I know the problem isn't there.

I'll try to give a bit more details (I spent the best part of the day working on that yesterday).

In my dev environnement, I'm able to create the variables (server and DB). The UI is a bit clunky as it kicks the connection everytime you open the form (you have to manually reset it), but it actually works fine in the app.

In the app, I'm able to use advanced tab as you've shown and connect to the dev DB. So far, so good. <3

Things start to look a bit fishy you check the dependencies. The DB variable is clearly dependant on the Server variable. But the app itself has no dependency whatsoever. Furthermore, when you unpack the project, you can see under canvs/src/<appname>/connections that the connection.json has hardcoded information in it rather than pointers to the variables. The plot thickens...

Finally, when I export/import the solution (after publishing all customisations of course), I get a prompt for the server variable but not the DB one, and the app itself doesn't take into account what was set in the server variable.

:'(

I'm very much hoping that either there's something I haven't understood about the feature, or that the feature just isn't deployed in my region (Europe) yet.

Was this reply helpful? Yes No