Grid uses API calls to call for data from a customer’s environment, and write-back updates based on user actions. The product has been designed to use very few API calls to operate. There are several situations outlined below which trigger API Calls from Troops to the customer’s third-party environment:

Opening a Grid

  • A user opening a Grid typically results in 2 API calls to facilitate calling for the data used in populating the Grid.

Refreshing a Grid

  • A user clicking the refresh button on an open Grid uses 2 API calls to facilitate calling for the data used in populating the Grid.

Updating a Single Field

  • A user updating any single field within a Grid uses 1 API call to facilitate making the update to that field.

Updating Multiple Fields via Bulk Update

  • A user performing a bulk update on a field across multiple records will use a number of API calls equal to the number of records selected.

Working with Reference Fields

  • A user adding a reference field as a condition when creating or editing a Grid results in 1 API call for each interaction with the value selector on the reference field condition row.

  • A user updating any single field within a Grid which is a reference field picklist may use multiple API calls as follows:

    • 1 API call to fetch the current values for the picklist when the field is opened

    • 1 API call for each search interaction when searching the picklist option

    • 1 API call to facilitate making the update to that field.

Special Notes

  • Grids do not refresh any data without your say-so. The only calls made to your data set are via authenticated user requests. As such, Grids will not inadvertently adversely impact your available API call number.

  • Salesforce’s APIs reserve control over the number of calls made to improve performance. In some scenarios Salesforce may require more than 2 API calls to load the records due to size limitations. For instance, creating a Grid with many columns and broad conditions may result in so much data that Salesforce breaks it up into more than 2 calls. This situation only occurs rarely and in Grids with extreme levels of records being returned.

Did this answer your question?