Engineering / Order data model
SALast edited by Saman Attar · Mithra Systems
Order data model
The project installs a custom Order__c object into your org (via the setup
ticket). Crate & Co.'s inbound actions read and write these records.
| Field | API name | Type | Notes |
|---|---|---|---|
| Account | Account__c | Lookup(Account) | The customer the order belongs to |
| Product SKU | Product_SKU__c | Text | e.g. SKU-DEMO-100 |
| Quantity | Quantity__c | Number | Units ordered |
| Destination | Destination__c | Text | Ship-to, e.g. Denver, CO |
| Tracking Number | Tracking_Number__c | Text | Business key, e.g. APX-SEED-1001 |
| Status | Status__c | Picklist | Placed · Shipped · Delivered · Cancelled |
Seed data
The setup ticket seeds two customers and their orders so the read/count/lookup tickets have something deterministic to work against:
- Meridian Design Co. - one order (
APX-SEED-1001). - Northwind Traders Ltd - three orders (
APX-SEED-3001..3003).
See the API Reference for how the inbound actions consume these records.