Showing results for 
Search instead for 
Did you mean: 
Level: Powered On

Cannot filter on SharePoint field to compare to Salesforce field

I'm trying to build a Flow that will trigger based on a modified record in Salesforce and then copy that record info to a list item in SharePoint. This works on a basic level, but I need to filter the record coming from Salesforce in order to avoid duplicate list items in SharePoint. When the list item already exists, I want to do an update instead.


So I'm trying to use a Get Items and an Odata filter to compare any of a few possible field names from the SharePoint list to its related Salesforce field. However, I can't get the filter to recognize the SharePoint field name as a field name, instead it just treats it as a text string.


Here's how it's configured:



But when the flow runs it always fails with the following error:


"status": 400,
"message": "The expression \"Title eq Customer Account 1\" is not valid.\r\nclientRequestId: e7876844-0df5-4b83-9abd-d8e597baabee\r\nserviceRequestId: ba44ae9e-5050-0000-1cb0-36a01983e7b9"


As you can see, it pulls back the value of the Salesforce account name, but I can't pull the value of the SharePoint field to compare with it. It simply equates it to the text of Title that I typed in.


Also, I notice that when creating the filter, dynamic content for Salesforce fields is available, but nothing for SharePoint. Is that expected?


Thanks for any help here!


Community Support Team
Community Support Team

Re: Cannot filter on SharePoint field to compare to Salesforce field

Hi @DaveBrom,


The format of Filter Query should look like this:

ColumnName eq ‘String’

You could try adding single quotes outside of Dynamic content, like:


Please take a try.


Best Regards,


Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Level: Powered On

Re: Cannot filter on SharePoint field to compare to Salesforce field

Hi Barry,


Thanks, I actually did try that already, but it doesn't make any difference in the outcome. Similar failure message, but now with single quotes around the dynamic content value being returned. The issue seems to be more with the ColumnName not being evaluated or related to anything - it's just treated as a static string value.

Helpful resources


Incoming: New and improved badges!

Look out for new contribution recognition badges coming SOON!


Power Platform Online Conference

Join us for the first ever Power Platform Online Conference!


New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!


Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!


Microsoft Learn

Learn how to build the business apps that you need.


Power Platform World Tour

Find out where you can attend!


Webinars & Video Gallery

Watch & learn from the Power Automate Community Video Gallery!

Top Solution Authors
Top Kudoed Authors
Users online (5,482)