cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
AndreSchlender
Helper I
Helper I

Trigger Condition Error on SharePoint Connector

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 usedTrigger condition usedError on test runError on test run

1 ACCEPTED SOLUTION

Accepted Solutions

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.

View solution in original post

3 REPLIES 3
v-litu-msft
Community Support
Community Support

Hi @AndreSchlender,

 

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

Annotation 2019-10-24 142639.png

Annotation 2019-10-24 142554.png

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.

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

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.

Helpful resources

Announcements
Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

New Ideas Forum MPA.jpg

A new place to submit your Ideas for Power Automate

Announcing a new way to share your feedback with the Power Automate Team.

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

MPA Licensing.jpg

Ask your licensing questions at the Power Automate AMA!

Join Priya Kodukula and the licensing team, super users and MVPs to find answers to your questions on Power Automate licensing.

Users online (1,827)