Forum Discussion
Change to Team's Channel "Email Messages" folder naming convention.
- Feb 05, 2021I'd definitely contact support first and complain about the change.
However, in the meantime, e-mails come into the folders as eml files, you should be able to just create a flow that triggers on files coming into the library regardless of folder then "Create a copy" into the e-mail folder so it triggers your existing flows, then deletes the file after. Moving might work depending on the trigger of existing flows, but I would look into something like that to just pick them up and move them for you in the meantime.
Can you please give a visual as to where you are placing this into your flow? Rehan Alibux
dcoulbourne Please see attached a moving files example. Our actual flow runs when a new item is added, but for testing manually triggering a flow here.
- Aurun ThirumeniFeb 15, 2021Copper Contributor
Rehan Alibux - I did try to use variable in our Logic app as suggested but then we are getting
"The resource you are looking for has been removed, had its name changed, or is temporarily unavailable" error. We are using "List Folder - SharePoint connector" in our Logic app.I checked in the Teams and the folder we are looking for is present. Any thoughts?- Rehan AlibuxFeb 16, 2021Copper Contributor
Aurun Thirumeni Are you able to output what the full path incorporating the variable is? Does this work if you hard code the path to the resource?
- Aurun ThirumeniFeb 16, 2021Copper Contributor
Rehan Alibux Apologies, I should have informed you. I have managed to fix the issue I was facing.
The reason for the failure was when I manually entered the path with slash (/) there was an encoding issue which returned as an invalid path. I had to replace slash (/) with '%2f' in my variable initialization which builds up my Folder path and flow started working ok.
Reference: https://powerusers.microsoft.com/t5/Building-Flows/sharepoint-list-folder-fail/m-p/585936#M77026