Look behind an action with Code View
Quiz question
What is an action's Code View good for?
Solution
- A) Editing the action directly in JSONWrong. Code View is read-only. You make changes in the designer or in the expression editor.
- B) Exporting the whole flow as a fileWrong. Code View shows only that one action. It has nothing to do with exporting the flow.
- C) Reading an action's expressions in fullCorrect. Code View shows the action's definition with all expressions, exactly as the flow runs them.
What it is about
In the designer you see fields, icons and dynamic content. What the action really runs is in its definition. From the action's menu with the three dots you open Code View, formerly Peek code. It shows the action as JSON, with all inputs and the complete expressions. You see, for example, that a harmless-looking field hides a nested concat() expression. That helps with debugging and with learning: you see how someone else solved a step and reuse the expression in your own flow. Code View is read-only. You still change the action in the designer.
When to use it, when not
Use it
When a field returns something other than expected and you want to see which expression is really behind it.
Better not
When you want to change something. You do that in the designer, Code View is read-only.
Most common mistake
Checking only the visible field in the designer. Only Code View shows the complete expression with all its functions.
License
Standard Runs without a premium connector, so the license from Microsoft 365 is enough. Source on Microsoft Learn: Power Automate licensing FAQ. For your whole flow: License check.
Share
Short link: powerautomate.ninja/en/89
Source: PowerPlatformTip #89, Microsoft Learn: Explore the cloud flows designer.