CiviCRM Community Forums (archive)

What is the task being performed that would use this relation? For example, if the task is: "Case manager is at manage case screen and wants to navigate to the appropriate book nodes (documentation?)", then you could do it with a custom field textarea, and copy and paste the urls of the book node(s) into that field. Low-tech but depends how much more you need.

I can't think of an off-the-shelf way to do it but you could write a little module that implements hook_nodeapi (drupal hook not a civi hook) for the view action and looks up all cases that reference the current node, then add that to the node for display.

To make it more robust/user-friendly, on the civi side make the custom field a multi-select widget and implement hook_customFieldOptions in your module to have the select options be all the book nodes (node id for the key, node title or whatever for the display value).

Alternatively, have your module present a custom field on the drupal book nodes to select from all cases, then on the civi side implement hook_caseSummary to display links to the nodes.

I think the first solution suggested is best--just directly relate nodes to Cases. You would need to custom code this in Drupal using hooks to fetch/display the information on both ends, as demeritcowboy wrote.

That's probably correct. There isn't an API for cases either, last I checked.

Therefore you would have to write the SQL to access the data you need.