Resolving "File Not Found" Errors in Power Automate When Using Custom File Paths

Introduction

In my recent experience with Microsoft Power Automate, I encountered a frustrating "file not found" error. This occurred while trying to access files using custom values in the "Get file content using path" action. In this article, I'll share how I resolved this issue, which might help others facing similar challenges.

The Challenge My flow was set up to retrieve content from a SharePoint file, for which I was using the "Get file content using path" action. Despite double-checking the Site Address and File Path, I kept encountering a "file not found" error.

Troubleshooting Attempts

Initially, I revisited the file path and permissions, ensuring everything was correctly set up. I also experimented with different formats of the file path in the flow, but the error persisted.

The Breakthrough After some research and experimentation, I decided to switch tactics. Instead of the "Get file content using path" action, I used "Get files (properties only)" with custom values. Crucially, I added a filter query for the file name.

Applying the Filter The key was to use the correct internal name of the SharePoint column in the filter query. For example, I used FileLeafRef eq '111517​.pdf' as the filter. This minor yet significant change made all the difference.

Success and Results This adjustment was a success! The flow executed perfectly, retrieving the file content without the dreaded "file not found" error. It was a clear reminder of the importance of understanding the intricacies of SharePoint's column naming conventions.