building-omnistudio-datamapper

To create an OmniStudio Data Mapper, specify the Data Mapper type, target Salesforce objects and fields, target org, and consuming component name. The skill generates production-ready OmniDataTransform and OmniDataTransformItem records for Extract, Transform, Load, and Turbo Extract scenarios.

Field-level security validation checks data integrity rules within your OmniStudio Data Mapper configuration to ensure field mappings respect user permissions and data access constraints before metadata deployment.

Yes, Turbo Extract is supported as a specific Data Mapper scenario. You can generate Turbo Extract OmniDataTransform configurations alongside standard Extract, Transform, and Load types to optimize query performance.

The best way to validate OmniStudio Data Mapper configurations is using a 100-point rubric evaluating design, naming, field mapping, data integrity, performance, and documentation, enforcing anti-pattern prevention before generating metadata.

Yes, the Data Mapper generation enforces anti-pattern prevention before producing any configuration. It applies query and performance guardrails alongside data-integrity checks to ensure production-ready OmniDataTransform metadata.

OmniDataTransform deployment failures downstream often stem from insufficient validation scores or missing FLS and data-integrity checks. Configurations must pass deploy thresholds across design, mapping, performance, and documentation rubrics before activation.