Skip to main content

Make your flows configurable using environment variables

Environment variables

Flows often require different configuration across your environments and this is where environment variables come handy. Environment variables allow you to store different configuration variables in each of your environments or to fallback to a default value.

I just recently used them to define the "sender" (name of a queue) of a notification e-mail in a flow.

Define environment variables

You can add a new environment variable via the new maker studio (make.powerapps.com), by opening one of your solutions and click on New -> Environment variable:



After having defined your default and environment specific value it should look like that:


Using environment variables in a flow

To retrieve the value of an environment variable, we add a list records action, where we search for the environment variable by schema name and expand the query with the environment specific value (stored in a linked entity):



Finally we initialize a variable, where we either set the default value (if no environment specific value is set) or the environment specific value via following formula:

if(
empty(body('List_records')?['value']?[0]?['environmentvariabledefinition_environmentvariablevalue']?[0]?['value']),
body('List_records')?['value']?[0]?.defaultvalue,
body('List_records')?['value']?[0]?['environmentvariabledefinition_environmentvariablevalue']?[0]?['value']
)

Result

If we test our flow, this is our result:

We can now use this variable, to fetch the queue with this name to reference it as a sender for our notification.

Comments

Popular posts from this blog

Power Automate Get absolute Sharepoint URL from document location

Document Locations If you enable Sharepoint document integration in your model driven apps, you can define for which entities the possibility to upload documents to sharepoint shall be offered and you can define a folder structure. Possible folder structures can either be based on account or contact, which means if you create child items (e.g. opportunities, activities, ...) sub folders are created below. If an entity is enabled for document management a "Files" tab is added to the form of your model driven app and as soon as you click on that tab a folder is automatically generated on Sharepoint. Once the folder has been created you have options to create new or upload existing file or to open the document location (folder) on Sharepoint: What happens behind the scenes is, as soon as you click on the files tab your model driven app checks, weither a "document location" for this item already exists, or not. The document location is an own entity in C

Send e-mails with a link to the record via Power Automate

Today we gonna have a look at how to send an e-mail with a link to a CDS record via Power Automate. In the good old classic workflows, you could directly reference the "record URL" from the dynamic data. But since UCI has been launched and you have the possiblity to target different apps, you already had to do a few more steps in the classic workflows as well. The URL to a CDS record consists of multiple things: CRM URL appid entity name record id So we will work this out one after the other. First we add a "List record" action to lookup the appid of the app, we target. We look for "model driven apps" and filter by the name of the app: Then we initialize a variable with the resulting app id: Then we initialize another variable and extract the CRM_URL: Then we fetch our records, where we want to send out a notification with a link, in this case we look for workorders fullfilling certain criteria: Now we compose the record URL: As a next step we create a new

Working with Optionset lables in Power Automate

Connector Types Power Automate currently offers 3 different connectors, to connect Power Automate with your Dynamics 365 instance: Dynamics 365 Common Data Service Common Data Service (current environment) Today we will look on ways how to retrieve option set labels via the different connectors, for our sample accounts: Dynamics 365 This connector should not be used any more , since in April 2019 it has been announced as being deprecated. https://flow.microsoft.com/en-us/blog/nine-new-connectors-in-april-and-improved-visibility-into-trigger-failures/ With the Dynamics 365 connector it was quite easy to work with optionsets, since it offered both the optionset value (int) and the optionset label (name) in the dynamic content: And here we go, these are our results: Common Data Service Since the Dynamics 365 connector has been deprecated, this is the connector you should use. If you perform a "Get record" or "List records&