Community
Showing results for 
Search instead for 
Do you mean 
Reply

OData filter for customFields on Contacts

Accepted Solution Solved
Copper Contributor
Posts: 123
Country: Canada
Accepted Solution

OData filter for customFields on Contacts

[ Edited ]

I'm trying to filter contacts on a customField called clientid like this:

 

api/Contacts?$filter=(customFields/clientid eq '119428')

 

I also tried this - as it looked like that might be what I needed to do:

api/Contacts?$expand=customFields/clientid&$filter=(customFields/clientid eq '119428')

 

Getting 400 / Bad Request - The parent value for a property access of a property 'clientid' is not a single value. Property access can only be applied to a single value.

How do I filter on the custom field called clientid?


Accepted Solutions
Solution
Accepted by topic author e_hoog
‎04-05-2016 08:17 AM
Employee
Posts: 236
Country: USA

Re: OData filter for customFields on Contacts

Filtering on custom fields is currently unsupported, but we're literally working on that right now.  Stay tuned!

View solution in original post


All Replies
Solution
Accepted by topic author e_hoog
‎04-05-2016 08:17 AM
Employee
Posts: 236
Country: USA

Re: OData filter for customFields on Contacts

Filtering on custom fields is currently unsupported, but we're literally working on that right now.  Stay tuned!

Copper Contributor
Posts: 123
Country: Canada

Re: OData filter for customFields on Contacts

Thanks again for your lightning fast responses Xavier!

This will be very important for us and I'm glad it's coming down the pipe.

We have reference to First and Last Name so I guess what I could do is filter for contacts that match first and last names and then in the program i'm consuming the API with I can just get the contact that has the matching clientid.

Anyways thanks again!  Really looking forward to the future changes.

-Eric

Copper Contributor
Posts: 123
Country: Canada

Re: OData filter for customFields on Contacts

Hey is there any update on this?  Is querying on Custom Fields supported yet?  Is there a list I can subscribe to for developer updates on the API?

Thanks1
-Eric

Employee
Posts: 236
Country: USA

Re: OData filter for customFields on Contacts

Yes, this has been addressed. You can query for custom fields, for example:

 

api/contacts?$filter=(customFields/spouse eq 'Pat')

Copper Contributor
Posts: 123
Country: Canada

Re: OData filter for customFields on Contacts

Ok thanks for the quick response as always!

 

Is there any way for me to subscribe to updates on the API other than checking in here?

I was waiting for the feature to query on customFields but am also waiting for the ability to interact with Custom Sub-Entities, is that something that you guys are working on?

Basically my boss doesn't want to upgrade to the new version of Act (we're still on 2013) until that feature has been added.

Let me know if have a moment.  Thanks again!

Employee
Posts: 236
Country: USA

Re: OData filter for customFields on Contacts

We don't have subscription based notification for change sets in the API currently, great feedback though.  Currently best is to check developer.act.com and the API documentation and/or forums.  

 

Custom sub-entitites in the API is not being worked on yet.

Copper Contributor
Posts: 123
Country: Canada

Re: OData filter for customFields on Contacts

Ok great thanks again!

New Member
Posts: 1
Country: USA

Re: OData filter for customFields on Contacts

I need to query a custom field that has a space in it, specifically 'is approved'. I've tried with the space and tried substituting the space with %20, x0020, and _. Nothing has worked yet. Is it possible to query a field with a space, or should I get the name of the field fixed in the program?
Employee
Posts: 38
Country: USA

Re: OData filter for customFields on Contacts

Replacing the space with x0020 is the correct way to handle this for OData, however the API is failing when building the query for Act!  I have found the issue and corrected it.  The fix will be in the API release version .194.