cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Grouping and Subtotal in Fiori Elements List report using OData V4 Service

Partha24
Discoverer
0 Likes
1,964

Hello Experts,

I have built a Fiori Elements-based list report application using an OData V4 service. This service consists of CDS views exposed as entities. I have a requirement to implement grouping and subtotals in the Fiori report. I followed the documentation and changed the table type to an Analytical Table in the manifest.json as shown below.

Partha24_0-1738016382024.png

 

Also I have maintained local annotations as per SAP  documentation.

 <Annotations Target="SAP__self.myEntityType">
 <Annotation Term="Aggregation.ApplySupported">
   </Annotation>
<Annotation Term="UI.PresentationVariant">
  <Record Type="UI.PresentationVariantType">
    <PropertyValue Property="GroupBy">
      <Collection>
        <PropertyPath>SalesOrder</PropertyPath>
      </Collection>
    </PropertyValue>
   
    <PropertyValue Property="Visualizations">
      <Collection>
       
        <AnnotationPath>@UI.LineItem</AnnotationPath>
      </Collection>
    </PropertyValue>
  </Record>
</Annotation>
</Annotations>

But when I try to run the app I am getting the error as below.

Partha24_1-1738016573568.png

So if anyone has some idea on how to overcome this, please do provide the inputs.

Thanks in Advance!!!

Best Regards,

Parthu.

Accepted Solutions (0)

Answers (1)

Answers (1)

MioYasutake
SAP Champion
SAP Champion
0 Likes

@Partha24 

Does your CDS view have fields annotated with @Aggregation.default ?

https://help.sap.com/docs/ABAP_PLATFORM_NEW/cc0c305d2fab47bd808adcad3ca7ee9d/5e5d319bd1a74552b99a36d...

 

Partha24
Discoverer
0 Likes

Hi @MioYasutake,

Yes I have maintained 

@Aggregation.default: #SUM

MyField,

But still no luck .Even Grouping is not appearing when I run the application. Getting the same error as I described above.

MioYasutake
SAP Champion
SAP Champion
0 Likes

@Partha24Now I remember that in 2023, I had a similar issue and raised a support ticket. They said that the Analytical Table was not supported with an OData V4 service developed using RAP. A fallback approach is to use OData V2 instead.