External ID Limits
The following data types do not support record matching by external ID:
- Geolocation
- Text (Encrypted)
- Text Area
- Text Area (Long)
- Text Area (Rich)*
* Deployed image links in rich text area fields do not point from the destination org to the actual image because Salesforce assigns new IDs in the img tag.
Field Property Limits
Geolocation type fields do not support Set Empty, Set Random Value, Fixed Value, Delay on Insert, Deploy Last, or Copy Relationship Value.
Unsupported Metadata Types
- AnalyticSnapshot
- Document
- DocumentFolder
- FolderShare
- ViewDefinition
- WorkflowSend
- WorkflowTask
Governor Limits
The main purpose of governor limits is to guard against software and system failures. By enforcing governor limits, Prodly ensures that both the Prodly Salesforce app and the Prodly backend service retain reasonable performance and do not breach sizes and limits for memory, CPU, heap, threads, and time.
| Category | Feature | Maximum Limit |
|---|---|---|
| Data Templates | Template size (including deployment plan step and item records and data sets) | 3MB |
| Displayable environments in the Schema Settings picklists | 300 | |
| Selected fields per data set element | 900 | |
| Long or rich text area fields per data set element | 40 | |
| Character length of the Query Filter field | 950 | |
| Deployment plan steps per deployment plan | 20 | |
| Data sets per deployment plan | 1,000 | |
| Data sets per deployment plan step | 100 | |
| Deployments | Records per data set element | 500,000 |
| Total deployment time | 25 hours | |
| Transformation | Fields you can transform per data set | 200 |
| Relationships you can transform per data set | 50 | |
| Picklist values you can transform per data set | 100 | |
| Invocation | Invocations per deployment | 10 |
| Total invocation execution time | 120 seconds | |
| Versioning | Salesforce orgs connected | 50 |
| Objects | 100 | |
| Records per object | 200,000 | |
| Fields per object | 900 | |
| Text area fields per object | 40 |