I'm trying to determine if tracking the outputs of my select query is a way to speed up the amount of time it takes to run my flow.
My Outputs are pretty straight-forward but they differ depending on what my tracking attempts are:
My most common error is "TrackedPropertiesEvaluationFailed." when I try things that look like
"@triggerBody('value').'first_name'"
However, I did get an "Encountered internal server error." when I tried to do something like
"@parameters('value').email"
This is all being done in the context of an Apply to each.
Any help would be greatly appreciated.
Solved! Go to Solution.
Reading this article: http://johnliu.net/blog/2018/10/hiding-your-microsoft-flow-valuables-i-mean-variables-out-of-sight
there was this statement that says "Unfortunately, an auction can't reference itself"
I took that and decided to go in another direction, create variables outside the loop and just set them inside the loop within their own loop and thankfully that worked like a charm. The objective of making my flow run faster is sufficiently met, so I'm moving on to the next challenge.
Thanks @abm for your attention.
Hi @eued
Could you try using the below expression please?
triggerBody()?['first_name']
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogPower Automate Video TutorialsHi @eued
Thanks for your reply. Could you please post a screenshot of your flow?
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogPower Automate Video TutorialsHi @eued
Thanks for the screenshot. Your flow look ok to me. Yes you can call database queries from a loop. You did mentioned about some errors. So in which step exactly you are getting these? I am kind of lost here?
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogPower Automate Video TutorialsAdmittedly, I'm throwing spaghetti on the wall for some of this stuff. I thought it would be super straight forward with triggerBody() but, I was wrong.
I just ran a couple examples of the types of errors I've encountered.
Reading this article: http://johnliu.net/blog/2018/10/hiding-your-microsoft-flow-valuables-i-mean-variables-out-of-sight
there was this statement that says "Unfortunately, an auction can't reference itself"
I took that and decided to go in another direction, create variables outside the loop and just set them inside the loop within their own loop and thankfully that worked like a charm. The objective of making my flow run faster is sufficiently met, so I'm moving on to the next challenge.
Thanks @abm for your attention.
Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!
Power Platform release plan for the 2021 release wave 1 describes all new features releasing from April through September 2021.
User | Count |
---|---|
34 | |
16 | |
15 | |
12 | |
9 |
User | Count |
---|---|
37 | |
26 | |
17 | |
8 | |
7 |