CiviCRM Community Forums (archive)

We've been seeing some issues with Drupal Views and custom CivicRM fields on a site we're building using CiviCRM 4.4.6, so I thought I'd test using the 4.5beta and see if they'd been fixed. Apparently not, at least on my local install of 4.5beta2.

Not sure what the position is with Views integration code, whether it is seen as a community contribution or as a core thing, but thought I'd report it anyway:

1. Custom country fields: If you create a custom field as a country select, then display that field in a view, the Views field label must be present and match the CiviCRM field label in order for the country name to be displayed. If no label is displayed, then the country data gets displayed as a 4 digit code. If a label is used that does not match the CiviCRM field label, nothing gets displayed at all, other than the label.

2. Custom file fields: If you create a custom field as a file upload field and then display the field in a view, the view will display the URL rather than the filename.

3. While testing this using my local 4.5beta2 install, i noticed that when trying to filter a view by activity type, Views did not provide a list of activity types, thus making it pretty tricky to use the filter. I also noticed that displaying the activity type field rendered an ID number and not the name of the activity type.

This tendency to display values rather than labels could well extend to other fields, we've not had time to test further.

Given that Views is very widely used in Drupal set-ups, and as I understand it is being moved into Drupal core for version 8, I would say that having a rock solid Views integration for CiviCRM is pretty important.