Skip to content

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_Catalog_Key Label: [MoveData] Commerce: Catalog - Platform Key Type: Auto-Launched Flow Template API version: 56.0 Status: Active

This flow generates standardised platform keys for catalog records by combining platform identifiers and external keys into a consistent format. These keys are used to match existing catalog items and prevent duplicates during commerce data processing.

Purpose#

The flow provides consistent platform key generation that:

  • Creates unique identifiers for catalog items across different external commerce platforms
  • Enables reliable catalog matching and deduplication during processing
  • Supports commerce extension functionality for product and ticket 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 catalog item

Output variables#

Variable Type Description
Result String Generated platform key in standardised format

Flow logic#

1. Input validation#

The flow first checks if a key value has been provided:

Has key decision#

  • Condition: Key is not null
  • True path: Proceeds to platform key construction
  • False path: Flow terminates without generating a key

2. Platform key generation#

Platform key format#

Platform:Key

Examples:

  • raisely:product_12345
  • funraisin:ticket_67890
  • shopify:prod_ABC123
  • eventbrite:event_789012

3. Key construction#

The flow performs direct string concatenation using a formula:

  • Formula name: GeneralPlatformKey
  • Expression: {!Platform}&":"&{!Key}
  • 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 includes basic validation:

  • Key presence check: Verifies that the Key variable is not null before proceeding
  • Graceful termination: If no key is provided, the flow terminates without error

Calling process responsibilities#

The flow relies on calling processes to ensure:

  • Platform identifier is provided and not null
  • External key contains valid characters for platform key construction
  • Platform identifier follows MoveData naming conventions

Dependencies#

None

Ask MoveData AI
Ask about setup, configuration, or troubleshooting
How can I help you with MoveData today?