Today is a quick #FlowNinja post on a strange technique.
Hiding Microsoft Flow valuables I mean variables out of sight
Yes, a very ninja technique.
This is actually an article about how to use tracked properties in the current Flow. But of course that’s the boring side to this. The fun side is how we can attach properties, like having a utility property bag and store properties as we go along!
Start with three compose (I guess we only need two really)
The expression give us the trackedProperties dictionary off the first action
actions('vars')?['trackedProperties'] // vars is the name of the first Compose action
Toggle to the … settings for the first action - that’s where different tracked properties are defined. We can use expressions if prefixed with the “@…” syntax, or define literal strings or numbers or even nested JSON objects.
What could we use Tracked Properties for?
Well, hide things that we don’t want to show - like the back of an envelope.
Unfortunately, an action can’t reference itself, so we can’t hide secrets that the action itself needs on the back of itself.
Tracking time between two actions - calculating the time difference between approvals can be useful.
https://flowstudio.app can ‘see’ tracked property values in the detailed Flow Runs - but there are no UI to display this for now. One idea is to use this to surface data within the Flow run that can be observed at the Runs level - like the Trigger URL or List Item ID of the runs, and allowing sorting on them. Powerful ideas but difficult to build an UI for. Let me know if you are keen about how this works below.