Skip to main content
Conga Support

Getting the Best Performance from ActionGrid

When ActionGrid displays for the first time, several factors can potentially increase the page loading time:

  • The number of records per page. ActionGrid can display 1,000 records per page but the display time will be slower than 100 records per page. Start with 500 records per page, then decrease the number if performance becomes an issue.
  • Complex filtering. This is the most common reason for a delay in page loading time. If the view is so slow that you are receiving timeout errors, you may need to filter additional fields or even ask Salesforce support to set a specific index on the particular field you are filtering. See ActionGrid Error Message: Unable to Connect to the Server (Transaction Aborted: Timeout).
  • Multi-field sorting. This type of sorting is done on the server side by Salesforce SOQL statements, and it can have a minor impact to your query results.
  • Too many fields displayed in the grid. Displaying hundreds of fields in the grid can impact performance. Consider using the Detail Grid Tab in the Reading Pane to display details about selected records.
  • Parent fields. Displaying many fields with foreign keys, or fields from those parent objects, can impact performance.
  • Displaying the Reading Pane with a large related list as the first tab. In this case, ActionGrid needs to load the queries for the Reading Pane and the related list, which impacts performance.
  • Long text fields. Displaying many long text fields in the grid can cause a minor delay. Consider using the Detail Grid Tab in the Reading Pane.
  • ActionGrid as related lists on embedded page layouts:
    • Set DelayLoad="true" in the Visualforce Markup for all tabs other than the first tab in a Multi-Tabular Related List.
    • Avoid multiple VisualForce pages such as one page that calls another page.