web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Power Automate Desktop...
Power Automate
Answered

Power Automate Desktop SharePoint actions can't use Variables for Site Address and File identifier ("Cloud connector call failed with status code 'NotFound'.")

(0) ShareShare
ReportReport
Posted on by 29

Hello,

I'm building Desktop flows that interact with a SharePoint site. I've found that the "Site Address" and "File Identifier" input fields for SharePoint actions will only work if the text is directly typed into them (or selected via the picker experience in designer UI). I'd prefer to use text variables so that I can pass in a different values for a development instance versus the eventual production instance of SharePoint folders.

 

Anyone else experienced this? PAD and SharePoint connector documentation doesn't mention this as a limitation. I couldn't find anything else online or in this forum after some searching.

 

Works:

Kinset_0-1694459751914.png

 

Doesn't work:

Kinset_1-1694459762506.png

 

  • Verified answer
    Agnius Bartninkas Profile Picture
    Most Valuable Professional on at

    I've tested this with PAD version 2.35.159.23221 and it works perfectly fine both ways for me. It was a bit tricky to get the File Identifier to work, as it seems to not really work well with anything deeper in the structure than "Shared documents".

     

    In order for that to work, you need to use the special characters in the File Identifier - %2b for whitespaces and %252f for forward slashes.

     

    So, for example, in your case, you'll need %252fShared%2bDocuments%252fDevelopment%252fInputs

    Also, since PAD uses % as the variable notation, using the above will throw a syntax error, so you need to escape it by using %%. Try this: %%252fShared%%2bDocuments%%252fDevelopment%%252fInputs

     

    -------------------------------------------------------------------------
    If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.

    I also provide paid consultancy and development services using Power Automate. If you're interested, DM me and we can discuss it.

  • longnguyenegs Profile Picture
    7 on at

    I have the same issue. Follow @Agnius guide and it works. Thanks!

  • Kinste Profile Picture
    29 on at

    Thank you @Agnius. That worked. To keep things simple at the variable level by not requiring users to encode slashes and spaces, I added "Replace text" actions initially in the flow that do it.

  • Kinste Profile Picture
    29 on at

    Well, I don't know what's changed. Yesterday it worked with the encoded forward slashes and white spaces and today it stopped working until I removed the encoded versions. I am using the same Power Automate Desktop version: 2.35.159.23221, the same as Agnius was. 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Leaderboard > Power Automate

#1
Mohsin Ali Profile Picture

Mohsin Ali 426

#2
11manish Profile Picture

11manish 349 Super User 2026 Season 2

#3
M Bilal Khan Profile Picture

M Bilal Khan 308

Last 30 days Overall leaderboard