Defining View Object Control Hints
View objects use the control hints from their associated entity objects, so you would not normally need to define them at the view object level. It is better to define them for the entity object so that displays are consistent throughout the application.
However, you can define the same control hints for view objects as you can for entity objects. If there is a control hint defined for a view object, it overrides the one defined at the entity object level.
There may be cases where you would want to override the entity object control hints for a specific view, such as the following:
You may need to display the data differently in different views. For example, in an application’s entity objects, you may define the label for all of the primary key items as ID, such as for ProductId, SupplierId, WarehouseId, and so on. But if you have a particular view that displays the IDs of multiple referenced entity objects, for that view object you may want to override the entity-level label for those IDs, as listed in the slide.