Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Defining data page access

Updated on April 5, 2022

To optimize data page performance and memory use, manage how the system responds when a requestor attempts to access a data page, or enable paging on the server for data pages that are sourced from a grid. The Page options section displays for read-only data pages with a scope of Requestor or Node, or savable data pages with a scope of Thread or Requestor.

  1. In the navigation pane of Dev Studio, click Records.

  2. Expand the Data Model category, and then click Data Page.

  3. Click the row of the data page that you want to open.

  4. Click the Load Management tab.

  5. To force the system to delete the clipboard instances of the data page after an interval passes with no access, in the Page options section, select Clear pages after non-use.

    Subsequent attempts by a requestor to access the data pages cause the pages to reload.

    Selecting this option displays different effects, depending on the scope of the data page:

    • Requestor – The data page instance that is created when any thread refers to the data page is removed when no more threads refer to it.
    • Node – The system checks the Reload if older than fields on the Load Management tab of the data page rule. If the fields are blank, the system uses the value of the dynamic system setting DeclarePages/DefaultIdleTimeSeconds, which is set by default to 86400 seconds, or one day.
    Note: Read-only data pages are never passivated. All read-only data pages in an idle requestor or thread that is passivated are then cleared and reloaded the next time they are referenced, regardless of whether you select Clear pages after non-use.
  6. If you are using parameters in your data page, to overwrite existing data page instances with a new instance each time the system references the data page, click Limit to a single data page.

  7. If you are using a savable data page, to invalidate the data page instance after you save it, click Invalidate the page after a successful save.

    • If you save a savable data page without saving an autopopulated property, when you select this check box, the system invalidates the instance you saved immediately after you save the savable data page.
    • If you save a savable data page with an autopopulated property, when you select this check box on the savable data page that the property references, the system invalidates the corresponding data page instance immediately after you save the savable data page.
  8. To enable paging on the server, click Enable pagination.

    This option appears when you set the following parameters on the Definition tab of the data page rule form:

    • Structure – List
    • Mode – Read-only
    • Scope – Thread or Requestor
    • Source – Report definition
      Note: The Report definition must be in the same class as the data page.
    For more information, see Creating a data page.

    Selecting this option improves data page memory use and performance for data pages that are used as the source of a grid. The data page loads only the rows that are included in the grid, and stores them in memory.

  9. Click Save.

  • Previous topic Configuring the refresh strategy for data pages
  • Next topic Defining the requestor for loading a data page

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