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 / SharePoint library met...
Power Automate
Unanswered

SharePoint library metadata...Solved?

(0) ShareShare
ReportReport
Posted on by 1,247 Super User 2024 Season 1

It's been a known issue that SharePoint library triggers lack the metadata fields, which is problematic. A workaround was to use the item created/modified trigger instead of the file created/modified trigger. When I've done this in the past, this technique gave me access to the metadata fields, but not the file fields, such as file name, path, etc. But this morning I set up a new flow, and using the item created trigger, I clearly have access to both the metadata and a rich set of file related fields, such as Name, Link to Item, and even Folder Path.

 

1. Any idea when these were added?

2. Are these fields available to all tenants at this point?

3. What blog/feed should I have been following to find out about this earlier?

4. And a more general question: does this solve this issue for you? Personally, the addition of these fields makes Flow quite a bit more usable for me, and removes the obstacles I had for a few Flows that I was working on, so thanks to the team for getting this in place! 

 

 

 

 

Categories:
I have the same question (0)
  • v-micsh-msft Profile Picture
    Microsoft Employee on at

    Hi @Mike2500,

     

    Is the workaround the following one?

    "Get Manager" For SharePoint Document Library Approvals

    By Community Manager

    Currently there is no new blog published for those newly added fields, but I think the Team is working on it.

    Mostly new features would be published through the following Blog:

    https://flow.microsoft.com/en-us/blog/

     

    Regards,

    Michael

  • Mike2500 Profile Picture
    1,247 Super User 2024 Season 1 on at

    The workaround was simply to use the item created/modified triggers instead of the file triggers. As noted, this didn't fully work, as the item triggers didn't have access to the file info, such as name and path. But again, this seems to be solved at this point, as the item triggers now do have access to those critical fields.

     

    It's a shame that documentation has been such a low priority for the team. MS is advertising that Flow should be preferred over SPD for new workflows, but I've found it extrememly difficult to build anything that isn't extremely simple, and keep running into issues where a little bit of documentation could have helped tremendously. 

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 711

#2
Vish WR Profile Picture

Vish WR 691

#3
Haque Profile Picture

Haque 525

Last 30 days Overall leaderboard