![]() To work around this issue, I had to use ResponsiveTable instead of AnalyticalTable. You can observe that “Stock” column in the below image is empty.įrom my investigation, AnalyticalTable requires simple aggregation annotation as shown below: annotate CatalogService.BooksAnalytics with you cannot display charts with this simple annotation. However, with this setting, measures are not displayed in the table. annotate CatalogService.BooksAnalytics with ],īy default, the table type for the Analytical List Page is set to “AnalyticalTable”. Without these annotations, Fiori tools may raise error indicating the absence of a suitable entity for ALP. These annotations are crucial for Fiori tools to properly recognize and support the Analytical List Page (ALP). The first block focuses on enabling aggregate functions. I will explain the annotations added by dividing them into four blocks for clarity. Service CatalogService entity BooksAnalytics as projection on my.Books using my.bookshop as my from './db/data-model' The data model is exposed to the service as is. ![]() I have created a very basic data model based on a Books entity generated by ` cds add samples` command. To build a very basic ALP app on top of CAP OData V4 service as shown below. ![]() I discovered this solution in deepak_singh99‘s GitHub repository, so I want to give credit to him. In this blog post, I am going to demonstrate how to annotate CAP service to enable the display of an Analytical List Page (ALP). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |