Fix display field not working when using non-default table in controller

[mentisy]

When there's a controller that uses the non-conventional name, one needs to use the defaultTable property to override what model is fetched in the controller. In this scenario, the display field cannot be fetched because it tries to get the model using the name of the controller. This model won't exist, so throws error.

Scenario:
A controller is named LocationsAliases and uses defaultTable value Locations. The app, before this fix, will try to get the entity of LocationsAliases, instead of Locations.