Good Video Matt. I've used this trigger before when using a list to manage data created using MS forms. I added conditions following the trigger that was based on where it was in the process. If it was a new entry, it send emails to certain people, if it was further in the process, it send emails to different people.
You should be able to put a filter on the column in the settings area. It would be something like 'columnName neq null'. neq = not equals, so basically, if it's not null.
That's a really interesting question. Technically yes. Although traditionally there was supposed to only be 1 trigger in a flow, the designer and engine does support multiple triggers. This is for scenarios where you want to poll for a response. Dataverse is the only confirmed data source I know that supports polling, so you might be doing something unsupported by doing it with SharePoint, but technically it does work.
Good Video Matt. I've used this trigger before when using a list to manage data created using MS forms. I added conditions following the trigger that was based on where it was in the process. If it was a new entry, it send emails to certain people, if it was further in the process, it send emails to different people.
How to do that?
Great example!
Great video Matt. I've got a question about how to trigger a flow if a particular column/field is no longer blank. Any suggestions on how to do that?
You should be able to put a filter on the column in the settings area. It would be something like 'columnName neq null'. neq = not equals, so basically, if it's not null.
Hello is there a video on that thanks
Matt, what exactly the compose will catch. What I mean is SharePoint list can have multiple rows changed basis the trigger time we put.
The compose is just there for demo purposes, you can put whatever you want after the trigger.
Hey, good video. I had a doubt though, can we use this trigger somewhere along the flow rather than at the beginning?
That's a really interesting question. Technically yes. Although traditionally there was supposed to only be 1 trigger in a flow, the designer and engine does support multiple triggers. This is for scenarios where you want to poll for a response. Dataverse is the only confirmed data source I know that supports polling, so you might be doing something unsupported by doing it with SharePoint, but technically it does work.