Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Best practices for configuring large data pages in offline-enabled mobile apps

Updated on March 3, 2022

Before you configure offline-enabled mobile apps to store reference data in large data pages, learn more about the related guidelines and limitations.


To ensure that large data pages work as expected, keep in mind the following guidelines:

  • Define separate data pages for each kind of data, for example, a separate data page for expense reports and a separate data page for employee data.
  • Define separate target data pages for multiple user interface elements (on the same user interface view) that interact with the same data source but use different query parameters.

    For example, if a view includes two drop-down lists, one that displays approved expense reports and one that displays rejected expense reports, then both lists source data from the same source data page, but require separate target data pages with corresponding filters, approval=approved and approval=rejected respectively.

    For more information, see Data population for large data pages in offline-enabled mobile apps and Referencing data.

  • If you source a data page by using the same parameters for multiple user interface elements, ensure that the elements reuse the target data page.
  • If you use SQL queries, keep in mind that Pega Mobile Client caches the function that generates SQL queries and not the generated SQL queries themselves. The WHERE clause of an SQL query might differ depending on the number of provided parameters. If you do not provide a necessary parameter, then the system ignores the part of the filtering logic that uses this parameter.
  • If your existing data page uses the pzInsKey key, and you want to create a new report definition, manually define the pzInsKey field in the report definition.
  • If you are creating a new data page, define the corresponding keys in the data type class.


Pega Mobile Client does not support the following features for large data pages:

  • The Select values button for defining filter logic
  • Aliases
    Note: Instead of using aliases, you can access columns by the names that you define in the Column source field when you create report definitions.
  • Calculations
  • Default parameter values
  • The Use Null if Empty strategy
  • Required parameters
Note: You can still use these features in report definitions.
  • Previous topic Improving the synchronization of offline-enabled mobile apps with large data pages
  • Next topic Sourcing large data pages from a report definition

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us