Changing relationship fields on the relationship tab

[Eileen]

We have had requests reasonably often to show relationship related fields on the relationship tab (description, sometimes custom fields against the relationship) rather than fields about the related contact which often don't seem terribly useful.

However, I guess someone somewhere probably finds them hugely useful....

The two possibilities I can think of to avoid some silly tpl customisation are having a setting that specifies which fields to show or removing the contact related custom fields but have an arrow next to the contact name which expands & shows more about the contact

Any ideas?

[Coleman Watts]

+1 for adding relationship fields and custom fields to the display. As it is they are so buried there's hardly any point having them.

[Eileen]

Would you support removing city, state, phone email in favour of them?

[Coleman Watts]

I would, but like you said we'd be likely to get disagreement from somebody about it.
I wonder if that table could be made configurable via a profile. I suppose not since profiles don't support relationship fields.

[Eileen]

No, that would increase the scope a lot.

At the moment it's a case of adding a setting & some tpl / php file edits. The ability to have custom fields would not necessarily be first round either :-( as that involves changing the query & I'm looking for a small manageable improvement here.

[xavier]

Hi,

What about doing it as an extension? modify the default template so it loops through all the fields in the row instead of a hardcoded list, and from the extension on buildform, add a single select all,the,custom,fields,you,want from ... where entity_id in (list of ids from the row) and add the results in the row

(or use hook_civicrm_searchColumns, but not sure if works for relationships)

[Eileen]

Yeah - but it is not less work as an extension to making it optionally available in core & we have been asked for it several times.

[Dave Greenberg]

If description is the main 'missing element', for a simple 'fix' I'd support a core change that would just add it in the first column of the selector below the relationship type label (IF description not empty, <br />$description).

[Eileen]

You're a genius Dave. I couldn't stop thinking about it in terms of an extra column but - yes that would work.