• Do not download any object’s records if the only reason is to display the name field value instead of SFID values when lookup fields of this object are included in page layouts.

◦ Name field value should be displayed automatically without Download Criteria.

◦ If SFID is displayed for any field, check if SET004 and SET008 can be used instead to achieve the same results.

• If the requirement is to download only the records referenced in other records associated with events, use Advanced Download Criteria instead. Example of this is downloading of accounts and contacts referenced in work orders currently scheduled in technician’s calendar.

• For iPad App, if connectivity is expected to be good, see if the specific records required can be downloaded on demand using SFM Search, instead of through Download Criteria.

• Define the criteria in such a way that number of records downloaded for any object is less than 15,000.

• Create an index by requesting from Salesforce if the number of records in an object is more than 200,000, and is used in DC or ADC.

• Keep the total number of records (across objects) downloaded to the mobile app to the minimum value possible, ideally less than 50,000 records.

• Avoid using formula fields in Download Criteria for large volumes of data. You can replace formula fields with Salesforce Custom Settings for improved query performance, and reduced sync time. To know more, refer to Salesforce Custom Setting in Download Criteria.

• Avoid using the formula fields when defining Download Criteria. Use ServiceMax Literals whenever possible.

• Suggest data archival policies if the number of records in the production org is expected to grow into millions.