I am trying to realize a UI5 app, where visibility and editability of each control in my view is controllable through a customizing table in our SAP ERP.
At this time my idea is a entity type which contains these information for each property. Therefore my entity does have two additional properties for controlling visibility and editability. E.g.:
This concept works, but it will bloat my entities. For me it looks more like a workaround, than a elaborate strategy.
Does someone have experiences which such a situation?
Over the past two years, it turns out that complex types are the most flexible way to solve this problem.
As Marc already wrote, this is exactly how we do it today.
I am sorry for the confusion. Our entities (e.g. Employee) consist of several complex types. Each complex type (e.g. Status) has a value (e.g. 5) and sometimes a descr (e.g. declined) (and sometimes multiple values + descr). The name of the complex type (e.g. Status) can then be the key to get the corresponding config set. The config set stores the editability, visibility and a translated label of all properties from a single complex type.