cancel
Showing results for 
Search instead for 
Did you mean: 

Create a trigger for SharePoint list columns

It would be nice to have a trigger if a certain column in a SharePoint list is modified. For example, if the column "Status" is modified, or if the column "Assigned To" is populated. So we don't have to use the trigger "When an item is created or modified", where you have to create a lot of workaround conditions just to make sure that the column that was updated is what you need. 

Status: Completed

Hi all,

 

Happy to update that this feature is now rolled out to and available for use. The documentation is updated as well:

For more info about how to use this action, see this tutorial: Introducing 'when an item or file modified' trigger and 'Get changes' action

 

Thank you all for the feedback and please let us know if you have any questions.

 

Thanks,

Chakkaradeep

Comments
Regular Visitor

@fugixi ,

 

I receive that exact same error when using @Chakkaradeep 's video tutorial.

 

Since I believe that I have inputs specified... Any ideas @Chakkaradeep ?

Power Automate

Can you confirm if you are indeed using the new trigger - "When an item or file is modified" - and that using the Since Token from that trigger as the input for the "Get changes for an item or file" action?

 

Also, please post the questions in the community forums so you can leverage other users in the community to validate quickly than posting here in the ideas exchange section. 

Regular Visitor

@Chakkaradeep ,

 

I'll confirm her with a couple of screenshots. I'm new to these forums, so I'll see if I can also post the question in the community forums.

 

Replying here because you were the one that put the link to the video tutorial and thought you might be the best person to interpret the error...

 

GeorgeAnderson_0-1598881754940.png

GeorgeAnderson_1-1598881897637.pngGeorgeAnderson_2-1598882082887.png

Since = Trigger Window Start Token

Until = Trigger Window End Token

 

GeorgeAnderson_3-1598883585284.png

In the Select an output field and in the first of the two conditions the Dynamic Content choice is Has Condition Changed: Status

 

Error message received:

GeorgeAnderson_5-1598884112244.png

GeorgeAnderson_7-1598884294100.png

 

What am I missing?

Regular Visitor

Found it!!! When you get the error message: sinceInput not specified

 

I wrote this flow starting from a template, thinking that the first step was the same as the new trigger... it was not!

 

Therefore, I was using an old trigger:

When an existing item is modified

 

Others on the forums were using the new trigger:

When an item or a file is modified

 

I thought I was using the new trigger... but I was not. My eye thought they were the same...
It does works properly, as advertised, when using the correct trigger.

 

So, if you use the wrong combination:

When an existing item is modified

with

Get Changes for an item or a file (properties only)

You will get the error: sinceInput not specified

 

This reminds me of the old days of "Bad command or file name" which could mean 31 different things. I do wish error messaging could be more revealing as to what the problem actually is. @Chakkaradeep you might put this in the documentation for the new trigger.

Regular Visitor

Wait a second guys.

So now i have to create 2 separate flows?! First with trigger "When an item is created" and second "When an item or a file is modified"?

@Chakkaradeep  why can't we use good old "When an item is created or modified" and "Get changes..." after this?

New Member

I tried the tutorial video and have read several solutions across multiple forums and my flows just keeps on RUNNING.

 

Any solution?

New Member

@Chakkaradeep 

I am with the other respondents here. Whilst what you have created will undoubtedly be useful, it is NOT the feature that was requested.

 

What was requested: a trigger based on column changes

What was provided: a trigger based on library/list changes + an action to see what those changes did at a column level.

 

To put it another way, a trigger directly affects flow runs. Your solution does not in any way affect flow runs beyond what existed already, only what you can do with those runs.

Advocate I

dsdeveloper has a good point.   I would love to have trigger based on column changes.