You’re offline. This is a read only version of the page.
313
I'm trying to understand Solutions, ALM and environment variables. Early days.
Like many, I'm sure, I have dozens of apps developed over the years in the Default environment, outside Solutions. Between them they have hundreds of connections to SQL Server on an Azure VM (not Azure managed SQL Server) and flows that call stored procedures for all the heavy lifting.
I can see the value of moving all this into Solutions, using environment variables, and improving ALM. I think I understand how to move an app from default environment into a Solution and thence into 'proper' environments. But does this also mean recreating every single connection to SQL in every app, and rewriting every flow, so as to use environment variables? That's a monumental task.
Most of the tutorials I've seen seem to be about Sharepoint or Dataverse data sources, not SQL. I can't quite grasp whether the environment variable concept operates at the connection level - the connection to a particular SQL database - or at the table level - the connection to an individual table or view within the database. The former might be just about tolerable, but the latter is really depressing. I don't want to start on weeks of work rewriting everything if either it's not necessary, or Microsoft is going to come along with a tool to automate this and spare the pain - if so, I'll wait!
Solutions are containers for virtually every kind of app and dataverse customization you can make in power platform. Adding your app is just the beginning.
Your custom connectors can also be added to a solution, your flows can be added to a solution, and yes, environment variables can be added to a solution. To move your app with all is dependencies, you need to add the app and it's dependences to your solution.
Share
Report
All responses (
Answers (
