Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, when a data writer creates an intermediary calculated field (e.g., field A) solely to derive a final calculated field (e.g., field B) in a Derived Dataset (DDS), they may want to exclude the intermediary field from the published output to keep the dataset clean and focused. According to the official Workday Prism Analytics study path documents, the recommended approach is to add a Manage Fields stage to the DDS and hide field A. The Manage Fields stage allows users to control the visibility of fields in the dataset, enabling them to hide fields that are not needed in the final output while retaining their calculations for internal use within the dataset’s transformation logic. By hiding field A, field B can still leverage field A’s calculations, and only field B will be visible in the published dataset or data source.
The other options are not suitable:
A. Mark field A as intermediate calculation: There is no specific feature in Prism Analytics to “mark” a field as an intermediate calculation; this is not a supported action.
C. Add a Manage Fields stage to the DDS and hide field B: Hiding field B would defeat the purpose, as field B is the intended output to be published.
D. Delete field A from their DDS and just leave field B: Deleting field A would break the calculation of field B, as field B depends on field A, making this option infeasible.
Using the Manage Fields stage to hide field A ensures that the dataset remains functional while presenting only the necessary fields in the final output, aligning with best practices for data transformation and publishing.
[References:, , Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Managing Fields in Derived Datasets, Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Configuring Field Visibility in Datasets]
