Contents
Please note the workaround I originally described is only valid when you create the Flow from the Sharepoint Document Library and invoke it manually from there. In such circumstances, the trigger includes both the List Name, the Item ID and the FileName. So, we get item related info, and also file related info.
Why are metadata changes not applied to list items?
I update a term and hit up and the changes are not reflected on a content type (wiki page) where I am using that meta data item. After making the term item update (changing text) and navigating back to the wiki page I inspect the properties and the value is not showing the updated value.
In the meanwhile, I followed @JRitmeijer recommendations at https://powerusers.microsoft.com/t5/Flow-Ideas/SharePoint-File-triggers-need-to-return-numerical-ID/… to implement a temporary workaround to update custom columns: The workaround if based on the fact you can create Flows from a SP Library, as explained here:
Where do I find the SharePoint document list?
This list is located in the same subsite as the folder. The sharepoint list contains additional information (number, Boolean, text) for each of the documents contained in the document folder. The sharepoint list contains a column with the file name of the document, therefore each record in the list is associated with a unique document.
How to update document meta data using PowerShell?
I’m iterating through all files of a document library using powershell trying to update some files in some folders. I can read the file properties but I’m not able to update them.
What happens when metadata is added to a document?
Once the metadata is added to the documents folder, the seperate list no longer serves a purpose and can be deleted. I’m new to flow, and I’m pulling my hair out a bit at this, in part i have been relying on dynamic content but this does not appear to be available for all triggers.
Can you manipulate custom metadata in Microsoft Flow?
As far as I know, you currently cannot manipulate Document Library custom metadata unless you get List related info. Let’s hope Microsoft Flow team will fix such limitations, in the meanwhile and since it looks like you need to have the whole process executed automatically without manual intervention, I would suggest you a different approach: