Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, joining datasets with different levels of granularity requires aligning their granularity to ensure a meaningful match. The sales data is at a daily level (one row per day), while the budget data is at a monthly level (one row per month). According to the official Workday Prism Analytics study path documents, to match the granularity of the monthly budget data, you should apply a Group By stage to the sales data (option B). The Group By stage aggregates the daily sales data into monthly totals (e.g., summing sales amounts by month), reducing the granularity from daily to monthly. This allows the sales data to be joined with the monthly budget data on a common key, such as the month.
For example, a Group By stage could group the sales data by a derived month field (e.g., using a function like EXTRACT(YEAR_MONTH, sale_date)) and aggregate the sales amounts using a function like SUM(sales_amount). The resulting dataset would have one row per month, matching the budget data’s granularity.
The other options are incorrect:
A. Union: A Union stage appends rows from one dataset to another but does not change granularity; it cannot aggregate daily data into monthly data.
C. Manage Fields: The Manage Fields stage modifies field properties (e.g., type, name) but does not aggregate data to change granularity.
D. Filter: A Filter stage removes rows based on conditions but does not aggregate data to align granularity levels.
The Group By stage is the appropriate transformation to align the sales data’s granularity with the monthly budget data for a successful join.
[References:, Workday Prism Analytics Study Path Documents, Section: Data Prep and Transformation, Topic: Aligning Granularity for Joins in Prism Analytics, Workday Prism Analytics Training Guide, Module: Data Prep and Transformation, Subtopic: Using Group By Stages for Data Aggregation, ]
Submit