Batch Data Transforms are designed to perform repeatable data-shaping operations before downstream analytical consumption. Salesforce describes batch transforms as canvas-based processing flows capable of adding, manipulating, joining, aggregating, filtering, and applying formulas or other transformations to data before writing the resulting dataset to a target object.
This makes A the appropriate solution when the requirement involves multiple structural transformations—such as pivots, aggregations, and calculations—before the resulting dataset becomes part of a semantic model.
Identity Resolution solves a different problem: reconciling and matching records across data sources to build unified profiles. It does not provide the generalized transformation pipeline required here.
Calculated fields can create derived values, but they are insufficient when the preparation requirement involves broad reshaping and aggregation of the underlying dataset. The transformations should occur at the Data 360 data-preparation layer, after which the output object can be used by downstream analytics.
Batch transforms can write to supported DLO or DMO output nodes depending on the source and design, providing a persistent transformed object that semantic modeling and other Data 360 processes can consume.
References/Topics: Data Setup - > Data 360 - > Batch Data Transforms - > Aggregate, Join, Transform, and Output Nodes.
===========================================================================
