support for custom fields?

It should. Mostly I just pass the names of CiviCRM profile fields back to CiviCRM and let it figure out what to fetch. For a custom field in CiviCRM 1.x, the name looks something like 'custom_5', where the "5" is the ID of that custom variable.

This should work work with the CCK stuff. If it doesn't, it's a bug, and by all means report it.

I'm fairly new to debugging Drupal and even more so to debugging CiviCRM issues, so bear with me. I've been trying to figure this out for custom fields too. I checked the bug reports for the CiviNode and CiviNode CCK projects but didn't see anything related to this issue. I've also tried lots of searching here and on civicrm.org.

So I've created a new view and am selecting "CiviCRM Contact" as the fields to pull. For the handler I choose "contact field" and put the name of the field in the option box. This works great for native civicrm fields, but not for custom ones.

I've tried using the name of the custom field and also the id, formatting it the following way "custom_ID#"

What happens is the civicrm ID number of the individual shows up for where the custom field data should be, as well as for those instances with the native civicrm fields (first_name, middle_name, etc.) where the data is null. Going back to the custom field...I know that the data for most of the records I'm listing is not null, so something should be there other than the civicrm ID #.

Hopefully, I'm just missing some easy step somewhere...And depending on how technical this gets...I'd be happy to help write some documentation on how to pull individual civicrm fields into Drupal.

Thanks in advance.

Cheers,
Kristin