SOLVED

Flow condition based on SharePoint file name

%3CLINGO-SUB%20id%3D%22lingo-sub-700987%22%20slang%3D%22en-US%22%3EFlow%20condition%20based%20on%20SharePoint%20file%20name%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700987%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20my%20case%2C%20I%20want%20to%20execute%20a%20flow%20if%20a%20specific%20file%20in%20a%20SharePoint%20library%20is%20modified.%20If%20it%20is%2C%20I%20want%20it%20to%20copy%20to%20our%20local%20file%20server.%20What%20I%20expected%20to%20be%20the%20hard%20part%20(getting%20the%20File%20System%20connector%20configured)%20was%20straightforward.%20However%2C%20the%20conditional%20expression%20that%20checks%20the%20file%20name%20is%20not%20working%20as%20I%20expect%20it%20to.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20test%20case%2C%20if%20the%20condition%20is%20FALSE%20(i.e.%20the%20file%20name%20does%20not%20match%20the%20expected)%2C%20I%20am%20sending%20myself%20an%20email%20containing%20the%20file%20name.%20The%20email%20sent%20in%20the%20TRUE%20case%20is%20a%20completely%20different%20text.%20Both%20the%20email%20and%20the%20flow%20check%20shows%20me%20that%20the%20FALSE%20case%20is%20the%20only%20case%20executing.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20screen%20shots%20I've%20attached%2C%20the%20file%20name%20in%20the%20condition%20and%20that%20in%20the%20email%20appear%20to%20match.%26nbsp%3B%20Why%20is%20the%20condition%20output%20not%20TRUE%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20examine%20the%20flow%20in%20a%20test%20case%2C%20the%20%22File%20Name%22%20output%20expression%20is%20the%20meaningless%20to%20me%20%22R01fTUFTVEVSX0lQLnhsc3g%3D%22%20--%20how%20do%20I%20get%20there%20from%20here%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-700987%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Flow%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-707241%22%20slang%3D%22en-US%22%3ERe%3A%20Flow%20condition%20based%20on%20SharePoint%20file%20name%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-707241%22%20slang%3D%22en-US%22%3E%3CP%3EI'll%20answer%20my%20own%20question%20in%20case%20it%20helps%20someone%20else%20later.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20solution%20was%20to%20add%20a%20string%20variable%20prior%20to%20the%20condition%20that%20has%20the%20value%20of%20the%20filename%2C%20then%20using%20it%20for%20the%20conditional%20evaluation.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F119733i40025E15770823E2%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22InitializeVariable.png%22%20title%3D%22InitializeVariable.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-891864%22%20slang%3D%22en-US%22%3ERe%3A%20Flow%20condition%20based%20on%20SharePoint%20file%20name%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-891864%22%20slang%3D%22en-US%22%3EDoes%20'Flow%20condition%20based%20on%20SharePoint%20file%20name'%20require%20a%20special%20license%20for%20PowerApps%20and%20or%20Flow%20or%20can%20it%20be%20implemented%20with%20standard%20O365%20(SPO%20%26amp%3B%20Flow)%20services%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-892120%22%20slang%3D%22en-US%22%3ERe%3A%20Flow%20condition%20based%20on%20SharePoint%20file%20name%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-892120%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F419056%22%20target%3D%22_blank%22%3E%40hilliards%3C%2FA%3E%26nbsp%3B-%20I%20can't%20say%20with%20complete%20certainty%2C%20as%20I'm%20not%20sure%20what%20my%20particular%20configuration%20is%20(I'm%20not%20the%20O365%20admin%20for%20our%20company)%2C%20but%20I%20don't%20think%20so.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

In my case, I want to execute a flow if a specific file in a SharePoint library is modified. If it is, I want it to copy to our local file server. What I expected to be the hard part (getting the File System connector configured) was straightforward. However, the conditional expression that checks the file name is not working as I expect it to. 

 

In the test case, if the condition is FALSE (i.e. the file name does not match the expected), I am sending myself an email containing the file name. The email sent in the TRUE case is a completely different text. Both the email and the flow check shows me that the FALSE case is the only case executing. 

 

In the screen shots I've attached, the file name in the condition and that in the email appear to match.  Why is the condition output not TRUE?

 

When I examine the flow in a test case, the "File Name" output expression is the meaningless to me "R01fTUFTVEVSX0lQLnhsc3g=" -- how do I get there from here?

 

3 Replies
best response confirmed by JH141494 (Occasional Contributor)
Solution

I'll answer my own question in case it helps someone else later.

 

The solution was to add a string variable prior to the condition that has the value of the filename, then using it for the conditional evaluation. 

 

InitializeVariable.png

Does 'Flow condition based on SharePoint file name' require a special license for PowerApps and or Flow or can it be implemented with standard O365 (SPO & Flow) services?

@hilliards - I can't say with complete certainty, as I'm not sure what my particular configuration is (I'm not the O365 admin for our company), but I don't think so.