07-27-2017 05:34 AM
The API can now do an ODATA search ($filter) on the customFields. yeah.
But I also like to $select them.
This does not work:
the customFields/tav syntax is the same for searching, which works:
07-27-2017 10:35 AM
Unfortunately, we do not support $select|$expand on custom fields yet. There are some complexities to overcome using the $select|$expands for custom fields and it is in our backlog. However, we do support $select|$expands on other related objects, such as businessAddress and homeAddress.
For custom fields the syntax will look something like this when we do implement this:
08-03-2017 01:37 AM
I knew about the address expand, that works indeed.
When do you guys have planned to have implemented the expand functionality on custom fields?
We have several clients who wants a contact list with fields in their web application, including custom fields (like kvk number, btw number, etc).
Now we solve these things by making our own Act! API, which allows us to do exactly what we want, but it's a bit reinventing the wheel off course and then it's not with a nice generic OData standard.
09-18-2017 07:39 AM
That is correct, it is still not implemented. The issue is being worked this week. Will keep you informed when the problem is resolved.
Sorry for the inconvenience
10-25-2017 08:01 AM
I was not able to get this into the latest release (API v225). But now that Act v20 /w act.insights have been released, I can spend more time getting this in the build. FYI: All new releases of the API will support Act! v18.0 or greater.
11-03-2017 01:28 AM
thanks for your answer, good to know v18 is always supported.
Can you give an estimation on when it's implemented?