Author Topic: activity api (Read 768 times)

lcdweb · January 18, 2012, 11:47:11 pm

I'm getting unexpected results from the activity get api.
passing:

Array
(
    [version] => 3
    [contact_id] => 10
    [activity_type_id] => 46
)

I receive all activities for the contact -- i.e. it's not filtering on type.

Eileen · January 19, 2012, 02:31:30 am

Yeah - that's the way the v2 version was written - it calls a fairly unsympathetic core function. The v3 api defaults back to a generic API call if you pass in source_contact_id instead of contact_id but that call doesn't support assignee_contact_id.

We have a bunch of generic API functions & they have standardised behaviour but aren't much more than an SQL query on a single table. The more elaborate BAO get functions based on the query object can do more but are more erratic

xavier · January 23, 2012, 07:50:25 am

Hi,

Part of the problem is that the way the tuples activity contact are stored is showing its age (spread between various tables...). Eileen & Lobo discussed about refactoring to a better solution (a single table with a contactid, role ENUM, activity id) if I recall.

That would likely speed a lot some requests (both for case or the activity tab for instance), but that's not broken enough to have had someone willing to have a go at it... so far...

X+

CiviCRM Community Forums (archive)

News:

Author Topic: activity api (Read 768 times)

lcdweb

activity api

Eileen

Re: activity api

xavier

Re: activity api