Just use the “Get a row“ action, and we’re good to go: Let’s try to access the information in an Excel file. It occurs on OneDrive files as well as SharePoint, so I’ll use OneDrive to demonstrate the issue and the solution. The issue is that the exception is not clear at all, making people question if their Flows are correct or not. It works in other actions in Power Automate, so why not here? Well, there’s a limitation in Power Automation that doesn’t allow that. Download the template and have your problem fixed in 2 minutes. One of the questions I see a LOT is the Power Automate Forum are issues with accessing Excel files where you provide a dynamic path. Click to share on Telegram (Opens in new window).Click to share on Pinterest (Opens in new window).Click to share on Tumblr (Opens in new window).Click to share on WhatsApp (Opens in new window).Click to share on Reddit (Opens in new window).Click to share on Facebook (Opens in new window).Click to share on Pocket (Opens in new window).Click to share on Twitter (Opens in new window).
Click to share on LinkedIn (Opens in new window).Click to email a link to a friend (Opens in new window).
0 kommentar(er)
