Submitted on01-18-201912:17 AMSubmitted byAnonymouson01-18-201912:17 AM
Hi fellow Flow enthusiasts, TL;DR: Make error-codes from the Terminate-action visible in the run history of Flow. Please UPVOTE this idea if you find it useful und would like to see this in the future. Additional improvements can be stated in the comment section We all have been there. You have X amount of flow runs, all succeeded but only 1 of them is the Flow which you are searching for. With the "Terminate"-action we finally can manually let the unimportant Flows fail or cancel instead of marking the exceptions as succeded. This is already a step in the right direction. Also they give u the opportunity to set custom error-codes and messages if we let the flow fail manually. If this error-code (and possibly even the message) would be dislayed and it could be filtered upon that property this would make troubleshooting flows way easier. There could possibly also a code be used in the cancelled runs.
... View more
Submitted on07-19-201701:47 AMSubmitted byLohiton07-19-201701:47 AM
Hi, I am working on a flow and the i have the below steps to work on Step1:- Using Get-Rows sql action to pull all the data Step2:- Using the apply to each action then compose to take out the specific column and to send it to kusto to check for update. Step2(a):- Using update sql action to update all the values but i am unable to go ahead to do an update as it is showing me an error as an output is an array and hence a foreach loop cannot be nested inside another foreach loop Can you please implement the nested loops functionality in Flow for the sql actions Thanks in Advance Regards Lohit
... View more