omnistudio-datamapper-generate

Create OmniDataTransform and OmniDataTransformItem records using sf api request rest with a JSON body file, then deploy with sf project deploy start -m OmniDataTransform:<Name>. The sf data create record command cannot handle JSON in textarea fields, so write the body to a temp file first.

Turbo Extract uses server-side compiled queries and runs 10x or more faster for high-volume read-only scenarios, but does not support formula fields, related lists, aggregate queries, or polymorphic lookups. Standard Extract supports full SOQL including relationship queries and formula fields.

Use Transform when reshaping JSON data in memory between Integration Procedure steps, such as renaming fields or flattening nested structures. Transform performs no SOQL or DML, so use Extract or Load whenever database interaction is required.

This error occurs when the Data Mapper is in Draft status, since only active Data Mappers can be retrieved or referenced. Activate the Data Mapper in the target org first, and verify the namespace prefix in sfdx-project.json matches the org.

Turbo Extract does not support formula fields, child-to-parent relationship queries, aggregate functions like COUNT or SUM, or polymorphic lookups such as WhoId on Task. For these requirements, fall back to a standard Extract Data Mapper.

Define a lookup mapping that resolves an external key to a Salesforce ID by specifying the lookup object and match field, such as matching Account.Name to populate AccountId. Handle no-match cases with a default value or graceful failure to avoid null foreign key DML errors.