Add Column to Run History Views for Custom Name/Key

[sressler]

It would be very helpful to be able to define a field or fields from the trigger action to be visible as a column or a part of the flow Run History tables. This would make finding a specific execution of a flow much simpler to find, especially for flows that may run frequently. An example would be the name of a Sharepoint list item that was created or the name of an opportunity that was created.

[YatinMumbai]

This is an absolutely essential feature. When you have so many runs in history, it is impossible to find the relevant one in case of troubleshooting or audit. Typically, it will be great if the SharePoint list link and ID is displayed as columns. SharePoint link or list name is important if you are reusing a Flo for multiple lists.

For example, I have a Flow that triggers when a file is created or modified (properties only). The actions need to be taken only when a certain column is modified (Closed is modified to "Yes").  I have a condition to check if the Closed column is changed to Yes then run actions, else terminate. What happens is that for several other modifications, this flow triggers. I am only interested to monitor the Flow for ID (Item No.) where Flow has run because Closed was modified to Yes. Across items there are several runs, typically 3 - 4 per item. Even if I can filter on a particular item no. or ID, it becomes easier to locate that Flow.

[ACC]

Please add

[Anonymous]

For the love of God please add this feature.

[sncueto]

Completelly agree, this feature is a must.

[kishbuy238]

@sressler  @YatinMumbai @ACC @sncueto  Hi! Troubleshooting flow runs with trigger output dynamic value is coming in 2022 Wave 1.Troubleshooting identifier column in the flow runs page - Power Platform Release Plan | Microsoft Do... With this feature, you are able to add a column to your Flow runs view and map it to a trigger output-the name of the SharePoint list that the flow triggered from. This means when the flow runs, the column gets populated dynamically with the SharePoint list item name that triggered the flow. 

[sncueto]

Really great news! Thank you!

[srduval]

@kishbuy238 will we be able to filter or sort by this new field? I have a flow that runs very frequently and if I need to go back and look at a run history, assuming it didn't fail, the current pagination of results takes a long time.  

[Dinesh]

@kishbuy238 I am already in 2022 Wave 1. But could not find this feature. Could you provide more details on how to add the identifier to the view?

[tp_ahaas]

Another no-brainer Microsoft, come on.

[srduval]

@kishbuy238  will we be able to filter or sort by this new field? I have a flow that runs very frequently and if I need to go back and look at a run history, assuming it didn't fail, the current pagination of results takes a long time.