CiviCRM Community Forums (archive)

OK, so the big challenge for the api going forwards is to get the acceptable fields, mandatory fields & getfields return function all working together.

So far on the activity api I have discovered that we advertise (through getfields)
Activity Type (activity_type)

but require one of these 2 which are not advertised:

'activity_name'
'activity_type_id'

Do we completely abandon trying to use exportable fields - as used in activity api?

Hi,

I think it would be worth making a time to talk this through on IRC - although it might be worth trying to articulate some of the problems / the goal here first.

It's probably also worth coming up with a list of api sore points / things we want so we can figure out if there are some priorities (and whether anyone actually has time to work on them).

Oh #2 - it looks like if we push all date fields through this function

            $params['activity_date_time'] = CRM_Utils_Date::processDate( $params['activity_date_time'] );

it will deal to the random date handling currently in place