Integrate VBO with Data module

VBO does not support Data module yet. Since this is critical for you, I assume you are ready to code VBO support for data tables. I will be happy to help you out.

To support data tables, you must implement hook_views_bulk_operations_object_info. Check views_bulk_operations.module for an example implementation of this hook. Be aware of the following points:

* Views of data tables have a type (attribute base_table in the view object) that is equal to the table name. Therefore, your implementation of the hook above must return one entry per table name. Specifically, the base_table attribute should match the table name. Give the type attribute the value data.
* You will also need to implement actions on the data tables, unless you can live with the generic "Execute arbitrary PHP script" action. Your new actions should be of type data, matching the object info type above. In your actions, you will probably use the Data API to manipulate fields.

Once this is done, edit the VBO style settings in the View admin interface. There, you will find your new actions.

I advise you to create your own module with the implementation of hook_views_bulk_operations_object_info and your action.

Make sure that the base_table in object info corresponds to your table name, and that the type of your object info is the same as thetype of your action info. Then the action will appear in the VBO settings.

You can just populate the $info with several keys:

$info['table_1'] = array(
...
);
$info['table_2'] = array(
...
);

I got VBO to work with the Data module and custom actions, it's pretty straight forward once you know how.

Step 1. Notify VBO about your Data module table using hook_views_bulk_operations_object_info.
Example:

/**
 * Implementation of hook_views_bulk_operations_object_info().
 */
function example_views_bulk_operations_object_info() {
  $object_info = array(
    'example_data_table' => array(
      'type' => 'example',
      'base_table' => 'example_data_table', //Must be Data table name.
      'load' => 'example_load_row', //Function which returns a single row
      'oid' => 'id', //Specific column used as your ID.
      'title' => 'name',
    ),
  );
  return $object_info;
}

Step 2. Create custom actions.

/**
 * Implementation of hook_action_info().
 */
function example_action_info() {

  $info['example_send_email_action'] = array(
    'type' => 'example',
    'description' => t('Send email'),
    'configurable' => FALSE,
    'hooks' => array(
      'any' => TRUE,
    ),
  );
  $info['example_send_delete_email_action'] = array(
    'type' => 'example',
    'description' => t('Delete'),
    'configurable' => FALSE,
    'hooks' => array(
      'any' => TRUE,
    ),
  );
  
  return $info;
}

Step 3. Setup your action functions.

function example_send_email_action($object, $context) { };
function example_send_delete_email_action($object, $context) { };

I just remembered that I had been working on a Data + VBO integration a few weeks ago. Here's the module (it's not published yet, I will probably submit it to the Data maintainers). This module gives VBO access to all data tables, and exposes a new action to delete data records. You can create your specific actions based on the code here.

You will need to use the latest VBO dev (12 hours from now because I just committed a necessary change to support this module).

Thanks Ivan for your contribution! I didn't notice your reply as I was writing mine.

The difference between Ivan's code and mine is that his code addresses particular data tables, while mine provides a generic mechanism for all data tables. If you want to go with the generic approach, be aware that the record title is currently taken to be the id itself, which is not very informative. To get around that, you need to implement hook_views_bulk_operations_object_info_alter():

<?php
function mymodule_views_bulk_operations_object_info_alter(&$object_info) {
  $object_info['example_table']['title'] = 'example_title_field';
}
?>

Setting to fixed unless OP has more issues.

To edit fields, you need to do write an action that exposes a form (called a configurable action). Read the Writing actions guide to find out how.

When you understand how to write configurable actions, you will need to do the following:

* In the action form, retrieve the object_info and use it to retrieve the data table (data_get_table). The returned object can be queried to find the table schema, which you need to iterate on to build a form input for each table field.

* Once you successfully write a submit function for the action, your new action function will be passed the edited fields in the context. Use the data handler (as in the delete action) to update the current record with the new values.

FYI, this is not a simple job, so if there are known fields to be edited, it's better to write code for these explicit fields instead of writing a generic action that will work for any field of any type.

Sorry to open up this thread.

despite the combination of VBO, Data module and data_vbo i still dont get any operation select list to choose a operation from.
A full description of my problem can be found in the Data issue cue:
http://drupal.org/node/997594

Thanks

webform_submissions is a table created by Webform module, correct? If so, it will not be picked up by Data and therefore VBO will not pick it up either.

thanks for your swift reply.

Using the webform_mysql_views-6.x-1.2 mentioned in this screencast:
http://nodeone.se/blogg/finally-webform-submission-data-in-views

webform tables can be picked up by Data.

As for the view i created, i can filter out all the webform submitted data without any problem.

As soon as i pick VBO as style in my view i get a checkbox in front of all my results as well.
Only the selectlist to pick out any operations is not available.

I'm experiencing the same problem (http://drupal.org/node/1041510) but I'm using tw, not the data module. The differences between data and tw module were explained here (http://drupal.org/node/580650).

Re #17: I understand. Not sure how Data deals with adopted tables, I will need to dig deeper in it.
Re #18: Table Wizard is not supported by VBO. Feel free to create a new feature request but I doubt I will get to it any time soon.

Thanks sofar...

Hi!

Did you find a solution to this issue? I am facing exactly the same problem as held69.

Thank you in advanced

@gepeto: I tested the latest dev with an adopted table and received some PHP warnings, but the actions were not empty. I committed a fix to avoid the warnings, so please try it and let me know.

@infojunkie I have tried it, but I'm still getting a blank list there

Cheers

I want a view of webform submissions with bulk operations (delete), any clue how to achieve this????

@gepeto, you need to make sure that data_vbo.module::data_vbo_views_bulk_operations_object_info() gets called and senses your webform submissions table. For example, insert the line

dsm($object_info);

just before the line

return $object_info;

and make sure to have Devel module turned on. What does it print out?

@infojunkie

It gives some warning now:
warning: htmlspecialchars() expects parameter 1 to be string, object given in /home/gener/workspace/elior/sites/all/modules/devel/krumo/class.krumo.php on line 1041.

*
... (Array, 1 element)
o
webform_views_work_with_elior (Array, 5 elements)
+
type (String, 4 characters ) data
+
base_table (String, 29 characters ) webform_views_work_with_elior
+
load (Array, 2 elements) | (Callback) ::load();
#
0 (Object) DataViewsBulkOperationsHelper
*
table_name (String, 29 characters ) webform_views_work_with_elior
#
1 (String, 4 characters ) load
+
oid (NULL)
+
title (NULL)
*
Krumo version 0.2a
| http://krumo.sourceforge.net
Called from /home/gener/workspace/elior/sites/all/modules/data_vbo/data_vbo.module, line 38

Any hints? Is the array coming from the adopted table, how to get the string it needs.

Thank you in advanced

The problem is that the table webform_views_work_with_elior does not have a primary key. Therefore VBO cannot load records from it. To fix this, you need to specify one of the table columns as being the primary key, both in the database and in the Drupal schema.

Oh Thank you, will try this.

Problem is that webform_view_ is based on a MySQL view, not a table, and so doesn't have a primary key. I ran into problems using a webform view for the basis of a bulk mailing because VBO makes assumptions that everything coming from the data module is a table, but it's not. I had to hack a bit of the code in the VBO.module to take care of the case where $object->{$object_info['title']} was not set to permit mass eMails to webform submission eMails. Not sure exactly where this should be addressed, as there are many layers, but not a lot of hooks to 'fix' things for an underlying SQL view as the base data table... There is of course hook_schema_alter, and I tried that in webform_mysql_views, but that didn't get me anywhere, really, and using hook__views_bulk_operations_object_info_alter wasn't enough to provide information for the load function...

May have found the simplest workaround after pouring through some code... a slight change to the data module. See https://drupal.org/node/889306 .

Shawn

Closing old issue again, you opened a new one anyway.