Forum Discussion
Change to Team's Channel "Email Messages" folder naming convention.
- I'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.
Ellya_Gold Spoke with MS Support and they advised this change was made by the product team for performance reasons. Going forward the folder naming convention will be be EmailMessages_month_year.
We have multiple Power Automate flows impacted by this change and one work-around is to use a variable and expression to get the correct folder name for each month. For example:
concat('EmailMessages_',replace(utcNow('MM'),'0',''),'_',utcNow('yyyy'))
Though we do have to update all the flows to add this, I think we should be set going forward.
Hi Rehan Alibux, thanks for your suggestion. Will it work in October (10)?
I was thinking about an option : create a scheduled flow that rename the previous folder (e.g EmailMessages_2_2021) to the new name (e.g. EmailMessages_3_2021) so that I only keep one folder and it is created before the first email is sent so I can update my triggers.Does someone know how to do that?
Thanks!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.
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?
- They should have at least put the folder inside the e-mail messages folder, not a bunch of folders in the channel root.....ugh.
ChrisWebbTech exactly this!
In my case, I'm syncing the entire folder structure to a local PC and, instead of using Graph, I'm parsing the emails with Python. If the new folder was nested in the existing one, it would have been a fairly trivial change to crawl the tree.
This has been handled badly. I can find no reference to any performance related issues in folders that, iin my circumstances, barely hold 1,000 messages let alone the massive volumes that Sharepoint purportedly allow!
ChrisWebbTech Perhaps an idea for the next round of performance enhancements!
