Showing results for 
Search instead for 
Did you mean: 

SharePoint Files - all fields not just a few

When working with the Flow SharePoint File connector (On File Create), I notice it is very limited as to the "fields" available.


In SharePoint, we often create new metadata fields for our libraries - like Customer, Value, Assigned To, and so on.


I tried making a Flow such that as a Salesman adds a new Proposal to SharePoint (Word doc format), it would create a Microsoft CRM Opportunity to track it.  However, not enough data is available from the SharePoint file metadata to add to the Opportunity.


Specifically, SharePoint files have Created Date/By, Modified Date/By, but these aren't available in Flow.  In additon, we have added Customer (text field) and Quoted Value (Number field) to the document library in order to capture the meta-data and show it in the SharePoint view.  I want to add these to the Opportunity.


The SharePoint List connector grabs all the fields/meta-data - the Files connector does not.

Status: Completed

Hello - this feature is now available. You can read more about it here:

Advocate I

When building SharePoint workflows with SharePoint designer, you are able to easily select from multiple options when inserting date/people fields - for instance short date/long date, or email address vs display name for "people" columns. It would be great if you could do the same in MS Flow. It pulls up all of the available fields on the list, but not the variations on the fields. 

New Member

Flow is a really easy to use product, but it seems extremely limited. I would like to use custom SharePoint columns in a flow (branch a workflow based on the selected option in a choice field, update a custom column, read the value out of a custom column, etc.). This doesn't seem to be possible at the moment.

Advocate V

When creating a condition logic against a document library, only default field are listed.  Custom fields (metadata) are NOT listed.

This greatly limits the usability of MS Flow on document libraries.

E.g. if I added 'department' as a custom field in a document library.. i cannot add 'department' in the condition logic.

New Member

This seems very obvious and important.  There is a workaround - but a clumsy one.

Regular Visitor

Can you point me to the workaround ?




Regular Visitor

I am also very interested.pls. can you post some more sentences about workaround?

New Member

It appears that any lookup fields, radio button, checkboxes or defined list (drop down boxes) fields which are included in my list are not presented as an option for creating a new list in SharePoint using Flow. This is keeping me from being able to use Flow completly. I am still using it to trigger the creation of an item but then a workflow will be used to fill in the rest of the items. It would be great to do all of this in Flow.

Not applicable

I need this. was a work around ever achieved? 

Kudo Kingpin

Currently Custom Columns from Doc libraries are not available as dynamic content in Flow, and at the same time there is no ability to connect to another Sharepoint List.


It would be great if it was possible to connect to more than one List and Doc library and to "join" them or atleast have an ID column to pick data from either the doc library or list. In this way it would be possible to attach a Doc to an approval e-mail and at the same time be able to update rows in lists based on the outcome of the approval e-mail.


It would open up so many use cases for Flow and PowerApps, both are fantastic products that just need little touches like this to make them that much more capable.


Advocate I

It would be very helpful if we have this feature OOTB.

As of today the only way to achieve this is to use SharePoint Designer Worfklow to extract the data (First/Last Name or Email from Outlook)