cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
CP153319 Advocate IV
Advocate IV

Approval Flow - Tracked Properties

In the settings for "Start An Approval" is a field called "Tracked Properties". Can someone who knows please tell me what that field is for and how it works? Thank you.

 

 

Flow - Tracked Properties.jpg

2 REPLIES 2
Community Support
Community Support

Re: Approval Flow - Tracked Properties

Hi @CP153319,

 

I have seen a blog on Tracked properties, from the blog we now that we could use Tracked properties for:

  1. Hide things that we don’t want to show
  2. Tracking time between two actions – calculating the time difference between approvals can be useful

Please check more details at here:

http://johnliu.net/blog/2018/10/hiding-your-microsoft-flow-valuables-i-mean-variables-out-of-sight

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
juresti Responsive Resident
Responsive Resident

Re: Approval Flow - Tracked Properties

You can use tracked properties for just that. 

That means any property you can normally get the output of, you can track it.

It is really useful since you can access the tracked property anywhere regardless if steps fail or are skipped.

This would tell you something is wrong because it could be "empty" or if it ran ok it would have the data.

 

What is also great about it is that when you access it, you don't have to refer to each property of an action, you just type one line for that action and they are output all together in a JSON type group.

Expression to access the tracked properties: actions('nameaction')?['TrackedProperties']

 

It is like being able to set a lot of variables without cluttering your flow steps.

Then these can easily be used for debugging, calculating, etc...

There are a lot of things you can do with it depending on what you would like to do.

 

I use it to check the output status code in conjunction with other error checking to notify admin of flow run failures.

 

So if a flow fails the email will notify admin and send the status code result of each different connection in use.

These will be either 200 OK or 400s 500s, etc... which ever, we know 200 is OK. So it would help to find the error.

Due to our set up, our connections do require monitoring.

 

Sample screenshot of how I'm using it

 

1.PNG

2.PNG

 

 

Helpful resources

Announcements
firstImage

New Ranks and Rank Icons released on April 21!

The time has come: We are finally able to share more details on the brand-new ranks coming to the Power Automate Community!

firstImage

Now Live: Power Virtual Agents Community!

We are excited to announce the launch of Power Virtual Agents Community. Check it out now!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Community Summit North America

The top training and networking event across the globe for Microsoft Business Applications

Top Solution Authors
Top Kudoed Authors
Users online (9,582)