Fiori Elements: @UI.CreateHidden with $Not + $Path expression is not working

[sandeep_rs]

Hi everyone,

I'm currently facing an issue with a Fiori Elements List Report application based on CAP (Cloud Application Programming Model). I’m trying to conditionally hide the “Create” button using the `@UI.CreateHidden` annotation with a $Not + $Path expression, like this:

annotate CatalogService.Books with @(
  UI.CreateHidden : { $edmJson: { $Not: { $Path: '/CatalogService.EntityContainer/FeatureControl/createEnabled' } } }
);

The EDMX output looks correct:

<Annotation Term="UI.CreateHidden">
  <Not>
    <Path>/CatalogService.EntityContainer/FeatureControl/createEnabled</Path>
  </Not>
</Annotation>

The singleton entity FeatureControl is correctly exposed and returns the following response:

{
  "createEnabled": false,
  "createHidden": true
}

When I reference createHidden directly with a simple $Path, it works as expected and the Create button is hidden. However, when using the $Not + $Path version, the Create button remains visible.

Has anyone successfully used $Not expressions in annotations like `@UI.CreateHidden` in a Fiori Elements List Report?

Any insights or workarounds would be greatly appreciated.

UI5 version: 1.135.0

Git repository link: https://github.com/miyasuta/cap-feature-control

[sandeep_rs]

Hi, Path not working would have been understandable but Path is working but only not when NOT is used seems a bug to me 🙂 Pls create a SNOW incident referencing this against CA-UI5-FE. Thanks and Best Regards, Sandeep

[Willem_Pardaens]

There are similar issues with the normal 'UI.Hidden' of fields. It worked in v1.132 but not in 133-135. In the next version which is due to be released this week (1.136.0) it looks to be working again so maybe it will resolve itself in your case as well..?