CiviCRM Community Forums (archive)

The current implementation of Views 2 integration does not allow to use custom fields - boolean variables as argument, filter or sort when creating a view.

Temporary workaround is to use Integer data type - selector - two values for custom field.

Later (when this will be fixed) it will be easy to transform this data back to logical by exporting and importing it as another custom field.

Regards,
Danila

This is an issue with custom field datatypes not getting correct handlers in civicrm.views.inc, in function civicrm_views_custom_data_cache($data, $entity_type, $groupID, $subType, $style)
...
$data[$currentgroup['table_name']][$currentfield['column_name']] = array(
'title' => $currentfield['label'],
'help' => $currentfield['help_post'],
'field' => array(
  'handler' => civicrm_get_field_handler($currentfield['data_type']),
  'click sortable' => TRUE,
  ),

'argument' => array(
'handler' => civicrm_get_argument_handler($currentfield['data_type']),
),

'filter' => array(
   'handler' => civicrm_get_filter_handler($currentfield['data_type']),
   ),

'sort' => array(
'handler' => civicrm_get_sort_handler($currentfield['data_type']),
),
);
For example, if one has a custom boolean field for a contact, and wants to use this field as a filter in views (for example, showing in the view only people who had finished a particular educational program), Views 2 will throw error

Error: handler for civicrm_value_profile_name_3 > graduated__29 doesn't exist!

However, using integer custom fields in filters works - meaning some code for handler allocation is working correctly.

I have not yet found a way to set breakpoints in PHP to check what's going on inside the code (did not spend time to build PHP testing environment), so my previous updates were tested as a complete code without looking step-by-step inside.

I'm now importing data from old datasource - and I need to finish it so that users could start using new system for data entry. I make imports partially, by groups of fields, and check if I can build something useful using Views along the way. Currently only "Who works where" grouping works as I want.

After I finish Import I will work on presentation - and then I will need a lot of functionality from Views integration, which I will contribute back.

Regards,
Danila

Thank you, Walt, I will check these tools.

Regards,
Danila

I may be in the wrong place to ask this but I'm not a drupal or civicrm developer so if you can point me in the correct direction I would appreciate it.

Running drupal6.10 with Views6.x.2.3 and civicrm2.2.1.
DanilaD,

When trying to create a filter in a view of  civicrm contacts using a customer boolean field I get the same error as you describe:

Error: handler for civicrm_value_src_child_8 > publish_public_info_42 doesn't exist!

I applied your patch to civicrm.views.inc:

new:/home/flo-new/www/sites/all/modules/civicrm/drupal/modules/views $>diff civicrm.views.inc civicrm.views.inc.orig
2805c2805
<         return 'views_handler_argument_boolean';
---
>         return 'views_handler_argument';
2832c2832
<         return 'views_handler_filter_boolean';
---
>         return 'views_handler_filter_boolean_operator';
2859c2859
<         return 'views_handler_sort_boolean';
---
>         return 'views_handler_sort';



 but it did not fix the problem.

Any hints?

- Kevin

Hello, kdog.

This means Views had not yet captured the change you made to code. Try going to Administer › Site building › Views › Tools and press "Clear Views cache".

Regards,
Danila

Could it be that you have old CiviCRM code in the modules folder? Not deleted from previous version?

Could you please check that you do not have a kind of backup copy that you created before applying patch? If present, it should be kept as far away from modules foles as possible.

Could you please attach your civicrm.views.inc here?

Hello, kdog.

I have just loaded CiviCRM install from Sourceforge, and it contains correct version of civicrm.views.inc. You do not need to apply patch to it, as this was a patch for 2.2.0, which is already included into 2.2.1.

I think applying this patch to 2.2.1 damages all thing. Please try to use the civicrm.views.inc supplied in civicrm-2.2.1-drupal.tar.gz.
Also, just clearing Views cache would be enough - Drupal cache and Apache server do not participate in Views regeneration.

Regards,
Danila