Power Platform Community Forum Thread Details

We have been trying to decide on the best approach to use for variables or values that potentially could change after the script is live in our production environment. One thought was to use a config file spreadsheet, put all variables/values in one row under a descriptive header, then call the "get a row" action at the start of the flow. This way the variables are completely outside of PA and can be managed by devs or the end user. We also have used environment variables but realize this can get cumbersome should multiple values change throughout the life cycle of the automation. Managing the change would require an update in the dev, test and then production environments if that environment variable value is the same in all three.

I would be interested in hearing how others manage variables without relying on hard coding the values within the flows.

Thank you

Categories:

Building flows