cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
AngusD
Level: Powered On

For a selected file (SharePoint) trigger not working

I'm encountering an issue with the "For a selected file" trigger (SharePoint).  It was working fine as recently as last week, but not now.

 

If I create a new blank flow and type "for a selected file" into the search connectors and triggers box, it finds "For a selected file" for SharePoint (as well as another one for OneDrive).  But if I click the SharePoint icon in the list of connectors at the top of the box, "For a selected file" does NOT appear in the list of available SharePoint triggers.  

 

So if I go back to the first step and just search for "for a selected file" and select the trigger, it will put it into the Flow.  BUT it is not producing any of the outputs it should.  This trigger is supposed to produce Name, Link to Item and ID as outputs, so my next action ("Get file properties") should be able to get the ID from the trigger as dynamic content.  But it is telling me there is no dynamic content available.

 

I have previously successfully built flows using this trigger and it has produced the correct outputs (including ID), allowing me to then get the properties of the file.  Something seems to have changed recently and it is no longer working, and no longer appears under the list of triggers when you select the SharePoint connector, even though just searching for the trigger name does find it.

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
Highlighted
Community Support Team
Community Support Team

Re: For a selected file (SharePoint) trigger not working

 

Hi @AngusD ,

 

MS Flow classifies actions and triggers. You could click on Built-in to find For a selected file.

133.PNG

I did a test on my side, using Compose to store FileId and configure Get file properties action still works.

134.PNG135.PNG

Please try again.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
AngusD
Level: Powered On

Re: For a selected file (SharePoint) trigger not working

 

 

Hi,

 

  Thanks for your response.  This definitely seems to have changed, as the trigger only appears under SharePoint in the "Built-In" tab, but not under "All"?  It is also not producing the output it says that it does.  The help for that trigger says that the outputs are Name, Link to Item and ID:

 

FlowIssue1.jpg

 

But none of those values are actually available as output from that trigger:

FlowIssue2.jpg

 

  This is why I'm wondering if this is a but or a deliberate change to how this trigger works?

 

In any case, the workaround you've suggested (ie using Compose to get the FileId and passing that to Get File Properties) worked for me when I tested it, so I'll change my Flow to work that way instead.

 

Thanks.

 

2 REPLIES 2
Highlighted
Community Support Team
Community Support Team

Re: For a selected file (SharePoint) trigger not working

 

Hi @AngusD ,

 

MS Flow classifies actions and triggers. You could click on Built-in to find For a selected file.

133.PNG

I did a test on my side, using Compose to store FileId and configure Get file properties action still works.

134.PNG135.PNG

Please try again.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
AngusD
Level: Powered On

Re: For a selected file (SharePoint) trigger not working

 

 

Hi,

 

  Thanks for your response.  This definitely seems to have changed, as the trigger only appears under SharePoint in the "Built-In" tab, but not under "All"?  It is also not producing the output it says that it does.  The help for that trigger says that the outputs are Name, Link to Item and ID:

 

FlowIssue1.jpg

 

But none of those values are actually available as output from that trigger:

FlowIssue2.jpg

 

  This is why I'm wondering if this is a but or a deliberate change to how this trigger works?

 

In any case, the workaround you've suggested (ie using Compose to get the FileId and passing that to Get File Properties) worked for me when I tested it, so I'll change my Flow to work that way instead.

 

Thanks.

 

Helpful resources

Announcements
firstImage

Microsoft Flow Online Conference

Join us for a FULL day of FREE Microsoft Flow Sessions from some of the best minds in the industry!

firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

Power Platform 2019 Release Wave 2 Plan

Power Platform 2019 Release Wave 2 Plan

Features releasing from October 2019 through March 2020

thirdimage

Flow Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

thirdImage

New Flow Community Board!

Check out the new Microsoft Flow Community Blog Topic Suggestion board!

fifthimage

Microsoft Learn

Learn how to build the business apps that you need

sixthImage

Power Platform World Tour

Find out where you can attend!

seventhimage

Webinars & Video Gallery

Watch & learn from the Flow Community Video Gallery!

Users Online
Currently online: 173 members 5,417 guests
Please welcome our newest community members: