04-05-2016 08:03 AM - edited 04-05-2016 08:04 AM
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?
04-05-2016 08:11 AM
Filtering on custom fields is currently unsupported, but we're literally working on that right now. Stay tuned!
04-05-2016 08:11 AM
Filtering on custom fields is currently unsupported, but we're literally working on that right now. Stay tuned!
04-05-2016 08:17 AM
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
03-21-2017 01:37 PM
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
03-22-2017 08:26 AM
Yes, this has been addressed. You can query for custom fields, for example:
api/contacts?$filter=(customFields/spouse eq 'Pat')
03-22-2017 08:31 AM
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!
03-22-2017 08:36 AM
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.
03-22-2017 08:37 AM
Ok great thanks again!
07-22-2017 03:56 PM
07-26-2017 08:17 AM
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.