OData syntax for sharepoint column with a space - Get Items action.

[martinav]

I really am not thrilled that I have to learn an entirely different language to do filters in Flow.  But, that is what we have to live with, so I have to bother everyone with how to do this.

My Sharepoint column has a space in it.  How do you format the filter statement with a space in a column name.  I have tried these methods without success.

Part Number eq DVPartNumber

'Part Number' eq DVPartNumber

Part_x0020_Number eq DVPartNumber

Its hard to believe there are yet other ways to do this.  I need to know the right way.

[martinav]

This is now urgent.  I hope for some help on this asap.  How to write this filter to account for a space in the column name.  I have way too much on this sharepoint list to change the name of the column.  I need the answer on how to include the space.  Please advise!!!

[martinav]

Of course, my band aid to make another column, calculated to contain the information of the other did not work either.  Flow does not like the calculated type.  HELP!!!

Thank you.

[martinav]

More failed attempts... HELP!!!!

PartNumber eq DVPartNumber "Column 'PartNumber' does not exist. It may have been deleted by another user."
'Part Number' eq DVPartNumber "Column 'T900004' does not exist. It may have been deleted by another user.
Part_x0020_Number eq DVPartNumber "Column 'T900004' does not exist. It may have been deleted by another user."
Part_Number eq DVPartNumber "Column 'Part_Number' does not exist. It may have been deleted by another user."
{'Part Number'} eq DVPartNumber
{'Part_x0020_Number'} eq DVPartNumber
{Part Number} eq DVPartNumber "The $filter expression \"{Part Number} eq T900004 and Rev eq 3\" is not valid."
{Part_x0020_Number} eq DVPartNumber "The $filter expression \"[Part_Number] eq T900004 and Rev eq 3\" is not valid."
['Part_Number'] eq DVPartNumber "The $filter expression \"['Part_Number'] eq T900004 and Rev eq 3\" is not valid."
[Part_Number] eq DVPartNumber "The $filter expression \"['Part_Number'] eq T900004 and Rev eq 3\" is not valid."
[Part Number] eq DVPartNumber "The $filter expression \"['Part_Number'] eq T900004 and Rev eq 3\" is not valid."

[v-yamao-msft · Accepted solution]

Hi @martinav,

Please try to enter the following code:

Part_x0020_Number eq ‘DynamicContentColumnName’

If you are trying to use a dynamic content in the code, please surround it with a single quote.

Please try it on your side.

Best regards,

Mabel Mao

[martinav]

Thank you so much.  That did work.  The nuacne of syntax is overwhelming.  I do not even know how to define what dynamic content is.  It is still a matter of trial and error.  The next column used in my statement, Rev, requires no quote.  This is my resulting statement that works.  

[martinav · Accepted solution]

I have learned with further experience that the single quotes are required for text columns, and no quotes are required for number columns.  

[casparLi]

End Date ne null

How to rewrite it

[martinav]

@casparLi ,

I'm not quite following your question.  if this is a sharpoint column named End Date, then use End_x0020_Date.  Null good as-is.  That turns into this:

End_x0020_Date ne null

[WillNow]

I just created an account specifically to thank you. This issue was a giant time sink and your post helped me solve it. To sum it up:

If the SharePoint Online column name has a space in it, then the space must be substituted with _x0020_
If what the column name is being compared to is a string, then it must be wrapped in single quotes, regardless of whether it's a hardcoded value, a variable, dynamic content, or an expression

[martinav]

@WillNow ,

I'm so glad it did.  Yea, I have eliminated using spaces for anything.  I now use sharepoint column names like EndDate or End_Date.  Never a space.

I also found that renaming a sharepoint column is very problematic.  The internal column name stays the same.  This is a huge pain in the rear.  If its in development, its better to delete the column and re-create it.  I know thats not an option if its an established list, etc.  

I have found the power platform forums to be absolutely ESSENTIAL!  So much is undocumented, or is documented in a way that does not lend itself to practical application.  Forums provide that context.

Good luck!

Rod

[Anonymous]

For me, the field "Source ID" worked when I used SourceID as shown below:

ID eq SourceID

[andrewsimmans]

I have found where you can determine the correct syntax for the field name which has spaces. In Sharepoint, go to the List Settings and open the field you want to use. If you look at the URL at the end it has "&Field=Field_x0020_with_x0020_Sp" where "Field_x0020_with_x0020_Sp" is the field name for use in Odata queries!

[pva_gg210]

This is an awesome add! In my case the column was Return Result but following your directions, it showed just Result as the name. 

[Monisor000]

If I want to use the spaced column name in the "order by" field, will i still have to use the  _x0020_ you think?

[bnderi]

This is a long-term solution. Thank you!

[cagepeh]

_x0020_ might have worked for <Filter Query.> But it does not work for <Order By>.

Anyone know's how to sort by column name with space?

There's some forum is saying us a filter array to see what is the name used to in the raw output. but is exactly the same column name in "Column Name". 

[SithembisoD]

Just remove the spaces when doing the query. Like 'Customer Name'  becomes CustomerName on the query and it will work

[lashotoSP]

Reza killed it here: 

https://powerusers.microsoft.com/t5/Webinars-and-Video-Gallery/Get-items-OData-Filter-Query-Simplifi...

[jblackcitrin]

I am trying to use this syntax and it's telling me it can't find the column! The column is "XCM PIC" and I wrote as my ODATA filter query:

XCM_x0020_PIC eq 'Last, First'

I have used this type of filter query successfully many times but can't figure out why it won't work now.

Anybody see what I'm doing wrong here?