Community
Showing results for 
Search instead for 
Do you mean 
Reply

OData filters on field X eq 'something', gets back results where it's null

Highlighted
Copper Contributor
Posts: 147
Country: Netherlands

OData filters on field X eq 'something', gets back results where it's null

Bug?

 

Request:

https://actdev01.actweb.nl/Act.Web.API/api/contacts?$filter=businessPhone eq '(212) 555-2485'&$select=businessPhone,fullName

 

Response:

[
{
"fullName": "Allison Mikola",
"businessPhone": null // ???
},
{
"fullName": "Chris Huffmanss",
"businessPhone": null // ???
},
{
"fullName": "Melissa Pearcing",
"businessPhone": "(212) 555-2485"
},
{
"fullName": "Betty Browser",
"businessPhone": "(212) 555-2485"
},
{
"fullName": "Sarah Whiting",
"businessPhone": null // ???
}
]

Greetings,

ACT Certified Consultants
TendenZ
the Netherlands
Employee
Posts: 80
Country: USA

Re: OData filters on field X eq 'something', gets back results where it's null

The API has struggled build Act! filters from OData syntax.  We are trying to build test for these filters to find them quicker.  This filter has been fixed in 

the current release of the API,   However phone related negative lookups still do not work, because of a bug in the SDK framework, such as  

 

   ?$filter=(businessPhone ne '(602) 745-8541')&$select=businessPhone,fullName

 

I have a request into the Act Premium team to fix this.

 

However,  The query you are doing will work in the new release of the API.  I would recommend getting off of .279 and moving to a new version.  I will be pushing a new API version that fixes most of your issues, maybe being of next week I will have a build for you.