Fiori Elements - List Report. Caching Feature

[#1]

Hi,

in Fiori Elements List Report, every time we scroll down. We will do another request to the back-end to request the "next page" data. Now, this is I common in a web application. But me, coming from an ABAP background, this is like a SELECT in a loop. Especially if we do quite complex logic for the report.

Is it ok to do this? Or is there a caching feature for Fiori Elements List Report (or the SADL), I checked in this class CL_SADL_GW_GENERIC_DPC method _GET_ENTITYSET, I see the following code:

...     
  IF mv_is_crp_cached_request = abap_true.
          get_cached_entityset( EXPORTING io_tech_request_context = io_tech_request_context
                                IMPORTING et_data = et_data es_response_context = es_response_context ).
        ELSE. "normal request processing
...

I tried to debug and seems every new request mv_is_crp_cached_request is never true.

Is there a caching feature that we can use for the paging? (Another way is to build some CDS and use push down method).

Thank you.

[nabheetscn · Accepted solution]

Hello Suwandi Cahyadi

This is not like a select in loop, it is more like paging you return only a set of records which actually enhances the fronted experience. Imagine you are waiting for you 1000 records with complex logic to be loaded in the browser for many minutes/hours etc. Rather than that you get a limited set of records and as you scroll the next set are loaded. Gateway does have a feature for caching but that is under certain circumstances. Read this for more details.

Thanks

Nabheet