85 posts tagged with "Power Automate"

Power Automate's expression editor told me This expression has a problem. You can fix it manually or with Copilot. The expression was correct, and the same one worked elsewhere in the flow. Selecting Add again, sometimes two or three times, added it. Once, though, the message was right, and the reason is worth knowing.

I saved a cloud flow, and the action I had open in Power Automate's new designer suddenly showed No additional information is needed for this step, Not connected. and an empty Code view. It looked as if Save had wiped the action. It hadn't: selecting the action again brought everything back.

I created a cloud flow from inside one solution, and the flow's details page said it belonged to two. The second one was my preferred solution. Microsoft documents why, and the fix moved the flow to a single solution without deleting anything.

Sooner or later a flow needs to find a person — the manager to notify, the owner of a request, the account behind an email address. The Search for users (V2) action from the Office 365 Users connector does exactly that: give it part of a name or an email address and it returns every matching Microsoft 365 user.

Power Automate is strict about data types. If you try to concatenate a number into a message, save it into a text column, or pass it to a connector that expects text, the flow fails with a type mismatch. The fix is the built-in string() expression, which converts a number or integer into its text or string representation.