I resolved the issue before posting, but would still like to share, in case anybody else has the same issue in the future. May the google algorithms be with you.
I followed this blog by Gregor, and implemented the counting of records in a similar way.
BUT I added the annotaion @UI.Hidden
which caused my dummy field to be excluded. Removing the annotation caused the issue to be resolved.
I am trying to create a FE analytical list page with an inteactive chart displayed (Hybrid mode). The intention is just testing and getting it to work.
The backend is build using CAP.
When loading the app the following error is given where the chart would go:
[50005] - valueAxis : does not meet the minimum or maximum number of feeds definition.
See the picture Below
- a Chart (qualifier MaterialMovement)
- a PresentationVariant (no qualifier) referencing the Chart
- a SelectionPresentationVariant (qualifier DefaultVariant) referenced in the manifest.json
I tried to solve it by adding the annotations described in the offical documentation here. A version with a dedicated SelectionPresentationVariant can be found in the branch PresentationVariantExtended
.
Even if the app is able to run with a specified SelectionPresentationVariant in the
manifest.json
of the app, would I be able to set a default SelectionPresentationVariant by providing SelectionPresentationVariant without a qualifier?
when observin the Network tab I noticed that a request is sent to the backend, loading the correct dimension (MATNR, only referenced in the interactive chart), not metioning the measure (DummyForCounting). The query in the console does not contain the necessary aggregation for DummyForCounting (the default aggregation type is defined for that field).
When googeling the error i found a note pointing out, that no measure was defined. Even though the note describes the error for a specific apllication, the underlying problem would be applicant to the observed network traffic.
The chart itself should be fine, as it loads as expected in an FE ovp app.
The code is available here
note: the ODatasercive used is using the v2 Version
Best Regards, Tristan