Handling of foreign key fields

Hi, 
I have been using the component creator extensively for a long time, and I'm generally very pleased with it, but: 

Recently the handling of foreign key fields was changed, so that when the field is loaded in the model, and returning $this->item->fkey_field in the view actually gives the text-title from the foreign key table, instead of the foreign key id. While I understand this can be useful in some cases, it is very bad anytime you need to get more than just the title-field from the foreign key table. 

In my opinion the best solution would be to return the whole foreign-key object (all fields in the foreign key table) as the fkey_field. This way the developer has access to everything in the foreign key object, and has the possibility to chose which fields he want to use in the template overrides. When displaying like a dropdown-list, or on the list view in the component, the display-field can still be used as an alias. 

Any other views on this her at the forum?

Jonas 

Im having the same issue. I have to comment the code that loads the Value of the key field instead of the ID, which is much better for me at least.

As i do extra stuff with that ID afterwards. Maybe an opt-in to select what we want to get?

Hello!

Thanks for your feedback. I'm moving this thread to feature suggestions and will inform our developers so they can study it.

Best regards,

Andrés.

Thanks, Andrés, this is probably my biggest issue with the component-creator now, which I otherwise think is great! Bug-reports are handled very quickly and nicely, I've been reporting quite a few lately, and VIctor seems to be fixing them more or less as soon as they arrive. This issue is a little different, though, so I thought I'd post it here first. 

I too would like to see an option for the whole foreign key object to be available so we can have access to all the fields.  But I think this should be an option when foreign key is selected, if a developer doesn't want or doesn't need the whole object, there is no reason to load it.