[5.x]: Eager loading requires the original name of a field instead of its renamed value about cms HOT 3 CLOSED

Hi, thanks for reaching out!

I just tested this with an entries field with the original handle of originalModel, which has the handle changed to model in the entry type. If I eager load model I get the related entry (if one is added to the entry) and an empty collection if there aren’t any entries added to that field.

I’m assuming that in the recording you attached, the model is the renamed handle and modelsLandingSectionsMultiple is the original one. If that’s correct, then the result you get for page.model when you query with modelsLandingSectionsMultiple is correct - you get the EntryQuery because you haven’t actually eager loaded the model.

I hope the above helps. I’m going to close this now, but feel free to reply if I misunderstood what you were saying!

from cms.

Hi @i-just, sorry about mugging up the issues feed, Thanks for the support and feedback! got it working!

from cms.

Great news. Thanks for confirming!

from cms.