Skuid on Salesforce

The Salesforce platform offers an array of enterprise-level features that make it an excellent system for a variety of business processes. And its flexibility and extensibility allow for a variety of user experience enhancements—including Skuid!

When using Salesforce, there are two interfaces to choose from, and the one you select influences how you deploy your Skuid apps:

Look for the deployment process in the table of contents that aligns with your Salesforce org.

Salesforce API Usage

When using Skuid on Salesforce, Skuid is a managed package installed within a Salesforce org. This means that almost every action Skuid takes does not consume API calls for the org it is installed in. However, there are some exceptions:

  1. Page support file generation for LockerService compliance will consume API calls.

  2. Any use of Salesforce data source actions will consume an API Call.

  3. Record type dependent picklists require an API call to confirm the available picklist values. Skuid aggressively caches to avoid consuming API calls, but some calls will still be incurred.

    Note

    If you have dependent picklists but do not have record types, those picklists will not consume an API call.

For both Skuid on Salesforce and Skuid Platform, accessing an external org’s data—whether through model queries or Salesforce data source actionswill consume API calls in the external org.