Order platform key flow
Note
This flow is self-documenting and should be viewed within Salesforce (Setup > Process Automations > Flows). This document is to support working through a visual flow. The flow commentary in this document was generated with AI assistance.
Overview#
Flow name: MoveData_Commerce_Order_Key Label: [MoveData] Commerce: Order - Platform Key Type: Auto-Launched Flow Template API version: 56.0 Status: Active
This flow generates standardised platform keys for order records by combining platform identifiers and external keys into a consistent format. These keys are used to match existing records and prevent duplicates during commerce transaction processing.
Purpose#
The flow provides consistent platform key generation that:
- Creates unique identifiers for orders across different external commerce platforms
- Enables reliable order matching and deduplication during processing
- Supports commerce extension functionality for transaction management
Salesforce fields#
| Field API name | Field type | Purpose in flow |
|---|---|---|
| movedata__Platform_Key__c | Text | Stores generated platform key |
Input variables#
| Variable | Type | Required | Description |
|---|---|---|---|
Platform |
String | Yes | Platform identifier (e.g., "raisely", "funraisin", "shopify") |
Key |
String | Yes | External platform's unique identifier for the order |
Output variables#
| Variable | Type | Description |
|---|---|---|
Result |
String | Generated platform key in standardised format |
Flow logic#
1. Platform key generation#
The flow uses a simple but effective key generation approach.
Platform key format#
Platform:Key
Examples:
raisely:order_123456funraisin:transaction_789012shopify:order_ABC123DEFeventbrite:order_456789123
2. Key construction#
The flow performs direct string concatenation:
- Combines the platform identifier with the external key
- Uses colon (
:) as the delimiter for consistency across all MoveData flows - No validation or transformation applied to maintain simplicity and reliability
Error handling#
Input validation#
The flow relies on calling processes to ensure:
- Platform identifier is provided and not null
- External key is provided and not null
- Both values contain valid characters for platform key construction
Dependencies#
None