Skip to Content

Issue with metadata annotation: field-control (deep entity)

Hi all,
I think I might have found an issue with metadata annotations.
I'm using Attribute sap:field-control to describe the fields that are editable / mandatory / etc..
According to this page, it should be possible to refer to a deeper (expanded) entity for the field-control value, but my Smartform doesn't automatically react to these attributes Am I missing something?

Below is a collage with the different screenshots, to clarify
And this is the slack thread for the same question:

image.png (186.2 kB)
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Feb 10 at 11:11 PM

    Hey Christophe,

    when you say that your SmartForm does not react on the given FieldControl value - I assume you mean the SmartField in your SmartForm, right?

    If yes... makes always sense to check the control-specific annotation documentation, as here the supported annotations in general and - in certain cases - the supported aspects are mentioned.

    When you look here: you can read one detail which might be the "anwer":


    Defines the rendering of the field from a dynamic value that can be provided as a path by referencing another Property within the same EntityType.

    So having a path with a navigation property in the fieldcontrol is - according to the SmartField documentation - not supported.


    Add comment
    10|10000 characters needed characters exceeded

    • Hello Christophe,

      long time ago...

      You ask: So whether or not the nested property can be read is control-specific then?

      Yes, indeed. The page you found describes the OData Specification, but doesn't reflect the real implementation. The implemented annotations ( of annotations...) are documented in the control-specific API Reference in the UI5 Demokit.