Unanswered

Excel sending empty "{}" rows into power automate

(0) Share

Report

Posted on by ACosta

Hello!

I have a flow that has the "for a specific row" trigger. This flow has worked fine in the past, but now for some reason, it broke. When I run the flow from my Excel file, instead of sending the row information, the displayed entity is an empty "{}". Has anyone seen this issue before? And how can I solve this? This has never happened before, and nothing has changed in neither the flow or the document.

Categories:

Using flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

creativeopinion

10,508 Moderator on at

Like (0)

Report

Copy link

Link copied!

@ACosta Can you show a screenshot of your flow? It would help to provide more insights.

In the meantime, you might find this YT Tutorial helpful:

5 Power Automate Troubleshooting FAQs and Helpful Tips for Creating Better Flows

IN THIS VIDEO:

✅ How to troubleshoot a false Condition action result

✅ How to get dynamic content when it isn’t selectable from the list of dynamic content

✅ How to troubleshoot an Apply to Each action that isn’t looping through

✅ How to troubleshoot a skipped Apply to Each action

✅ How to troubleshoot a Filter Query

✅ How to use a SharePoint yes/no column in a Filter Query

✅ How to use Compose actions to troubleshoot a Power Automate flow

✅ How to troubleshoot multiple emails being sent

✅ How to troubleshoot multiple Teams messages being sent

Hope this helps!

If I helped you solve your problem—please mark my post as a solution ✅.
Consider giving me a 👍 if you liked my response! If you're feeling generous— ☕️ Buy me a coffee: https://www.buymeacoffee.com/acreativeopinion

👉 Watch my tutorials on YouTube
👉 Tips and Tricks on TikTok

Was this reply helpful? Yes No

ACosta 31 on at

Like (0)

Report
Copy link

Link copied!

The video doesn't seem to cover my issue. Here are some screenshots of the flow, though there are some "Initialize Variable" that I did not include to the sake of brevity. Also, the second screenshot is nestes inside a "Switch" function.

Was this reply helpful? Yes No