Problem with conditions when building a flow

[Anonymous]

Hi I have 2 lists 

1/ Validation list with the following headers 

the items in the red box are populated via a MS form using Power automate 

the items in the green box are completed in a meeting 

at this point the "approval column" becomes a trigger for the item to be copied into the 2nd list 

2/ Coordinator Progress tracker

the source ID column maps to the ID column - this list is updated manually and via the 1st list if a value changes eg date or deal description 

I have built the flow but cannot get it to work properly 

I am getting the following error

keen to get some assistance here as Im fairly new at this 

thanks Tracey

 

 

 

[Reimi]

It seems the input of "Condition 2" is null. Can you please elaborate on the expression of condition 2?

You can avoid the error by handling null input of parameter in length function.

[efialttes]

Hi!
I believe the purpose of your 'Condition 2' is to evaluate the number of elements contained on the 'filter array' output, right? If I am right I would doublecheck  the expression assigned to the 'Condition 2' left term is the following

length(body('Filter_array'))

IF so, the error thrown is intriguing. I mean, 'Filter array' execution succeeds, meanng its body('Filter_array') output should be an array, no matter it has 0, 1 or several elements... but it should never be 'null'

One more comment: I also try by adding a 'Terminate' action block on the 'negative' branch of your first condition. 
Hope this helps!

[Anonymous]

Hi Reimi

thank you for your reply

the expression on condition 2 is Length (Body) of the get items - looking at create or update item 

I hope that answers the question? 

[Anonymous]

these are the values I have 

 

[Anonymous]

here is the condition expanded

 

[efialttes · Accepted solution]

Hi again and thanks for the additional info shared!
My guessing: Your flow execution took the right branch on your first 'Condition' action block... so 'Filter array' was not executed and thus body('Filter_array') is null (i.e. does not exist) and length((body'Filter_array') throws an error. If so, I would add a 'terminate' action block on such 'If no' branch.
Please note you can configure such 'TErminate' action block so it ends your flow execution either with 'Succeeed', 'Cancelled' or 'Error'. I would suggest you to set it as 'Cancelled' so on your 'Run history' you can easily distinguish it from real internal execution errors.

Hope this helps

[Anonymous]

thank you all for that I have put the terminate in and am now getting success

however now I am getting multiple entries instead of updating what is already there - any suggestions?

[Anonymous]

 

[efialttes]

Hi again!
So, your current status seems to be as follows:
1.-When first Condition is evaluated as 'false', your logic works now as expected, but
2.- When first Condition is evaluated as 'true', and your expectation is your 'Condition 2' is also evaluated as true, there is some weird behaviour, so you are getting multiple entries instead of updating what is already there?
Is my understanding correct?

[Anonymous]

Yes 

[Anonymous]

 Condition 1 gets the items based on the value 'approved'

a filter array is used to match the ID columns 

condition 2 is supposed to check the length of the body against the ID and then if there is something there update the item and if there is nothing there create the item 

[efialttes]

hi again!
I guess there can be several reasons you experience multiple items created although you expect only one to be created.
First, I would doublecheck if 'Condition 2' always takes the right branch... meaning the 'Condition 2' evaluation rule is probably wrong
SEcond, I would doublecheck if your first list item (i.e. the one triggering the flow) is being updated several times and in all of them the status column being evaluated on your first Condition keeps the value 'approved'. If so, I would recommend  either to transition such status to another value, or to extend your flow logic to doublechek if your status column did or did not change when your flow was triggered . Assuming 'Version history' is activated on your Sharepoint list, get-changes-for-an-item-or-a-file-(properties-only) action block should provide you such info
Hope this makes sense

Hope this makes sense

[Anonymous]

Ok so first i checked no versioning then I marked the column settings for "enforce unique values" which stopped the flow working as in wouldnt update - I got the message skipped.

So I created a new flow which is not working at all now - see below  - what would be the solution? im really stuck