Skip to Content
Technical Articles

How to reset the limit of rows in Fiori apps

A number of reporting Fiori applications available in the Fiori Launchpad are using the query engine. Such applications have an implicit limit of records set to 10000. This is for performance reasons, but the problem is that you will get an incomplete set of records without any notice.

To get the full list of records, you should set the parameter limiting the number of rows to value “-1” so that the application does not restrict the selection.

You have access to the parameters without changing the application itself, as the target mapping allows to provide some values to the application.

First of all, you have to create a Customizing transport request that will host the changes.

Then you have to open the Fiori Launchpad Designer with transaction /UI2/FLPD_CUST or /UI2/FLPD_CONF (depending on which one you used to define your catalogs). Be sure to open it in the same SAP mandant as the one where you created the transport request.

Next step is to identify the original application to be changed. The goal is to change it once and get the change everywhere the application is used. In the left column, specify a catalog containing the tile linked to the Fiori app, then click on the button “Target Mappings”.

In the list of target mappings, select the application (the navigation type is always SAPUI5 Fiori Apps) and click on the button “Original” which is the last one in the bottom toolbar. This will show you the original application in its standard SAP catalog.

By changing the parameters in the original location of the Fiori App, you will get the benefits of the change everywhere it is used. Click on the button “Configure” to access to the configuration of the app.

If you see the parameter XQUERY in the list of additional parameters, then the Fiori app is using the query engine and you will be able to influence how the data is selected just by providing new parameters in the list.

As we already mentionned, the number of rows is implicitly limited to 10000, as the number of columns is also implicitly limited to 50. If you want to get rid of those limitations you have to provide another value explicitly.

Click on the button “Add” two times and add the parameters XDATALIMIT_ROWS and XDATALIMIT_COLS. The value “-1” means no limit. Of course it is possible to specify another value depending on your need, but keep in mind that no message will inform the user that the number of rows/columns has been reduced due to some parameter.

 

Now you just have to transport the Customizing transport request to get the modification in Production environment.

This is quite easy to do, but I spent some time to get the info about it. That’s why I wanted to share it with the community so that you can find the way to change the number of rows. I guess that most of the customers will want to get the complete list of results.

 

2 Comments
You must be Logged on to comment or reply to a post.
  • Another one of those blogs that I’m saving under “how to”.   I do wonder on the performance of this.  I’m assuming loading more rows will take more time.  It’s probably another it depends answer.  On how much processing is going on in the backend, and when the FIORI app gets the data.  All at once?  By paging and pulling it in by pages?   I don’t know enough to say that.

    It seems like at some point, I’m going to need this option.

    Thank you for taking the time to write about it,

    Michelle

  • The problem is described in the SAP note 2557541.

    It is said in the note that we can add the parameter directly in the url.

     

    Note: it works well for most of Fiori applications that we use, but it happens not working for the Asset History Sheet.