So, turns out I’m glad I decided to do this topic as my foray back into tech blogging cause it reminded me to always finish the article before assuming I understand the concept.
(This admission of guilt was brought to you by our new sponsor! Crow – Eating it will make you humble!)
My assumption was that environment variables would function similarly to other dynamic content that was available to both connectors/actions alike. However, that’s not the case and I owe you, fellow readers, a follow up to the previous post that explains the where my assumption was incorrect.
(This is where anyone else who finished the entire article and actually read the example can post a comment that simply says “CAW CAW CAWWWW!!!”)
Essentially, instead of a piece of dynamic content that can be inserted into a Flow as an action/trigger, Microsoft has created another configuration entity for us to add default values to. So what you’re seeing in the gif is what the article says needs to be in place for the environment varible to function as intended.
Phew. That’s a mouthful.
In other words, if my understanding is correct, for the time being we’ll have to add that entire section to each Flow in which we want to use our environment variable(s) until they improve the feature which they mention will happen sometime in the future.
So, the practial use of Environment Variables comes down to this important question: are they really worth the initial set up or should I simply bite the bullet and make the changes each time I push a new build?
The answer, of course, depends. One of the current projects I’m involved with could definitely have used the initial effort of getting these right since we have many, many places to try and update our Portal subdomains each time we move a solution from one environment to the next. On the other hand? I doubt I’d take the time to set these up for every flow that could use them if the project only requires a few to be created. At least, for the time being until they update the feature like I mentioned previously.
Thoughts? What scenarios can you imagine yourself using them in? Would love to hear ’em for my own benefit as well as those who may have stumbled upon this thread.
Also, after following the steps outlined in the article from yesterday, I’ve encountered the following error that I’m not sure how to solve:
It’s saying there’s not a property called “environmentvariabledefinitionid” on the output but, if you can see in the gif, it’s literally right there…sooooo…looks like I’m gonna be digging into this for a bit and I’ll let you know the findings in part 3 tomorrow!
I’ve been challenged. And, as anyone who knows me understands, that challenge cannot go unanswered! 🙂
My friend and colleague Mohsin Khalid and I have decided to focus a more concerted effort in giving back to the community who has given us so much. So, it’s with verylittle fanfare that I announce this is where I will be blogging, posting original video tutorials and creating a weekly podcast, hosted by the two of us, in which we explore Microsoft’s Power Platform from both a functional (mine) and technical (Mohsin’s) perspective.
The challenge is to not let this lapse for a year at the least, do 2 posts a week, answer as many Power Platform Community questions as I can (links to the individual community websites below) and record the weekly podcast. It’s…a lot, to be sure. Not to mention that whole pesky full time job, quarantine, home schooling and the other various creative projects I have in myriad states of completeness. So, I’ll need all the encouragement I can get! Please comment, subscribe, follow, bookmark, etc. if you’re at all interested in this stuff cause I can promise you that you’ll find something interesting here…eventually…maybe…actually, nevermind. I can’t make that promise lol. HOWEVER, I’m sure gonna give it that good ‘ole college try.
(Photo Credit: Dick Clark – Neowise in my backyard)