Support Article

Large Data Page fetching in mobile application



User followed below PDN article and implemented procedure to store large data page content for offline mobile application:

User has some supplemental questions regarding the same.

As suggested in the article, when user is injecting the following through the android console:

varmyCustomPopulatorFunction = function(parametersMap, clientStore, onSuccess, onFailure) {
// add pre-process work -> do something with parametersMap here.
vartargetDatapageName = "D_SaleRegisteredVehicles";
var query = "SELECT * from D_SaleRegisteredVehicles";
varqueryParameters = [];
varmyOnSuccess = function(resultArrayOfMaps) {
// post-process work -> do something with resultArrayOfMaps here.
clientStore.runQuery(query, queryParameters, targetDatapageName, myOnSuccess, onFailure);

myCustomPopulatorFunction([],launchbox.PRPC.ClientStore,null, null);

User is not able to see the sub pages in resultArray for D_SaleRegisteredVehicles, for example SaleInfo.SaleLane, SaleInfo.SaleRun & SellerInfo.SellerName.

Error Messages

Data for subpages is appearing when data page is executed stand along, while the value is not available in the mobile browser when debugged in to the console.

Steps to Reproduce

Create a data page with sub pages embedded within it.

Root Cause

A defect in Pegasystems’ code or rules

Pega does not support pages in large data pages by default thus limiting to exploit full functionality of data pages in mobile side.

It makes user to have different data structures on the server side and mobile side.


An enhancement request, FDBK-19793, has been created for consideration by Pega Product Management.

Published June 7, 2017 - Updated August 7, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.