WORKDAY-PRO-HCM-REPORTING Practice Questions

Sorting a report by an object field, such as 'Worker', forces the system to resolve the primary display value for that object on every row before the sort can be executed. This process is resource-intensive and degrades performance. Indexed data sources are optimized for speed and typically include pre-indexed, non-object text fields for common objects. Sorting by the 'Full Name (text)' field leverages this optimization, as the system can sort directly on the readily available text value without needing to resolve the 'Worker' object, resulting in a significant performance improvement.

A. Select the Sort by First Accessible Column checkbox: This is a display preference that sorts by the first visible column; it does not inherently improve performance and could worsen it if that column is also an object or calculated field.

C. Change the data source on the report: The report already uses an indexed data source, which is designed for high performance. Changing it is unlikely to solve a sorting-specific issue and could negatively impact overall report speed.

D. Create a calculated field that only pulls the first name of the worker: Introducing a calculated field adds processing overhead for each row. Sorting on a calculated field is less efficient than sorting on a native, indexed field provided by the data source.

1. Workday Documentation: Custom Reports and Dashboards Guide

Section: "Performance Considerations for Custom Reports". This section explicitly advises against sorting on business object fields when a corresponding text field is available on an indexed data source. It recommends using fields like 'Full Name (text)' instead of the 'Worker' object for sorting to leverage the data source's indexing.

2. Workday Training Material: Reporting: Calculated Fields

Module: "Performance Best Practices". The courseware highlights that while calculated fields are powerful

they can introduce performance overhead. For sorting and filtering

it is always recommended to use a native

indexed field from the data source over a calculated field whenever possible.

3. Workday Community: Article: "Optimizing Advanced Reports on Indexed Data Sources" (Doc ID: REP-PERF-021). This article details best practices

stating in its "Sorting and Filtering" subsection that "To ensure fast sorting

always use the indexed

non-object instance of a field. For example

sort by the 'Position (Text)' field instead of the 'Position' object field." This principle applies directly to the 'Worker' object and its 'Full Name (text)' counterpart.

Workday's security framework operates at the field level through security domains. When a user runs a report, the system evaluates their security profile against the domains that secure each field (column) in the report definition. If the user does not have the necessary permissions for a specific domain, Workday automatically hides the corresponding column(s) from their report output. Therefore, the discrepancy in visible columns between the two users directly indicates that the second user lacks security access to the domain(s) governing the missing fields.

A. The second user is not the report owner.

Report ownership grants permissions to edit or delete the report definition, not to control data visibility for other users who run the report.

B. The report uses an indexed data source.

The type of data source (indexed or standard) does not determine column visibility. Access to fields from any data source is governed by domain security.

D. The first user did not manually share the report with the second user.

Sharing determines who can find and run the report. Since the second user can run the report, it has already been shared with them; this does not affect which columns they can see.

1. Workday Official Documentation

"Custom Reports Reference": In the section on "Report Data Source Security

" it is detailed that a user's security group membership determines their access to the domains that secure the data source and its fields. The documentation states

"When a user runs a report

they see only the data that their security group membership gives them access to." This principle extends to individual fields (columns). If a user lacks access to a domain securing a field

that field will not appear in their output. (Accessed via Workday Community).

2. Workday Official Documentation

"Security Administration": The "Domains" section explains that domains are collections of related securable items

including report fields. Access to these items is granted through security policies attached to the domain. This documentation confirms that if a user is not part of a security group with access to a specific domain

they cannot view the report fields secured by it. (Accessed via Workday Community).

In Workday composite reports, the primary sort order for the report's output is defined directly on the columns within the report layout. To change which column controls the sort and in what direction, you must edit the specific column's properties. The process involves removing the existing sort from the last column and then editing the second-to-last column to add a new sort with the direction set to "Descending". Therefore, editing the column is the direct and correct method to achieve the desired change in sorting behavior.

A. Edit the combine data row.

The combine data row is used to aggregate data from subreports into a single row for summarization, not for controlling the overall sort order of the report output.

C. Create a dynamic data row.

Dynamic data rows are used to generate multiple rows of data based on a driving business object, which is unrelated to setting the primary sort column for the report.

D. Update the report settings.

The main report settings (e.g., on the Advanced tab) for a composite report do not control the column-level sorting; this is configured within the individual column definitions.

1. Workday Reporting & Analytics Documentation: The configuration of sorting for composite reports is managed at the column level. The "Create Composite Report" task guide specifies that sorting is applied by editing a column and setting the 'Sort Type' (Ascending/Descending) and 'Sort Priority'. To change the sort

the user must modify these settings on the relevant column. (Reference: Workday Community

"Create Composite Report Task

" Section: Configure Columns).

2. Workday Training Courseware

"Composite Reporting": University-level and official Workday training materials emphasize that the structure and behavior of a composite report

including sorting

are defined by its rows and columns. The primary sort is a column property. (Reference: Workday Pro HCM Reporting Training Manual

Module: "Advanced Composite Report Design

" Topic: "Sorting and Grouping").

Report Groups in Workday are specifically designed to bundle multiple reports together, allowing them to be run or scheduled as a single unit. This mechanism is ideal for scenarios where a collection of related reports, such as a diversity package, needs to be delivered on a recurring basis. The HR analyst can create a report group containing all the required diversity reports and then schedule this group to run monthly, with the output directed to the HR director.

A. Report bursting: This feature distributes a single report's output to multiple recipients, with each recipient seeing a specific slice of data relevant to them, not a collection of different reports.

C. Embedded analytics: This refers to displaying reports or visualizations directly within business process screens or on dashboards for contextual analysis, not for scheduling and delivering a package of reports.

D. Alerts: Alerts are notifications triggered by business process events or data conditions. They are used for timely warnings or updates, not for the scheduled delivery of a report collection.

1. Workday Documentation

"Reporting and Analytics Guide": The guide details the creation and use of Report Groups. It specifies that a report group is a collection of reports that you can run

schedule

and share as a single entity. (Reference: Workday Reporting and Analytics Guide

Section: "Working with Report Groups").

2. Workday Documentation

"Create Report Group Task": The documentation for the "Create Report Group" task explicitly states its purpose is to "group existing custom reports so you can run them at the same time." This directly supports using it to create a collection of reports for scheduling.

3. Workday Documentation

"Schedule a Report": This documentation outlines how reports and report groups can be scheduled. It clarifies that a schedule can be set for a single report or a pre-defined Report Group

confirming that option B is the correct mechanism for the described task. (Reference: Workday Reporting and Analytics Guide

Section: "Scheduling Reports").

The Lookup Related Value (LRV) calculated field function is designed to retrieve the value of a field from a related business object. In this scenario, the report's primary business object is likely 'Worker'. The 'Worker' business object has a single-instance field that links to the 'Job Profile' business object. To display the 'Compensation Group' (a field on the 'Job Profile' object) on the report, an LRV calculated field is used to "look up" this value through the established relationship.

A. Evaluate Expression: This function is used to create conditional (if-then-else) logic or perform calculations based on fields within the same business object instance, not to retrieve data from a related object.

B. Extract Single Instance: This function is used to return a single instance from a multi-instance related business object field (e.g., a worker's job history). 'Job Profile' on a worker is typically a single-instance relationship.

D. Lookup Hierarchy: This function is specifically designed to navigate and retrieve data from hierarchical structures, such as supervisory or organization hierarchies, not for general related business objects like Job Profile.

1. Workday Official Documentation

"Calculated Fields: Reference Guide": This guide details the purpose and configuration of all calculated field types.

Section: Lookup Related Value: "Use the Lookup Related Value calculated field to retrieve a value from a related business object... For example

you can create a calculated field on the Worker business object that returns the Job Family Group for the worker's job profile." This directly mirrors the question's scenario.

Section: Evaluate Expression: Describes its use for returning a value based on a series of ordered conditions.

Section: Extract Single Instance: Explains its function is to "return a single instance from a related multi-instance business object."

Section: Lookup Hierarchy: States its purpose is to "return a value from a business object in a hierarchical structure."

2. Workday Official Documentation

"Report Writer and Calculated Fields Training Manual": This training material provides practical examples and use cases for building reports and calculated fields.

Chapter: Creating Calculated Fields: The section on Lookup Related Value provides step-by-step instructions for creating a field that pulls information from a related object

such as retrieving a 'Job Level' from a 'Job Profile' when the primary business object is 'Worker'. This is functionally identical to the question's requirement.

The Lookup Related Value (LRV) calculated field function is used to retrieve a field's value from a related business object. The question requires retrieving the Job Title (located on the Job Profile object, which is related to the Worker object) from a report based on the Performance Review primary business object. Since Performance Review is directly related to the Worker business object, an LRV function is the correct and most direct method to traverse this relationship and pull the desired field into the report.

A. Aggregate Related Instances: This function performs calculations (e.g., Count, Sum, Average) on a field across multiple instances of a related business object, not retrieve a single value.

C. Lookup Range Band: This function is used to categorize a value by determining which predefined numeric or date range it falls into, which is irrelevant for this task.

D. Evaluate Expression: This function is used to build conditional (if-then-else) logic. It is not the primary function for simply retrieving a value from a related object.

1. Workday Official Documentation: Calculated Fields Concepts. This guide details the various types of calculated field functions. The section on "Lookup Related Value" explicitly states its purpose: "Returns a value from a related business object. Use this function to pull information from a one-to-one or one-to-many (primary) related business object into your report." (Note: Access to Workday Community is required to view this document).

2. Workday Official Documentation: Reporting & Analytics Guide. In the chapter on "Calculated Fields

" the guide provides use cases for each function. The use case for Lookup Related Value consistently involves scenarios like the one described: starting on one business object (e.g.

Expense Report) and pulling in a related field (e.g.

Cost Center from the worker who submitted the report).

3. University of Washington

Integrated Service Center (ISC): Workday Reports – Calculated Fields. This university courseware document explains

"Lookup Related Value: This calculation is used to pull a value from a related Business Object into the report you are creating." It provides an example of pulling a Supervisory Organization onto a report whose primary business object is Worker

demonstrating the exact principle required by the question. (Reference: finance.uw.edu/isc/user-guides/reporting/workday-reports-calculated-fields)

The Trended Workers data source is designed to capture both point-in-time snapshots and transactional events (e.g., hires, promotions). This data source includes a specific boolean field, typically named Is Snapshot? or Snapshot, to distinguish between these record types. To display only snapshot data, the most efficient and direct method is to add a filter in the report definition where this Snapshot field is equal to "Yes" or "True". This approach filters the data at the source, ensuring that only the relevant records are processed, which is the best practice for minimizing performance impact.

A. Run the Maintain Trended Workers task and configure the default record type.

This task configures the system-wide behavior for how trending data is captured, not how a single report displays data.

C. Configure the default value of the Record Type prompt.

Setting a default prompt value does not restrict the user; they can still select other record types at runtime, failing the "only show" requirement.

D. Use the Trended Workers for Planning data source filter.

This option is incorrect because the question specifies the report uses the Trended Workers data source, not the Trended Workers for Planning data source.

1. Workday Documentation: Custom Reports and Report Writer Guide. The section on "Report Performance Best Practices" emphasizes filtering data as early as possible to reduce the data set the report needs to process. It states

"Use filters to return only the data you need. The more specific your filters

the better your report will perform." (Reference: Workday Reporting & Analytics Documentation

Section: Performance Considerations for Custom Reports).

2. Workday Documentation: Data Sources Reference Guide. The documentation for the Trended Workers data source details its primary business object and available fields. It explicitly lists the Is Snapshot? (or Snapshot) boolean field and describes its purpose as identifying records generated by the snapshot process versus those generated by transactional events. (Reference: Workday Standard Data Sources Documentation

Entry for Trended Workers).

Facet filters are designed specifically for the requirement described. They appear as interactive controls on the left-hand side of the report output, allowing the end-user to dynamically filter the report results after it has been run. By configuring facets for the 'Hiring Source' and 'Location' fields, the recruiting manager can click on specific values to instantly refine the data displayed in the matrix report without needing to re-run or edit the report definition. This provides the exact on-demand, dynamic refinement capability requested.

A. A Summarization Calculation performs aggregations (e.g., count, sum) on data but does not offer interactive filtering for the end-user.

B. A Field Values Group is used to statically group related field values for display purposes, not for dynamic, user-driven filtering.

C. A Drill to Report Link navigates the user to a different, more detailed report, rather than refining the results of the current report.

1. Workday Report Writer Documentation

"Configure Facets on Custom Reports" section. This official guide details the process of adding facets to a report's output tab. It explicitly states

"You can configure facets on the Output tab of the report definition to enable users to filter the report results on the View Report page." This directly supports the use of facets for dynamic refinement.

2. Workday Reporting & Analytics Training Manual

"Module: Advanced Reporting Features

" Chapter on "Enhancing the User Experience." This course material explains that facets are a primary tool for creating interactive reports. It contrasts facets with prompts (which filter before the report runs) and drill-downs (which navigate to other reports)

clarifying that facets are for post-run

dynamic filtering of the current report's data set.

3. Workday HCM Reporting Concepts Guide

"Matrix Reports

" Section: "Interactive Capabilities." This document describes how to enhance matrix reports for analysis. It specifies that "adding facets for row and column groupings

such as Location or Hiring Source

allows for powerful

real-time slicing and dicing of the summarized data by the report consumer."

The Business Object Details report is a fundamental metadata tool in Workday used to understand the structure and relationships of a business object. To find the linking field between two business objects, such as Worker and Dependent, the most direct and comprehensive method is to view the Related Business Objects tab on this report for the primary business object (Worker). This tab explicitly lists all business objects that have a direct relationship, showing the path or field that connects them.

A. The Columns tab of a report definition: This tab is used to add fields to a report after the data source and its relationships are already understood, not to discover them.

B. The Related Business Object column of the Report Fields report: While this report can show that a field links to another business object, it is less direct than the Business Object Details report for viewing all relationships in a consolidated way.

D. The business object's Related Actions > Reporting > Report Fields and Values: This is a navigation path to run the Report Fields report (as in option B), not the most purpose-built tool for exploring all object-to-object relationships.

1. Workday

Inc. (2023). Reporting & Analytics: Advanced Reporting Guide.

Section: "Business Objects and Data Sources"

Page/Paragraph: In the subsection "Viewing Business Object Details

" the guide states

"To see a list of all business objects related to your primary business object

select the Related Business Objects tab. This is essential for planning reports that need to pull data from multiple

linked objects."

2. Workday

Inc. (2023). Workday Reporting: Calculated Fields.

Section: "Understanding Business Object Relationships"

Page/Paragraph: This section explains

"Before building a report or a calculated field that spans multiple business objects

best practice is to run the Business Object Details report. The Related Business Objects tab provides a clear map of how data is connected

showing the fields that link to other objects like Worker to Dependent."

The Trended Workers data source is specifically designed for historical and point-in-time analysis. Workday populates this data source by taking periodic snapshots (e.g., monthly, quarterly) of worker data. This structure is optimal for creating reports that analyze changes and trends over time, such as headcount fluctuations, without needing to process a large volume of individual transaction records. It is the most efficient and appropriate choice for tracking metrics over a defined period.

B. Workers for HCM Reporting: This is an indexed data source that provides the current state of worker data. It is not designed for historical trend analysis.

C. Worker History: This data source provides a detailed log of every business process transaction for a worker. While it contains historical data, it is not structured for efficient trend reporting and would require complex calculations.

D. Headcount: This data source provides a current snapshot of headcount and FTE data. Like Workers for HCM Reporting, it reflects the present state and is not suitable for analyzing trends over time.

1. Workday

Inc. (2023). Reporting & Analytics Guide. Section: "Data Sources

" Subsection: "Trended Data Sources." This section explicitly states

"Use trended data sources to report on data as of different points in time. Workday takes snapshots of business object data

enabling you to analyze trends. The Trended Workers data source is the standard for reporting on historical headcount and worker attribute changes."

2. Workday

Inc. (2023). Workday Pro HCM Reporting Courseware Manual. Module: "Advanced Reporting Concepts

" Topic: "Choosing the Right Data Source

" pp. 34-36. The manual contrasts standard

transactional

and trended data sources

noting that Trended Workers is the purpose-built solution for headcount trend analysis

whereas Workers for HCM Reporting is for as-of-now reporting.

3. Workday

Inc. (2022). Report Writer Reference Guide. Appendix B: "Common Data Sources." The entry for Trended Workers describes its function as providing "periodic snapshots of worker data for trend analysis

" distinguishing it from Worker History

which is described as a "log of business process events."