Answered

Send email update with changes to Sharepoint Column in the last 24 hours.

(0) Share

Report

Posted on by AR78

Hi all,

I want to create a flow that sends out a daily email listing all the items on a Sharepoint list where a column has been changed to a specific value, instead of an instant email at column change.

I have set up the flow to run daily, and on the "Get Items" I have set a filter to get items changed/created in the last 24 hours. My idea is to loop through the returned items, get the ones only where the column "Priority" has changed to "High" and build an HTML table to send via email.

I keep getting an error "sinceInput not specified clientRequestId:" at "Get changes for an item or file" and I don't understand why...

Any help would be highly appreciated.

Thanks

Alex

Categories:

Using flows

I have the same question (0)

All responses (14)

Answers (1)

jiwhite 500 on at

Like (0)

Report
Copy link

Link copied!

Could you post an image of the flow as it ran with the complete text of the error? There seems to be information missing.

Since is looking for the integer version number to start at. You'll need to subtract at least 1 from the current version to get changes and Until should be blank. Also, you'll need to include items that are new, version 1. The versions are passed as text floats, so you need to convert to an integer to subtract and put it in the field, for example:

Was this reply helpful? Yes No
ScottShearer 25,290 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

@AR78

Can you double check the values that you selected from Dynamic properties for Since and Until and post here please?

Was this reply helpful? Yes No
AR78 13 on at

Like (0)

Report
Copy link

Link copied!

Here the full error, thanks

Was this reply helpful? Yes No
AR78 13 on at

Like (0)

Report
Copy link

Link copied!

Hi @ScottShearer here the values for the the since and until token, they are select from the "Get Items" block

Was this reply helpful? Yes No
ScottShearer 25,290 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

@AR78

I learned something in researching your issue. My understanding is that the Get Changes action will not work unless it is used in conjunction with a When an item or file is modified action.

My understanding is that the Get Changes action will not work unless it is used in conjunction with a When an item or file is modified action. See this post.

Was this reply helpful? Yes No
jiwhite 500 on at

Like (0)

Report
Copy link

Link copied!

No, I was able to get changes using a manual trigger. The When an item or file is modified trigger is not required.

Was this reply helpful? Yes No
ScottShearer 25,290 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

@jiwhite

You are correct but that do you much good without meaningful data in the Since field. If you can make it work in a meaningful way, I will stand corrected.

Was this reply helpful? Yes No
jiwhite 500 on at

Like (0)

Report
Copy link

Link copied!

The Since field requires an integer for the version number. It works as designed. There is no more meaningful data. I could put in a variable as I did above, but I was just demonstrating that the trigger is irrelevant.

Was this reply helpful? Yes No
jiwhite 500 on at

Like (0)

Report
Copy link

Link copied!

This error indicates that there is a problem with the input in Since. It looks like you tried to pass the version from the trigger. The version in the trigger is a string, but Since requires an integer, so the input was malformed. If you put the current version in Since, even as an integer, it shouldn't return any changes because there are no changes between the current version and the current version. Change the version to an integer then subtract at least one to get any changes. If the version is 1, all of the data is new.

Was this reply helpful? Yes No
AR78 13 on at

Like (0)

Report
Copy link

Link copied!

Thanks for your help, however reading more carefully it does look "since" could be either a Version (like you're suggesting) or a "Trigger Window start Token".
This token express the time of the last flow check, which is what I am after because my intention is to send out an email on what has changed since the last flow ran.
If I use the version, I may send out the same email multiple time because I don't have a way to control if the update has been sent out or not already.

Was this reply helpful? Yes No