Environment variables - separate solution?!

(0) Share

Report

Posted on by LimeLeaf

278

Hi community,

currently I got some use cases - Apps and Flows where environments variables might be handy.
E.g. SAP System parameters for DEV and PROD or even multiple E-Mail Adresses of a group of people for approval flows.

At first I was thinking of creating the environment variables in the solution where I consume them. But somehow I feel like these can get messy over time. You will end up with multiple solutions that contain multiple environment variables which are consumed by multiple other solutions.

So I was thinking of creating a centralized solution to just manage environment variables, this way you have a central storage location for all of them and the mess would be at least reduced.

What are your thoughts on this? How do you manage environment variables?

Cheers

Categories:

Application Lifecycle Management (ALM)

All responses (1)

Answers (0)

LimeLeaf 278 on at

Like (0)

Report

Re: Environment variables - separate solution?!

From my point of view the answer is: It depends on what you want to do and how your environment landscape lookslike.

Mike Bodell@ Bulb Digital made a great Video series on You Tube regarding environment variables:
Everything You Need To Know About Environment Variables in the Power Platform - YouTube