Added a note to a current bug

[John-H-Smith]

If using a line item criticality with a qualifier, at least one field without a qualifier must be included in the view to take effect. This is probably a bug, maybe should be escalated to the devs.

[cla-assistant[bot]]

All committers have signed the CLA.

[cla-assistant[bot]]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[KvM2]

Hi @John-H-Smith , thanks for your contribution. We appreciate it and will look into this.

[JannaLisa]

Hello @John-H-Smith , I'm still waiting for a response from my team on this. Will let you know as soon as I have an answer.

[GwendalMoreau]

@John-H-Smith : this seems to be a bug and should be treated as such (and not a a note in the documentation). Could you share your use case or raise a ticket?

[John-H-Smith]

Hi @GwendalMoreau , Alright, I will share my use case. I created a cds view entity in the backend with associations to a child view. As that child view should be on its own table in the object page, I've set a qualifier on all fields and the view and even the line criticality. But the line item criticality wasn't shown on the table, so I added (in trial) a field without any qualifiers. And then, the criticality was shown.

[GwendalMoreau]

@John-H-Smith : could you share your application metadata?

[OlMue]

Hi @John-H-Smith, could please give @GwendalMoreau some information on the metadata? Thank you! :-)

[OlMue]

Hi there 👋 There's been no activity on this issue for a while, so we're closing it. If you've further information to provide, please comment below and add that information. We'll review it and reopen the conversation if necessary. Until next time, thanks!