CiviCRM Community Forums (archive)

I've found that one of our unit tests (a test we've actually had for a while) is failing because an API call it does is not returning the requested custom data. It works from the API explorer, and the information shows in civicrm/contact/view, but when the example code is pasted it doesn't return the custom field. It also doesn't return the custom field when I put the same params into drush cvapi.

API explorer call:
/civicrm/ajax/rest?entity=Contact&action=getsingle&debug=1&sequential=1&json=1&contact_type=Individual&contact_sub_type=Student&return=custom_32&contact_id=90948
Sample code from that:
$params = array(
  'version' => 3,
  'sequential' => 1,
  'contact_type' => 'Individual',
  'contact_sub_type' => 'Student',
  'return' => 'custom_32',
  'contact_id' => 90948,
);
$result = civicrm_api('Contact', 'getsingle', $params);
drush cvapi:
drush cvapi Contact.getsingle sequential=1 contact_type=Individual contact_sub_type=Student return=custom_32 contact_id=90948
getvalue is the same, it returns the custom value in the API explorer but not in code or drush. The relevant CustomValue.get call works in all three of these places.

We've had similar issues with Activity custom fields, but that was fixed by passing the activity_type_id. I'm already passing the contact type and subtype the custom field applies to, and it's the same with or without.

Can you see anything wrong with the code above? Is this something known not to work in 4.4.6?

Thanks,
David

That worked on the command line. I had to change part of the bootstrap for our unit tests and in my standalone API call testing script to get it working there- it was supposed to be logging in uid 1 but obviously wasn't doing it properly.