cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
GeorgeAnderson
Regular Visitor

New Trigger for Changes to a Column in an Item in SharePoint Fails

A new trigger has just been released. A video tutorial posted by @Chakkaradeep is found at Video Walkthough of New Trigger/Action. This is meant to allow you to trigger when a column within an item in SharePoint changes, not just when the item changes anywhere in it.

 

I attempt to set up the flow to detect when the Status column changes and then send an email. However it fails for me.
The error message is: sinceInput not specified.

 

Here's the attempt:

 

 

When an existing item is modifiedWhen an existing item is modified

 

Get changed for an itemGet changed for an item

Since = Trigger Window Start Token

Until = Trigger Window End Token

 

 

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:

 

InputsInputs

 

 

What am I missing?

1 ACCEPTED SOLUTION

Accepted Solutions

Found it!!!

 

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

 

@Pstork1 and 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.

View solution in original post

20 REPLIES 20
Pstork1
Most Valuable Professional
Most Valuable Professional

First, is the Status column included in the view you are using for the trigger and the action?

Second, is versioning enabled for the list?

 

Also, could you show us the condition statements you are using to check for changes?



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

@Pstork1 ,

 

I made a reply to your questions and got a message that my reply was marked as spam and removed. I'll try again without any screenshots.

 

First: Yes. The Status column is included in the view that I'm using.

Second: Yes. Versioning is enabled for the list.

Third: The condition is shown, but I'll type it out for clarity

 

Has column changed:Status is equal to true

AND

Status Value is equal to Draft

 

What I do then... Save the item with a status NOT equal to Draft (one of the other status possibilities on the drop down). Then, go into the item again and save the item with the status equal to Draft. And, then, I get the error message.

I didn't try with a second condition (status value = draft), but it does work for me with just the main condition.  I'll add checking for a specific value and let you know.  But the screenshot stops at the end of the Get Changes.  The error is shown, but not the definition of the condition.

image.png



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Pstork1
Most Valuable Professional
Most Valuable Professional

I just tried with both conditions and its working for me.  Can you show me the definition of your condition statements?



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

@Pstork1 ,

 

OK. Hold the horses!

 

Your screenshot shows an "fx true", mine just has the text "true" typed in the field (you couldn't see mine cuz they labeled my first reply as spam and removed it). Can you explain your fx true, and why that instead of just text "true"? In the tutorial video that @Chakkaradeep created and posted, he only used the text "true" not the fx true. Is fx true important for some reason, or is it equivalent to the text "true"?

 

Also, you didn't put your condition inside a Apply to Each box. The video did... so I did... though I don't know why or what exactly the Apply to Each does for me in this situation. Now looking back at the video again, @Chakkaradeep was talking about getting the collection of changes from an item, but then he kind of faded out on that discussion, maybe abandoned that line of thought, and then switched to another demo. Very confusing to me! I thought the point was that you need to capture all of the changes of an item in order for this all to work... but... maybe not.

@Pstork1 ,

 

So, I modified my flow to be more like yours, rather than what was in the first part of the tutorial by @Chakkaradeep .a

 

It fails on the 2nd step before it ever gets to the conditional

 

Here's what the General steps are now:

2nd try - General Steps2nd try - General Steps

Here's the Step 1 Detail:

2nd Try - Step 1 Detail2nd Try - Step 1 Detail

Here's the Step 2 Detail (where it fails):
2nd Try - Step 2 Details2nd Try - Step 2 Details

When run it fails on Step 2 with this message:
Try 2 - Error messageTry 2 - Error message

 

I could show you the inputs and outputs of the first two steps, but I'm concerned the Moderator is going to call this spam and deleted, maybe because of too many screenshots. Let me know if you want to see the inputs and outputs, or can you see the problem without that?

1) When trying to compare to a boolean I find it best to use the true or false expression rather than a literal.  The literal will work, but it is actually a string, not a boolean and the automatic cast seems to be case sensitive.  So whenever testing against a boolean I always enter the value via the expressions tab to make sure I'm getting a boolean value and not a string.

 

The apply to each isn't really needed if you are using a singular trigger.  The trigger fires when one item is modified and i'm just testing the one item to see if the column changed.  I don't remember whether the video used a loop or not, but its not necessary unless you are doing a recurrence flow and retrieving multiple items.  You do get all the changes for that one item, but its not in a collection.  They show as independent values.  They may have been a collection of changes in an earlier version of the trigger.  @Chakkaradeep has been working with that trigger since its earliest inception.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

I'm assuming your list is set for both major and minor versions.  I would try setting the second step to include minor versions = Yes.  If its ignoring minor versions it may not find any changes even though changes occurred, but were stored as a minor version.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Found it!!!

Found it!!!

 

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

 

@Pstork1 and 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.

That's one of the problems starting with templates.  They can be great learning instruments, but they are a snapshot in time and as things change, they don't.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

We are attempting to refactor simple SP OnPrem Leave Calendar Workflows to SP online using Power Automate. Does anyone know how to use the 'column changed' feature within a single flow that is based on the “When an item is created or modified’ trigger?

I've created both types of flows and both worked (as described here) but this ends up duplicating a large set of the follow-on actions after the column-change logic. I’d prefer to put all the logic in one flow for when an item is created and when it is changed (simple CRUD using DRY principle as much as possible).

When we use the 'When Item is created or modified' trigger then add a step for 'Get changes for an item or file (properties only)', the flow errors when tokens are used. Using the 'version trick' or Modified date will not work due to firing orders -- the SLA does not guarantee version 5 will fire after version 3 or that Modified on is accurate. If fact, I've watched version 5 fire before version 3 (mileage/version numbers may vary).

We are attempting to refactor simple SP OnPrem Leave Calendar Workflows to SP online using Power Automate. Does anyone know how to use the 'column changed' feature within a single flow that is based on the “When an item is created or modified’ trigger?

I've created both types of flows and both worked (as described here) but this ends up duplicating a large set of the follow-on actions after the column-change logic. I’d prefer to put all the logic in one flow for when an item is created and when it is changed (simple CRUD using DRY principle as much as possible).

When we use the 'When Item is created or modified' trigger then add a step for 'Get changes for an item or file (properties only)', the flow errors when tokens are used. Using the 'version trick' or Modified date will not work due to firing orders -- the SLA does not guarantee version 5 will fire after version 3 or that Modified on is accurate. If fact, I've watched version 5 fire before version 3 (mileage/version numbers may vary).

Pstork1
Most Valuable Professional
Most Valuable Professional

The problem is that by definition there are no changes when you first create an item.  That's why you are getting errors.  You'll either need to build two flows or find some way to differentiate whether its triggered by a modification or creation.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Thank you for the comment @Pstork1. I started to state the obvious in my quest for a solution, but I didn't want to waste anyone's time. The actual issue is the lack of 'Windows Token' during the CREATE operation. Completing web workflow products mark all non-null values as changed during the CREATE operation - nothing new. IMHO, larger organizations with hundreds of departments will not be able to sustain two or three flows per Leave Calendar (i.e. Create flow, Modify flow, Delete flow, etc.). In our case, that’s over 240 flows for only Leave Calendar implementations.

Pstork1
Most Valuable Professional
Most Valuable Professional

Not really my place to discuss whether the design is lacking or not since I didn't write the code.  Just trying to explain the error.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Hello @GeorgeAnderson,

Went through your post and also the video demo by @Chakkaradeep.

Does this mean that "Get Changes for an item or a file (properties only)" is only supposed to be working with the trigger "When an item or a file is modified"?

I have an existing flow which runs every 24 hours with a recurrence as a trigger. I want to find if the items were changed in the past 24 hours. I tried to use "Get Changes for an item or a file (properties only)" with Since = Trigger Window Start Token. This is not supposed to work which you described.

I also tried with Since = getPastTime(24,'Hour'), hoping to get the changes. However this also returns the same error as yours.

 

Can you please help?

Thank you

Yes, you are correct. It only works with the modified trigger and will not work with the recurrence trigger.  You can check the Modified Date/Time to see if it was modified in the last 24 hours, but you won't be able to get the specific columns that were changed.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

I am getting the same exact error (sinceInput not specified) but I have the correct trigger "When an item or a file is modified" . What am I missing?

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (3,845)