writerpolt.blogg.se - Excel get file path

#EXCEL GET FILE PATH HOW TO#
#EXCEL GET FILE PATH ARCHIVE#

We have a “Response” action that can help us with this. Sending the information back is quite easy. All we need to do is to send it back from the Flow.

#EXCEL GET FILE PATH HOW TO#

I included in this template examples in how to get “Worksheets,” “Tables,” and “Rows” so that, in case you need any of them, you can adapt the template to get that information. Now we can do a call to Excel to obtain any information we want since the ID is a valid way to call right? The syntax is the one required by the API, so we’re just providing it and adding the path that we get from the trigger. So we’re making a “Get” request to SharePoint to get the information about a file that exists on a particular path. In this case, we have to go a little bit deeper, but it’s simple to understand: Actions like “Get Item“ for example, use the same API, but they are just abstracting the technical details.

With this action, we can access Sharepoint using the SharePoint’s API. You may be using Power Automate for a while and never had the need to use this action, but it can be quite handy when some of the pre-defined actions don’t cut it. Now we have to use the “Send an HTTP request to SharePoint” action. Here’s the definition in case you want to build it yourself: If you’re not familiar with how to call another Flow using an HTTP call, I have an article that explains this in detail. The trigger is the most straightforward part of the process. As I mentioned before, accessing an Excel file using an ID is perfectly valid, so let’s use that. Roughly what we’re doing is triggering the Flow with external parameters, fetching the Excel details, and using its ID to get the information. I’ve enclosed all the logic there and, once Microsoft fixes the issue, I need to replace that action with the future action, and that’s it. The solution can look a little bit complex, but I’ll guide you through each step of the process.įirst, since I use Excels all the time, I decided to build a separate Flow that takes care of this for me. I have another article that describes in detail how to call an HTTP triggered Power Automate in case you’re not familiar with that. Use it and use the following information as a reference.

#EXCEL GET FILE PATH ARCHIVE#

Note Before we go any further, I have a template that you can find in my Template Archive ready for you that you can upload and have all. It’s a limitation, and we have to deal with it. It’s a strange limitation since, if we use the same strategy to access any SharePoint file, we don’t have this issue, but I digress.

Use output from the SharePoint connector’s triggers/actions (file’s Id or Identifier property depending on which one is present for the particular Sharepoint’s action or trigger).

Use output from the OneDrive for Business connector’s triggers/actions (file’s Id or File identifier property depending on which one is present for the particular OneDrive for Business’s action or trigger). It isn’t stated directly in the official documentation, but there are only three ways to access the file (quoting from the documentation): The error itself doesn’t tell us much, but the issue is with the dynamic path since we’re using the same strategy, just building the path before using it.