Unanswered

Get Folder Metadata using Path - String path not working

(0) Share

Report

Posted on by Community Power Pla...

Good day community,

I'm trying to check if a Folder exists in a SharePoint Document Library before creating a new one, since currently if it exists, the create folder simply replaces the existing folder.

Basically I try to "Get Folder Metadata using Path" by inserting the PATH from a VARIABLE to check, and if success then folder exists and if not then it doesn't.

The problem is it doesn't accept the folder path i am trying to pass from a variable

Attached a screenshot of the error, any help is appreciated

Error text:

InvalidTemplate. Unable to process template language expressions in action 'Get_folder_metadata_using_path' inputs at line '1' and column '2793': 'The template language expression 'json(decodeBase64(triggerOutputs().headers['X-MS-APIM-Tokens']))['$connections']['shared_sharepointonline_1']['connectionId']' cannot be evaluated because property 'shared_sharepointonline_1' doesn't exist, available properties are 'shared_sharepointonline'. Please see https://aka.ms/logicexpressions for usage details.'.

PATH ERROR.png

Categories:

Building flows

I have the same question (0)

All responses (9)

Answers (2)

Verified answer

v-bacao-msft on at

Like (1)

Report

Hi @Anonymous ,

Are you using the PowerApps button as the trigger?

If yes, after you edited the flow, you need to remove the flow from the specified app and re-add it again, then this error will be solved.

Please take a try and check if the issue still exists.

Best Regards,

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi @v-bacao-msft ,
I'm now using a manual trigger just to test the correct syntax to use with my "PATH" field
This is my actual path /CL DIGITIAL ARCHIVE/TEST123
I think there should be %2FCL%20DIGITAL%20ARCHIVE%2TEST123
Still, it doesn't work - It doesn't make any sense
Any advice going forward?

Was this reply helpful? Yes No
v-bacao-msft on at

Like (0)

Report

Hi @Anonymous ,

You could export this flow as .zip file and import it as new flow, after configuring the connection, this error should be solved.

https://flow.microsoft.com/en-us/blog/import-export-bap-packages/

Please take a try.

Best Regards,

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Apologies for my stubbornness @v-bacao-msft
Your suggestion worked, all set now 🙂
Thank you for your help

Was this reply helpful? Yes No
pauldj 150 on at

Like (0)

Report

I am having a similar issue with the "Get_folder_metadata_using_path" Action results in the error:

Folder not found
clientRequestId: 1d96e901-1f9a-47fb-bd3d-0f5a2e517388
serviceRequestId: 1d96e901-1f9a-47fb-bd3d-0f5a2e517388

The flow has worked for over 8 months or more in a live environment and suddenly stopped working.
Anyone have this issue and have a resolution for this?

Was this reply helpful? Yes No
DannyB72 on at

Like (0)

Report

Hi,
i have the same issue... flow worked without any problems for months and now suddenly for each flow-execution "folder not found"-error - the requested folder still exists in library.
Solution to this is highly welcome 🙂

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi @pauldj & @DannyB72 ,
did you try the earlier suggestion of recreating the flow - that fixed my issue back then and haven't been facing any issues recently (Not that I'm aware of - no one reported any errors yet)
Hope this helps

Was this reply helpful? Yes No
Verified answer

pauldj 150 on at

Like (2)

Report

Hi @Anonymous Yes, the Dynamic Content "Folder path" has been changed by Microsoft, I have an open Case with them now. The flow will not work as is - there is an issue with the ending slash "/" and the only fix right now is to remove it via a compose action. I added a post regarding the solution to my specific problem here
https://powerusers.microsoft.com/t5/General-Power-Automate/Re-Folder-Not-Found-404-error/m-p/1233253

Also I have this and other flows all working on lists in SharePoint, not in an app, so removing and re adding didn't make a difference, the connector is the issue suddenly adding a "/", maybe different within apps... but there seems to be a lot of users with this issue right now.

Was this reply helpful? Yes No
DannyB72 on at

Like (1)

Report

Hi pauldj,
i've updated the flow following your advice and it runs again - thank you 🙂

Was this reply helpful? Yes No