Invalid base_field "id" defined in maestro_all_flows view

Sadly, after a few updates on the view, it looks like the base_field value is set back to id instead of the expected process_id.

Hopefully, a simple export/import with the right base_field value fixes the problem.

But will probably have to be done again every time the view is updated.

Ok, looks like the above problem can be fixed with a simple hook:

function vbo_maestro_views_data_alter(&$data) {
  if (isset($data['maestro_process'])) {
    $data['maestro_process']['table']['base']['field'] = 'process_id';
  }
}

Fix as been added to the VBO Maestro → module.

Correct, you can override views config as you see fit.

Probably also best to not reuse core Maestro views just to be sure.

Closing.

I would not say that it works as designed as it doesn't work in some cases, but ok I'll keep my patch applied.

Actually the base field should be corrected in the MaestroProcessViewsData class.

Would you mind having a look at it again? Just updated the MR accordingly.

Otherwise could you explain the reason we need to keep that invalid base field in place?

Sorry, yes, you are correct. I had looked at this as if we were swapping the field in the Process entity. I'll commit this.

The Maestro workflow history view can now use Views Bulk Operations natively, thanks!

Automatically closed - issue fixed for 2 weeks with no activity.