Only trigger flow when sharepoint path does not end with specified string

[HenrikFranzen]

I rarely use the settings conditions so I'm a bit out of my comfort zone here.

We want to trigger a flow when a sharepoint file is uploaded, but because our folder structure is built (with 4 levels) it gets triggered when its not supposed to be triggered.

We want the trigger to exclude all paths ending with "sss2_prosjekt/" and "Prosjekter/" since these are top level folders. I've tried some tips out here but nothing works for me, here is where I'm at right now:

Since we can't only trigger the flow when the 4th level file is created we need to exclude in some way. Here is the paths we have to use. We get this from the downloaded output data for the trigger. Any help here?

[Nived_Nambiar]

Hi @HenrikFranzen 

Instead of Not condition you have specified above, 

Why don't you specify the condition that trigger should work when file is created in that folder like below

I have a folder structure like below

I want to trigger when file is created in Test3 folder, so i used below trigger conditions 🙂

Hope this helps 🙂

Mark it as solution if it resolves your query 🙂

[HenrikFranzen]

@Nived_Nambiar Thanks for the response. This won't work sadly since the files are everything from text to pictures uploaded by our customers. So this flow is meant to notify us whenever a customer has uploaded a file to the shared sharepoint.

We could however look at who uploaded the file and exclude users that end with our tenant. Any tips there?

[Nived_Nambiar]

Hi @HenrikFranzen 

I did not get you

I hope your question how to trigger a flow when someones creates a file in a specific subfolder? am i right ?

[HenrikFranzen]

@Nived_Nambiar 

We have all our customers that have been sold on within 1 sharepoint folder (sounds worse than it is) and whenever a file is uploaded in their respective folders which are within the main folder we want to trigger the flow. Whenever a sale is made on a new customer the customer gets its own folder within the main folder as mentioned. So we only want to trigger the flow when a file is uploaded by a customer, not when the customers folder is created.

[Nived_Nambiar]

Hi @HenrikFranzen 

Ok i think i have understood your flow, so let's say if you have mainfolder NN, and inside it you have added some folders like NN1, NN2 etc, so whenever someone add files to any of folder inside the subfolder, it should trigger the flow, same scenario applies when folder for that customer is created and file is moved to ?

Am i right ?

[HenrikFranzen]

@Nived_Nambiar Pretty much, except we dont want to trigger the flow when the folder is created. So my thought is now to use a condition for the author of the file/folder that gets uploaded. If we can make the flow ignore all files/folders uploaded by an author ending with our tenant (for example "123.com") that should fix my problem here. I actually think this would be the best way to handle this if possible.

[Nived_Nambiar]

Hi @HenrikFranzen 

I think i am little confused at author part

[HenrikFranzen]

@Nived_Nambiar Ye sorry its called different things throughout our system. What I'm thinking is we look at who created/modified the file. Since the folders from our part are created with a certain user we could exclude that system user or email address.

The image shows whats inside the trigger, this can be downloaded from the trigger. Almost furthest down we can see "editor" in the body which contain email among other things. So if we can exclude all users that have an email address that enda with "123.com" that would solve my problem. 

 

[Nived_Nambiar]

Hi @HenrikFranzen 

Ok so you need to create a trigger condition for that right to exclude those emails ?

[HenrikFranzen]

@Nived_Nambiar Yes that would solve this

[Nived_Nambiar · Accepted solution]

Hi @HenrikFranzen 

Give a try with this trigger condition 🙂

@equals(endsWith(triggerOutputs()?['body/Editor/Email'],'123.com'),false)

Hope it helps !

[HenrikFranzen]

@Nived_Nambiar Amazing, that works (with some additions)!

Thank you so much for the help!