Answered

Trigger Condition Error on SharePoint Connector

(0) Share

Report

Posted on by AndreSchlender

Trying to use a trigger condition against a "yes/no" column in the SharePoint list that triggers the Flow.

Maybe missing something in syntax, so any help would be appreciated. The error I'm getting when testing the trigger isn't very helpful.

Trigger condition usedError on test run

I have the same question (0)

All responses (3)

Answers (1)

v-litu-msft on at

Like (0)

Report

Re: Trigger Condition Error on SharePoint Connector

Hi @AndreSchlender,

It works well on my side that adds a condition into the trigger @equals(triggerBody()?['Completed'],true).

Could you confirm the Completed column really has existed in the SharePoint list? The error shows the property undefined, I assume the column has been changed name. You can have a test that without ant condition in the trigger, then create an item to check the column name.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
AndreSchlender 34 on at

Like (0)

Report

Re: Trigger Condition Error on SharePoint Connector

Thanks for the quick reply. I did think of that and the original name for this column is actually "Completed". However it has since been changed to "Job done". I tested the expression with the new name as well and get the same error. I tested without condition to just retrieve the value of the columns and this worked ok. The returned value in this case is true, so still not clearer why the trigger condition errors out.
Andre

Was this reply helpful? Yes No
Verified answer

AndreSchlender 34 on at

Like (0)

Report

Re: Trigger Condition Error on SharePoint Connector

So I did some more testing myself. The actual problem was that the 'Yes/No' column was actually never initialised. It had a default setting but that never actually executes if that makes any sense. When I went in and updated the checkbox and saved the record again the trigger did work as expected. Could also have been a result of the list being migrated from SP2010 to SharePoint Online recently.
By the way it doesn't seem to matter in this scenario if you use a capital or not. So both true and True work fine.
Thanks again for your help.

Was this reply helpful? Yes No