Why is it not possible to use the RAP dynamic feature control for hiding fields?

[Andreas_M]

Hello community,
I'm interested in the design decision why the dynamic feature control inside RAP doesn't support hiding fields. It is really impractical to implement field control with SADL/virtual elements to hide fields and to implement the dynamic feature control for make fields read-only or mandatory. Reading trough documentation I think it was possible in OData v2 with the field-control annotation but RAP doesn't allow the hidden value (0) as it maps it to another value inside the framework.

See documentation for OData v2:

andre.fischer maybe you can give some insights about this.

Thanks

Andreas

[sandeep_rs]

Hi,

Maybe I miss the point but why is UI.Hidden=<path> not a good option..?

Thanks and Best Regards,

Sandeep

[Andreas_M]

Hi Sandeep,

thanks for your answer. If i just want to hide a field I think it is a good option. But if you have field control I don't understand why it is separated and I have to define the rap feature control and additionally the UI.Hidden Annotation. We have hundred of fields which makes it a little bit ugly. Why isn't it possible to control hidden feature over RAP feature control. I would be interested in the design decision. Because it seems that for OData v2 there was the possibility to control it at one spot.

Best regards
Andreas

[Nadia_S]

Totally agree and such a pity that nobody answered. If you implement the hidden with the annotation for each field, it doubles the number of the fields in the entity and the logic for the field attributes is split in two different places, one for mandatory, read-only and another for hidden.

[Andreas_M]

Hi Nadia, thanks for your feedback. Do you have any contacts to the RAP team or the UI5 team to discuss this topic? It was so nice with oData v2. I would also have two other topics regarding feature control to discuss or to be improved by the framework. Thanks & Best regards Andreas