When using complex table fields in the CMS for DataObjects, we are able to set a function called summaryFields() like so:

which allows us to call a complex table field like so:

Notice i have not had to define the summary fields for the object. What CTF does is assumes I want it to use the summaryFields method on MyDO.

However, when using DOM, it intercepts this assumption and instead looks for a static variable called summary_fields on the class.

This means instead (to make it degradable) we have to do:

Is there any particular reason this standard behaviour is being hijacked by DOM, rather than sticking to the SS convention? I'm sure that summaryFields() used to work in DOM and recently stopped.

relevant code lines:
DOM Hijack: DataObjectManager.php line 98
Default behavior: TableListField.php line 257

Perhaps this is so DOM can show different fields to the CTF, but surely it should see if the class has the method summaryFields() first?

I propse (in replacement to lines 97 - 108 of DataObjectManager.php):

rather than it assuming we dont want to use summaryFields() at all.

Ah, ok.

It would be nice to see it pushed into the trunk 0:-)

cheers cheesey.

Also, did you see this issue: http://silverstripe.org/dataobjectmanager-module-forum/show/282867?start=0#post282894

Any plans to add set_source_id() to the core?

EDIT:
Actually, i just noticed that DataObject has a method summaryFields(), so my condition will always be true. But, the inbuilt summaryFields looks for the summary_fields static anyway. So it can end there really. [line 3157 of DataObject.php]

it seems like your code is slightly redundant and restrictive as it doesn't facilitate the use of a summaryfields decorator :/

So really I think the best idea would actually to remove that code (line 97 - 108 of DataObjectManager.php), rather than modify it.