SharePoint list item field updated

[MaWi]

I want to hook onto this...

I created a flow like suggested with a switch statement on a column value. Works fine, thanks for sharing!

I have one issue.

Out of this line with the changed value i create a new list item in my calendar list. I try to set the start and end time of the new evnet to corresponding values of the list.

when I look into the results it looks like follows

This is what I have in my "trigger"

This is what i want to do as action

This is what happens

It always sets end date = null and thus the event will not show up in my calendar 😞

Any ideas?

[MWilliams86]

Looking at the screenshots you provided it looks like you're accidentally using the wrong variable to assign the end time.  You're using a variable called "End Time" in the flow when in the output screenshot you're showing a variable named "END Date" which looks like the correct format and the variable you want to assign the field End Time to.  👍

[MaWi]

Would be too easy. I Just created both. One is a calculated one. (Start + duration) the other is one i created for testing purpose. Manually added Date.

[JenniferFGI]

I was wondering if "a new trigger based soley on when a value changes" (as mentioned in the last post) was ever implemented.

[Anonymous]

I would wonder the same thing myself. Was this implemented?

[rgbrasel]

It's implemented in Nintex, which is far superior to Microsoft. Unfortunately, I no longer have Nintex Workflows. Maybe Micro$oft should just buy Nintex and use it.

[rebeccas]

Can you please elaborate on this. When I try the Modified it just pulls in a date...how do you use this to tell you which column you are looking to see if it was modified?

[JimmyWork]

This is defintly something we need now.

[GarciaMcG]

Hi,
I’m trying this with an Options column and I’m getting an error message every time I try to trigger the flow.
I have a Status column with pre-established options and I want to trigger different actions depending on what Status the column is updated to.
The Switch control after the item change trigger seems ideal but I cant get it to work.

Help!

[rebeccas]

@GarciaMcG 

If you are clicking the field from the Dynamic content make sure you click ont he one that says "ColumnName Value" not just "ColumnName".

Choice fields are a pain in Flow sometimes!

[HeidiAnn]

Thank you for this thread, it helped to understand this issue a lot. I agree, this issue needs an simple solution ASAP. I just spent 30 minutes of my work time erasing duplicates from a log that updates everytime a change is made. Ideal would be to update the log only when one column changes. I'm not going to do any fancy coding solutions to achieve this, it would not serve our purposes, since we need a solution that regular non-IT-people can understand if it needs to be updated in the future. Until a solution is made, I'll just keep manually erasing the extra rows. 

[rebeccas]

@HeidiAnn 

I followed these notes and got it to work good on my end. 

http://johnliu.net/blog/2018/5/microsoft-flow-sharepoint-trigger-on-specific-fields-changed-via-sp-h...

This guy here has some of the best Flow solutions.

Hope this helps!

Rebeca

[JimmyWork]

I use this to but this is not what we are requesting.

Flow should only be triggerd when a column is changed.

Using John Liu's way is a temporary workaround. It triggers on modified or new and not on column change. This means the flow runs each time anything is modified.

[HeidiAnn]

Dear @rebeccas , 

thank you for taking the time to reply. If you read my reply, I said that this solution is too complex for our users. The Flows we use need to be simple enough for non-IT-personell to update and modify when necessary. 

There seems to be demand for this feature, I hope that Microsoft implements it at some point. 

Kind regards, 
Heidi 

[rebeccas]

@JimmyWork 

His solution is a "work around" ..they should add an option for just modified. But with his work around it will "run" for either a creation or a modification but you only have an action with it is modified and for a specific column. I use it for one that looks for only when the status of an item is modified. It works really good.

But I do agree for sure...it would be awesome if they came up with a more simple/straight forward solution that is just when an item is modified and then you can put in what you are looking for to be modified. Hopefully they will do that soon.

@HeidiAnn 
I agree, hopefully they will add in an easier solution soon.

[Jethrooooo12]

Still no solution to this issue? I've been searching everywhere..

[Eliot]

Hi, @Jethrooooo12 ,

This can be done using a combination of a *bit* of the 'hard stuff' (no insult - I'm flying blind, too!), but you can use the inbuilt functions to (gradually) build the data and logic that you need. I'm going to provide a more 'in depth' version of this, that includes how I've done the logic part of this, it's simple, but initially involved.

The reason for this is that now this doesn't actually allow you to type in 'Value' to get to the request's value, instead, it just provides the 'Body' which contains that. So you need to use a "Parse JSON" to work with the data. This means that you'll need to do a hefty few run-throughs to work out some of the generic values, and/or actually get the right template.

So, my first suggestion, before you get in to configuring the HTTP request, is to pipe anything you're going to use frequently in to a variable, because, sometimes, it's just easier than playing "Please let me" tennis with Flow. Then get that HTTP Request's 'Body', and give your JSON a schema to work with.

So pre-flow work is:

1. Setup variables, I always set up at least an ID variable:
   
2. Setup the HTTP Request:
   
3. Setup a "Compose" to get the 'Body'
   
   (or you can just take it from the request in the test result - I just like to separate things down)
4. Run a test on the flow, by updating a row on your list.
   Just update one column, and make sure it ** isn't  ** an appendable multi-line text field.
   (this messes up the JSON somehow)
5. Copy the "Compose" test result contents somewhere safe, verbatim, and remove the "Compose".

Now you can do the thing (ju li):

1. Parse JSON:
   
2. Using either trial and error, or an insanely brilliant ability to read JSON, figure out which fields to map in the "Select" ...
3. Now you can work the logic in!

So, you do kind of need to do the first bits of John Liu's fix on this (at his dot net domain), but you should be able to lean on the Flow basic functions to do all the hard work for ya.

*Nearly* no code ... and what code there is you're just copying and pasting ;-).

OK ... now for the more complicated version!

We need more variables set, so that we can differentiate between the new and old version. So. The bigger pre-flow work is:

1. Initialise variables for:
   1. creaModId - from trigger - This is the created or modified item's ID.
   2. currentVers - from trigger - This is the most recent version of the item. 
   3. currentValue1 - from trigger - Most recent data in Value1 column.
   4. currentValue2 - from trigger - Most recent data in Value2 column.
   5. oldVers - from logic - elder of the 2 versions taken through HTTP get.
   6. oldValue1 - from logic - eldest of 2 Value1 data taken through HTTP get.
   7. oldValue2 - from logic - eldest of 2 Value1 data taken through HTTP get.
      
2. Set variables for the following, so we can differentiate if required:
   1. creaModId - trigger's ID
   2. currentVers - trigger's Version number
   3. currentValue1 - trigger's Value1
   4. currentValue2 - trigger's Value2
      
      
3.  
4. Setup the HTTP Request:
   
5. Setup a "Compose" to get the 'Body' of that request.
   
   (or you can just take it from the request in the test result - I just like to separate things down)
6. Run a test on the flow, by updating a row on your list.
   Just update one column, and make sure it ** isn't  ** an appendable multi-line text field.
   (this messes up the JSON somehow)
7. Copy the "Compose" test result contents somewhere safe, verbatim, and remove the "Compose".

Next comes a slightly more involved process to grab and compare the details. Once I've saved this post, I'll see if I can sum it all up with some imagery, somehow, more easily. So, in the pre-run, you've run a test run, and have an HTTP Request that's all correct, now you'll want to use a "Select" to pick out the data that you need, but Flow can't understand the information natively, so we need to do some of those pre-amble steps again in the flow building proper:

1. Create a "Parse JSON" from the body of the "HTTP request".
2. Click on "Use sample payload to generate schema" and paste in the "Compose" data that you'd saved above.
   This helps "Parse JSON" understand your data, it uses your example to build a framework (SCHEMA) from.
3. Your flow now understands the HTTP Request output!
   
4. Now we need to pick the data that we want from that "Parse JSON", done using a "Select", so:
   
5. The annoying thing is that now we need to "Parse JSON" again, to understand what the "Select" in #4 there puts out ...
   ... ... ... sooooooo ... we need to copy/paste again:
   
   Run another test (same restrictions!) and copy paste the results somewhere safe.
6. Now, back into Flow building, you can paste that test result into the generate schema of your second "Parse JSON".
   
   Now flow understands the data that you've selected. Let's tidy that up.
7. Plonk the request to the second parse into a scope, and minimise.
   
   Now we have an array of two sets of data that we now need to pick out the oldest stuff from.
8. Create a "Filter array" from the Body of the second JSON to get anything that isn't the current version:
   
   We've used the currentVers variable! Since we have only taken 2 results in the HTTP request, there will only be one result!
9. Now we need to set the "OLD" variables from the "Filter Array", and thank the maker we don't have to parse it (the "currentValue1" should read "oldValue1" - I'll correct it later!):
   
   You can see the "apply to each" here, that's because it's kinda going through 2 sets of data. The reality is that it's only going to be the one, older, set.
10. *NOW* we can *finally* work out what we want to do with the data ... if I get the chance, I'll edit that in, too ... but logic is all you, really. 😘

Very quickly, as an example of logic work on this, I've just done a quick IF/THEN brancher on the assumption that we can only change 2 values. Here's the whole thing:

Here it is broken down:

1. If currentValue1 matches oldValue1,
   
2. ... then record the obvious change in an entry in another list with oldValue2.
   
3. However, if it doesn't match, then we still need to check currentValue2 against oldValue2 and add both to our other list, accordingly.
   

Best

Eliot Cole @ projectfive UK

[Joe3]

Hi, how you can put in a condition in Flow checkfield IsBlank() -> Yes ?

[Eliot]

@Joe3 

Would probably need a bit more information, mate, and I recommend you raise a new thread for it, but just guessing:

Use a condition and select the things that you wish to filter, then leave the other side blank, and say equals this.