0% found this document useful (0 votes)

26 views845 pages

Admin Guide Reporting and Analytics

Uploaded by

raj

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

26 views845 pages

Admin Guide Reporting and Analytics

Uploaded by

raj

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 845

Reporting and Analytics

Product Summary

July 2023

Contents

Reporting and Analytics........................................................................... 12

Custom Reports and Analytics................................................................ 12

Workday Reporting Concepts........................................................................................................... 12
Concept: Custom Reports...................................................................................................... 12
Concept: Business Objects, Data Sources, and Fields......................................................... 13
Concept: Indexed Data Sources and Fields.......................................................................... 15
Concept: Selecting a Data Source.........................................................................................17
Concept: Report Security....................................................................................................... 19
Reference: Report Types....................................................................................................... 19
Set Up Reports..................................................................................................................................21
Setup Considerations: Custom Reporting.............................................................................. 21
Setup Considerations: Charts.................................................................................................26
Copy Reports..........................................................................................................................28
Create Custom Reports..........................................................................................................29
Create Reports from Business Object Instances................................................................... 31
Find Custom Reports by Data Source................................................................................... 32
Set Up Drill Down for Custom Reports.................................................................................. 32
Set Up Sort Options for Custom Reports.............................................................................. 33
Set Up Filter Options for Custom Reports............................................................................. 36
Set Up Prompt Options for Custom Reports..........................................................................38
Set Up Output Options for Custom Reports.......................................................................... 39
Set Up Share Options for Custom Reports........................................................................... 42
Set Up Advanced Options for Custom Reports..................................................................... 43
Set Up Facet Configurations.................................................................................................. 47
Concept: Charts......................................................................................................................48
Concept: Effective and Entry Dates....................................................................................... 49
Reference: Chart Types......................................................................................................... 50
Reference: Filter Operators.................................................................................................... 52
Fields and Prompts........................................................................................................................... 59
Create Analytic Indicators.......................................................................................................59
Create Prompt Sets................................................................................................................ 61
Concept: Analytic Indicators................................................................................................... 62
Concept: Displaying Currency Fields..................................................................................... 62
Concept: Global Fields........................................................................................................... 63
Concept: Logical Sort Order...................................................................................................63
Concept: Report Sorting Behavior..........................................................................................64
Reference: Field Options........................................................................................................64
Reference: Field Types.......................................................................................................... 66
Example: Sort Fields by the Related Business Object.......................................................... 67
Run and Schedule Reports...............................................................................................................69
Group Reports........................................................................................................................ 69
Burst Reports..........................................................................................................................71
Attach Excel Templates to Custom Reports or Report Groups............................................. 73
Schedule Reports or Report Groups......................................................................................74
Manage Scheduled Future Processes................................................................................... 76
Save Filters.............................................................................................................................76
Save Searches....................................................................................................................... 77

Concept: Interacting with Report Results...............................................................................77

Concept: Report Schedules and Weekly Service Update Window........................................ 78
Report Administration........................................................................................................................ 78
Add Custom Reports to Workday Menus.............................................................................. 78
Share Custom Report Definitions...........................................................................................79
Transfer Ownership of Report Groups................................................................................... 79
Translate Custom Reports......................................................................................................80
Concept: Custom Report Deletion..........................................................................................81
Concept: My Reports..............................................................................................................81
Concept: Report Definition Usages........................................................................................ 82
Concept: Report Tags............................................................................................................ 82
Concept: Temporary Reports................................................................................................. 83
Reference: Custom Reports with Objects Planned for Retirement........................................ 83
Reference: Report Run History.............................................................................................. 85
Reference: Reports for Managing Custom Reports............................................................... 86
Reference: Security Domains for Reporting...........................................................................87
Report Performance and Limitations.................................................................................................88
Create Report Performance Logs.......................................................................................... 88
Reference: Report Performance Log Fields...........................................................................89
Reference: Improving Report Performance............................................................................96
Reference: Reporting Limits................................................................................................... 97
Simple Reports................................................................................................................................ 104
Steps: Create Simple Reports..............................................................................................104
Set Up Columns for Simple Reports....................................................................................104
Advanced Reports........................................................................................................................... 106
Steps: Create Advanced Reports.........................................................................................106
Set Up Columns for Advanced Reports............................................................................... 107
Set Up Outlining in Advanced Reports................................................................................ 109
Create Gauge Ranges..........................................................................................................110
Concept: Advanced Reports.................................................................................................111
Matrix Reports................................................................................................................................. 112
Steps: Create Matrix Reports............................................................................................... 112
Set Up Grouping and Summarizing for Matrix Reports........................................................112
Set Up Field Values Groups for Matrix Reports.................................................................. 117
Create Drill-To Report Links.................................................................................................118
Concept: Matrix Reports.......................................................................................................120
Example: Create a Matrix Report for Employee Data..........................................................121
Example: Create a Drill-To Report Link for Ledger Account Reports.................................. 122
Composite Reports.......................................................................................................................... 124
Setup Considerations: Composite Reports.......................................................................... 124
Steps: Create Composite Reports........................................................................................128
Enable Business Objects for Filtering and Grouping........................................................... 129
Set Up Composite Report Columns..................................................................................... 130
Set Up Composite Report Rows.......................................................................................... 133
Set Up Composite Report Cells........................................................................................... 135
Set Up Additional Options for Composite Reports...............................................................137
Set Up Output Options for Composite Reports....................................................................139
Create Outline Structures for Composite Reports................................................................142
Concept: Composite Reports............................................................................................... 144
Concept: Formatting Styles.................................................................................................. 145
Concept: Prompt Sets for Composite Reports..................................................................... 145
Reference: Composite Report Columns...............................................................................146
Reference: Composite Report Rows....................................................................................147
Reference: Composite Report Cells.....................................................................................149
Example: Create a Report on the Gender Breakdown of Active Workers............................150
Example: Composite Reports for Income Statements......................................................... 151

Trending Reports............................................................................................................................. 162

Steps: Create Trending Reports...........................................................................................162
Set Up Trending Reports..................................................................................................... 163
Concept: Trending Reports.................................................................................................. 168
Setup Considerations: Trended Workers Report Data Source............................................ 168
Steps: Set Up Tenants for Trended Worker Reporting........................................................ 171
Set Up the Trended Workers Report Data Source.............................................................. 172
Concept: Trended Workers Report Data Source................................................................. 175
Reference: Reporting on the Trended Workers Report Data Source...................................176
Transposed Reports........................................................................................................................ 178
Steps: Create Transposed Reports......................................................................................178
Set Up Rows for Transposed Reports................................................................................. 178
Concept: Transposed Reports..............................................................................................180
Search Reports................................................................................................................................180
Steps: Create Search Reports............................................................................................. 180
Example: Export Workers Using a Search Report...............................................................181
nBox Reports...................................................................................................................................183
Steps: Create nBox Reports................................................................................................ 183
Set Up Matrix Options for nBox Reports............................................................................. 184
Worklets and Dashboards............................................................................................................... 185
Steps: Set Up Custom Dashboards..................................................................................... 185
Create Custom Dashboards................................................................................................. 186
Configure Dashboard Content..............................................................................................187
Enable Reports for Related Worklets...................................................................................189
Save Custom Prompt Values for Worklets...........................................................................190
Concept: Custom Worklets...................................................................................................190
Concept: Worklet Performance............................................................................................ 192
Custom Metrics and Scorecards..................................................................................................... 192
Steps: Create Custom Metrics and Scorecards................................................................... 192
Set Up Analytic Scorecard Profiles and Metric Sets............................................................193
Create Custom Metrics.........................................................................................................195
Set Up Custom Reports for Scorecards.............................................................................. 196
Process Metrics.................................................................................................................... 198
Review Metrics..................................................................................................................... 198
Concept: Workday Scorecards.............................................................................................199
Reference: Custom Scorecard Report Definition................................................................. 201
Reference: Scorecard Results..............................................................................................202
Reference: Metric Calculations for Dependent Metrics........................................................ 204
Custom Data Sources..................................................................................................................... 205
Set Up Extended Indexed Data Sources............................................................................. 205
Concept: Extended Indexed Data Sources.......................................................................... 206
Maintain Custom Data Source for the Worker Business Object.......................................... 208
Quicklinks.........................................................................................................................................209
Steps: Display a Quicklinks Worklet on a Dashboard..........................................................209
Maintain Quicklinks............................................................................................................... 210
Create a Quicklinks Worklet.................................................................................................210
Reports as a Service (RaaS).......................................................................................................... 211
Concept: Reports as a Service (RaaS)................................................................................211
Concept: Accessing RaaS Output........................................................................................213
Concept: Reports as RSS Feeds.........................................................................................215
Workday Query Language (WQL)...................................................................................................215
Concept: Workday Query Language (WQL)........................................................................ 215
Convert Reports to WQL Queries........................................................................................ 216
View WQL Query Results.................................................................................................... 217
Concept: Related Business Objects in WQL....................................................................... 218
Concept: Pagination of WQL Query Results........................................................................219

Reference: WQL REST API................................................................................................. 219

Reference: WQL Aliases...................................................................................................... 222
Reference: WQL Result Limits............................................................................................. 223
Reference: WQL and RaaS Comparisons........................................................................... 223
WQL Reference.................................................................................................................... 225
Business Form Layouts...................................................................................................................238
Create Business Form Layouts with Report Designer in Workday Studio........................... 238

Workday Report Designer...................................................................... 245

Setup Considerations: Report Designer..........................................................................................245
Creating and Deploying Report Designs.........................................................................................248
Steps: Create Business Form Layouts with Report Designer.............................................. 248
Create Report Design Projects............................................................................................ 248
Create Report Design Files..................................................................................................248
Create Data Sources............................................................................................................ 249
Create Data Sets..................................................................................................................250
Deploy Report Designs to Workday..................................................................................... 251
Concept: Report Designer Overview....................................................................................252
Concept: Data Sources, Data Sets, and Tables.................................................................. 252
Reference: Data Type Mapping........................................................................................... 253
Designing and Formatting Reports................................................................................................. 254
Add Labels to Report Designs............................................................................................. 254
Add Text Blocks to Report Designs..................................................................................... 254
Add Dynamic Text to Report Designs..................................................................................255
Add Rotated Dynamic Text to Report Designs.................................................................... 255
Add Data Sets and Data Set Fields to Report Designs....................................................... 256
Add Images to Report Designs............................................................................................ 256
Add Background Images to Master Pages.......................................................................... 257
Add Grids to Report Designs............................................................................................... 257
Add Lists to Report Designs................................................................................................ 258
Add Tables to Report Designs............................................................................................. 258
Add Charts to Report Designs............................................................................................. 259
Add Barcodes to Report Designs.........................................................................................259
Group Report Data............................................................................................................... 260
Edit Master Pages................................................................................................................ 261
Prevent Broken Image Links from Displaying...................................................................... 261
Display Multiple Labels on the Same Line...........................................................................262
Display Rich Text Data in Tables........................................................................................ 262
Apply Global Formatting....................................................................................................... 263
Use JavaScript to Conditionally Alter Layout....................................................................... 263
Insert Page Breaks............................................................................................................... 264
Create Report Design Templates.........................................................................................264
Navigate Report Designs Using the Outline View................................................................264
Update Report Designs to Match Custom Report Changes................................................ 265
Debug JavaScript in Report Designs................................................................................... 265
Concept: Applying a Report Design Separately to Each Row............................................. 266
Concept: Report Designer Fonts..........................................................................................266
FAQ: Font Issues in Report Designs................................................................................... 267
Sharing Report Designs.................................................................................................................. 268
Export Report Design Projects............................................................................................. 268
Import Report Design Projects............................................................................................. 268
Concept: Workday Solution Sharing and Report Designs................................................... 268
Translation Support......................................................................................................................... 269
Steps: Translate Labels Using Resource Files.................................................................... 269
Create a Translation Resource File for the Default Locale Language................................. 269

Create Translation Resource Files for the Target Languages............................................. 270

Associate Labels with Resource File Key Pairs...................................................................271
Preview a Translated Report Design................................................................................... 272
Conditionalize Label Translation with JavaScript................................................................. 272
Troubleshooting: Translation Issues on Custom Reports.................................................... 273
Previewing and Printing...................................................................................................................274
Preview Report Designs as PDFs........................................................................................274
Print Custom Reports after Design Deployment.................................................................. 274
Examples......................................................................................................................................... 275
Example: Create a Report Design with a Single Data Set...................................................275
Example: Create a Report Design with Multiple Data Sets..................................................277
Example: Create a Report Design with Resource-Based Translation..................................281

Discovery Boards.................................................................................... 283

Steps: Set Up Tenant for Discovery Boards...................................................................................283
Steps: Create a Discovery Board................................................................................................... 285
Steps: Create Visualizations........................................................................................................... 286
Set Up the Viz Data Source........................................................................................................... 287
Set Up Prompt Values for Discovery Boards................................................................................. 287
Set Up Curated Data Sources........................................................................................................ 289
Set Up Curated Field Lists..............................................................................................................290
Set Up Discovery Boards as Home Page Worklets....................................................................... 292
Reference: Supported Fields in Discovery Boards......................................................................... 293
Reference: Reporting Limits............................................................................................................295
Discovery Board Concepts..............................................................................................................302
Concept: The Discovery Board Workflow............................................................................ 302
Concept: Visualization Types............................................................................................... 302
Concept: Discovery Board Workspace.................................................................................305
Concept: Interactive Viz Queries..........................................................................................306
Concept: Using Drop Zones in a Viz................................................................................... 307
Concept: Chart Viz Mark Types........................................................................................... 307
Concept: Discovery Board Controls..................................................................................... 308
Concept: Sharing Discovery Boards.................................................................................... 309
Concept: Discovery Board Security......................................................................................309
Reference: Summarization and Attribute Viz Fields.............................................................310
Workday-Delivered Discovery Boards.............................................................................................311
Copy Workday-Delivered Discovery Boards........................................................................ 311
Modifying Visualizations.................................................................................................................. 311
Steps: Modify Visualizations.................................................................................................311
Adjust Mark Size in a Viz.....................................................................................................312
Group Data by Color in a Viz.............................................................................................. 313
Change Viz Colors............................................................................................................... 313
Change Field Options for Visualizations.............................................................................. 314
Change the Formatting of a Numeric Summarization in a Viz............................................. 314
Set Up KPI Viz Options........................................................................................................315
Set Up Waterfall Viz Options............................................................................................... 316
Concept: Color in Discovery Boards.................................................................................... 317
Filtering and Sorting Data in Visualizations.................................................................................... 318
Filter Data in a Viz............................................................................................................... 318
Sort Data in a Viz.................................................................................................................320
Limit Viz to the Top N Values..............................................................................................321
Concept: Viz Filters.............................................................................................................. 322
Sharing Visualization Insights......................................................................................................... 322
Export a Viz as a Custom Report........................................................................................ 322
Download Visualizations....................................................................................................... 323

Prism Analytics........................................................................................323
Steps: Set Up Tenant for Prism Analytics...................................................................................... 323
Steps: Set Up Tenant for Analytic Data Source............................................................................. 326
Concept: Prism Analytics Data Management Workflow..................................................................327
Concept: Creating Reports to Import into Tables and Datasets..................................................... 330
Concept: Prism Data Sources.........................................................................................................331
Reference: External Data Limits..................................................................................................... 332
Table and Dataset Concepts.......................................................................................................... 333
Concept: Tables....................................................................................................................333
Concept: Table Error File..................................................................................................... 335
Concept: Datasets................................................................................................................ 336
Concept: Dataset Workspace...............................................................................................336
Concept: Data Catalog......................................................................................................... 338
Concept: Dataset Schema Changes.................................................................................... 340
Concept: Dataset Pipelines.................................................................................................. 342
Concept: Dataset Stages......................................................................................................342
Concept: Unpivot Stages......................................................................................................343
Concept: Dataset Field Origin.............................................................................................. 343
Concept: Field Lineage.........................................................................................................343
Concept: Table and Dataset Field Types.............................................................................344
Concept: NULL Values in Tables and Datasets.................................................................. 348
Concept: Prism Calculated Fields........................................................................................ 350
Concept: Hiding Dataset Fields............................................................................................350
Concept: Dataset Integration Schedules..............................................................................351
Reference: Dataset Stages.................................................................................................. 353
Reference: Table Error File Error Codes............................................................................. 354
Creating Tables and Datasets........................................................................................................ 355
Steps: Create a Table by File Upload..................................................................................355
Steps: Create Table from a Workday Report.......................................................................357
Steps: Create Table from an Existing Table or Dataset...................................................... 358
Steps: Create a Table Manually...........................................................................................359
Steps: Create a Dataset with External Data (SFTP Server)................................................ 360
Steps: Create a Dataset with External Data (Upload a File)................................................364
Steps: Create a Dataset Using Workday Data.................................................................... 365
Steps: Create a Derived Dataset......................................................................................... 367
Import a Table or Dataset into a Derived Dataset............................................................... 368
Manage Dataset Integration Schedules............................................................................... 369
Upload a New File to a Dataset...........................................................................................371
View Prism Data Usage....................................................................................................... 372
View Table and Dataset Lineage......................................................................................... 372
View Field Lineage............................................................................................................... 373
View Dataset Dependencies................................................................................................ 374
Reference: Supported Date Formats for External Data in Tables and Datasets.................. 374
Reference: Naming Guidelines.............................................................................................376
Reference: Supported File Formats for External Data in Tables and Datasets....................378
Reference: Currency Format Requirements for External Data............................................ 378
Reference: Date Format Symbols........................................................................................ 379
Reference: WPA_ Fields...................................................................................................... 380
Editing Tables..................................................................................................................................381
Parse External Data in a Table............................................................................................381
Edit a Table.......................................................................................................................... 384
Reference: Table Field Attributes.........................................................................................385
Editing Datasets.............................................................................................................................. 386
Parse External Data in a Dataset........................................................................................ 386

Add a Prism Calculated Field to a Dataset..........................................................................389

Add a Stage to a Dataset.................................................................................................... 391
Manage Dataset Fields.........................................................................................................392
Change Dataset Field Types................................................................................................393
Convert Dataset Text Fields to Date Fields......................................................................... 394
Change the Dataset Example Rows.................................................................................... 395
Concept: Dataset Example Data.......................................................................................... 397
Reference: Explode Stages..................................................................................................398
Reference: Filter Stages.......................................................................................................398
Reference: Group By Stages............................................................................................... 400
Reference: Join Stages........................................................................................................ 401
Reference: Union Stages..................................................................................................... 402
Reference: Unpivot Stages...................................................................................................403
Reference: Boolean Expressions......................................................................................... 404
Example: Unpivot Stock Vesting Data in a Dataset.............................................................406
Example: Bring in International-Formatted Numeric Fields..................................................408
Changing Data in Tables................................................................................................................ 410
Create a Data Change Task................................................................................................ 410
Create a Data Change Task Schedule................................................................................ 413
Concept: Data Change Tasks.............................................................................................. 415
Concept: Mapping Fields in Data Change Tasks.................................................................416
Managing Connections.................................................................................................................... 416
Create an SFTP Connection................................................................................................ 416
Securing Data in Tables and Datasets........................................................................................... 419
Set Up Table Sharing...........................................................................................................419
Set Up Dataset Sharing....................................................................................................... 421
Share a Table with Others................................................................................................... 423
Share a Dataset with Others................................................................................................423
Edit Prism Data Source Security..........................................................................................424
Concept: Security in Prism Analytics................................................................................... 427
Concept: Sharing Tables and Datasets............................................................................... 430
Concept: Relax Sharing Options.......................................................................................... 430
Concept: Sharing Datasets Using Relax Sharing Rules...................................................... 432
Preparing Data for Analysis............................................................................................................ 440
Enable Contextual Publishing for Datasets..........................................................................440
Publish a Dataset as a Prism Data Source Manually.......................................................... 441
Create Dataset Publish Schedules.......................................................................................442
Concept: Making Prism Data Available for Analysis............................................................ 444
Concept: Dataset Publish Schedules................................................................................... 445
Concept: Coordinating Publish Schedules with Dataset Integration.................................... 447
Example: Create Dependent Publish Schedules for Datasets............................................. 447
FAQ: Dataset Publish Schedules......................................................................................... 448
Deleting Prism Analytics Data.........................................................................................................450
Truncate Data in a Table..................................................................................................... 450
Delete Rows of Data in a Table...........................................................................................450
Truncate Data in a Dataset.................................................................................................. 452
Unpublish a Dataset............................................................................................................. 452
Delete Rows from a Prism Data Source..............................................................................453
Concept: Deleting Prism Data.............................................................................................. 453
Managing Analytic Data Sources.................................................................................................... 455
Install and Schedule an Analytic Data Source.....................................................................455
Uninstall an Analytic Data Source........................................................................................456
Concept: Workday-Delivered Analytic Data Sources........................................................... 456
Concept: Managing Analytic Data Source Schedules..........................................................456
Concept: Peakon Employee Voice Analytic Data Source.................................................... 457
Reference: Prism Expression Language.........................................................................................458

Concept: Prism Expression Language................................................................................. 458

Comparison Operators..........................................................................................................460
Logical Operators................................................................................................................. 461
Arithmetic Operators............................................................................................................. 462
Conversion Functions........................................................................................................... 463
Date Functions......................................................................................................................472
Informational Functions.........................................................................................................478
Instance Functions................................................................................................................479
Logical Functions.................................................................................................................. 482
Math Functions..................................................................................................................... 483
Text Functions...................................................................................................................... 487
URL Functions...................................................................................................................... 505
Window Functions................................................................................................................ 511
Regular Expression Reference.............................................................................................535

People Analytics...................................................................................... 542

Setup Considerations: People Analytics......................................................................................... 542
Steps: Prepare for People Analytics Installation.............................................................................546
Maintaining People Analytics.......................................................................................................... 547
Steps: Change People Analytics Configuration....................................................................547
Steps: Configure a Pipeline in People Analytics.................................................................. 548
Steps: Set Up Constrained Security to People Analytics.....................................................550
Steps: Set Up Skills in People Analytics..............................................................................551
Steps: Set Up VIBE Index in People Analytics.................................................................... 553
Configure Pipeline Field Mappings.......................................................................................554
Concept: Hierarchies and Organizations in People Analytics.............................................. 555
Concept: Security in People Analytics................................................................................. 558
Concept: Data Quality Module............................................................................................. 559
Concept: People Analytics Activities.................................................................................... 561
Reference: Requirements and Considerations for Changing People Analytics
Configuration....................................................................................................................563
Reference: Choosing and Creating Intersections.................................................................568
Reference: Fields in People Analytics..................................................................................573
Reference: Business Objects and Data Sources in People Analytics..................................591
Example: Create an Intersection.......................................................................................... 593
Troubleshooting: Data Quality Module................................................................................. 595
VIBE Index in People Analytics...................................................................................................... 599
Concept: VIBE Index in People Analytics............................................................................ 599
Concept: Belonging in the VIBE Index.................................................................................601
Concept: Calculating the VIBE Score.................................................................................. 602
Concept: Skills in People Analytics.................................................................................................604
Concept: Filtering in People Analytics............................................................................................ 605
Concept: Export and Download Options.........................................................................................607
Concept: Providing Feedback on Story Quality.............................................................................. 608
Concept: Storyteller Engine.............................................................................................................609
Concept: Trends, Gaps, Top Drivers, and Detailed Data............................................................... 610
Reference: Business Questions by Topic Area.............................................................................. 611
Reference: Metrics in People Analytics.......................................................................................... 614
Reference: Visualizations by Topic Area........................................................................................ 632
FAQ: People Analytics.................................................................................................................... 645

Worksheets...............................................................................................649
Worksheets Setup........................................................................................................................... 649
Set Up Worksheets.............................................................................................................. 649

Copy Live Data Workbooks Between Tenants.................................................................... 651

Reference: Security Domains and Worksheets Actions.......................................................652
Download All Comment Data..........................................................................................................653
Edit, Delete, or Purge Workbook Comments by Other Users........................................................ 654
Concept: Managing Workbooks...................................................................................................... 654
Concept: Live Data in Workbooks.................................................................................................. 657
Concept: Structured References in Workbooks.............................................................................. 659
Concept: Using External References to Refer to Data in Other Workbooks...................................663
Concept: Creating Reports to Insert into Workbooks..................................................................... 665
Concept: Single- and Multi-Instance Field Values in Workbooks................................................... 667
Concept: Array Formulas in Workbooks......................................................................................... 670
Concept: Editing Workbooks........................................................................................................... 672
Concept: Automatic and Manual Calculation in Workbook Formulas............................................. 681
Concept: Data Analysis with Worksheets Functions.......................................................................683
Reference: Workbook Limits........................................................................................................... 687
Reference: Workbook Actions Available Based on Permissions.................................................... 688
Reference: Automatic Data Updates in Workbooks........................................................................690
Reference: Array Formula Keyboard Shortcuts.............................................................................. 691
Reference: Mobile Features for Worksheets.................................................................................. 693
FAQ: Collaboration and Security in Worksheets............................................................................ 693
FAQ: Workbook Performance......................................................................................................... 694
Example: Use Worksheets with the What's New in Workday Report............................................. 696
Workbook Templates.......................................................................................................................701
Concept: Workbook Templates............................................................................................ 701
Create and Distribute Workbook Templates........................................................................ 701
Reference: Template Actions Available Based on Permissions...........................................702
Worksheets Function Reference..................................................................................................... 704
Reference: Worksheets-Unique Functions........................................................................... 704
Reference: Worksheets Functions by Category...................................................................706
Reference: Formula Errors................................................................................................... 717
Reference: Worksheets Rounding Functions....................................................................... 719
Worksheets Functions.......................................................................................................... 721
Reference: Measurement Units in Worksheets Functions................................................... 786

Slides.........................................................................................................796
Steps: Set Up Security for Slides................................................................................................... 796
Concept: Slides............................................................................................................................... 797
Concept: Managing Slides Presentations....................................................................................... 798
Concept: Editing Slides Presentations............................................................................................ 799
Reference: Access to Linked Worksheets Data in Slides...............................................................802
Reference: Slides Presentation Limits............................................................................................ 803
Reference: Presentation Actions Available Based on Permissions................................................ 803

Reporting on Modeled Data Sources.................................................... 804

Steps: Set Up Your Tenant for OfficeConnect for Financial Management..................................... 804
Enable OfficeConnect for Workday Financial Management........................................................... 805
Set Up the Financial Reporting Data Model................................................................................... 805
Connect OfficeConnect to Your Financial Management Tenant.....................................................808
Concept: Modeled Data Sources.................................................................................................... 809
Concept: Reporting on the Financial Modeled Data Source...........................................................810
Concept: The Financial Reporting Data Model...............................................................................810
Concept: Caching and Refreshing the Financial Modeled Data Source......................................... 813
Concept: Enforcing Security in OfficeConnect................................................................................813
Concept: Currencies and Currency Translation.............................................................................. 814

Concept: Differences Between OfficeConnect and Report Writer.................................................. 814

Concept: Differences in OfficeConnect Between Financials and Planning Data Sources...............816

Benchmarking.......................................................................................... 817
Setup Considerations: Workday Benchmarking..............................................................................817
Steps: Set Up Workday Benchmarking.......................................................................................... 820
Steps: Set Up Workday Benchmarking Subcategory Security....................................................... 822
Opt in to Benchmarking.................................................................................................................. 823
Concept: Workday Benchmarking...................................................................................................824
Concept: Workday Benchmarking Reports..................................................................................... 826
Reference: Benchmarking Security Domains and Report Data Sources........................................828
FAQ: Workday Benchmarking.........................................................................................................829

Glossary....................................................................................................830
Glossary........................................................................................................................................... 830
Cross Application Services Glossary.............................................................................................. 830
Financial Management Glossary.....................................................................................................835
HCM Glossary................................................................................................................................. 836
Integration Glossary........................................................................................................................ 841
Payroll Glossary.............................................................................................................................. 843
Student Glossary............................................................................................................................. 844

Reporting and Analytics

In this book, you can learn about Workday reporting and analytics features.

Custom Reports and Analytics

Workday Reporting Concepts

Concept: Custom Reports

You can create custom reports to serve your requirements beyond the Workday-delivered standard
reports.
As with standard reports, you can:
• Access the related actions menu on custom report results.
• Download custom report outputs as a PDF or spreadsheet.
• Enable a custom report as a worklet.
• Translate a custom report to another language.
You can create a custom report by:
• Accessing the Create Custom Report task.
• Copying a Workday-delivered standard report.
• Copying an existing custom report.
• Selecting Custom Report > Create from the related actions menu of a report data source (RDS).

Report Ownership
When you create a report, you own it, and can perform these actions on it:
• Edit
• Delete
• Run
• Share
• Test
You can use the Transfer Ownership of Custom Reports task to transfer the ownership of a report to
anyone who has access to the RDS and data source filter. When you transfer ownership of a report that
you shared with other users, those users continue to have access to the transferred report.

Custom Report Sharing

When you change a shared report, other users can view the results of your changes immediately.
When you copy a custom report, Workday sets the sharing option to Don't share report definition on the
copy of the report. You can change the sharing options on the Share tab of your custom report.

Report Performance
You can improve report performance by:
• Filtering out instances of the primary business object or of related business objects that you don't need.
• Minimizing the number of calculated fields.

• Only using indexed RDSs and indexed fields.

Report Filtering
You can filter your report by:
• Prompting report runners for filter values when they run the report.
• Setting up facet filters so that the report runner can interactively filter report results.
• Setting up filters and subfilters in the report definition.
The report first applies filters to instances of the primary business object that are in the RDS or data source
filter. The report then applies any subfilters to instances of related business objects.
Related Information
Concepts
Concept: Indexed Data Sources and Fields on page 15
Concept: Report Security on page 19
Reference
Reference: Report Types on page 19
Reference: Security Domains for Reporting on page 87
The Next Level: Define Your Organization's Workday Reporting Guidelines
The Next Level: Factors Impacting Report Performance
The Next Level: Definition of Report Types - Standard and Custom
The Next Level: Reporting Foundation Community Guide
The Next Level: Reporting Housekeeping
The Next Level: Taking the Stress Out of Reporting: Getting Started

Concept: Business Objects, Data Sources, and Fields

Business Objects
Workday stores data in business objects. A business object has fields and instances, which are similar to
rows and columns in a spreadsheet. Each row is an instance, and each column represents an attribute or
field related to that instance.
Example: Logan McNeil and Teresa Serrano are each an instance of the Worker business object. The
Worker business object contains fields such as Job Title, Age, Gender, and Dependents.

Worker (Self- Job Title (Text) Age (Numeric) Gender (Single Dependents
Referencing) Instance) (Multi-instance)
Logan McNeil Chief Human 47 Female Megan McNeil
Resources Officer
Pat McNeil

Teresa Serrano Chief Financial 61 Female Juan-Carlos

Officer Serrano
Pablo Serrano

Workday links related business objects together through single instance or multi-instance fields. Related
business objects enable you to access fields in a report that don’t belong to the primary business object.
Example: The Worker business object has a multi-instance field called Dependents. Dependents has a
related business object of Dependent. In a report with a primary business object of Worker, you can use
the Dependents field to access the fields belonging to the Dependent business object.
Run the Business Object Details report to view:

• Custom and standard reports that use the business object.

• Data sources using the business object as the primary business object.
• Fields associated with the business object.
• Related business objects.

Data Sources
When you create a report, you must select a data source. Each data source contains instances of a
business object, which serves as the primary business object of the data source. Multiple data sources can
have the same primary business object. Example: Both the All Workers and Workers for HCM Reporting
data sources have Worker as the primary business object.
Workday delivers many data sources. Example: Workers for HCM Reporting, Journal Lines for
Financial Reporting. Consider selecting a data source with a primary business object that includes a
majority of the fields you need.
Some data sources return all instances of the primary business object, such as All Workers. Some data
sources also include:
• Built-in filters that limit the number of business object instances. Example: All Active Employees.
• Prompts that you can use when running the report. Example: Employees by Organization.
Workday secures data sources and data source filters by security domains. Different domains might secure
a data source and its data source filters. Example: Many domains secure the Workers for HCM Reporting
data source, but only the Worker Data: Headcount Reports and Worker Data: Turnover Summary domains
secure the Workers by Role filter on the data source.
From the related actions menu of a data source, you can:
• Select Custom Report > Create to create a custom report using the data source.
• View Alternate Data Source and Alternate Data Source Filter for a deprecated data source, if
available.
Run the Data Sources report to view these data source details:
• Built-in prompts.
• Data source filters.
• Permitted security groups.
• Primary business object.

Fields
Workday supports field types such as:
• Boolean
• Numeric
• Text
• Single instance
• Multi-instance
Workday secures fields by security domains. Users must have access to the security domain to:
• Use the field in a report definition.
• View data in that field when running the report.
You can only use some fields in certain areas of Workday, such as Business Rules or Compensation
Eligibility. To see where you can use a field, click its related actions menu and check the Authorized
Usage. If a field has an Authorized Usage value of Default Areas, you can use that field in any area.
Run the Report Fields report to view details such as:
• Business object name.

• Field description.
• Field type.
Related Information
Reference
Reference: Field Types on page 66
The Next Level: Report Performance Recommendations for Large Volume Customers
The Next Level: Report Security Overview
The Next Level: Workers for HCM Reporting Data Source: Report Migration
The Next Level: Taking the Stress Out of Reporting: Getting Started

Concept: Indexed Data Sources and Fields

A Workday business object can have several standard report data sources (RDSs) associated with it, each
representing a different filter or selection into instances of that object. Workday indexes certain RDSs and
report fields for:
• Aggregation.
• Faceted filtering.
• Report performance on large volumes of data.
When you create a custom report based on an indexed RDS, Workday prompts you to select from a list of
predefined data source filters, if available.

Report Data Sources and Report Types

You can create these custom report types using standard or indexed RDSs:

Report Type Report Data Source Type

Advanced Standard or Indexed
Matrix Standard or Indexed
nBox Indexed
Search Indexed
Simple Standard or Indexed
Transposed Standard or Indexed
Trending Standard or Indexed

When creating or editing custom reports that use indexed RDSs, you can select the Optimized for
Performance check box to display only indexed report fields in field prompts.

Indexed Data Sources and Fields

The View Indexed Fields for Data Source report lists all indexed report fields for each RDS and the focus
for indexing:

Column Description
Indexed for Filter Workday indexes the report field for use on the
Filter tab of report definition.
Indexed for Facets Workday indexes the report field for use in Facet
Filter options on the Advanced tab.

Column Description
Indexed for Aggregation Workday indexes the report field for summarization,
such as Sum, Average, Minimum, or Maximum.
Indexed for Group By Workday indexes the report field for column or row
grouping.

Workday displays an Indexing Information section on the related actions menu of a report field. Workday
also displays an Indexed column on the:
• Filter tab for advanced, matrix, and trending report.
• Matrix tab for matrix reports.
• Trending tab for trending reports.
The Indexed column indicates whether the report can run in indexed mode for the condition.

Limitations on Indexed Data Sources

Report Type Tab Limitation

All report types Filter When you select an indexed RDS
that requires a data source filter,
Workday populates the Data
Source Filter prompt. If needed,
you can select another filter from
a list of predefined filters for the
RDS.
Consider these filter limitations for
all report types:
• You can filter only on report
fields indexed for facets or
indexed for search.
• You can't filter on a calculated
field.
For text and rich text fields, you
can't use filter count operations
on instance fields.

Advanced Filter You can't filter on an indexed

object as a related business
object.
Matrix and nBox Matrix For group by fields, you can use:
• Boolean fields indexed for
grouping.
• Single instance fields indexed
for grouping.
For group by fields, you can't use:
• Calculated fields.
• Numeric fields.
• Text fields.

Report Type Tab Limitation

For fields to summarize, you can't
use calculated fields.

Matrix and nBox Advanced The same limitations that apply

to group by fields apply to the
drillable fields.
Search Advanced You can use only report fields
indexed for facets as facet filters.
Simple, Advanced, Matrix, nBox, Prompts You can't prompt for the Effective
Search, and Transposed Date or Entry Date.

Consider these additional limitations:

• Indexed RDSs that include Event fields only enable the Positions I Support option in a role-based
security group (constrained).
• Reports using indexed RDSs don't support effective dates other than the current moment when you run
the report. If you need to specify an effective date other than the current moment, use a standard data
source.
• Workday might take several hours to update an indexed RDS with the most recent data in your
tenant. Example: Workday updates the Trended Workers RDS weekly for nonproduction tenants
(Implementation and Sandbox), and either nightly or every Monday for production tenants depending on
your retroactive period selection.
Related Information
Reference
The Next Level: Factors Impacting Report Performance
The Next Level: Report Performance Recommendations for Large Volume Customers

Concept: Selecting a Data Source

The data source you select for a report determines what fields you can access and is the largest factor in
report performance.
For optimal report performance, select the data source that returns the fewest business object instances
that you need. Example: Use the My Direct Reports data source instead of filtering the All Active
Workers data source by manager.

Questions to Consider

Question Considerations
What fields do you need? List all the fields you want the report to display. If
you don't know the business object that contains
these fields, use the Workday-delivered Report
Fields report to look up the fields.
What business object should you report on? Select the business object that contains the
majority of the fields you want as the primary
business object for the report. Then, you can use
the Business Object Details report to find a data
source.
You can also run the Workday-delivered Data
Sources report and filter by Category to help you
find a data source.

Question Considerations
Who needs access to this report? Ensure that the target audience of the report has
access to the data source and fields you use.
Where will the report run? Reports that run as worklets on a dashboard time
out after 30 seconds, so it's important to consider
performance when you select a data source.
For scheduled reports or reports you run in the
background, report performance isn't as important.

Data Source Characteristics

If you know the business object that you want to report on, consider these data source characteristics.

Characteristic Description Examples

Indexed Returns large volumes of data • Indexed Workers
efficiently. • Trended Workers
Whenever a report needs to run
fast, such as in a worklet, use an
indexed data source.

Filtered Includes built-in filters that limit • Workers by Organization

the number of instances the data • Workers Supported by Role
source returns.
If an indexed data source doesn't
meet your requirements, use a
filtered standard data source.

Focused Returns only the instances for a • My Direct Reports

specific security group. • My Team's Goals
If you want to report on a small
set of business object instances,
use a focused data source.

Data Sources with Built-In Filters

Instead of creating your own filter in the report definition, use the faster built-in data source filters whenever
possible. Example: Use the Workers by Role filter on the Workers for HCM Reporting data source.

Data Sources with the (Do Not Use) Label

Don't use data sources that have the (Do Not Use) label. Example: Job Applications, Prospects and
Referrals (Do Not Use). Workday retires data sources with the (Do Not Use) label, sometimes because
there's a new and better data source. You can search for replacements for retired data sources in the
What's New in Workday report.
Related Information
Concepts
Concept: Business Objects, Data Sources, and Fields on page 13
Tasks
Create Custom Reports on page 29
Reference
The Next Level: Factors Impacting Report Performance

The Next Level: Reporting on Non-Worker HCM Data: Considerations to Optimize Performance
The Next Level: Reporting on Worker Data: Considerations to Optimize Performance
The Next Level: Workers for HCM Reporting Data Source: Report Migration

Concept: Report Security

Report Data Sources

Workday secures every report data source (RDS), RDS filter, and report field through a security domain.
Example: When you view workers on a report, you might see their legal name but not their Social Security
number.
Workday might secure an RDS and its RDS filters by different domains. Example: A user could have
access to the Workers for HCM Reporting RDS, but can’t access the Workers by Role filter.
The Data Sources report displays which security groups can access each RDS and RDS filter.

Constrained Security Groups

Workday secures some RDSs, RDS filters, and report fields by constrained security groups. Users in
constrained security groups can only view the instances available to their organization or role. Example:
Managers in different organizations might all have access to employee performance data, but they can
only view the performance data of employees in their respective organizations.

Report Sharing and Exporting

Sharing a report doesn't override report security. You can only share a report with users authorized to
access it, and they might not see the same data as you.
The Export to PDF and Excel domain in the System functional area restricts who can export these types of
files:
• Excel
• PDF
• PowerPoint
(For Workday Extend only) The Export to Excel feature on grids in Workday Extend doesn't support
security policies configured on the Export to PDF and Excel domain. To prevent users from exporting grid
data, the Workday Extend app developer must disable the Export to Excel feature on the grid.
Related Information
Reference
The Next Level: Factors Impacting Report Performance
The Next Level: Report Security Overview
The Next Level: Report Security Troubleshooting Scenarios

Reference: Report Types

Report Type Description Example Standard Report

Advanced Display fields from the primary Job History
business object and related
business objects with advanced
design options, including:
• Filtering
• Subfiltering
• Prompting
• Sharing

Report Type Description Example Standard Report

Advanced report results can
display on charts and worklets
and with multiple headings and
subtotals.
You can enable advanced
reports for use as web services in
outbound EIBs.

Composite Combine multiple reports into 1 Budget vs Actual Spend by

report. Each subreport can have Quarter
a different report data source.
Matrix Group and summarize data by 1 Headcount & Open Position
or 2 fields that contain repeating Analysis
values.
You can display matrix results in
a chart or table that you can drill
down on for additional details.
This enables you to perform
custom analytics and interactive
reporting across dimensions.
Matrix reports are similar to pivot
tables and crosstabs.

nBox Display counts of business object Talent Matrix - Performance by

instances in a 2-dimensional Potential
matrix, enabling you to compare
and visualize objects across 2
fields.
Search Display instances of a business Find Candidates
object that you can narrow down
with facet filters or search terms.
You can enable search reports for
use as web services in outbound
EIBs.

Simple Display fields from the primary None

business object with basic and
limited design options, such as
filtering and sorting.
Transposed Compare and analyze data by Employee Timeline
swapping rows for columns.
Trending Group data by time period for Hires and Terminations by
trend analysis. You can also Quarter
group, summarize, and drill down
on data.

Related Information
Concepts
Concept: Custom Reports on page 12

Tasks
Steps: Create Simple Reports on page 104
Steps: Create Advanced Reports on page 106
Steps: Create Matrix Reports on page 112
Steps: Create Composite Reports on page 128
Steps: Create Transposed Reports on page 178
Steps: Create Trending Reports on page 162
Steps: Create Search Reports on page 180
Steps: Create nBox Reports on page 183

Set Up Reports

Setup Considerations: Custom Reporting

You can use this topic to help make decisions when planning your configuration and use of custom
reporting. It explains:
• Why to set it up.
• How it fits into the rest of Workday.
• Downstream impacts and cross-product interactions.
• Security requirements and business process configurations.
• Questions and limitations to consider before implementation.
Refer to detailed task instructions for full configuration details.

What It Is
You can create custom reports to serve reporting and analytics requirements specific to your business
needs.
As with standard reports, custom reports enable you to:
• Access real-time, relevant data.
• Take action on the data directly from the report results.
• Use configurable security to limit access to reporting data.

Business Benefits
Custom reports enable you to:
• Create reports for your specific business needs.
• Enable a report as a worklet.
• Maintain greater control of your reports, since they remain unchanged when Workday updates standard
reports.
• Schedule reports and share results with different groups in various formats.
• Transfer data into or out of Workday by enabling reports as web services.
• Translate a report to another language.

Use Cases
• Copy an existing standard report and modify it for your business.
• Create a new custom report.
• Create or edit dashboards to display multiple related reports.
• Extract data from Workday through an Enterprise Interface Builder (EIB) integration.

Questions to Consider

Questions Considerations
Which standard report can you use to provide the You can run the Workday Standard Reports
results you need? report to view these 2 types of Workday-delivered
standard reports:
• Report Writer reports. You can copy these
reports and perform additional edits on the
copy, in addition to using them on custom and
Workday-delivered dashboards.
• XpressO reports. You can’t copy, edit, or
use them on custom dashboards. You can
use XpressO reports on Workday-delivered
dashboards.
If none of the standard reports meet your needs,
you can copy then edit an existing report, or create
a custom report.

Do you want to delegate report management to 1 You can designate a report administrator to
role in your organization/tenant? manage all the reports in your tenant.
What report data source (RDS) should you select? The data you can access in a report depends on
the RDS you select. Each RDS contains instances
of a business object, which serves as the primary
business object. Multiple RDSs can have the same
primary business object.
Consider selecting an RDS with a primary business
object that includes most of the fields you need.
Whenever possible, select an indexed RDS.
Indexed RDSs enable your report to run faster than
standard RDSs.
If your report needs to be effective dated, you must
use a standard RDS.

How can you use multiple RDSs on 1 report? You can combine data from multiple RDSs in
composite reports. Composite reports access data
through the RDSs of subreports. You can reference
these report types as subreports:
• Advanced
• Matrix
• Trending

How can you include fields that aren't in the RDS? You can create calculated fields that use existing
data in Workday to:
• Change your data into different formats.
• Configure constant values for your data.
• Perform simple calculations on your data.
• Retrieve your data.
You can also add custom fields to business objects
when you create a custom object.

Questions Considerations
Do other users need access to the data in this If users have access to the correct security
report? domains, they can run the report and edit the report
definition.
You can also export report results as a spreadsheet
or PDF and share the file with other users.
Spreadsheets and PDFs don't retain any security
restrictions.

Do you want to enable your report as a web You can enable advanced and search reports as
service? web services, which enable access to report results
through URLs. You can use these web services in:
• Integrations between Workday and external
business services. Example: Payroll or benefits
providers.
• External reporting tools to access Workday data.
Example: Microsoft Excel.

Do you need reports to run at specific times or at You can schedule when and how often reports run.
regular intervals? Scheduled reports run in the background, and you
can download the report output files.
Do you want to run multiple reports at the same You can create groups of related reports and
time? schedule them to run at the same time. Example:
Year-end financial reports.
You can also burst reports by using a report group
to run a single report with different prompt values in
quick succession.

How do you want the report results to display? You can display report results in a chart, table, or
both. Matrix reports are the best report type for
displaying most chart types.
You can also display reports as worklets on a
dashboard to give stakeholders an overview of
important data. Examples: The Workday-delivered
Compensation and Benefits and Diversity
dashboards.

How do you organize and manage all the reports in You can tag reports to organize them and make
your tenant? them easier to search for.
Workday recommends that you regularly review
your custom reports and delete unused reports.

Recommendations
Use the Workday Standard Reports report to search for existing standard reports that might fit your
requirements before creating a new custom report.
Create custom reports in Implementation or Sandbox tenants before migrating them to your production
tenant.
For optimal performance:
• Use indexed RDSs.
• Select the smallest RDS that includes all the business object instances you need.

• Instead of creating your own filter in the report definition, use the faster built-in RDS filters whenever
possible. Example: Use the Workers by Role filter on the Workers for HCM Reporting RDS. The Data
Sources report has a column that indicates RDS filters.
• Select an RDS that includes built-in prompts instead of creating your own prompts. The Data Sources
report has a column that indicates whether an RDS includes built-in prompts.
• Limit the number of calculated fields in your report.

Limitations

Limitations Considerations
Copying Reports Your report must have a Type of Report Writer on
the Workday Standard Reports report.
Filtering Workday doesn't support filtering on fields that
return derived instances, such as lookup date rollup
calculated fields.
Report Processing Time Reports have different processing time limits
depending on where you run them:
• 30 minutes for all reports.
• 6 hours for background reports, scheduled
reports, and web services.
After 20 seconds, Workday enables you to
schedule the report to run as a background
process. If report processing exceeds 30 minutes,
Workday displays an error.

Dashboard Processing Time Dashboards time out after 30 seconds, so reports

you deploy as worklets on dashboards must finish
running within that time.

Security
These security domains are in the System functional area:

Domains Considerations
Ability to Create Only Temporary Reports Enables you to restrict users to create only
temporary reports.
Custom Report Administration Enables you to take these actions on custom
reports:
• Add to the related actions menu of a business
object.
• Add to the sitemap.
• Transfer ownership.

Custom Report Creation Enables you to create and modify custom reports.
Data Translation Enables you to translate custom reports.
Manage: All Custom Reports Enables you to take these actions on custom
reports:
• Delete.
• Edit.

Domains Considerations
• Give users view-only access.
• Transfer ownership.
• View.

Report Definition Sharing - All Authorized Users Enables you to share report definitions with all
users authorized to access the RDS of the report
definition.
Report Definition Sharing - Specific Groups Enables you to share report definitions with other
users in a security group.
Report Definition Sharing - Specific Users Enables you to control which users can share
report definitions with specific, named users.
Report Tag Management Enables you to provide access to users to manage
report tags.

Business Processes
You can run a custom report as a business process step by adding a Report type step. Example: In the
Hire business process, Workday sends a report of subordinates to the manager, including the new hire.
When the business process runs, Workday enforces the security associated with the report. The report
displays only the information that the recipient has permission to access.

Reporting
You can use these Workday-delivered reports and dashboards to track report usage in your tenant:
• Dashboard Run History report: Displays dashboard usage statistics from the previous 6 months and
includes details such as who ran the report and at what time.
• Data Sources report: Displays these RDS details:
• Built-in prompts.
• RDS source filters.
• Permitted security groups.
• Primary business object.
• Report Administrator dashboard: Displays reports and tasks that help you manage the reports in your
tenant.
• Report Run History report: Displays how many times a report ran and includes details such as who
ran the report and at what time.
• Workday Standards report: Displays Workday-delivered reports.
You can create custom reports and track information, such as report owner and time of last update, based
on these RDSs:
• All Custom Reports
• All Standard Reports
• Indexed Dashboard Run History
• Indexed Report Run History

Integrations
You can enable custom advanced and search reports as web services and use them in integrations
between Workday and external business services.

Connections and Touchpoints

Workday offers a Touchpoints Kit with resources to help you understand configuration relationships in your
tenant. Learn more about the Workday Touchpoints Kit on Workday Community.
Related Information
Concepts
Concept: Business Objects, Data Sources, and Fields on page 13
Concept: Object Transporter 2.0
Concept: Report Step
Concept: Report Tags on page 82
Concept: Selecting a Data Source on page 17
Setup Considerations: Calculated Fields
Setup Considerations: Payroll Register
Tasks
Schedule Reports or Report Groups on page 74
Reference
Reference: Reporting Limits
Reference: Report Types on page 19
The Next Level: Define Your Organization's Workday Reporting Guidelines
The Next Level: Move up the Workday Maturity Curve: Considerations in Defining an Analytics Strategy
The Next Level: Report Types - Standard & Custom
The Next Level: Reporting Foundation Community Guide
The Next Level: Taking the Stress Out of Reporting: Getting Started

Setup Considerations: Charts

You can use this topic to help make decisions when planning your configuration and use of charts. It
explains:
• Why to set them up.
• How they fit into the rest of Workday.
• Downstream impacts and cross-product interactions.
• Security requirements and business process configurations.
• Questions and limitations to consider before implementation.
Refer to detailed task instructions for full configuration details.

What They Are

Charts enable you to display data in an output type that best fits your business needs. You can compare
metrics, view the relationship between sets of data, and visualize changes for these report types:
• Advanced
• Composite
• Matrix
• Trending

Business Benefits
Charts in Workday:
• Are the most efficient way to analyze and dynamically interact with your data.
• Enable you to change from 1 chart type to another when the report runs, so you can determine the best
chart type to represent your data.
• Enable you to gain insight by drilling into the data.

Use Cases
The chart type that you select depends on the data that you need to display and how Workday should
display it. You can:
• Analyze the relationship between the whole and each part of the whole by using a donut chart.
Example: The percentage of open positions against all positions in your organization.
• Compare metrics with different scales by overlaying 2 charts.
• Display consolidated management information and actionable items by adding a worklet to a
dashboard.
• Display data in 3D using an area, bar, or line chart.
• Plot data over time by using a line chart. Example: The number of new hires for each quarter over a
fiscal year.
• Plot relationships between data by using a bubble chart. Example: The average invoiced amount versus
the total invoiced amount for each supplier.
• Plot the relationship between numeric values by using a scatter chart. Example: The performance of a
worker population as a percentage against their retention risk.
• View a single value on a gauge, like a speedometer in a car, by using a gauge chart.
• View data for each category by using a bar or column chart. Example: The top 10 organizations in your
company with the highest headcount.

Questions to Consider

Questions Considerations
What kind of data do you need to represent in You can deliver data in different ways to capture
charts? averages, benchmarks, trends, and so on, as:
• Comparisons.
• Parts of a whole.
• Patterns and relationships among multiple
values.
• Target line deviation.
• Time series analysis.

How do you want to present your data visually? The availability of some chart types depends on the
report type that you select. You can:
• Combine an area - overlaid, column - clustered,
or line chart to create a dual-axis chart on
composite, matrix, and trending reports.
• Use a gauge on advanced reports to display a
single value of data on a dial.
• Use a scatter chart on advanced reports to
plot the relationship between pairs of numeric
values.
• Use a table with columns and rows to display
your data in a grid.
You can use all other chart types on any report type
that enables output options.

Recommendations
Use the Table output option on subreports so that data displays on a composite report without errors.

Requirements
• To display area, bar, and line charts in 3D, use Report Designer, which is an application of the Eclipse
Business Intelligence and Reporting Tools (BIRT) project.
• To display your data on a chart, you must have enough data to populate the chart. Example: If you have
only 1 category or data series to plot, a donut chart wouldn't be the best option for displaying your data.

Limitations
• Workday doesn't support dual-axis and combination charts on mobile devices.
• You can't print charts or export them to Excel.

Tenant Setup
No impact.

Security
The Custom Field Management domain in the System functional area enables you to create and manage
custom fields, including gauge ranges.

Business Processes
No impact.

Reporting
You can view the chart types supported by custom reports on the All Custom Reports report.

Integrations
No impact.

Connections and Touchpoints

Workday offers a Touchpoints Kit with resources to help you understand configuration relationships in your
tenant. Learn more about the Workday Touchpoints Kit on Workday Community.
Related Information
Concepts
Concept: Charts on page 48
Setup Considerations: Report Designer on page 245
Tasks
Set Up Output Options for Custom Reports on page 39
Set Up Output Options for Composite Reports on page 139
Reference
Reference: Chart Types on page 50

Copy Reports

Prerequisites
Security:
• Custom/Standard Report Copy domain in the Tenant Non-Configurable functional area.
• Set Up: Tenant Setup - General domain in the System functional area.

Context
You can create a new custom report by copying any:
• Custom report.
• Report on the Workday Standard Reports report that lists Report Writer in the Type column.
Some standard reports are available as worklets in dashboards, but you can’t search for nor copy them.
These reports don’t display on the Workday Standard Reports report.

Steps
1. Access 1 of these tasks:
• Copy Custom Report
• Copy Standard Report to Custom Report
2. (Optional) For custom composite reports, select the Copy Subreports check box on the Copy Custom
Report task to copy the underlying subreports for the copied composite report.
Workday appends a timestamp to each subreport with the same name where the timestamp represents
the:
• 4-digit year.
• 2-digit month.
• 2-digit day.
• 2-digit hour.
• 2-digit minute.
• 2-digit second.
• 3-digit millisecond.
• Time zone.
Example: 2023 03 10 09 39 45 440 -0800.

Next Steps
For copied subreports, update the sharing permissions from the populated Don't share report definition
selection.
You can access the Hide Workday Delivered Report task to hide the original standard report so that you
don't have 2 versions of the report on:
• Menus.
• Related actions menus.
• Scheduling options.
• Search results.
You can't hide the report when Workday references it in another location, including integrations or
scheduled report group.
Related Information
Reference
The Next Level: Report Types - Standard & Custom
The Next Level: Report Actions Against Existing Reports (Run, Copy, Hide, Edit, Migrate from WDSETUP)

Create Custom Reports

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation

• Manage: All Custom Reports

• Report Tag Management

Context
In addition to using Workday-delivered standard reports, you can create custom reports to analyze data in
your tenant.
Workday recommends you create custom reports in Implementation or Sandbox tenants before migrating
them to your production tenant.

Steps
1. Access the Create Custom Report task.
2. As you complete the task, consider:
Option Description
Temporary Report (Optional) Select the check box to enable
Workday to delete the report after 7 days.
For all report types except simple reports, you can
change the deletion date on the Advanced tab.

Enable As Web Service (Optional) For advanced or search reports, select

the check box to:
• Use the report in an outbound EIB.
• Enable external web sites to access the report.
Set up Web Services Options on the Advanced
tab.

Optimized for Performance (Optional) For reports using indexed data

sources, select the check box to display only
indexed fields in field prompts.
If you need to use nonindexed fields, clear the
check box on the Advanced tab.
This option is unavailable for search and nBox
reports.

Data Source For nBox and search reports, you can only select
an indexed data source.
Note: When the Optimized for Performance
check box is active, you can only select an
indexed data source. Clear the Optimized for
Performance check box to select a standard or
nonindexed data source.
See Concept: Selecting a Data Source on page
17.

Report Tags (Optional) Create or select Report Tags to

categorize your report and make it easier to find.
Comments (Optional) In the Additional Info section, enter
comments to track information, such as report
notes, who requested the report, and so on.

Option Description
These internal comments won't display in the
report output.

Next Steps
You can click Grid Preferences on the table toolbar when you edit, run, or view reports to:
• Change the order of columns.
• Display or hide columns.
• Freeze columns.
The availability of Grid Preferences depends on the report type. Workday:
• Doesn't display Grid Preferences on reports that use column groups or column group headings.
• Doesn't retain your grid preferences when you export the report.
• Retains your grid preferences when you log into Workday.
Related Information
Concepts
Concept: Object Transporter 2.0
Reference
Reference: Report Types on page 19
The Next Level: Factors Impacting Report Performance
The Next Level: Migratable Custom Reports Useful for Report Writers
The Next Level: Taking Action Against Existing Reports (Run, Copy, Hide, Edit)
The Next Level: Defining the Description Fields on Report Definitions

Create Reports from Business Object Instances

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports
• Report Tag Management

Context
To report on familiar data, you can create a custom report based on a business object instance. Example:
Create a report from Logan McNeil, a Worker business object instance.

Steps
1. Search for the business object instance that you want to use as the basis of your custom report.
2. From the related actions menu of the business object instance, select Reporting > Create Custom
Report from Here.
3. Select the fields to include in your custom report.

Next Steps
Complete the tabs on the Edit Custom Report task.

Find Custom Reports by Data Source

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can copy the All Custom Reports report and configure it to display reports that use a specific report
data source (RDS). Example: You can find reports that use the Trended Workers RDS so you can
manage reports in your tenant.
You can also configure the report to display report-specific calculated fields so you can view their Indexing
Information.

Steps
1. Access the All Custom Reports report.
2. From the related actions menu, select Custom Report > Copy.
3. (Optional) On the Columns tab, select Calculated Fields for Report on the Field prompt to include
reports that contain report-specific calculated fields.
4. As you complete the Filter on Instances grid on the Filter tab, consider:
Option Description
Field Data Source
Operator in the selection list
Comparison Type Prompt the user for the value
Comparison Value Default Prompt
5. (Optional) To include reports with report-specific calculated fields, select:
Option Description
Field Calculated Fields for Report
Operator is not empty
6. On the Prompts tab, select the Populate Undefined Prompt Defaults check box.

Result
When you run the report, Workday displays all custom reports that use the report data source specified on
the prompt. Optionally, Workday displays reports with report-specific calculated fields so you can view the
Indexing Information from the related actions menu. Using indexed calculated fields might improve the
performance of your report.

Set Up Drill Down for Custom Reports

Prerequisites
• Create a custom report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can configure the column and sort options that display when report runners drill into instances for
these report types:
• Matrix
• nBox
• Trending

Steps
1. Access the Edit Custom Report task.
2. As you complete the Group By Fields section on the Drill Down tab, consider:
Option Description
Sort Dimensions Alphabetically Select to sort dimensions alphabetically instead of
by their order in the grid.
Fields That Can Be Summarized Select to add or remove fields from the populated
list. Workday enables these field types for
summarization:
• Boolean.
• Date.
• Numeric.
• Single instance.
• Text.

Field Specify fields to enable drilling. If you specify a

field, Workday changes the Fields That Can Be
Summarized option to Specific Fields.
Label Override Specify a name to use instead of the populated
name on this report to ensure that any future
renaming by Workday doesn't impact your labels.
Indexed (Available for matrix and trending reports only.)
Workday selects the check box to indicate if your
report has the potential to run faster based on
your Drillable Fields grid selections.
3. As you complete the Detail Data section, consider:
Option Description
Column Heading Override Specify a name to use instead of the populated
name on this report to ensure that any future
renaming by Workday doesn't impact your labels.
Options Available options depend on your field type.
4. (Optional) In the Sort section, set up how Workday should sort the fields and associated fields in the
Detail Data section.
5. (Optional) Select from the Drill Down Options prompt to disable drilling options in your report.

Set Up Sort Options for Custom Reports

Prerequisites
• Create a custom report.

• Security: These domains in the System functional area:

• Custom Report Creation
• Manage: All Custom Reports

Context
You can configure the sort order for data groups in these report types:
• Advanced
• Search
• Simple
• Transposed
You can configure sorting on search reports only with these report data sources:
• Find Candidates
• Job Posting
• Job Posting Anchor
• Learning Content

Steps
1. Access the Edit Custom Report task.
2. (Optional) As you complete the Sort tab for search reports, consider:
Option Description
Sort by Relevance Select the check box to sort the search results
based on how well they match your search
criteria.
Note: Workday must render and sort all results
before returning the results to you. Workday runs
indexing as a background process every 24 hours
for nonproduction tenants, and every 12 hours for
production tenants. When you select the check
box, use indexed fields so that Workday can
update results efficiently, such as on external
sites.
You can clear the check box so that Workday
displays all report results before the background
indexing process completes.

Display Matching Fields (Available when you select Sort by Relevance.)

Select the check box to display the fields that
match your search criteria under each search
result.
3. (Optional) As you complete the Sort and Group section for advanced, simple, and transposed reports,
consider:
Option Description
Sort by first accessible column (Advanced reports only.) Select the check box to
sort by the first column on the Columns tab users
have access to when the Sort and Group section
is empty.

Option Description
If you don't select the check box and the Sort and
Group section is empty, Workday doesn't apply
sorting to any column.

Field Select a field from the prompt to use as the sort

criteria. The order of the fields specifies the sort
sequence and group hierarchy for the report.
Display Headers (Advanced and simple reports only.) Select the
check box to display group headers for the sort
and group level and provide a logical separation
of data on the report.
You must include Group Name as a Field on the
Columns tab.

Summarize Detail Rows (Advanced reports only.) Select the check box to
group and summarize the detail rows and display
them as summary rows for each sort/group field
on the report. The field must be the last row in the
Sort and Group grid.
Display Subtotals (Advanced and simple reports only.) To specify
that you want to display subtotals for a sort or
group level, select the check box to include:
• An aggregate function for a currency or
numeric field in the Options of the Columns
tab.
• Count as a Field on the Columns tab.

Group Name Override (Advanced reports only.) You must include Group
Name as a Field on the Columns tab.
4. (Optional) As you complete the Grouping and Totaling Options section for advanced and simple,
consider:
Option Description
Enable Outlining based on Grouping (Advanced reports only.) Select the check box
to summarize detail data or subtotal currency or
numeric data. You must include Group Name as a
Field on the Columns tab.
To group data, select the Display Headers check
box for each sort field to include in the outline.
To subtotal currency or numeric data, select the
Display Subtotals check box, then select an
aggregation from the Options prompt on the
Columns tab.
When enabling outlining, consider:
• All fields on the report must associate with the
primary business object associated with the
report data source.
• If you export an outlined report to Microsoft
Excel, all levels of the report display without
outlining.

Option Description
• If you print to PDF, only the top level of the
outline prints.
• Outlined reports can't display as worklets.
• Outlining doesn't support some languages due
to right-to-left formatting limitations.
• Workday supports up to 8 levels of outlining.

Include Group Name in Headers and Subtotals (Advanced reports only.) Select the check
box to display the group name and the group
name value in the group name column of the
report. Example: Workday displays the value
San Francisco and the group name City as San
Francisco (City).
Display Grand Totals Select the check box to display the grand total of
1 of these selections:
• An aggregate function for a currency or
numeric field in the Options of the Columns
tab.
• Count as a Field on the Columns tab.

Detail-Summary Reporting (Advanced reports only and available when you

access Create Report Field from the Field
prompt in the Sort and Group grid.) Select the
level of detail to display for the lines in your report.

To enable subtotaling for fields associated with a related business object, select Sum from the Options
prompt of currency and numeric fields on the Columns tab.
Workday doesn't support:
• Grand totaling for currency or numeric fields associated with a related business object.
• Totaling currency fields with different currency codes. Example: Workday can't total USD with EUR.
5. (Optional) For advanced reports, complete the Sub Level Sort section to enable additional sorting for a
related business object.
Related Information
Concepts
Concept: Logical Sort Order on page 63
Concept: Advanced Reports on page 111
Concept: Report-Specific Calculated Fields
Reference
The Next Level: Factors Impacting Report Performance
The Next Level: Report Performance Recommendations for Large Volume Customers

Set Up Filter Options for Custom Reports

Prerequisites
• Create a custom report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can configure the Filter tab to filter the data Workday displays on custom reports. For advanced
reports, you can also add subfilters.
Workday doesn't support filtering on fields that return derived instances, such as lookup date rollup
calculated fields.

Steps
1. Access the Edit Custom Report task.
2. As you complete the Filter on Instances grid on the Filter tab, consider:
Option Description
Parentheses (Unavailable for simple reports.) Use parentheses
to group conditions together.
Operator Available operators depend on option you select
from the Field prompt.
Comparison Type (Unavailable for simple reports.) Specify how
Workday compares the values against the option
you select in the Field prompt. You can:
• Prompt the report runner for the value before
running the report.
• Specify a value from another field or within the
report definition.

Indexed (Advanced and matrix reports only.) The check

box indicates if Workday might index your report
for filtering so it can run faster.
Workday selects the check box based on the
Comparison Type, indexed option you select for
the Field, and the value in the Operator prompt.

3. (Optional) For advanced, matrix, and trending reports, complete the Filter on Aggregations grid to
filter on an aggregation function of a field.
Example: You can display the average compensation by position, excluding employees who earn more
than $200,000 per year.
4. As you complete the task, consider:
Option Description
Aggregation Function Select the function to apply to the aggregated
values.
Field Select a value to evaluate based on the related
business object.
To select text-based fields for count distinct on
matrix and trending reports that use standard
RDSs, clear the Optimized for Performance
check box on the Advanced tab.

You can't use advanced, matrix, or trending reports with filter aggregations as subreports for composite
reporting.

5. (Optional) As you complete the Subfilter tab for advanced reports, consider:
Option Description
Business Object Select a multi-instance or single instance field
based on the primary business object.
Field Select a field to evaluate based on the related
business object.
Condition as Text Workday displays your subfilter condition in
textual format when you set it up.

You can't add subfilters to reports with facet filters.

Related Information
Reference
Reference: Filter Operators on page 52
The Next Level: Factors Impacting Report Performance
The Next Level: Report Performance Recommendations for Large Volume Customers

Set Up Prompt Options for Custom Reports

Prerequisites
• Create a custom report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can set up populated values for prompts and reports data sources with built-in prompts in your report.
Workday doesn't support prompt options for simple reports.

Steps
1. Access the Edit Custom Report task.
2. As you complete the Prompts tab, consider:
Option Description
Instructions Enter text to display above the prompt fields,
including instructions for entering prompt values.
Effective Date (Available for standard data sources. Unavailable
for search or nBox reports.) Select to prompt
report runners for an effective date and time for
when the report runs.
Entry Date (Available for standard data sources. Unavailable
for search or nBox reports.) Select to prompt
report runners for an entry date and time for when
the report runs.
Populate undefined Prompt Defaults Select to enable Workday to populate the Prompt
Defaults grid with undefined prompt values.

Option Description
Field Specify the field associated with the primary
business object to use as the prompt.
Prompt Qualifier If you select a data range or a data set prompt for
the Field, select the prompt you want to override.
Label For Prompt XML Alias Available for reports enabled as a web service.
Default Value Available if you select Specify default value or
Determine default value at runtime as the Default
Type.
Select the field or value to use as the populated
prompt.

Related Information
Concepts
Concept: Effective and Entry Dates on page 49
Reference
The Next Level: Factors Impacting Report Performance
The Next Level: Report Performance Recommendations for Large Volume Customers
The Next Level: Using the Free-Form Fields on Report Definitions

Set Up Output Options for Custom Reports

Prerequisites
Create a custom report.
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can configure output display options, including:
• Help text.
• Output types to display your data as a chart, chart and table, gauge, table, or layout.
• Time series.
• Worklets.
Workday doesn't support output configurations for simple reports.

Steps
1. Access the Edit Custom Report task.
2. (Optional) Set up the Output Type section on the Output tab for these report types:
• Advanced
• Matrix
• Trending
(Advanced reports only.) You can select Gauge to specify the gauge range and metered values.

3. As you complete the Chart Options section for Chart or Chart and Table, consider:
Option Description
Scatter Chart Type Available only for advanced reports.
Horizontal/Vertical Axis Select the horizontal/vertical axis of the chart
by referencing the column grouping, the row
grouping, or other specific metrics.
If your matrix or trending report includes only
1 column grouping category, Workday doesn't
display a legend.

Add Secondary Axis (Unavailable for advanced reports.) Select the

check box to visualize changes in your data and
compare metrics with different scales using dual
axis charts. A dual axis enables you to overlay 2
of these chart types when you select 1 of them for
the Primary Axis:
• Area - Overlaid
• Column - Clustered
• Line
Select the Metrics to Include and Secondary
Vertical Axis Chart Types to use on the dual
axis chart.

Top n Values Enter the number of top results to display on your

report.
Select the Sum Remaining Values check box
to display an Other option to view the remaining
results. Clear the check box to exclude the
remaining results.
Example: You can enter 10 as the Top n Values
to view only the top 10 of 22 locations based on
the total salary expense of your organization. You
can select the Sum Remaining Values check
box to summarize the bottom 12 locations.

Sum Remaining Values Use with the Top n Values option.

Example: If you include only the top 10 locations
out of 22, you can sum the remaining 12 locations
into a single value labeled as Other on the chart.
(Available for matrix and trending reports only.)
Workday displays more than 1 Other grouping if:
• You select the Sum Remaining Values check
box.
• You enter values for the Maximum Number
of Columns, Maximum Number of Rows, or
Top n Values fields on the Matrix tab.
• Your data output exceeds the maximum
number of columns, rows, or Top n Values
you set up.

Option Description
Filter by Use with the Top n Values option.
Example: You can filter the top 10 locations by
annualized salary amount or by the last bonus
amount.

Target Line Type Set up these target line options for clustered or
stacked bar and column charts:
• Display one target line for all groups:
Enables you to select a tenant-wide calculated
field to use for drawing a single target line on
the chart. You can enter a value for the Target
Line Label.
• Display multiple target lines for each group:
Enables you to display a unique target line for
each group displayed in a bar or column chart.
Include at least 1 numeric or currency report
field to use as a target line on the Advanced
tab of the report.

Horizontal/Vertical Axis Scale If you enter an increment, maximum, or minimum

fixed value, it must match the format selected on
the Columns tab.
Example: If the maximum value is 5,000 and the
format on the Columns tab is #,##0,"K", enter 5
in the Maximum Value > Fixed field.
When plotting multiple metrics, Workday uses
the format of the first metric plotted, based on the
sequence of the metrics on the Columns tab.

Quadrants Available for scatter chart types.

Select the report fields that set up the Horizontal
Quadrant Line, the Vertical Quadrant Line, and
specify colors for each quadrant.

4. (Optional) Set up the Worklet Options.

Worklet Options are unavailable for search reports.
Before you can add this report as a worklet to a dashboard, you must also share the report with the
security groups you want to access the dashboard.
5. As you complete the Enable as Worklet section, consider:
Option Description
Available On Select the dashboards or landing pages on which
to display your worklet. Select Mobile Reports to
enable your report for mobile use.
Maximum Number of Rows You can't set a maximum number of rows for
advanced reports that include:
• Sub Level Sorts.
• Subfilters.

Option Description
Maximize Report Options Select how the worklet behaves when you click
View More... and maximize the report:
• Display this Worklet when Maximized:
Workday runs the report definition as a normal
Workday report.
• Run a Different Report when Maximized:
You can specify a report that you have the
security to run. If you don't have security
access or the report no longer exists, Workday
displays the worklet as a maximized report.
For dashboards with prompt sets, clicking View
More... enables you to view and change prompt
values populated by Workday.

6. As you set up the Help Text, consider:

Option Description
Brief Description Workday displays the description in search results
and in the related actions menu of the report.
More Info For reports you run in the browser, Workday
displays the text above the report results. For
worklets, the text displays when you click More
Information under the gear icon.
7. (Optional) Set up the Time Series Options for these report types:
• Matrix
• nBox
• Trending
Workday selects the Include All Time Periods check box to include time periods for reports. When the
report runs, Workday prompts users for the Time Series Start Date and Time Series End Date.
Related Information
Concepts
Concept: Charts on page 48
Setup Considerations: Charts on page 26
Tasks
Create Gauge Ranges on page 110
Reference
Reference: Chart Types on page 50
2020R1 What’s New Post: Dual Axis and Combination Charts
The Next Level: Using the Free-Form Fields on Report Definitions

Set Up Share Options for Custom Reports

Prerequisites
• Create a custom report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can set up sharing options to enable users to:
• Run the report.
• Use the report as a worklet.
When you change a shared report, other users can see the results of your changes immediately.
Workday doesn't support sharing options for simple reports.

Steps
1. Access the Edit Custom Report task.
2. As you complete the Share tab, consider:
Option Description
Don't share report definition Only you can view and run the report.
Share with all authorized users All users with access to the report data source
and data source filter can view and run the report.
Share with specific authorized groups and Only the security groups and users you select can
users view and run the report.
You can only select from security groups and
users who have access to the report data source
and data source filter.

Related Information
Reference
The Next Level: Report Performance - Tuning Thresholds
The Next Level: Report Security Overview

Set Up Advanced Options for Custom Reports

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can configure these report options on the Advanced tab:
• Facets to refilter your report results without rerunning the report.
• Prism data sources.
• Temporary reports.
• View options.
• Web services.
• Worksheets.
Workday doesn't support advanced options for simple reports.

Steps
1. Access the Edit Custom Report task.

2. (Optional) As you complete the View Options section on the Advanced tab, consider:
Option Description
Enable Preferred Currency (Advanced and transposed reports only.) Select
to display the preferred currency on a second line
within the same report cell.
Enable Save Parameters (Unavailable for search reports.) Select to enable
saving prompt values as report filters. You can
load these saved prompt values instead of
manually entering them when you run this report
later.
Exclude Execution Link from Search Select to hide this report from global search
so only users with the appropriate security
permission can run and view reports.
Appropriate security permission includes groups
listed as Unconstrained, such as Administrators or
Implementers.
Example: Select this check box for a report that
you want to:
• Display only as a worklet on a dashboard.
• Display only as a worklet using embedded
analytics associated with a task.
• Use as a subreport to build a composite report.
• Use to create a data view in Worksheets.

3. (Optional) (Advanced and search reports only.) As you complete the Web Services Options section,
consider:
Option Description
Enable As Web Service Select to:
• Use the report in an outbound EIB.
• Enable external web sites to access the report.
Note: When you enable a report as a web
service, Workday limits access to the external
report link to users with:
• A valid account for the tenant.
• The proper security permissions to view the
report and the data.

Namespace Workday generates a Namespace when you

enable the report as a web service, but you can
change it. Each report that's a web service must
have a unique Namespace, but Workday doesn't
enforce unique naming.
Note: If you update the Namespace in the report
definition without updating requests to the web
service, the request fails.

4. (Optional) For advanced reports only, in the Worksheets section, select the Enable for Worksheets
check box to enable users to add data from this report into workbooks. Workday doesn't support
creating custom reports with an output type of Worksheets.

5. (Optional) For advanced reports only, in the Prism section, select the Enable for Prism check box to
enable users to create a Prism dataset from the report.
6. (Optional) Select the Temporary Report check box in the Temporary Report section to schedule this
report for deletion in 7 days or on a date you select. Workday doesn’t delete temporary reports until
you run the Delete My Temporary Report Definitions task. Report Admins can run the Delete All
Temporary Report Definitions task to delete all expired temporary report definitions.
7. (Optional) (Unavailable for search and nBox reports.) For reports based on indexed data sources,
select the Optimized for Performance check box in the Report Performance section to display only
indexed fields in field prompts.
If you need to use nonindexed fields in your report, clear the Optimized for Performance check box.
8. (Optional) Set up Facet Options to enable users to refilter the report results without rerunning the
report.
Facet filtering is unavailable for advanced reports with:
• Outlining
• Subfilters
As you complete this section, consider:
Option Description
Field Select a business object or create a report field to
filter report results by.
Your security configuration determines the fields
that you can view and select.

Label Override To ensure that any future renaming by Workday

doesn't impact your facet headings, enter a label
override value.
Facet Field XML Alias (Search reports only.) Specify the web service
XML alias for the facet field. This option is only
available when you select the Enable As Web
Service check box.
Facet Configuration (Unavailable for composite reports.) Select or
create a facet configuration to focus your facet
results into bins or ranges. Facet Configuration
options are only available for currency, date,
and numeric field types and for certain hierarchy
fields.
You can create facet configurations by accessing
the Create Facet Configurations task. You
must have access to the Facet Configuration
Management domain in the System functional
area.
For search reports, you can use distance facet
configurations for report fields that:
• Return the Location business object.
• Support geographical faceting.
To use multi-instance field distance facets, select
the Sort by Relevance check box on the Sort
tab.

Option Description
Action Instance Selection Field (Search reports only.) Select the self-referencing
field associated with the business object for the
search report. The field determines the availability
of mass actions.
If you specify a value, the Enable Compare
check box becomes unavailable.

Single Action (Search reports only.) Select an action from the

prompt to perform on a search result instance.
Mass Action (Search reports only.) Select a mass action to
perform on multiple search result instances.
Example: Export more than 50 search result
instances to Microsoft Excel. You can export
more than 50 search result instances using an
advanced report that:
• Has only 1 prompt.
• Matches the business object of the mass
action.

Name (Search reports only.) Workday displays the mass

action as a button with this name.

When you enable Facet Options, the report results display a search bar if the report data source
contains searchable fields. Workday determines which fields in each data source are searchable.
Workday searches against all searchable fields in the report data source, not just the fields in the report.
Workday displays facets in these ways:

Number of Unique Values for the Facet Field Workday Displays...

Zero No results. The facet doesn't display.
1-7 All facet field values.
8-55 The 5 facet field values with the most results and
a More button that you can expand to view all
values.
>55 The 5 facet field values with the most results and
a search prompt you can use to view all other
values.
9. (Search reports only.) Select the Enable Compare check box in the Compare Options section to
enable displaying comparisons of search results.
The check box is only available for certain data sources.
Related Information
Concepts
Concept: Creating Reports to Insert into Workbooks on page 665
Concept: Displaying Currency Fields on page 62
Tasks
Lookup Hierarchy Rollup
Save Filters on page 76

Examples
Example: Export Workers Using a Search Report on page 181

Set Up Facet Configurations

Prerequisites
Security: Facet Configuration Management domain in the System functional area.

Context
Facet configurations enable you to refine the results of your facet filters further into bins or ranges.
Example: As a recruiter, you can create a facet configuration that filters for candidates within 50 miles.
Facet configuration options are available for currency, date, and numeric field types and for certain
hierarchy fields.
You can't apply facet configurations on composite and simple reports.
Only the creator of a facet configuration can view, edit, and delete it.

Steps
1. Access the Create Facet Configuration task.
2. (Optional) As you complete the Definition tab for Date or Numeric facet field types, consider:
Option Description
Sort Ranges by Count Select to sort the facet configurations from high to
low instance count.
From Value (Date field types only) Specify the number of
days to include in the facet filter range. A value
To Value
of 0 indicates the current day. Negative values
indicate days before the current day.
Example:
• A From Value of -7 and a To Value of -1
indicates a range of 1 week before the current
day.
• A From Value of 7 and a To Value of 20
indicates a range of 1-2 weeks after the
current day.

3. (Optional) As you complete the Country Filter Options section for the Distance facet field type,
consider:
Option Description
Use Country Report Field Display search results by postal codes within the
countries users select on the specified report field.
The report field must match a report field on the
Facet Filters section of the report definition.
Example: Boston, United States and Saint-
Quentin, France use postal code 02101. Display
results for only the United States when users
select the country on the report.

Select Default Countries Display search results for only postal codes within
the specified countries.

Option Description
Example: Boston, United States and Saint-
Quentin, France use postal code 02101. You can
enter United States to hide results for France.

4. (Optional) As you complete the Distance in Miles and Distance in Kilometers sections for the
Distance facet field type, consider:
Option Description
To Value Include an option on your report that filters for
results within the specified distance.
Example: Enter 50 in Distance in Miles to enable
users to filter for results within 50 miles of a
specified postal code.

Example
Date facet configurations:

Facet Value Name From Value To Value

1 Day Ago -1 0
1 Week Ago -7 -2
2-4 Weeks Ago -28 -8
5+ Weeks Ago -999 -29

Next Steps
To use your facet configuration in your report, select the facet configuration in the Facet Options section
on the Advanced tab. You can only select facet configurations that you create.

Concept: Charts
You can display report results as a chart, gauge, or table for these report types:
• Advanced
• Composite
• Matrix
• Trending
Workday plots rows as categories along the horizontal axis. Columns represent the data series, and each
data series has a unique color in the chart legend.
For all charts types except for donut, you can plot more than 1 data series on a chart.
When viewing a chart, you can:
• Drill into matrix report charts the same way you can drill into matrix report tables.
• Switch the categories with the data series so that rows represent the data series.
For composite, matrix, and trending reports, you can visualize changes in your data and compare metrics
with different scales using dual axis charts. A dual axis enables you to overlay 2 of these chart types:
• Area - Overlaid
• Column - Clustered
• Line

The Secondary Axis section is available when you select the Add Secondary Axis check box or select 1
of these chart types as the Primary Axis:
• Area - Overlaid
• Column - Clustered
• Line
Related Information
Concepts
Setup Considerations: Charts on page 26
Reference
2020R1 What’s New Post: Dual Axis and Combination Charts

Concept: Effective and Entry Dates

Workday enables you to specify an effective date when you create or change most business objects.
Effective dates identify when changes go into effect, which might differ from when data entry occurs.
Effective dates can be in the past, present, or future. Example:

Product Example
Expenses Specify when new hotel rates take effect.
Human Capital Management Specify when workers become eligible for time off
for the birth of a child.
Pay Specify when employee raises begin.
Specify when increased union dues went into
effect.

Recruiting Specify when new hires become official employees.

Student Specify when students officially enroll in classes for
next semester.

Workday never prompts you for an entry date, but always records one.
Entry dates identify when data enters Workday. Entry dates can provide a more accurate representation of
your data for auditing or security purposes. You can:
• Identify when employees complete learning modules.
• Identify when managers complete performance reviews.
• View employees who had Workday accounts on a certain date.
The 2 date types together enable you to create various types of reporting.
Workday records effective and entry dates in Pacific Standard Time (PST). Example: Workday records
employees hired on 2021-03-02T10:30:00 ACT as 2021-03-01T16:30:00 PST. Consider this discrepancy
when you report on effective and entry dates.

Example
James in Recruiting hires candidates on 2021-03-01. The candidates start on 2021-04-01, so James sets
the effective date for each candidate to 2021-04-01. When he reports on employees as of 2021-03-15, the
new hires don’t display even though their information entered Workday on 2021-03-01.
Related Information
Reference
The Next Level: Report Performance Recommendations for Large Volume Customers

Reference: Chart Types

Workday enables you to configure output display options for your data by supporting these chart types:

Chart Type Description

Area - 100% Plots the trend of the percentage each value
contributes to the total for each category over time
or categories.
Each item in the data series makes up a portion of
the area based on its percentage of the category
total.

Area - Overlaid Plots the trend of values over time or categories

and overlays each item in the series on top of
another.
Workday plots the first item in a data series first,
then overlays the remaining items in the data
series.
Overlaid area charts display best in 3D.

Area - Stacked Plots the trend of the amount of each value over
time or categories.
Bar - 100% Displays the percentage each value contributes to
the total for each category in horizontal bars.
Each bar represents 1 category. Each item in
the data series makes up a portion of the bar
width. Workday bases the width of the bar on the
percentage of the category total.

Bar - Clustered Displays the value of each category in horizontal

bars.
Bar - Stacked Displays the amount each value contributes to the
total for each category in horizontal bars.
Each bar represents 1 category. Each item in
the data series makes up a portion of the bar
height. Workday bases the height of the bar on the
proportion of the category total.

Bubble Plots the relationship between triplets of numeric

values along a horizontal and vertical axis. 2 values
determine the bubble position, while the third value
determines the bubble size.
You can plot 1 or more data series on a bubble
chart. Each data series has a unique color or
pattern.

Column - 100% Displays the percentage each value contributes to

the total for each category in vertical columns.
Each column represents 1 category. Each item in
the data series makes up a portion of the column
based on its percentage of the category total.

Chart Type Description

Column - Clustered Displays the value of each category in vertical
columns.
Column - Stacked Displays the amount each value contributes to the
total for each category in vertical columns.
Each column represents 1 category. Each item in
the data series makes up a portion of the column
based on its proportion of the category total.

Donut Displays the relationship between the whole and

each part of that whole.
Donut charts display only 1 data series. Each
category has a unique color for each donut
segment.

Gauge Displays a single value on a gauge, like a

speedometer in a car.
Line Plots data points over time.
The slope of the line indicates the trend.
Line charts are most useful if you want to display
at least 10 data points over a period of time. If you
have fewer than 10 data points and you want to
display a count or amount at specific times, use a
column chart.

Scatter Plots the relationship between pairs of numeric

values along a horizontal and vertical axis.
You can plot 1 or more data series in a scatter
chart. Each data series has a unique color or
pattern.

Using Business Intelligence and Reporting Tools (BIRT), you can display these chart types in 3D:
• Area
• Bar
• Line
For composite, matrix, and trending reports, you can visualize changes in your data and compare metrics
with different scales using dual axis charts. A dual axis enables you to overlay 2 of these chart types:
• Area - Overlaid
• Column - Clustered
• Line
The Secondary Axis section is available when you select the Add Secondary Axis check box or select 1
of these chart types as the Primary Axis:
• Area - Overlaid
• Column - Clustered
• Line
Related Information
Concepts
Setup Considerations: Charts on page 26

Reference
BIRT: Report Designer
2020R1 What’s New Post: Dual Axis and Combination Charts

Reference: Filter Operators

• Text Operators on page 52
• Currency and Numeric Operators on page 54
• Date Operators on page 54
• Boolean Operators on page 55
• Single Instance and Multi-Instance Operators on page 55
• Single Instance Examples on page 57
• Multi-Instance Examples on page 58
• Optional Prompts on page 59

Text Operators

Operator Description
is blank Field value is empty.
is not blank Field value isn’t empty.
equal to Field value is equal to comparison value.
Case insensitive.
Example: Cat is equal to cat.

not equal to Field value isn't equal to comparison value.

Case insensitive.
Example: Cat is not equal to cat.

contains Comparison value is a subset of field value.

Case insensitive.
Example: Cat contains AT.

contains (case sensitive) Comparison value is a subset of field value.

Example: Cat contains at.

does not contain Comparison value isn't a subset of field value.

Case insensitive.
Example: Cat does not contain dog.

does not contain (case sensitive) Comparison value isn't a subset of field value.
Example: Cat does not contain AT.

starts with Comparison value is a subset of field value, and

the first character of the field value matches the first
character of the comparison value.
Case insensitive.
Example: Cat starts with ca.

Operator Description
starts with (case sensitive) Comparison value is a subset of field value, and
the first character of the field value matches first
character of comparison value.
Example: Cat starts with Ca.

ends with Comparison value is a subset of field value, and

the last character of the field value matches the last
character of comparison value.
Case insensitive.
Example: Cat ends with AT.

ends with (case sensitive) Comparison value is a subset of field value, and
the last character of the field value matches the last
character of the comparison value.
Example: Cat ends with at.

greater than Field value comes before the comparison value in

alphabetical order.
This operator compares alphabetic sort order, not
length.
Case insensitive.
Example: Cat is greater than dog.

greater than or equal to Field value is the same as or comes before the
comparison value in alphabetical order.
This operator compares alphabetic sort order, not
length.
Case insensitive.
Examples:
• Cat is greater than or equal to dog.
• Dog is greater than or equal to dog.

less than Field value comes after comparison value in

alphabetical order.
This operator compares alphabetic sort order, not
length.
Case insensitive.
Example: Dog is less than cat.

less than or equal to Field value is the same as or comes after the
comparison value in alphabetical order.
This operator compares alphabetic sort order, not
length.
Case insensitive.
Examples:
• Dog is less than or equal to cat.

Operator Description
• Cat is less than or equal to cat.

Currency and Numeric Operators

Operator Description
equal to Field value is equal to comparison value.
Example: 123 is equal to 123.

not equal to Field value isn't equal to comparison value.

Example: 12 is not equal to 123.

greater than Field value is greater than comparison value.

Example: 321 is greater than 123.

greater than or equal to Field value is greater than or equal to comparison

value.
Examples:
• 321 is greater than or equal to 123.
• 123 is greater than or equal to 123.

less than Field value is less than comparison value.

Example: 12 is less than 123.

less than or equal to Field value is less than or equal to comparison

value.
Examples:
• 12 is less than or equal to 123.
• 123 is less than or equal to 123.

Date Operators

Operator Description
is blank Field value is empty.
is not blank Field value isn't empty.
equal to Date value is equal to comparison value.
not equal to Date value isn't equal to comparison value.
greater than Date value is later than comparison value.
Example: 10/20/2016 is greater than 05/20/2016.

greater than or equal to Date value is later than or equal to comparison

value.
Examples:
• 10/20/2016 is greater than or equal to
10/20/2016.

Operator Description
• 10/20/2016 is greater than or equal to
05/20/2016.

less than Date value is before comparison value.

Example: 05/20/2016 is less than 10/20/2016.

less than or equal to Date value is before or equal to comparison value.

Examples:
• 10/20/2016 is less than or equal to 10/20/2016.
• 05/20/2016 is less than or equal to 10/20/2016.

Boolean Operators

Operator Description
is blank Field value is empty. Represents False.
is not blank Field value isn't empty. Represents True.
equal to Field value is equal to the comparison value.
For True, select the Comparison Value check box.
For False, clear the Comparison Value check box.

not equal to Field value isn't equal to the comparison value.

For True, clear the Comparison Value check box.
For False, select the Comparison Value check
box.

Single Instance and Multi-Instance Operators

Field Type Operator Usage

Single Instance exact match with the selection list Field value matches exactly with
comparison value.
Multi-instance
For single instance fields, this
operator restricts a prompt so
that it accepts a single value only.
To enable a prompt for a single
instance field to accept multiple
values, use in the selection list.

Single Instance NOT exact match with the Field value doesn’t exactly match
selection the comparison value.
Multi-instance

Single Instance subset of the selection list Field value is a subset of the
comparison value. Blank field
Multi-instance
values are a subset of the
comparison values.
Single Instance NOT subset of the selection list Field value isn’t a subset of
the comparison value. Blank
Multi-instance

Field Type Operator Usage

field values are a subset of the
comparison values.
Single Instance superset of the selection list Comparison value is a subset of
the field value. Blank comparison
Multi-instance
values are a subset of the field
values.
Single Instance NOT superset of the selection list Comparison value isn’t a
subset of the field value. Blank
Multi-instance
comparison values are a subset
of the field values.
Single Instance count is equal to The number of field values is
equal to the comparison value.
Multi-instance
Example: To view workers with
2 dependents, set a filter for
Dependents where count is
equal to a Comparison Value of
2.

Single Instance count is not equal to The number of field values isn't
equal to the comparison value.
Multi-instance
Example: To view workers
with dependents, set a filter for
Dependents where count is not
equal to a Comparison Value of
zero.

Single Instance count is greater than The number of field values is

greater than the comparison
Multi-instance
value.
Example: To view workers with
more than 1 dependent, set a
filter for Dependents where count
is greater than a Comparison
Value of 1.

Single Instance count is greater than or equal to The number of field values is
greater than or equal to the
Multi-instance
comparison value.
Example: To view workers with
1 or more dependent, set a filter
for Dependents where count
is greater than or equal to a
Comparison Value of 1.

Single Instance count is less than The number of field values is less
than the comparison value.
Multi-instance
Example: To view workers with
fewer than 2 dependents, set a
filter for Dependents where count

Field Type Operator Usage

is less than a Comparison Value
of 2.

Single Instance count is less than or equal to The number of field values is less
than or equal to the comparison
Multi-instance
value.
Example: To view workers with
2 or fewer dependents, set a
filter for Dependents where
count is less than or equal to a
Comparison Value of 2.

Single Instance in the selection list Comparison value is 1 of the

possible field values.
Example: A is in the selection list
A, B, C.

Single Instance not in the selection list Comparison value isn't 1 of the
possible field values.
Example: D is not in the selection
list A, B, C.

Multi-Instance any in the selection list Field value is 1 of the possible

comparison values.
Multi-Instance none in the selection list Field value isn't 1 of the possible
comparison values.
Single Instance is empty Field value is blank.
Multi-instance

Single Instance is not empty Field value isn't blank.

Multi-instance

A field value is a subset of the comparison value if all instances of the field are instances of the
comparison. Inversely, the comparison value is a superset of the field value if it contains all instances of
the field. Example: The field value is 1, 2, 3 and the comparison value is:
• 1, 2, 3, 4, 5. The comparison value contains all instances of the field value. Therefore, the field value is
a subset and the comparison value is a superset.
• 4, 5, 6, 7. The comparison value doesn't contain any instances of the field value. Therefore, the field
value isn't a subset and the comparison value isn't a superset.

Single Instance Examples

This table contains examples of expected results for the logical operators that compare single instance
field values against a selection list.

Single Selection in the not in the exact match subset superset

Instance List selection list selection list with the of the of the
Field Value selection list selection list selection list
Atlanta Chicago False True False False False

Single Selection in the not in the exact match subset superset

Instance List selection list selection list with the of the of the
Field Value selection list selection list selection list
Chicago Chicago True False True True True
Atlanta Chicago False True False False False
Sacramento

Chicago Chicago True False False True False

Sacramento

<blank> Chicago False True False True False

Sacramento

<blank> Chicago False True False True False

Chicago <blank> False True False False True
<blank> <blank> False True True True True

These operators provide specialized logic that might not be appropriate when comparing a single instance
field value against a selection list:
• exact match with the selection list
• subset of the selection list
• superset of the selection list
In most cases, you should use either the in the selection list or not in the selection list operator.

Multi-Instance Examples
This table contains examples of expected results for the logical operators that compare multi-instance field
values against a selection list.

Multi- Selection any in the none in the exact match subset superset
Instance List selection list selection list with the of the of the
Field Value selection list selection list selection list
Atlanta Chicago False True False False False
Sacramento

Chicago Chicago True False False True False

Sacramento

Chicago Chicago True False False False False

Atlanta Sacramento

Chicago Chicago True False True True True

Sacramento Sacramento

Chicago Chicago True False False False True

Sacramento Sacramento
Dallas

Multi- Selection any in the none in the exact match subset superset
Instance List selection list selection list with the of the of the
Field Value selection list selection list selection list
<blank> Chicago False True False True False
Sacramento

<blank> Chicago False True False True False

Chicago <blank> False True False False True
<blank> <blank> False True True True True

Optional Prompts
If you want to evaluate blank values as True, you must include an Or statement as part of the filter. The
Or statement prompts the user for a superset of the selection list. If the user doesn't select a prompt value
when running the report, the superset of the selection list filter condition evaluates as True. In this case, an
empty prompt value is the equivalent of selecting all possible values.
Example: To prompt for a location and ignore the prompt if the user doesn't enter a location, enter these
values in the Filter on Instances grid.

And/Or Field Operator Comparison Type

And Location in the selection list Prompt the user for the
value
Or Location superset of the selection Prompt the user for the
list value

Related Information
Tasks
Set Up Filter Options for Custom Reports on page 36

Fields and Prompts

Create Analytic Indicators

Prerequisites
Security: Custom Report Administration domain in the System functional area.

Context
Analytic indicators enable you to analyze data quickly by viewing visual representations in your reports.
You can create report-specific or tenant-wide analytic indicators to:
• Display ratings.
• Highlight data exceptions.
• Illustrate progress.
• Indicate status.
• Monitor thresholds.
• Visually categorize and group data.

Steps
1. Access 1 of these tasks:
• Create Analytic Indicator.
• Edit Custom Report and select Create > Create Analytic Indicator for Report from the Options
prompt of eligible fields.
2. Select the Business Object and the Field as the basis of the analytic indicator.
You can use the analytic indicator throughout Workday in reports with matching business objects and
fields.
Workday doesn't support analytic indicators for rich text field types.
3. As you complete the task, consider:
Option Description
Default Help Text Workday displays the text you enter here as hover
text for the visualization when the report runs.
Display Conditions Workday evaluates the conditions in sequential
order until a condition returns as true. Only 1
analytic indicator displays even if Workday returns
multiple true conditions. To configure more
complex condition rules, use calculated fields.
Enable Display Option by default When you select this check box, Workday
selects the analytic indicator in the Options field
whenever you add the corresponding field to a
report.
Display Analytic Indicator on Totals Select this check box to use the analytic indicator
whenever Workday displays a total. Otherwise,
Workday displays analytic indicators on detail
rows on the report.

Example
You can use analytic indicators to:
• Flag data for employee salaries that are out of range, employees on international assignment, and
managers with overdue performance reviews.
• Illustrate progress on performance reviews completed for an organization.
• Indicate status of training business process items.
• Visualize ratings of employee performance or vendors.
• Visually highlight salary percent increase and attrition that exceeds or falls below specified limits.

Next Steps
Select the Hide Analytic Indicator check box on the Options prompt to hide analytic indicators on these
cells and rows:
• Calculation cells.
• Data cells.
• Calculation rows.
• Combine data rows.
• Dynamic data rows.
• Lookup data rows.

Related Information
Concepts
Concept: Analytic Indicators on page 62
Concept: Calculated Fields
Tasks
Create Calculated Fields

Create Prompt Sets

Prerequisites
Security: Report Prompt Set Management domain in the System functional area.

Context
Prompt sets are groups of interdependent fields that add more flexibility when running reports. They enable
you to set up populated values for prompts used in:
• Composite reports and subreports.
• Custom dashboards.
• Report groups.
Example: In financial reporting, fiscal schedules and periods depend on a company. You can configure a
prompt set to include the company, fiscal year, and period.
You can use Workday-delivered prompt sets or create your own to define the order of the prompts, make a
prompt required, and so on.

Steps
1. Access the Create Prompt Set task.
2. (Optional) On the Description field, enter a description for the prompt set that Workday displays when
you view the prompt set.
3. On the Category prompt, select a value to group the prompt sets into functional categories. Example:
Financial Reporting, Payroll, or Talent.
4. Configure the Prompt Fields grid to specify the requirements and values of the prompt set.
5. As you complete the task, consider:
Option Description
Prompt Field Workday displays the Description and Category
on the related actions menu of a prompt field so
you can:
• Understand which prompt fields with identical
names to include in your prompt set.
• View additional details about the prompt field.

Display Label on Report If Workday renames a prompt field, the new name
displays in the Display Label on Report column.
Workday might rename a prompt field to include
more specific text so you can select the correct
prompt field when creating a prompt set.
Default Label Override Specify a name to use instead of the default name
for the prompt.

Next Steps
You can use the View Prompt Set report to view detailed information on prompt set fields. You can also
drill to the instances that use the prompt set from the Prompt Set Usages field.
Related Information
Concepts
Concept: Prompt Sets for Composite Reports on page 145

Concept: Analytic Indicators

Analytic indicators enable you to analyze your data quickly by viewing visual representations in your report.
You can create and use report-specific or tenant-wide analytic indicators to:
• Display ratings.
• Highlight data exceptions.
• Illustrate progress.
• Indicate status.
• Monitor thresholds.
• Visually categorize and group data.
Consider these conditions when using analytic indicators:
• For the Total row in advanced reports, analytic indicators display only on aggregated fields.
• If you select is empty as the Condition, Workday doesn't display the analytic indicator visualization for
empty data in multi-instance or single instance fields.
• In the Drill to Detail view for advanced, matrix, and simple reports, Workday might base analytic
indicator conditions on fields other than the field associated with the analytic indicator.
• In the matrix view for matrix reports, analytic indicators display only on aggregated fields.
• Workday doesn't support analytic indicators for rich text field types.
• You can configure only 1 analytic indicator for a column on a report.
Related Information
Reference
Reference: Field Options on page 64
The Next Level: Other Report Types and Analytic Indicators

Concept: Displaying Currency Fields

You can display currency fields in several reporting, formatting, and web service options.

Currencies and Formatting Options

Formatting options are independent of currency codes. Example: If you select a formatting option of
#,##0.00, Workday determines what decimal and thousands separators to display based on the currency
code.

Currencies and Web Services

When you enable a report as a web service, the web service output doesn't include the currency symbol or
formatting. On the Columns tab, you can select Show Currency Code Column from the Options prompt to
display the currency code in the web service output. Example:

<wd:Budget_Amount>1500</wd:Budget_Amount>
<wd:Actual_Amount wd:Currency_Code="USD">1200</wd:Actual_Amount>

User's Preferred Currency

You can display the user's preferred currency as a separate column in a report. Create a convert currency
calculated field with the Users Preferred Currency global field.
Related Information
Tasks
Convert Currency
Create Locations

Concept: Global Fields

Global fields are variables and constants that use the Global business object. You can use them in:
• Business process condition rules.
• Custom reports with any report data source.
• Scheduled recurring processes.
You can create custom global fields by creating calculated fields that use the Global business object.
To view all global fields in your tenant, access the Report Fields report and select Global from the
Business Object prompt.
Related Information
Reference
The Next Level: Report Performance Recommendations for Large Volume Customers

Concept: Logical Sort Order

Logical sorting enables Workday to sort your data based on the leftmost column of the report and display
your data in a manner that makes sense. Example: Instead of sorting the months alphabetically, you can
understand how your data changes over time by sorting logically, such as January, February, and so on.
Ordinarily, Workday first sorts data based on the primary business object, then sorts the related business
objects according to the contextual relationship to the primary business object. You can use calculated
fields to sort by the related business object first.
Your field selection determines if logical sorting is available. Workday enables logical sorting for the lookup
range band calculated field and for these report types:

Report Type Description

Composite Enable logical sorting for combine data rows.
Matrix and trending On the Create Custom Report task, enable logical
sorting on the:
• Matrix tab for column and row grouping.
• Drill Down tab for the Drillable Fields grid and
the Sort section.

Simple and transposed Enable logical sorting by accessing the Sort tab on
the Create Custom Report task.

Related Information
Tasks
Set Up Composite Report Rows on page 133
Set Up Field Values Groups for Matrix Reports on page 117
Set Up Sort Options for Custom Reports on page 33
Examples
Example: Sort Fields by the Related Business Object on page 67

Concept: Report Sorting Behavior

Workday uses International Components for Unicode (ICU) collation to compare and sort text strings,
making it easier to find data within a list. Because sorting data alphabetically can vary among languages,
Workday sorts the data according to the locale of the report runner. Example: The letters A through Z sort
differently in English than in Bulgarian, Lithuanian, or Japanese.
Workday takes these characters into consideration when sorting for custom or standard reports and drill-
down data:
• Spaces.
• Special characters, such as dashes, parentheses, and tildes.
Example: Workday sorts data based on the placement of spaces within a text string. Spaces take
precedence over letters and numbers.

Sort Order for Spaces Before ICU Collation Sort Order for Spaces After ICU Collation

1. John Apple 1. John Apple

2. Johnny Mango 2. John Pear
3. John Pear 3. Johnny Mango

Example: Workday sorts data based on the use of special characters within a text string. Special
characters take precedence over letters and numbers, but not spaces.

Sort Order for Special Characters Before ICU Sort Order for Special Characters After ICU
Collation Collation

1. 123456789 1. 123-456-789
2. 123-456-789 2. 123456789
3. 213456789 3. 213456789

Note: The current Unicode Standard determines special character precedence. The selection is consistent
across tenants.
Related Information
Reference
ICU Documentation: Collation

Reference: Field Options

When you create a report, you can specify these options for a field. Not every option is available for every
field type.

Option Field Types Description

[Analytic Indicator] All Displays an analytic indicator next
to the field.
This option is only available for
fields with analytic indicators
associated with them.
You can select the related actions
menu for this option to preview
the analytic indicator definition.

Average Currency Calculates the average for

the field and displays it on the

Option Field Types Description

Numeric subtotal or grand total line on the
report.
Display As Thumbnail Single Instance Displays an image as a
thumbnail.
This option is only available for
fields with a related business
object of Image.

Display Field as Icon Text Displays a speech bubble icon

instead of the field value. You can
view the field value by clicking the
icon.
Do Not Show if Empty All Hides the column containing this
field if all values are empty.
Do Not Show On Worklet All Hides the field if you deploy the
report as a worklet.
Maximum Currency Calculates the maximum value
for the field and displays it on the
Numeric
subtotal or grand total line on the
report.
Minimum Currency Calculates the minimum value
for the field and displays it on the
Numeric
subtotal or grand total line on the
report.
Related Tasks Only Single Instance Hides the field and displays the
related actions menu for the field.
Multi-instance

Show No When False Boolean Displays No when a Boolean

value is false. If you don't select
this option, false values display
as blank.
Show Blank When Zero Currency Displays a blank value if a
numeric field value is zero.
Numeric

Show Currency Column Currency Displays the currency code in a

separate column on the report.
Show Currency Symbol Currency Displays the currency symbol.
Example: $.
Show Icon Only All Displays the analytic indicator
only and hides the field value.
This option is only available for
fields with analytic indicators
associated with them.
You can only select this option in
advanced reports.

Option Field Types Description

Show Report as Executable Single Instance Displays the report name as a
hyperlink that you can click to run
the report.
This option is only available for
the custom report name field.

Sum Currency Displays the sum of all values for

the field on the subtotal or grand
Numeric
total line on the report.

Related Information
Concepts
Concept: Analytic Indicators on page 62

Reference: Field Types

The Report Fields report enables you to gain insight into the calculated and Workday-delivered report
fields and their types. You can also gain additional information on report fields by accessing the related
actions menu.

Field Type Considerations and Examples

Boolean Also known as a true/false field type where a field
must meet a condition.
Example: Is Active Employee or Is Manager.

Currency Example: Base Pay – Amount or Benefits Annual

Rate.
Date Workday recommends that you view the description
of the field to determine what information the field
returns. If you select a date field associated with
a worker, you might yield results outside the date
range of the report. Example: A company hires an
employee on January 1, terminates the employee
on June 1, and then rehires on September 1. If
you create a custom report to list employees with
a hire date before July 1, the report includes the
employee hired on January 1. However, the report
displays September 1 as the hire date because the
Hire Date field returns the most current hire date.
Example: Date of Birth or Hire Date.

DateTimeZone Example: End Date/Time or Start Date and Time.

Multi-Instance Multi-instance field types represent the one-to-
many relationship the primary business object has
with the related business object. A multi-instance
field can contain multiple values with each value
representing an instance in the related business
object that links to the primary business object.
Example: Assigned Organization or Dependents.

Numeric Example: Age or Location - Scheduled Hours.

Field Type Considerations and Examples

Rich Text A field with text formatting that changes the overall
look of the field.
Workday doesn't support analytic indicators for rich
text field types.
Example: Job Description or Overall Comment -
Manager.

Self-Referencing A self-referencing field type returns an instance of

the business object.
Example: If the data source returns Workers and
you configure a field for the primary business
object, the self-referencing field returns a Worker.

Single Instance Single instance field types represent the one-to-one

relationship that the primary business object has
with the related business object. A single instance
field contains 1 value representing the instance in
the related business object that links to the primary
business object.
Example: Compensation Grade or Position.

Text Example: Candidate ID or Last Name.

Time Example: End Time or Start Time.

Example: Sort Fields by the Related Business Object

This example illustrates how to sort fields in your report by the related business object.

Context
You want to change how your report that uses the Worker business object sorts data. Instead of sorting
by the first column on the report, you want to sort by location. You create 2 calculated fields that use the
Worker business object so that you can sort your data by the related business object, Location.

Prerequisites
Security: These domains in the System functional area:
• Custom Field Management
• Custom Report Creation
• Manage: All Custom Reports

Steps
1. Access the Copy Standard Report to Custom Report task.
Copy a Workday-delivered standard report that includes location data.
a) Select Active Employees - Indexed from the Standard Report Name prompt.
b) Click OK.
c) Enter By Location - Active Employees - Indexed on the Name field.
d) Click OK twice.

2. Access the Create Calculated Field task.

Create an extract single instance calculated field for the location data.
a) Enter ESI Location on the Field Name field.
b) Select Worker on the Business Object prompt.
c) Select Extract Single Instance on the Function prompt.
d) Click OK.
e) Select these values on the Calculation tab:

Prompt Value
Source Field Locations
Condition Is True
Sort Field Location Name
Sort Direction Ascending (A to Z)
Instance to be Returned Last occurrence
f) Click OK.
3. Click Create Another Calculation.
Create a lookup related value calculated field for the location data.
a) Enter LRV Location on the Field Name field.
b) Select Worker on the Business Object prompt.
c) Select Lookup Related Value on the Function prompt.
d) Click OK.
e) Select these values on the Calculation tab:

Prompt Value
Lookup Field ESI Location
Return Value Location
f) Click OK.
g) Click Done.
4. Access the Edit Custom Report task.
Add the LRV Location calculated field to your advanced report.
a) Select By Location - Active Employees - Indexed from the Report Name prompt.
b) Click OK.
c) Access the Sort tab.
d) In the Sort and Group section, clear the Sort by first accessible column check box.
e) Add a row to the grid.
f) In the grid, select LRV Location from the Field prompt.
g) Click OK.
h) Click Run.

Result
The lookup related value calculated field sorts your data by the Location Name instead of the Employee ID.

Next Steps
You can create additional calculated fields that enable you to sort your data by fields on the related
business object instead of the primary business object.

Run and Schedule Reports

Group Reports

Prerequisites
• Verify that reports you add to the report group have at least 1 saved filter.
• Security: Scheduled Report Processes domain in the System functional area.

Context
You can group multiple reports and schedule them to run as a single unit. Example: For financial reporting,
you can group reports to run at the end of a fiscal period.
If the reports in a report group share prompt fields, you can use prompt sets to populate those prompts
more efficiently. You can also:
• Add a Report Group step to a business process so users can share instances of reports or tasks.
• Share report groups so that other users can schedule them.
• Transfer ownership of report groups to other users.

Steps
1. Access the Create Report Group task.
2. On the Prompt Set prompt, create or select a prompt set.
If you select Empty Prompt Set and share a report group that contains prompts, Workday restricts users
from entering prompt values when they schedule the report group.
3. (Optional) Select the Use Excel Template check box to attach report results to Excel templates.
Instead of generating separate Excel files, Workday creates up to 200 sheets in a single workbook and
delivers it to My Reports.
4. On the Prompts tab, configure the requirements and values for each prompt in the report group.
5. As you complete the grid, consider:
Option Description
Label for Prompt Specify a name to use for the prompt field instead
of the populated name.
Default Value (Available if you select Determine default value
at runtime or Specify default value as the Default
Type.) Select the field or value to use for the
prompt field.
Report Tags Select a tag to categorize the report group and
make it easier to search for. Workday adds the
report tags to the generated output file of each
individual report when you schedule the report
group.
6. On the Reports tab, select a different saved filter for each report or task that's the same.
7. As you complete the Report Prompts grid, consider:
Option Description
Prompt Field Select a field from the saved filter of the report
prompt.

Option Description
Value Type To map a report Prompt Field to a Field from
the report group prompt set, select Report Group
Prompt.
If you map 1 or more report prompt fields to a
prompt set field, the prompt set overrides all
saved filter values on the report. To ensure that
the report runs correctly when you use prompt set
field values, map all required report prompt fields.

Field Select a field from the report group prompt set.

Securing Entity Select the check box to enable each entity
you specify to view only data relevant to their
organization.

If you share the report group, you must map all report prompts to the report group prompt set.
Otherwise, the person you share the report group with can't run the report group.
8. (Optional) On the Share Output tab, configure sharing options for the report output.
Security: Report Output Sharing and Reporting Functionality domains in the System functional area.
9. As you complete the tab, consider:
Option Description
Report Output Sharing Options If you select Share report output with other users,
you can specify which security groups and users
will:
• Always be able to view all reports in the report
group.
• Conditionally be able to view each report
as a member of the specified organizational
security entity.
By sharing the report output with users, you're
authorizing them to view the report and its data
exactly as you see it, regardless of their security
permissions.

Always Share (Available if you share the report output.) Specify

the security groups and users that you want to
share all the reports in the report group with.
Always Share overrides any sharing you enable
based on securing entities.

Share based on Securing Entity (Available if you share the report output.) Specify
the securing entities and security groups you want
to share each report with conditionally. These
users will only be able to view data relevant to
their organizational role.
I agree to the statement above Select the check box to acknowledge that you
understand the implications of sharing the report
output with other users.
10.(Optional) On the Share Report Group tab, configure sharing options for the report group.
Security: Report Output Sharing and Reporting Functionality domains in the System functional area.

11.As you complete the tab, consider:

Option Description
Do not Share Report Group Select so that only you can schedule and view the
report group.
Share with all authorized users Select so that all users who have access to the
report data source and data source filter can
schedule and view the report group.
When you share the report group, Workday also
shares the saved filter for each report.

Share with specific authorized groups and Select so that only the security groups and users
users you specify can schedule and view the report
group.
You can only select from security groups and
users who have access to the report data source
and data source filter.

I agree to the statement above Select the check box to acknowledge that you
understand the implications of sharing the report
group with other users.

Next Steps
• Access the Schedule a Report task to schedule the report group.
• Select Report Group > Maintain Excel Template from the related actions menu of the report group to
attach an Excel template.
Related Information
Concepts
Concept: Report Group Step
Concept: Report Tags on page 82
Tasks
Create Prompt Sets on page 61
Save Filters on page 76
Schedule Reports or Report Groups on page 74
Transfer Ownership of Report Groups on page 79
Reference
Reference: Reporting Limits
Workday Community: Using Worksheets Templates to Share Multiple Reports
The Next Level: Report Distribution: Report Groups and Bursting

Burst Reports

Prerequisites
• Create a report group.
• Security: These domains in the System functional area:
• Maintain Excel Template
• Scheduled Report Processes

Context
Instead of manually running a report for multiple organizations, you can schedule a bursting set that
generates a report for each organization in a prompt field.
Example: Create a bursting set for a financial report that generates 1 report for each company.

Steps
1. Access the Edit Report Group task.
2. (Optional) Select the Use Excel Template check box to attach report results to Microsoft Excel
templates.
Workday creates up to 200 sheets in a single workbook and delivers it to My Reports.
When you don't attach an Excel template, Workday creates a separate file for each organization you set
to burst on.
3. On the Reports tab, set up the Report Prompts grid.
As you complete the grid, consider:
Option Description
Prompt Field Select the organization type that you want to burst
on. Examples:
• Company
• Cost Center
• Supervisory Organization

Value Type Select Bursting Set.

Don't select Bursting Set for more than 1 Prompt
Field. Selecting multiple fields to burst on might
cause unexpected report behavior.

Field Select a global calculated field to narrow down the

organizations to include in the bursting set.
Example: Select Active Companies for a Prompt
Field of Company.
You can also create custom calculated fields that
narrow down the list of organizations you want to
include.
If the prompt set for the report group has the
same field, the value of Field overrides the
prompt set field value when you schedule the
report group.

Securing Entity Secure the report output based on the

organization that you selected as the Prompt
Field when using an Excel template.
4. On the Share Output tab, set up sharing options for the report output.
When you select Share report output with other users, consider:
Option Description
Securing Entity Select the organization type that you want to use
to secure report output. This is the same field that

Option Description
you select the Securing Entity check box for on
the Report Prompts grid on the Reports tab.
Security Groups Select the role-based security group that you want
to share the report output with.

Example: Select Company as the Securing Entity and Accountant as the Security Groups option to:
• Run the report for each company in your tenant.
• Send the report results to the accountant for each company.
5. (Optional) Select Report Group > Maintain Excel Template from the related actions menu of the
report group to attach an Excel template.
If you can't access the Maintain Excel Template menu option, enable the Maintain Excel Template
domain security policy in the System functional area.

Next Steps
Access the Schedule a Report task and schedule the report group.
Related Information
Tasks
Create Prompt Sets on page 61
Group Reports on page 69
Schedule Reports or Report Groups on page 74
Reference
The Next Level: Report Distribution: Report Groups and Bursting

Attach Excel Templates to Custom Reports or Report Groups

Prerequisites
• Verify the System Setup section in the Edit Tenant Setup - System task enables xlsm and xlsx as file
types.
• Enable report group definitions to use Microsoft Excel templates by selecting the Use Excel Template
check box.
• Security: These domains in the System functional area:
• Set Up: Tenant Setup - System
• Custom Report Creation
• Manage: All Custom Reports
• Maintain Excel Template

Context
You can automate Excel processing and formatting by attaching a custom Excel template to a custom
report or report group. Workday only applies your Excel template when you run a report using the
Schedule a Report task, or when you run the report in the background by clicking Notify Me Later.
Workday doesn't apply your Excel template when you click the Export to Excel icon from the report
results.
Workday supports Excel features available in Excel 1997-2010.
Workday doesn't support:
• Password-protected workbooks.
• Signed macros.

• Slicers.

Steps
1. In Excel, create an Excel workbook and include any macros. Save the workbook as an .xlsx or .xlsm
file.
2. In Workday, access the custom report or report group you want to export to Excel.
Attach the Excel template by selecting 1 of these options:
• For a custom report, select Custom Report > Maintain Excel Template from the related actions
menu.
• For a report group, select Report Group > Maintain Excel Template from the related actions
menu.
3. (Optional) On the Worksheet Name prompt, enter the name of an existing sheet on Excel template that
you want to populate with the report output. Otherwise, Workday creates a new sheet with the same
name as the report and populates that sheet with the report output.
Workday overwrites the existing sheet with the report output.

Next Steps
Access the Schedule a Report task, select your report or report group, and select Excel as the output
type. For report groups, you must also select the Use Excel Template check box.
Related Information
Tasks
Group Reports on page 69
Reference
Workday Community: Using Worksheets Templates to Share Multiple Reports

Schedule Reports or Report Groups

Prerequisites
Security: Scheduled Report Processes domain in the System functional area.

Context
You can use the Schedule a Report task to run a report or report group in the background.
When you transfer ownership of a scheduled report or process, the sharing options reset to Do not share
report output.

Steps
1. Access the Schedule a Report task.
2. As you complete the Report Criteria tab, consider:
Option Description
Value Type If you select Determine Value at Runtime,
Workday calculates the selection criteria each
time the report runs. Example: Use Determine
Value at Runtime for date fields that can vary over
time for a recurring process.
Value If the Value Type is Determine Value at Runtime,
the report determines the prompt value each time
it runs.

Option Description
You can set the Value to be a calculated field.
Example: You can create a calculated field whose
value computes as a set number of days before
the current date.

Workday only displays this tab when the report contains prompts.
3. As you complete the Output tab, consider:
Option Description
Output Type If a report has a high volume of results, Workday
might deliver a file type other than the Output
Type you select.
You can't output search reports as PDFs. The
scheduled process fails if you select Report
(PDF) for a search report.

Do Not Output an Empty Report Select the check box so that when a report has
no results, Workday doesn’t create output files or
send email notifications.
Workday doesn't support this option for standard
reports created with XpressO.

4. (Optional) On the Share tab, share the report output with other users.
You can only share scheduled report output with unconstrained security groups.

Result
The output files load in My Reports.

Next Steps
Access the Scheduled Future Processes report to delete, modify, or suspend a scheduled report.
To disable notification emails for recurring reports that are about to expire, access the Edit Tenant Setup -
Notifications task and disable Scheduled Future Processes for the report. Workday notifies you when 2
or fewer occurrences remain.
Related Information
Concepts
Concept: My Reports on page 81
Concept: Workday Scheduled Processes
Tasks
Increment or Decrement Date
Reference
Reference: Edit Tenant Setup - Notifications
Reference: Reporting Limits
The Next Level: Report Performance Recommendations for Large Volume Customers
Workday Community: Using Worksheets Templates to Share Multiple Reports

Manage Scheduled Future Processes

Prerequisites
Security: Scheduled Process Management domain in the Tenant Non-Configurable functional area.

Context
You can view all background processes scheduled to run once in the future or on a recurring basis.
Workday displays batch processes, integrations, and reports. You can perform these actions by accessing
the related actions menu of a scheduled future process:
• Activate or suspend.
• Edit or delete.
• Restrict the environments where they run.
• Transfer ownership.
• Set the priority. Setting a higher priority can reduce potential queuing.

Steps
1. Access the Scheduled Future Processes report.
2. Filter the process you want to edit.
3. Select the process on the Scheduled Process column to view detailed schedule criteria.
4. Manage the process by accessing the related actions menu of the process on the Scheduled Process
column.

Next Steps
You can view reports of future occurrences filtered by date or schedule by accessing these reports:
• View All Scheduled Occurrences by Date
• View All Occurrences for a Schedule
Access the Process Monitor report to view the status of all background processes that Workday is
running or ran in the past.
Related Information
Reference
Reference: Scheduled Future Processes
The Next Level: Report Performance - Tuning Thresholds

Save Filters

Prerequisites
Enable Save Parameters in the Advanced tab on the report you want to save prompt values for.

Context
Instead of manually entering prompt values every time you run a report, you can save the values as a filter
to load them automatically.
You can't save filters for search reports.

Steps
1. Run a report you want to save prompt values for.
2. Enter the prompt values you want to save.

3. Enter and save a Filter Name.

Result
The next time you run the report, you can select the filter from the Saved Filters drop-down menu.

Next Steps
Access the Manage My Saved Filters report to edit or delete your saved filters.

Save Searches

Prerequisites
Add facet filters on the report definition where you want to save searches.

Context
When you run a report, you can save your search parameters to load:
• Facet filters.
• Prompt values.
• Search terms.
You can't add facet filters to composite reports or advanced reports with outlining.
You can delete your saved searches by accessing the Manage My Saved Searches task. You can't delete
a saved search with a Usage value of 1 or more.

Steps
1. Run a report.
2. (Optional) Enter the prompt values that you want to save.
3. (Optional) Enter the search terms that you want to save.
4. Select the facet filter values that you want to save.
Related Information
Tasks
Set Up Advanced Options for Custom Reports on page 43

Concept: Interacting with Report Results

Drilling Down to View Additional Fields

When you enable Drill Down Options for matrix, nBox, and trending reports, you can:
• Drill down on a cell value and group results by another field.
• View detail data for summarized amounts.
Detail data displays current field values, but Workday calculates summary values when you run the report.
There might be a difference between summary values and detail data if the data changed after you ran the
report.

Exporting Report Output

To access report results outside of Workday, you can export report output as:
• PDF.
• Excel file.

When you export the report output as an Excel file, Workday runs the report again in the background. A
report that includes date or time fields might have different output in the Excel file than what you view in
Workday. Examples: Current Moment, Days Since Completed.
You can’t download search report results as PDFs or Excel files.

Filtering by Facets
For advanced and search reports, you can add a search bar and facet filters that enable users to further
filter report results without running the report again.
When you enable Facet Options, the report results display a search bar if the report data source contains
searchable fields. Workday determines which fields in each data source are searchable. When you search
for a term, Workday searches against all searchable fields in the report data source, not just the fields in
the report.

Concept: Report Schedules and Weekly Service Update Window

Workday scheduled report runs can perform differently when your tenant enters our Service Update Mode,
which occurs 30 minutes before the Weekly Service Update begins.
These scenarios apply to report runs scheduled during the Weekly Service Update:

Scenario Impact
The report run starts before the tenant enters the No impact to the report run.
Service Update mode and completes in the 30-
minute window before the start of the Weekly
Service Update.
The report run starts before the tenant enters the Reports that start but don’t complete before the
Service Update mode and doesn't complete before tenant enters the Service Update mode result in an
the start of the Weekly Service Update. error. Run the report again after the Weekly Service
Update completes.
You schedule the report run to start after the tenant The report run doesn’t start at its scheduled time;
enters the Service Update mode. the report run starts at the completion of the Weekly
Service Update.

For scenarios that can impact your report executions, don't schedule your reports to run during the Weekly
Service Update window.

Report Administration

Add Custom Reports to Workday Menus

Prerequisites
Security: Custom Report Administration domain in the System functional area.

Context
You can use the Maintain Custom Reports on Menus task to make your custom reports more accessible
by adding them to the:
• Sitemap.
• Related actions menu of a business object, such as Organization or Worker.
To add a custom report to a related actions menu:

• Associate the custom report with only 1 business object and only 1 action category.
• Ensure the report prompts for a business object. Example: Supervisory Organization or Worker.
You can add a maximum of 100 custom reports to Workday menus.

Steps
1. Access the Maintain Custom Reports on Menus task.
2. As you complete the task, consider:
Option Description
Sitemap Category (Optional) Add the custom report to a standard
menu category.
Related Actions Select the Business Object and Menu Category
to which you want to add the custom report. The
associated Prompt Field displays for reference.

Share Custom Report Definitions

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Report Definition Sharing - All Authorized Users
• Report Definition Sharing - Specific Groups
• Report Definition Sharing - Specific Users

Context
If you own a custom report, you can share the report definition with other groups or users. Workday
considers all security permissions before a user can access and run a shared report.
Workday doesn't support sharing simple reports.

Steps
1. Access the custom report that you want to share.
2. On the Share tab, select an option from the Report Definition Sharing Options section.
If you select Share with specific authorized groups and users, you can specify authorized groups and
users to share the report with, or you can create your own group.
Related Information
Tasks
Set Up Share Options for Custom Reports on page 42
Reference
The Next Level: Report Performance - Tuning Thresholds

Transfer Ownership of Report Groups

Prerequisites
Ensure that the user you transfer the report group to has access to all the reports in the report group.
Security: These domains in the System functional area:
• Custom Report Administration

• Manage: All Custom Reports

Context
When a report group owner transitions to a different role, report administrators can transfer their report
groups to another user.
Report group owners can also transfer report groups that they own to other users.

Steps
1. Access the Transfer Ownership of Report Group task.
If you're transferring a report group you own but don't have access to the Transfer Ownership of
Report Groups task, you can select Report Group > Transfer Ownership from the related actions
menu of your report group.
2. Select a Report Group and New Owner.
3. Confirm that the new owner has access to all the reports in the report group.

Result
The new owner can edit and schedule the report group.
Related Information
Tasks
Group Reports on page 69

Translate Custom Reports

Prerequisites
Security: Data Translation domain in the System functional area.

Context
You can translate custom reports from the default tenant language to other languages that your tenant
supports.

Steps
1. From the related actions menu of a custom report, select Translation > Translate Instance.
You can translate these parts of a custom report:
• Brief Description
• Instructions
• Label Override
• More Info
2. From the related actions menu of a custom report, select Custom Report > Translate.
You can translate these parts of a custom report:
• Column heading overrides.
• Group name overrides for sort fields.
• Labels for prompts.
• Report name.

Next Steps
Access the Change Preferences task and change the Preferred Display Language to view your
translations.
Related Information
Concepts
Concept: Translations

Concept: Custom Report Deletion

You can access these tasks to delete custom reports that have no usages:
• Delete Custom Report enables you to delete 1 report.
You must have access to the Custom Report Management and Manage: All Custom Reports domains
in the System functional area.
• Mass Delete Custom Reports enables you to delete 1 or more reports.
You must have access to the Custom Report Management and Manage: All Custom Reports domains
in the System functional area.
You can't delete custom reports that you use in:
• Business form layouts.
• Business process steps.
• Other custom reports.
• Report groups.
• Scheduled future processes.
You can’t recover deleted reports in your production tenant. Before you delete reports in your production
tenant, Workday recommends you:
• Delete them in your Sandbox tenant.
• Discuss reports that you want to delete with report owners.
• Rename or tag reports you want to delete. You can send a report of those custom reports to others who
you might impact by their deletion.
If you inadvertently delete reports, you can check your Sandbox tenant for copies before the weekly
Sandbox tenant refresh runs.
You can view deleted reports by accessing the View User or Task or Object Audit Trail report.
Related Information
Concepts
Concept: Report Definition Usages on page 82
Reference
Workday Community: Refresh Exemption Tenant Request

Concept: My Reports
My Reports is a virtual storage area for report output and integration documents. Workday saves report
output in My Reports when:
• Someone schedules a report and shares the output with you.
• You run a report in the background.
• You schedule a report.
• You generate a spreadsheet from a composite report that includes outlining.
When you open My Reports, Workday displays the 10 most recent report output files and integration
documents. From the related actions menu of a File, you can:

• Assign, create, or remove report tags by selecting Repository Documents > Maintain Tags.
• Share report output with up to 2,000 users by selecting Repository Documents > Shared Users.
You must have access to the Report Output Sharing domain to share report output.

Mobile Support
My Reports is available on Workday for:
• Android
• iPad
• iPhone
In the Mobile section on the Edit Tenant Setup - System task you can select these check boxes:
• Disable My Reports On Mobile.
• Enable Attachments to be Imported From or Shared With External Sources.
Related Information
Concepts
Concept: Mobile Devices and Features
Reference
Reference: Edit Tenant Setup - System
Reference: Core Navigation

Concept: Report Definition Usages

When a report has usages, Workday displays the number of Report Definition Usages on the View
Custom Report task.
You can click the count of Report Definition Usages to view the area and usage of the report.
You can't delete reports that you use in:
• Business form layouts.
• Business processes.
• Other custom reports.
• Report groups.
• Scheduled future processes.

Concept: Report Tags

Report tags enable you to categorize reports and report output files for easier searching. You can also add
report tags to a report group definition. When you schedule the report group, Workday adds the tags to the
generated output file of each individual report.
Workday enables you to use these report tag types:
• Prompt value report tags, which you can apply to a report group. You can base tags on the dynamic
values of prompts in the report group prompt set. Example: You can select report tags based on
prompts for company or cost center.
• Static tags, which you can apply to an individual report or report group definition. You can select from a
list of Workday-delivered report tags, or create your own from report or report group edit tasks. You can
also create report tags by accessing the Maintain Report Tags task.
To create or maintain report tags, you need access to the Report Tag Management domain.

Inactivating or Deleting Report Tags

You can access the Maintain Report Tags task to inactivate or delete report tags. Consider:

• If you deactivate a report tag, you can't apply the tag to a report output.
• You can't delete a report tag if you use it in a report or report group definition.

Searching for Reports and Report Output Files Using Report Tags
You can search for reports with a specific report tag by using the rdt: prefix followed by the name of the
report tag. Example: You can search rdt: payroll to find all custom report definitions tagged with Payroll.
You can access the My Report Output Files report to search for output files with a specific report tag. You
can limit results to output files that Workday generated within a specified number of days. Example: You
can locate report output files that include the Workforce Planning tag within the last 30 days.
Related Information
Tasks
Group Reports on page 69

Concept: Temporary Reports

Temporary reports enable you to reduce clutter in your tenant by marking obsolete reports for deletion, and
then deleting them in bulk. You can make any custom report temporary.
You can restrict users to create only temporary reports by assigning them to the Ability to Create Only
Temporary Reports domain. They can still access all other reporting features.

Deleting Expired Temporary Reports

Expired temporary reports remain in your tenant until you run the Delete My Temporary Report
Definitions task. Report Admins can run the Delete All Temporary Report Definitions task to delete all
expired temporary report definitions.
You can also schedule the task to run on a regular basis. When the task runs, Workday permanently
deletes any temporary reports that expire on or before the current date.

Changing Report Expiration Dates

Temporary reports expire 7 days after you create them. For all report types except for simple reports, you
can change the expiration date on the Advanced tab of the report definition.

Saving Temporary Report Results

If you need to save temporary report results, you can export them as a spreadsheet or PDF.
Related Information
Concepts
Concept: Custom Reports on page 12
Tasks
Activate Pending Security Policy Changes
Create User-Based Security Groups
Set Up Advanced Options for Custom Reports on page 43

Reference: Custom Reports with Objects Planned for Retirement

The All Custom Reports with "Do Not Use" Items report enables you to identify custom reports that use
objects planned for retirement. Workday labels these objects with (Do Not Use) because there's a new or
better object available. The report lists the do not use (DNU) objects in the custom report, so you can make
updates appropriately.

Option Description
Report Run History Start Date The date range you specify determines the count
displayed in the Number of Times Executed
Report Run History End Date
column on the report.
You can select a date range of 6 months.

Custom Report Displays the custom report that uses an object with
a DNU label.
Report Owner Displays the custom report owner.
Number of Times Executed Displays the number of times Workday executed
the custom report within the report run history date
range you specified.
The count excludes when the report runs as a
worklet.

"Do Not Use" Report Fields Displays the calculated field and report field with a
DNU label that the custom report uses.
"Do Not Use" Data Source Displays the report data source (RDS) with a DNU
label that the custom report uses.
Alternate Data Source Displays the recommended RDS to use in place of
an RDS with a DNU label.
"Do Not Use" Data Source Filter Displays the RDS filter with a DNU label that the
custom report uses.
Area Where Used Displays all custom report usages in your tenant.
Last Run By Displays who last ran the custom report, including
running the report in the background or as a
worklet.
Last Run Date Displays the date and time within the past 6 months
when the custom report last:
• Executed as an integration.
• Executed as a worklet.
• Ran.
• Ran in the background.
Workday captures the date and time once per day
for each custom report.

Domains Securing Report Definition based on Displays the domains that secure the RDS and
RDS and SMD the domains the RDS uses for the secure method
definition (SMD) on the custom report.
The SMD is for Workday internal use only and it
determines security permissions for viewing data in
a report.

Domains Securing Alternate RDS Displays the domains that secure the RDS
Workday recommends you use in place of an RDS
with a DNU label.

Option Description
Enable As Worklet Indicates whether the custom report is enabled as a
worklet.
Available Usage Displays the embedded and landing pages for the
custom report configured as a worklet.
Worklet Landing Pages Displays the landing pages for the custom report
configured as a worklet.
Enable As Web Service Indicates whether the custom report is enabled as a
web service.
Attached Excel Template Displays the Excel workbook attached to the
custom report.

Related Information
Concepts
Concept: Selecting a Data Source on page 17
Reference
Reference: Reports for Managing Custom Reports on page 86

Reference: Report Run History

The Report Run History report enables you to identify who runs reports and how often. The report can
display up to 6 complete months of run history for standard and custom reports. To view more than 6
months of run history, build an integration to extract data once a month.
When you run the report, you can filter for these Execution Mode options:

Option Description
Column Outlining Request Displays the number of times the report ran with
expanded column groupings.
Drill Down Displays the number of times you drill down the
report when the task executes.
Drilling down adds to the count.
Example: When you drill down twice in a report, 3
counts display. 1 for the initial report execution and
2 for the drill-down selections.

Drill Down - Id Set Details Displays the number of times you drill down on a
cell in a report with paginated results.
Excel Outlining Request Displays the number of times the report exports
to Microsoft Excel and contains expandable
groupings.
Facet Selection Displays the number of times you select a facet for
a report when the task executes.
Facet selection adds to the count.
Example: When you run a report and select 2
facets, 3 counts display here: 1 for the initial report
execution and 2 for the facet selections.

Option Description
Internal Displays the number of times where other tasks ran
in the report.
Report Displays the number of times the reports ran.
Row Outlining Request Displays the number of times the report ran with
expanded row groupings.
Scorecard Metric Reports Displays the number of times the matrix report ran
during calculations of Scorecard Metrics.
Sub Report Displays the number of times the subreport ran as
part of composite reports.
Test Report Displays the number of times the report ran as a
test.
Worklet Displays the number of times the report ran as a
worklet on a dashboard.
WQL Displays the number of Workday Query Language
requests that execute.

To enable the Report Run History report, access the Edit Tenant Setup - Reporting and Analytics task
and select the Enable Access to Report Run History check box. Workday begins capturing report run
history after you enable the feature and therefore might not initially display any data on the Report Run
History report.
Related Information
Reference
Reference: Edit Tenant Setup - Reporting and Analytics

Reference: Reports for Managing Custom Reports

Workday provides these reports to help you create and manage custom reports.

Report Description
All Calculated Fields View all calculated fields in your tenant.
All Custom Reports View all custom reports in your tenant.
All Custom Reports with "Do Not Use" Items View all custom reports in your tenant that use
objects planned for retirement.
Business Objects by Category View all business objects for a category.
Business Object Details View all of these reporting objects for a business
object:
• Related business objects.
• Report data sources.
• Report fields.
• Reports.

Calculated Fields Defined View all report-specific and tenant-wide calculated

fields configured in your tenant.
Custom Reports for Person View all custom reports the person owns.

Report Description
Dashboard Run History View and filter dashboard usage statistics from the
previous 6 months.
My Custom Reports with "Do Not Use" Items View all custom reports you own that use a data
source filter, report data source, or report field
planned for retirement.
Report Fields View all calculated fields and Workday-delivered
fields in your tenant.
Report Run History View the number of times a report ran. If you don't
enter any prompt values, the report displays the
reports that ran the most frequently in the last 6
months.
View Business Form Layout View all custom business form layouts created in
your tenant.
View Delivered Business Form Layout View Workday-delivered business forms, such as
an IRS form 1099.
View Indexed Fields for Data Source View the fields in an indexed RDS that Workday
indexes for:
• Aggregations.
• Facets.
• Filters.
• Group by.

Workday Data Dictionary View all Workday-delivered fields for a business

object, excluding fields with the (Do Not Use) label
and retired fields.
Workday Standard Reports View all Workday-delivered reports.

Related Information
Reference
Reference: Custom Reports with Objects Planned for Retirement on page 83
The Next Level: Factors Impacting Report Performance

Reference: Security Domains for Reporting

You can assign administrators who manage all your report definitions and outputs to these security
domains in the System functional area:

Domain Report Management Task

Manage: All Custom Reports • View Custom Report
• Edit Custom Report
• Delete Custom Report

• Manage: All Custom Reports Transfer Ownership of Custom Reports

• Custom Report Administration The user you transfer the report to must also have
access to the Custom Report Creation domain.
Select the Allow Mixed-Language Transactions
check box for your Workday account to view all

Domain Report Management Task

the items you have access to in your preferred
language and in English. This check box enables
access to tasks and objects that aren't translated
in your preferred language when your preferred
language is different from the default tenant
language. See Steps: Manage Translations.

Data Translation Translate Custom Report

To provide users with view-only access to custom reports, Workday recommends that you use the
Manage: All Custom Reports domain in the System functional area.
Related Information
Reference
The Next Level: Report Security Overview

Report Performance and Limitations

Create Report Performance Logs

Prerequisites
Security: Core Navigation domain in the Tenant Non-Configurable functional area.

Context
You can use report performance logs to troubleshoot slow reports.

Steps
1. Access the Edit Report Performance Log Settings task.
2. Select the Report Log Settings tab.
3. As you complete the tab, consider:
Option Description
Enabled Select the Enabled check box to enable Workday
to collect the report performance data.
Report Definition(s) Select the reports that you want to log.
Log Name Enter a name for the report performance log.
Log Data Until Select an end date and time that's less than 24
hours from the current time.
Each time you run the report before the date and
time you set, Workday creates a new log for the
report.

Report Timeout Limit (min) Enter a maximum amount of time for the reports
to run before they time out. You can use this
option to help you determine why the reports take
a long time to run without having to wait for each
report to finish.

Option Description
The default value of 0 indicates no timeout limit.

Enable Pagination (ID Set) Details Select to create:

• 1 report log for the initial set of report results
that load.
• A separate report log for each additional page
of report results that you load.
Otherwise, Workday creates 1 report log for all
the report results that you load.
Example: If the Find Candidates report returns
500 instances, Workday creates a total of 11 logs,
including:
• 1 log for the report as a whole.
• 1 log for the initial set of instances that load.
• 1 log for each additional set of 50 or so
instances that load.

4. Run the reports that you want to log.

Next Steps
Access the View Report Performance Logs report.
Related Information
Reference
The Next Level: Factors Impacting Report Performance

Reference: Report Performance Log Fields

• Report Summary
• Report Performance Metrics
• Failure Information
• Report Prompts
• Field Performance Metrics
• Subreports
• Advanced Metrics

Report Summary

Log Field Description

Log Name The log name you entered on the Edit Report
Performance Log Settings task.
Report Definition The report selected for logging.
Report Type A 3-letter abbreviation for the type of report logged.
Possible values:
• ADV - Advanced
• FAC - Faceted Search
• MTX - Matrix
• TRD - Trending
• NBX - nBox

Log Field Description

• SIM - Simple
• TPS - Transposed

Executed by User The user who ran the report.

Data Source Data source of the logged report.
Execution Status Displays if the report ran successfully.
If you select the Notify me later check box when
you run the report, the original report log displays a
status of Failed and creates another report log for
the report when it runs in the background.

Data Source Processing Mode Displays how the report processed the data source:
as standard, indexed, or hybrid. This field doesn’t
display for composite reports.
Possible values:
• Object Graph: The report processed the data
source as a standard data source.
• Indexed: The report processed the data source
as an indexed data source. This processing
mode results in the best report performance.
• Hybrid: The report processed the data source
as an indexed data source with additional
functions.

Filter Processing Mode Displays how the report processed the fields used
for filtering: as standard, indexed, or hybrid.
Possible values:
• Object Graph: The report evaluates the fields
selected for filtering outside of an indexed data
source.
• Indexed: The report evaluates the fields
selected for filtering inside of an indexed data
source. This processing mode results in the best
report performance.
• Hybrid: The report evaluates the fields selected
for filtering both inside and outside of an indexed
data source.

Grouping Processing Mode Displays how the report processed the fields used
for grouping: as standard, indexed, or hybrid.
Possible values:
• Object Graph: The report evaluates group by
fields outside of an indexed data source.
• Indexed: The report evaluates group by
fields inside of an indexed data source. This
processing mode results in the best report
performance.

Log Field Description

• Hybrid: The report evaluates group by fields
both inside and outside of an indexed data
source.

Report Execution Date and Time Date and time when the report finished running.
Maximum Report Processing Time (s) Maximum time a report runs before timing out.
By default, a report run by a user runs for 30
minutes. A report that ran in the background runs
for 6 hours. A report that ran as a worklet runs for
30 seconds.

Subreport Count (Composite reports only.) Number of subreports run

as part of the composite report.
Data Source Instance Count Number of business object instances the data
source returns.
This field displays a count of zero if the:
• Data source returns zero instances.
• Report is a matrix report that's Optimized for
Performance.
• Data source is a hybrid of standard and indexed
data sources.

Data Source Instance Count (Post Security Number of business object instances remaining
Processing) after security processing.
This field displays a count of zero if the:
• Report runs contextual security on the data
source.
• Report runs contextual security and eliminates
all instances from displaying.
• Report is a matrix report that's Optimized for
Performance.

Report Instance Count Number of business object instances the report

returns after security, filter, and other processing.
This field displays a count of zero if the report is a
matrix report:
• That's Optimized for Performance.
• And the data source is a hybrid of standard and
indexed data sources.
If the report is a matrix report that's Optimized for
Performance, a unique instance count of all groups
displays in the Matrix Summarization section of
the:
• Development Report Performance Log.
• Support Report Performance Log.
If the Report Instance Count is much less than
the Data Source Instant Count, consider using

Log Field Description

a more focused data source to improve report
performance.

Report Performance Metrics

Log Field Description

Total Execution Time (ms) Time spent running the report.
A high value might indicate performance issues.
Review the other timing log fields to identify a
problem area.

Total CPU Execution Time (ms) Total time of each concurrent thread for each time
bucket. This value doesn’t contribute to Total
Execution Time (ms). This field is only available if
you enable Parallel Processing.
Initialization Time (ms) Time spent building the report definition model.
During this time, the report evaluates parameter
processing and static filters.
Data Source Time (ms) Time spent identifying the data source and
retrieving the business object instances that the
report uses.
To reduce the data source time, you can use the
Data Sources report to find a more targeted and
efficient data source for your report.

Data Source Security Time (ms) Time spent evaluating security access to the data
source.
This field displays zero if the data source contains
no security.
If the data source is secured to an unconstrained
security group while some instances of the
business object are secured to a constrained
security group, this field displays the time spent
evaluating security access for the constrained
security group.

Top Level Filter Time (ms) Time spent applying all filters in the report
definition, including filters at the data source, field,
and subfilter levels.
This field displays zero if there's no filtering on the
data source.
To reduce the filter time, you can:
• Ensure that the top-level filter removes the
highest number of instances from your report.
• Simplify filter logic.
• Try using different fields to filter your report.

Contextual Security Filter Time (ms) Time spent evaluating contextual security access to
the data source.

Log Field Description

This field doesn't display if there's no contextual
security on the data source.

Top Level Sort Time (ms) Time spent applying all sort options in the report
definition.
This field displays zero if the report:
• Is a search report based on a Syman data
source.
• Is a facet selection.
• Has paginated results.
To reduce the sort time, you can sort by simple
field types, such as text fields, instead of by single
instance or multi-instance field types.

Processing Time (ms) Time spent processing all calculations and fields
and delivering all business object instances in the
report results. Includes time for generating data for
fields and columns.
This field displays zero if the report ran for the first
time and contains paginated results.

Subreport Invocation Time (ms) (Composite reports only.) Time spent running
subreports, including time starting and ending each
subreport request.
Filter Tree Time (ms) Time spent building the filter tree while initializing
the report definition.
This field displays zero if:
• There are no filters on the report.
• The report execution is an interaction. Example:
Drill down, paginated report results, outlining, or
facet search.

Report Parameters Evaluation Time (ms) Time spent evaluating all user-entered prompt
values while initializing the report.
This field displays zero when:
• There are no prompts on the report.
• The report execution is an interaction and
reuses the initial prompt values from the initial
report execution. Example: Drill down, paginated
report results, outlining, facet search.

Failure Information
This section only displays if the report fails to run.

Log Field Description

Failure Info Exception Message Description of why the report failed to run.
Failure Info Fail Type Report failure type.

Log Field Description

Failure Info Main Stats Bucket The process running at time of report failure.
Failure Info Sub Stats Bucket The subprocess running at time of report failure.

Report Prompts
The report prompts in this section can come from the data source and data source filters.

Log Field Description

Prompt Field Prompt fields that the report evaluates.
Prompt Value(s) Values for the prompt field.
Count (Workday Support only.) Count of how many
instance prompt values are selected.
Possible values:
• Blank: The value for the prompt isn’t an instance
value.
• Zero: No instances were selected for the
prompt.
• Greater than zero: The number of instance
values selected for the prompt.

Hash Code (Workday Support only.) Hash code used to

recreate the instance prompt selected values.

Field Performance Metrics

Log Field Description

Field Name of the field in the report, data source, or data
source filter.
Parent Field The parent field for the child calculated field.
All child fields below the second level roll up to the
second-level child field.
In some cases, a field that is either referencing
itself or another field is the Parent Field.
In some composite reports, there are parents fields
due to report nesting.

Field Type Type of field in the report.

Possible values:
• Calculated
• Calculated - Report Specific
• Computed
• Custom Field
• Workday Delivered

Total Field Security (ms) Time spent evaluating the security for the field.

Log Field Description

Total (ms) Time spent processing this field, not including Total
Field Security time.
The total time is the sum of the Data Source
Processing time and the Report Processing time.

Initialization (ms) Time spent initializing static values. Example:

Effective moment.
Data Source (ms) Time spent evaluating the field in the data source.
This field displays zero when the data source:
• Doesn't use the field.
• Is indexed and Workday doesn't evaluate the
field outside of the data source.

Data Source Security (ms) Time spent evaluating the field security in the data
source.
This field displays zero when the field isn’t used for
data source security.

Contextual Security Filter (ms) Time spent filtering logic for the data source that
calls this field during execution.
This field displays zero when there’s no contextual
security.

Report Processing (ms) Time spent filtering, sorting, processing, and so on.
This field displays zero when the report field is only
in the data source.

Times Executed Number of times the field executes, including when

the field nests under other fields.

Subreports
This section is only available for composite reports.

Log Field Description

Subreport Name of the subreport in the composite report.
Referenced in Composite Entries Where the composite report references the
subreport.
Report Performance Log The link to the report performance log for the
subreport.

Advanced Metrics
This section is for Workday Support use only.
Related Information
Tasks
Create Report Performance Logs on page 88
Reference
The Next Level: Factors Impacting Report Performance

The Next Level: Report Performance Recommendations for Large Volume Customers
The Next Level: Report Performance - Tuning Thresholds
Workday Community: A Practical Guide for High Performance Reporting

Reference: Improving Report Performance

When a report runs slowly, access the Edit Report Performance Log Settings task to log the report.
You can then access the View Report Performance Logs report and click View to identify areas for
improvement.

Report Performance Log Field What to Do

Data Source Processing Mode Indexed processing mode results in the best
report performance. Ensure that the Data Source
Processing Mode is Indexed by:
• Creating a report with an indexed data source.
• Selecting the Optimized for Performance
check box when you create a report to limit your
report to indexed fields.

Filter Processing Mode Indexed processing mode results in the best report
performance. Access the View Indexed Fields for
Data Source report to ensure that the fields you
use to filter the report are indexed for filtering. If
needed, replace nonindexed fields with indexed
fields.
Filter Processing Mode Some fields in an indexed data source aren't
indexed for all usages. If you're using an indexed
Group Processing Mode
data source and your report still runs slowly, you
can:
• Access the View Indexed Fields for Data
Source report to confirm that the fields in
your report are indexed for filters, facets,
aggregation, and group by.
• Replace nonindexed fields with indexed fields.
When creating a report, you can select the
Optimized for Performance check box to ensure
that the report uses only indexed fields.

Data Source Instance Count If the Report Instance Count is much less than
the Data Source Instant Count, consider using
Report Instance Count
a more focused data source to improve report
performance.
Example: Use My Direct Reports instead of
filtering Workers for HCM Reporting.

Related Information
Concepts
Concept: Selecting a Data Source on page 17
Concept: Indexed Data Sources and Fields on page 15
Tasks
Create Report Performance Logs on page 88

Reference
Reference: Report Performance Log Fields on page 89
Reference: Reporting Limits
The Next Level: Factors Impacting Report Performance
Workday Community: A Practical Guide for High Performance Reporting

Reference: Reporting Limits

• Data Sources on page 97
• Prism Data Sources on page 98
• Financial Modeled Data Source on page 98
• Processing on page 98
• Discovery Board Visualizations on page 98
• Scheduled Report Output on page 100
• Reports Run in the Browser on page 100
• Displaying Report Designer in the Browser on page 102
• Exporting to Excel on page 103
• Report Performance Logs on page 103
• Mobile Devices on page 103

Data Sources
Workday limits the number of returned instances based on the type of report data source (RDS) you use
and whether filtering applies. Filtering includes:
• Drill down filters.
• RDS filters.
• RDS security.
• Report filters.

Report Criteria Returned Instances Limit

Indexed RDS 3 million
Prefiltering

Indexed RDS 3 million

Postfiltering

Nonindexed RDS 3 million

Prefiltering

Nonindexed RDS 1 million (for grouping only)

Postfiltering
Pregrouping

Nonindexed RDS 3 million

Postfiltering
Indexed report fields

If your report displays an error, consider using a different data source filter for indexed data sources or a
different data source type. Example: When you use a nonindexed RDS, try using an indexed RDS instead.

For reports that use a Prism data source, Workday returns up to 1 million rows for these report types you
run in the background:
• Advanced
• Matrix
• Simple
• Transposed
Prism data sources can return up to 512 MB of data.

Prism Data Sources

Workday limits from where you can query a Prism data source created from a Prism Analytics table that is
enabled for analysis.
If the table contains more than 2,000,000,000 rows, then you can't use the Prism data source in a
discovery board viz or a custom report as a worklet on a dashboard. You can use the Prism data source in
a custom report that you run in the browser or in the background.

Financial Modeled Data Source

Workday limits the data it puts in the financial modeled data source when you set up the financial reporting
data model.

Description Limit
Time duration of journal line data Up to 3 years, rolling (current year plus 2 years
prior)
Maximum number of optional dimensions 15
Maximum number of values per dimension 100,000

Workday returns up to 1,000,000 cells that contain data in the query response.

Processing
Workday limits report processing to:
• 30 minutes for all reports before displaying an error. After 20 seconds, Workday enables you to
schedule the report to run as a background process.
• 6 hours for background reports, scheduled reports, and web services. Workday terminates the
scheduled background report if processing time takes longer.

Discovery Board Visualizations

Workday limits viz query processing to 45 seconds and limits the returned viz data size to 50 MB. Workday
displays an error in the viz if the viz query times out at 45 seconds or if the amount of data returned
exceeds 50 MB. Example: A table viz fails to display if Workday returns 500 rows and each row of data
contains 1 MB of data. This might happen if field values for a text field in a drop zone contain a lot of
information, such as survey result data.

Viz Type Results

Area Chart Workday returns up to:
• 100 values on the x-axis.
• 250 color groupings per x-axis value, plus the
Other group.

Viz Type Results

• 40 million cells, whether or not the cell contains
data. Empty cells don't display in a chart viz
like they do in a pivot table viz. However, this
limitation still applies.

Bar Chart Workday returns up to:

• 100 values on the x-axis.
• 250 color groupings per x-axis value, plus the
Other group.
• 40 million cells, whether or not the cell contains
data. Empty cells don't display in a chart viz
like they do in a pivot table viz. However, this
limitation still applies.

Chart Workday returns up to:

Donut Chart Workday returns up to 250 color groupings, plus the

Other group.
Heatmap Workday returns up to:
• 100 values on the x-axis, plus the Other group.
• 100 values on the y-axis, plus the Other group.

Line Chart Workday returns up to:

Pivot Table Workday returns up to:

• 50,000 data rows.
• 12,000 row groupings (rows displayed in the
pivot table).
• 250 column attribute groupings.
• 40 million cells, whether or not the cell contains
data.

Scatterplot Workday returns up to 250 color groupings, plus the

Other group.
Table Workday returns up to 50,000 data rows.

When you filter on a field that contains more than 5,000 values, Workday returns up to 5,000 distinct
values in the Filter panel.

Scheduled Report Output

Access the Schedule a Report task to set up a schedule to run custom reports and deliver them to My
Reports. You can also schedule reports to run as a single unit by grouping and bursting up to:
• 200 report groups that use an Excel template.
• 2,500 report groups that don't use an Excel template, such as a report that's in PDF or a nontemplate
XLS format.
The limitation refers to the number of reports generated by the report group.
You can select 1 of these output types for the report:
• Excel
• Report (PDF)
• Text (CSV)
Depending on the file size or number of rows returned for report results, Workday might deliver a file type
other than the target Output Type you select.

Number of Rows Supported Formats Results

Fewer than 10,000 Excel, Report (PDF), and Text Workday generates the report in
(CSV) the selected Output Type format.
Between 10,000 and 500,000 Excel and Text (CSV) If you select Excel as the Output
Type format, Workday generates
the report in Excel.
If you select Report (PDF) or Text
(CSV), Workday generates the
report in Text (CSV) format.

Between 500,000 and 1 million Text (CSV) Workday generates the report in
Text (CSV) format.
More than 1 million Not supported Workday doesn't generate a
report.

You can use the Process Monitor report to determine if Workday switched to another supported format, or
if Workday didn't generate the report.

Reports Run in the Browser

Report Type Results

All • The file size limit for report results is 50 MB and
15 GB for scheduled reports.
• The XML string limit is 2 GB.
• Workday limits tabular data processing to 5
seconds.

Advanced Workday returns up to:

• 1,000 instances.
• 10,000 rows for nonsupported pagination.

Report Type Results

• 50,000 rows for reports with drill to details or
supported pagination.
Workday processes the Group by Field only for
reports with column or row grouping if there are
1 million or fewer post-filter instances. The limit
doesn't affect indexed fields.

Composite Workday returns up to:

• 100,000 cells.
• 1,000 columns.
• 16,000 rows.
For reports with drill-down, Workday returns up to:
• 50,000 rows for supported pagination.
• 10,000 rows for nonsupported pagination.
Workday returns up to 50,000 rows for reports that
use Prism data sources.

Matrix Workday returns up to:

• 250 columns.
• 12,000 rows.
In the report definition, you can add up to 15
summarization rows.
For reports with drill-down, Workday returns up to:
• 50,000 rows for supported pagination.
• 10,000 rows for nonsupported pagination.
• 80,000 drill-down cells.
For reports using Prism data sources, Workday
returns up to:
• 5,000 instances for count distinct aggregations.
• 50,000 rows.
Workday can process up to 1 million rows for
reports with aggregations and up to 40 million rows
for:
• Background reports.
• Scheduled reports.
• Web services.
Workday processes the Group by Field only for
reports with column or row grouping if there are
1 million or fewer post-filter instances. The limit
doesn't affect indexed fields.

nBox Workday enables up to 100 images for each nBox

cell.
For reports with drill-down, Workday returns up to:
• 50,000 rows for supported pagination.
• 10,000 rows for nonsupported pagination.

Report Type Results

Workday returns up to 50,000 rows for reports
using Prism data sources.

Search Workday returns up to 2,000 instances.

The limit doesn't affect mass actions within search
reports.

Simple Workday returns up to:

• 1,000 instances.
• 50,000 rows.

Transposed Workday returns up to:

• 1,000 instances.
• 50,000 rows.

Trending For reports with drill-down, Workday returns up to:

• 50,000 rows for supported pagination.
• 10,000 rows for nonsupported pagination.
• 80,000 drill-down cells.
For reports using Prism data sources, Workday
returns up to:
• 5,000 instances for count distinct aggregations.
• 50,000 rows.
Workday can process up to:
• 1 million rows for reports with aggregated rows.
• 40 million rows for background reports,
scheduled reports, and web services.
Workday processes the Group by Field only for
reports with column or row grouping if there are
1 million or fewer post-filter instances. The limit
doesn't affect indexed fields.

Displaying Report Designer in the Browser

Workday limits the number of:
• Cells for multi-instance columns and fields to 1 million for composite, matrix, and trending reports.
• Top-level rows to 50,000 for all reports.
Your composite report can have an unlimited number of columns and rows. Adding more columns or rows
might affect the response time of the report designer. These browser limits restrict what you see in the
report designer:

Browser Rows Displayed Columns Displayed

Internet Explorer 11 50 20
All other browsers 200 50

Exporting to Excel
Workday adheres to these Microsoft Excel 2007 or newer limitations when exporting a composite report
with outlining:

Type Limit
Cells 1,000,000
Columns 16,384
Rows 1,048,576

Report Performance Logs

You can use report performance logs to troubleshoot performance issues in your reports.

Mobile Devices
You can enable dashboards and reports for mobile so that it's easier to view reporting data on Android,
iPad, and iPhone devices. Managers and executives can also view metrics and key performance indicators
on mobile applications.
Workday designs mobile apps for self-service, so not all reporting features are available. To access all
features, sign in on a browser or desktop.
Your tenant configuration determines how dashboards and reports display. For custom reports and
worklets on iPads, Workday doesn't support:
• Hiding table borders and column headings.
• Manually refreshing data. The data refreshes every time you access the report or worklet.
• Maximizing reports.
• Using 3D chart options.
For mobile devices, Workday doesn't support:
• Creating composite reports.
• Creating custom dashboards.
• Saving custom prompt values for worklets.
• Using dual-axis and combination charts.
• Viewing all or conditional formatting styles for composite reports.
Workday doesn't support these reports on mobile:
• Calendars.
• XpressO reports with 2 tabs.
• XpressO reports that use data pulled from the related business object.
Dashboard availability depends on your security configuration, but we support many Workday-delivered
dashboards on mobile. To determine if Workday enables a dashboard for mobile devices:
1. Access the Maintain Dashboards report.
2. From the related actions menu of a dashboard, click Dashboard > Edit.
3. Access the Settings tab.
4. View the enabled Device Type in the Task Information section.
Related Information
Tasks
Create Report Performance Logs on page 88
Create Report Performance Logs on page 88

Reference
The Next Level: Breaking Through With Mobile
The Next Level: Breaking Through with Mobile

Simple Reports

Steps: Create Simple Reports

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can create a simple custom report with options for filtering and sorting data.

Steps
1. Create Custom Reports on page 29.
2. Set Up Columns for Simple Reports on page 104.
3. Set Up Sort Options for Custom Reports on page 33.
4. Set Up Filter Options for Custom Reports on page 36.

Next Steps
Test the report to ensure Workday displays the data correctly.
When you test a report, Workday displays the first 10 results. When the report includes a:
• Filter, Workday applies the filter to all instances of the primary business object and displays the first 10
results.
• Subfilter, Workday applies the subfilter to the 10 filtered instances and displays the results.
Related Information
Concepts
Concept: Custom Reports on page 12
Concept: Business Objects, Data Sources, and Fields on page 13

Set Up Columns for Simple Reports

Prerequisites
• Create a custom simple report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can select fields from associated business objects to display on simple reports.

Steps
1. Access the Edit Custom Report task.
2. As you complete the Columns tab, consider:
Option Description
Order Select the order that the fields should display in
for your report. The first row in the grid represents
the first column on the report, the second row
represents the second column, and so on.
Field Select the field associated with the business
object to include in your report.
Column Heading Override Specify a name to use instead of the populated
name on this report to ensure that any future
renaming by Workday doesn't impact your labels.
Workday supports translations for this field on
your report.
Format Select a format to apply to currency and numeric
fields. When displaying numbers in Thousands
or Millions format, Workday rounds each number
independently.
Options Available options depend on your field type.
You can also select the Create prompt to create
these custom display options:
• Create Analytic Indicator, which enables you
to use the indicator in other reports throughout
your tenant.
• Create Analytic Indicator for Report, which
enables you to use the indicator only in the
current report.
• Create Percentile for Report, which enables
you to create custom percentiles up to 2
decimal places to use in your report. Workday
uses an approximate value for currency and
numeric fields in the percentile (PCTL).

Next Steps
To convert a simple report to an advanced report, access the related actions menu of your simple report
and select Custom Report > Change to Advanced Report Type.
Related Information
Concepts
Concept: Advanced Reports on page 111
Reference
Reference: Field Options on page 64

Advanced Reports

Steps: Create Advanced Reports

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can create an advanced report that includes:
• Multiple levels of headings and subtotals.
• Related business objects.
• Subfilters.
You can also use 1 or more advanced reports as subreports in composite reporting.

Steps
1. Create Custom Reports on page 29.
Create a custom advanced report.
2. Set Up Columns for Advanced Reports on page 107.
3. Set Up Sort Options for Custom Reports on page 33.
4. Set Up Filter Options for Custom Reports on page 36.
5. Set Up Prompt Options for Custom Reports on page 38.
6. Set Up Output Options for Custom Reports on page 39.
7. Set Up Share Options for Custom Reports on page 42.
8. Set Up Advanced Options for Custom Reports on page 43.

Next Steps
Test the report to ensure Workday displays the data correctly.
When you test a report, Workday displays the first 10 results. When the report includes a:
• Filter, Workday applies the filter to all instances of the primary business object and displays the first 10
results.
• Subfilter, Workday applies the subfilter to the 10 filtered instances and displays the results.
Related Information
Concepts
Concept: Advanced Reports on page 111
Concept: Business Objects, Data Sources, and Fields on page 13
Concept: Custom Reports on page 12
Tasks
Set Up Outlining in Advanced Reports on page 109

Set Up Columns for Advanced Reports

Prerequisites
• Create a custom advanced report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can select fields from associated business objects to display on advanced reports.

Steps
1. Access the Edit Custom Report task.
2. As you complete the Columns tab, consider:
Option Description
Order Select the order that the fields should display in
your report. The first row in the grid represents
the first column on the report, the second row
represents the second column, and so on.
Business Object Select a self-referencing, single instance, or multi-
instance field based on the primary business
object.
Field Select the field associated with the business
object to include in your report. If you select a:
• Self-referencing field on the Business
Object column, select a field from the primary
business object.
• Single instance or multi-instance field on the
Business Object column, select a field from a
related business object.
When you select a multi-instance field on the
Business Object column, that field displays as
a column group heading. Fields from the related
business object display as subcolumn headings.
Select Count to compute the total of the detail
data or summarized rows displayed in your report
and display a value of the subtotals and grand
totals. Workday displays a value only on subtotals
and grand totals and displays a blank value
for detail or summarized rows. When counting,
Workday doesn't include detail data rows that
make up the summarized row nor displayed report
rows associated with related business objects.
To count the detail data rows that make up
the summarized row, select One for the Field
and Sum on the Option prompt. Selecting One
enables Workday to calculate group totals and
grand totals.

Option Description
Column Heading Override Specify a name to use instead of the populated
name on this report to ensure that any future
renaming by Workday doesn't impact your labels.
Workday supports translations for this field on
your report and web services.
Column Heading Override XML Alias (Available only after selecting the Enable As Web
Service check box on the Advanced tab.)
Workday displays a properly formed XML alias
based on the selected Field or Column Heading
Override.
XML aliases must be unique. You can use the
Maintain Custom Report XML Alias task to
resolve an error caused by duplicate XML aliases.
When you translate a report, Workday doesn't
translate the Column Heading Override XML
Alias.

Format When displaying numbers in Thousands or

Millions format, Workday rounds each number
independently.
To display 12 decimal places when you
export reports to Excel or PDF, you can select
#,##0.000000000000 or #,##0.############ for
these aggregated numeric fields:
• Average
• Maximum
• Minimum
• Sum
The data must include 12 digits to display 12
decimal places, otherwise Workday trails the
number with zeros.

Options Available options depend on your field type.

You can also select the Create prompt to create
these custom display options:
• Create Analytic Indicator, which enables you
to use the indicator in other reports throughout
your tenant.
• Create Analytic Indicator for Report, which
enables you to use the indicator only in the
current report.
• Create Percentile for Report, which enables
you to create custom percentiles up to 2
decimal places to use in your report. Workday
uses an approximate value for currency and
numeric fields in the percentile (PCTL).

3. (Optional) To override the column heading for a multi-instance field on the Business Objects column,
complete the Group Column Headings grid.
As you complete the grid, consider:
Option Description
Business Object Select a multi-instance field that you used in the
Business Object column of the first Columns
grid.
If you enable the report as a web service, add a
row for each multi-instance field.

Group Column Heading Specify a name to use for the column heading.
Workday supports translations for this field on
your report and web services.
Group Column Heading XML Alias (Available only after selecting the Enable As Web
Service check box on the Advanced tab.)
Workday displays a properly formed XML alias
based on the selected Business Object or
Group Column Heading.
XML aliases must be unique. You can use the
Maintain Custom Report XML Alias task to
resolve an error caused by duplicate XML aliases.
When you translate a report, Workday doesn't
translate the Group Column Heading XML
Alias.

Related Information
Concepts
Concept: Report-Specific Calculated Fields
Concept: Reports as a Service (RaaS) on page 211
Tasks
Steps: Create Advanced Reports on page 106
Reference
Reference: Field Options on page 64

Set Up Outlining in Advanced Reports

Prerequisites
• Create a custom advanced report.
• Security: Custom Report Creation domain in the System functional area.

Context
You can use outlining in advanced reports to expand and collapse various levels of data when report
results display. You can also use outlining to subtotal currency or numeric data. Workday preserves
outlining when you export advanced reports to Microsoft Excel, but all levels of the report display without
outlining.
Consider these conditions when using outlining:
• All fields on the report must associate with the primary business object associated with the data source.
• Outlined reports can't display as worklets.

• Outlining doesn't support some languages due to right-to-left formatting limitations.

• When you print to PDF, only the top level of the outline prints.
• Workday doesn't support facet filters in advanced reports with outlining.
• Workday supports a maximum of 8 levels of outlining.

Steps
1. Access the Edit Custom Report task.
2. On the Columns tab, select Group Name for the Field as the first column on the report.
3. On the Sort tab, select the Enable Outlining based on Grouping check box to specify the data to
display in your report as an outline.
4. (Optional) To group data and provide a logical separation of data on the report, select the Display
Headers check box.
5. (Optional) To subtotal numeric data and display the result of the aggregation on the subtotal row of the
outlined report:
a. Select a currency or numeric value on the Field prompt on the Columns tab.
b. Specify an aggregation on the Options prompt.
c. Select the Display Subtotals check box on the Sort tab in the Sort and Group section.

Create Gauge Ranges

Prerequisites
Security: Custom Field Management domain in the System functional area.

Context
You can configure gauge parameters to use with gauge charts in your advanced reports. The gauge
displays a single value, like a speedometer in a car.

Steps
1. Access the Create Gauge Range task.
2. Enter a unique value in the Name field for the gauge range.
3. From the Type prompt, select a zone.
You can select up to 5 zones. Each zone must be contiguous and can't overlap values.
4. From the Decimal Places prompt, select the number of decimal places to use for the From Value in
the grid.
Example: If you select 2 Decimal Places and enter 1 for the To Value, Workday displays 1.01 as the
From Value for the next row in the grid.
5. From the Rounding prompt, select a rounding method for Workday to apply in the report results:
• Round: Depending on the value, Workday rounds it either down or up. Example: If you enable zero
decimal places and have a value of 1.5, Workday rounds up to 2. If the value is 1.4, Workday rounds
down to 1.
• Round down: Rounds the value down unconditionally. Example: If you enable zero decimal places
and have a value of 1.9, Workday rounds down to 1.
• Round half down: Halves the number of decimal places in the value. Example: If you enable 4
decimal places and have a value of 2.1234, Workday halves decimal places of the value to 2.12.
• Round up: Rounds the value up unconditionally. If you enable zero decimal places and have a value
of 1.1, Workday rounds it up to 2.

6. As you complete the grid, consider:

Option Description
From Value Enter a value to configure the lower limit of the
gauge range for Zone 1.
Workday populates the From Value for each
subsequent zone based on the:
a. To Value of the previous zone.
b. Number of decimal places specified on the
Decimal Places prompt.

To Value Enter a value to establish the upper limit of the

gauge range.
Meaning Select an indicator for the range. Workday
associates each indicator with a color:
• Bad is red.
• Good is green.
• Neutral is gray.
• Warning is yellow.

Label Enter a description that displays when the report

runs.

Next Steps
Access the Output tab of an advanced report that uses a gauge output type and add your configured
gauge range to the report.
Related Information
Tasks
Set Up Output Options for Custom Reports on page 39

Concept: Advanced Reports

Advanced reports enable you to perform many actions on your data from primary business objects and
related business objects, including:
• Computing the average, minimum, or maximum value of currency and numeric fields.
• Counting.
• Grouping data up to 9 levels.
• Filtering and sorting data.
• Including group headers and group names in your report to separate your data logically based on the
group level hierarchy.
• Outlining data.
• Subtotaling and totaling data based on the group hierarchy configured in the report.
• Summarizing detail data rows.
• Using 1 or more advanced reports as subreports in composite reporting.
You can include fields from the related business objects directly in your report without needing a calculated
field. The fields from the related business objects must directly relate to the primary business object.
Related Information
Concepts
Concept: Business Objects, Data Sources, and Fields on page 13

Matrix Reports

Steps: Create Matrix Reports

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can create a matrix report to drill on and report across dimensions as well as group and summarize
data. You can also use 1 or more matrix reports as subreports in composite reporting.

Steps
1. Create Custom Reports on page 29.
Create a custom matrix report.
2. Set Up Grouping and Summarizing for Matrix Reports on page 112.
3. Set Up Drill Down for Custom Reports on page 32.
4. Set Up Filter Options for Custom Reports on page 36.
5. Set Up Prompt Options for Custom Reports on page 38.
6. Set Up Output Options for Custom Reports on page 39.
7. Set Up Share Options for Custom Reports on page 42.
8. Set Up Advanced Options for Custom Reports on page 43.

Next Steps
Test the report to ensure Workday displays the data correctly.
When you test a report, Workday displays the first 10 results. When the report includes a:
• Filter, Workday applies the filter to all instances of the primary business object and displays the first 10
results.
• Subfilter, Workday applies the subfilter to the 10 filtered instances and displays the results.
Related Information
Concepts
Concept: Business Objects, Data Sources, and Fields on page 13
Concept: Matrix Reports on page 120
Tasks
Set Up Field Values Groups for Matrix Reports on page 117
Reference
The Next Level: Creating Your Composite Report's Subreports
Examples
Example: Create a Matrix Report for Employee Data on page 121

Set Up Grouping and Summarizing for Matrix Reports

Prerequisites
• Create a custom matrix report.

• Security: These domains in the System functional area:

• Custom Report Creation
• Manage: All Custom Reports

Context
You can configure the Matrix tab on matrix reports to:
• Group instances of the primary business object.
• Summarize metrics for each grouping.
You can use matrix reports as subreports in composite reporting unless the matrix report includes:
• Only percentile summarization fields.
• Text-based count distinct summarization fields.

Steps
1. Access the Edit Custom Report task.
2. As you complete the Column Grouping (Optional) or the Row Grouping section on the Matrix tab,
consider:
Option Description
Group by Field Select a field of 1 of these types:
• Boolean
• Date
• Numeric
• Single Instance
• Text
Configure at least 1 row grouping for the report.

Sort Columns/Rows Select an option so that values sort in ascending

or descending:
• Alphabetical order based on the Group by
Field value.
• Order based on the column or row total.
Sorting isn't case-sensitive.
When enabled, Workday uses the logical sort
order for the field specified in the Group by Field
value.
The Other column or row and the Total column
or row always display as the right-most column or
row in the report results.

Options When you select Sequence Defined in Field

Values Group on the Sort Rows prompt, access
the Create Field Values Group task to configure
sorting options.
Indexed Workday selects the check box when you select:
• An indexed data source.
• A Group by Field indexed for grouping.

Option Description
If the Indexed check box is clear for a row, your
report might run slowly. Consider replacing the
Group by Field with a field indexed for grouping
so that your report can run faster.
Maximum Number of Columns/Rows Enter a value to specify the maximum number
of column or row results. When the number of
columns or rows exceeds the limit, Workday
displays an Other column or row that summarizes
the remaining values.
Workday displays more than 1 Other when:
a. You select the Sum Remaining Values check
box on the Output tab.
b. The data exceeds the number of Top n
Values that you specify.

Hide Total Column/Row Select the check box to hide the total column or
row in your report. Workday retains the check box
selection when you:
• Copy a standard report that hides column or
row totals.
• Export your report to Excel or PDF.

3. In the Define the Field(s) to Summarize grid, specify how Workday should aggregate the data.
As you complete the grid, consider:
Option Description
Summarization Type Specify the aggregation method used for the field.
The results of the aggregation method display in
the cells on the report or chart, such as a column
or donut segment.
Select:
• Calculation to create a custom calculation
based on an arithmetic expression or to look
up a prior value.
• Count Distinct to drill into and view the distinct
number of instances based on a field or row in
your report results.
You can't include a Lookup Prior Value summary
calculation on a matrix report when using the
report in a scorecard metric calculation.

Summarization Field This field is inactive when the Summarization

Type is Count.
Select a currency, instance, numeric, or text field
for 1 of these Summarization Type options:
• Average
• Calculation
• Count Distinct

Option Description
• Maximum
• Minimum
• Percentile
• Sum
Workday indexes report fields on Prism RDSs, but
might not index all fields on standard RDSs. To
select text fields for count distinct on a standard
RDS, clear the Optimized for Performance
check box on the Advanced tab.
For a Calculation Summarization Type, select
Create > Create Summarization Calculation
for Report or Create > Create System-Wide
Summarization Calculation to:
• Create a summary calculation based on an
arithmetic expression.
• Look up a prior value based on:
• Average x time periods.
• Prior rollup period.
• Prior time period.
• Sum x time periods.
Note: To create tenant-wide summarization
calculations, configure the System-Wide
Summarization Calculation Management domain
in the System functional area.
You can create fields calculated from values in
report-specific or tenant-wide calculated fields.
For faster report performance, limit the number of
calculated fields you include in the report.

Format The format applies to:

• Numeric labels.
• Table and charted outputs.
• The horizontal axis.
• The vertical axis.
When displaying numbers with Thousands and
Millions formatting, Workday rounds each number
independently, so a group of numbers might not
add up to the total displayed.
To display 12 decimal places when you
export reports to Excel or PDF, you can select
#,##0.000000000000 or #,##0.############ for
these aggregated numeric fields:
• Average
• Maximum
• Minimum
• Sum

Option Description
The data must include 12 digits to display 12
decimal places, otherwise Workday trails the
number with zeros.

Options Specify options that control how the field data

displays. The options available depend on the
field type, such as currency, date, or text.
You can select these options from the Valid
Options prompt:
• Percent of Overall Total: The value at the
intersection of a column and row. Workday
automatically changes the Format column to a
percentage format.
• Show Currency Symbol: Workday displays
Invalid on fields that aggregate values in
different currencies.
• Use as Target Line: Creates 1 or more target
lines for each data group based on numeric or
currency fields. You can configure target lines
on the Output tab.
You can also select the Create prompt to create
these custom display options:
• Create Analytic Indicator for Report, which
creates a report-specific analytic indicator. To
create an analytic indicator for use in other
reports, access the Create Analytic Indicator
task.
• Create Detail Data Override. Workday
generates a detail data override for your
summarization field when your report uses
the Trended Workers RDS. You can enter a
unique drill-down layout for the field. The detail
data that you specify overrides the selections
on the Drill Down tab. You can select these
display options for the columns:
• Display format.
• Drill down window columns displayed.
• Field label overrides.
• The sort order.
When you complete the Create Detail Data
Override task, you can select Translate
from the related actions menu of the Detail
Data Override. The Translate Detail Data
Override task enables you to specify an
override to translate and a language for
translation.
You can also control which fields to sort on
and the sort direction to use.
• Create Drill-To Report Link: Use to link to
another report from the summarization field.

Option Description
You can also map fields from the source report
to the prompt fields of the target report.
For multi-instance fields, Workday only passes
a single value to the target report. Example:
If the Country field on the source report has
values of USA and France, Workday only
passes 1 value onto the target report.
• Create Percentile for Report, which enables
you to create custom percentiles up to 2
decimal places to use in your report. Workday
uses an approximate value for currency and
numeric fields in the percentile (PCTL).

Indexed Workday selects the check box based on the

indexed RDS, indexed data source filter, and the
indexed field you select. The check box indicates
if your report has the potential to run faster.

Related Information
Concepts
Concept: Analytic Indicators on page 62
Tasks
Create Drill-To Report Links on page 118
Set Up Output Options for Custom Reports on page 39
Reference
The Next Level: Creating Your Composite Report's Subreports
Examples
Example: Create a Matrix Report for Employee Data on page 121

Set Up Field Values Groups for Matrix Reports

Prerequisites
• Create a custom matrix report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can use field values groups in matrix reports to display:
• A field value, even when there are no instances with that value. Example: Add Below Expectations to a
field values group to display when employees don't have performance ratings.
• Only the values you select.
You can also sort data in a logical order rather than alphanumerically. Example: Sort performance ratings
in this order:
• Below Expectations
• Meets Expectations
• Exceeds Expectations
When you create a field values group, you can use it in other reports that use the same field.

Steps
1. Access the Edit Custom Report task.
2. As you complete the Row Grouping or Column Grouping grid on the Matrix tab, consider:
Option Description
Group by Field Select a single instance field.
Sort Rows or Sort Columns (Available options depend on the Group by Field
selection.) Select Sequence Defined in Field
Values Group to display only the values that you
add to the field values group.
Options Select an existing group or Create Field Values
Group.
3. As you complete the Create Field Values Group task, consider:
Option Description
Include Blanks Select the check box to display a column or row
for instances that have a blank value for the
Group by Field.
Field Values and Order to be Displayed Select values for the Instance based on the
business object of the Group by Field.
Select the order to display the field values in.

Related Information
Concepts
Concept: Logical Sort Order on page 63

Create Drill-To Report Links

Prerequisites
• Create a custom matrix report.
• Security: These domains in the System functional area:
• Custom Report Administration
• Custom Report Management
• Manage: All Custom Reports

Context
You can use drill-to report links to run other reports directly from the results of a matrix report. Example:
Create a drill-to link from a summary report containing an overview of ledger account types to a more
detailed report that breaks down each ledger account type.
You can also add a matrix report with a drill-to report link as a subreport to a composite report.

Steps
1. Access your matrix report from the Edit Custom Report task.
2. From the Options prompt on the Define the Field(s) to Summarize grid, select Create > Create Drill-
To Report Link.
You can create up to 5 drill-to report links for each summarization and link to any type of report.

3. As you complete the Create Drill-To Report Link task, consider:

Option Description
Drill-To Report Name Select the report that you want to drill to.
The grid displays all prompts from the drill-to
report that don't have Do Not Prompt at Runtime
selected.

Label Specify a name to use for the drill-to report

instead of the populated name.
Enable Blank Values Select the check box to enable Workday to pass
these values from the source report to the target
report:
• Blank values for text fields.
• Zero values for numeric fields.
When you clear the check box, Workday omits the
field from the target report results.
To enable Workday to display a field with a blank
value on the target report results, configure the
blank field on these Value Type prompts:
• Use prompt value from source report
• Use value from axis dimension
Workday supports blank values only on instances
and when the operator is In the selected list.

4. As you complete the grid, consider:

Option Description
Value Type Workday populates some prompts with No default
value when the composite report doesn't have
populated prompt values.
Select:
• Specify default value.
• Use prompt value from source report to pass
the prompt value from the source report. This
option applies when the source report has the
same prompts as the drill-to report.
• Use value from axis dimension to pass the
value from a group by field on the source
report, or a drillable field when you access
View By. You can also pass a drillable field
value when you configure the field to display
on the report output.

Field/Parameter When you select:

• Use prompt value from source report from the
Value Type prompt, select a prompt field from
the source report.
• Use value from axis dimension from the
Value Type prompt, select a group by field or
drillable field from the source report.

Option Description
For multi-instance fields, Workday only passes a
single value to the target report. Example: If the
Country field on the source report has values of
USA and France, Workday only passes 1 value
onto the target report.

Value (Available when you select Specify default value

from the Value Type prompt.)
Select a populated value for the prompt field.

Next Steps
You can add the matrix report you created as a subreport to a composite report. You can then access drill-
to report links from these parts of a composite report:
• Calculation columns from the first dimension when you click View By.
• Cell values on summary nodes of single hierarchy outlined rows.
• Data columns with or without an outline structure.
• Data columns with or without a repeating column group.
• Data columns directly from the column and the first dimension when you click View By.
• Lookup data rows with 1 filter criteria configured and a single instance.
• Single hierarchy.
• Summarization values.
• Summary rows.
When you copy the:
• Matrix source report, Workday copies the drill-to link to the copied report.
• Composite report that uses a matrix source report, Workday doesn't copy the drill-to link to the copied
report.
To drill to another report from a:
• Calculation field, drill down on a calculation value.
• Summary row, drill down on a summary value and then select a View By field from the matrix
subreport.
Related Information
Reference
2022R1 What’s New Post: Drill-To Report Links for Composite Reports
Examples
Example: Create a Drill-To Report Link for Ledger Account Reports on page 122

Concept: Matrix Reports

Matrix reports are similar to pivot tables and crosstabs. You can group data by column or row and
configure cells to display summary values where groupings intersect.

Matrix Report Use Cases

You can use matrix reports to:
• Explore data relationships to identify correlations.
• Identify patterns that could predict future behavior.
• Locate anomalies and exceptions and determine their cause.

• Use charts and graphs to find specific quantities and relationships.

• Validate assumptions about how your organization behaves.
You can export matrix reports to Excel or deploy them as worklets. You can use matrix reports as
subreports in composite reporting unless the matrix report includes:
• Only percentile summarization fields.
• Text-based count distinct summarization fields.

Matrix Report Capabilities

From matrix report results, you can:
• Drill down on a cell value and group the results by another field.
• Summarize numeric data and display the results in a chart.
• View detail data for summarized amounts.
Detail data is current, but Workday calculates summary values when you run the report. There might be a
difference between summary values and detail data if the data changed after you ran the report.
You can’t expose matrix reports as a web service.
Related Information
Concepts
Concept: Global Fields on page 63
Reference
The Next Level: The Matrix Report
The Next Level: Creating Your Composite Report's Subreports

Example: Create a Matrix Report for Employee Data

This example illustrates how to set up options in your matrix report to group and summarize employee
data.

Context
You want to create a matrix report that provides these insights about employees based on their location:
• The annual salary each employee receives.
• The average age of employees.
• The gender and ethnicity of employees.
• The ratio, as a percentage, of contingent workers to all employees.

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Steps
1. Access the Create Custom Report task.
2. Enter Employee Data Matrix Report as the Report Name.
3. From the Report Type prompt, select Matrix.
4. Clear the Optimized for Performance check box.
5. From the Data Source prompt, select All Workers.
6. On the Matrix tab, set up the Group by Field in the Row Grouping grid.

7. Select Gender in the first row and Race/Ethnicity in the second row.
8. In the Column Grouping (Optional) grid, select Location as the Group by Field.
9. Enter values for these fields in the Define the Field(s) to Summarize grid:

Summarization Type Summarization Field Label Override Format

Average Age
Sum Annual Salary USD Salary
(End of Last Year)
Calculation Percentage #,##0.00%
10.In the grid, set up the ratio by selecting Create > Create Summarization Calculation for Report in the
Summarization Field of Calculation.
11.On the Create Summarization Calculation for Report task, enter Contingent Worker to Employee
Ratio in the Field Name.
12.From the Function drill-down menu, select Summarization Calculation.
13.On the Calculation tab, select the Return Zero on Error check box.
14.In the Arithmetic Expression grid, enter these values:

Summarization Type Field Operator

Sum Contingent Worker Counter / (Divide)
Sum Employee Counter

Workday populates the Summarization Field in the Define the Field(s) to Summarize grid with your
created summarization calculation.
15.Run the report and drill down on the summarized data to interact directly with the report.
Related Information
Concepts
Concept: Indexed Data Sources and Fields on page 15
Tasks
Set Up Grouping and Summarizing for Matrix Reports on page 112
Steps: Create Matrix Reports on page 112

Example: Create a Drill-To Report Link for Ledger Account Reports

This example illustrates how to create a drill-to link from a ledger account summary report to a ledger
account detail report.

Context
You're the Chief Financial Officer of Global Modern Services, and you want to create a summary report of
debit minus credit amounts for each ledger account type. You also want to create a detailed report of the
actual ledger accounts and display the debits and credits for each account.
Using drill-to report links, you can link these reports so that clicking on a value from the summary report
takes you to the detailed report.

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Custom Report Management

Steps
1. Access the Create Custom Report task and enter:
Option Description
Report Name Ledger Account Details
Report Type Matrix
Data Source Journal Lines
2. Click OK.
3. On the Matrix tab in the Row Grouping grid, select:

Group by Field
Ledger Account Type
Account Posting Rule
Ledger Account
4. In the Column Grouping (Optional) grid, select Year from the Group by Field prompt.
5. Add 2 rows in the Define the Field(s) to Summarize grid, remove the Count summarization type, and
enter:

Summarization Type Summarization Field Label Override Format

Sum Ledger/Budget Debit Debit Amount #,##0
Amount
Sum Ledger/Budget Credit Credit Amount #,##0
Amount
6. On the Filter tab in the Filter on Instances grid, add 2 rows and select:

And/Or Field Operator Comparison Type Comparison

Value
And Ledger Account in the selection list Prompt the user Default Prompt
for the value and
ignore the filter
condition if the
value is blank
And Ledger Account in the selection list Prompt the user Default Prompt
Type for the value and
ignore the filter
condition if the
value is blank
7. On the Prompts tab, select the Populate Undefined Prompt Defaults check box.
8. In the Prompt Defaults grid, add 2 rows and select:

Field Prompt Qualifier Default Type

Ledger Account Type Default Prompt No default value
Ledger Account Default Prompt No default value
9. On the Share tab, select Share with all authorized users.
10.Click OK.

11.Access the Create Custom Report task and enter:

Option Description
Report Name Ledger Account Summary
Report Type Matrix
Data Source Journal Lines
12.Click OK.
13.On the Matrix tab in the Row Grouping grid, select Ledger Account Type from the Group by Field
prompt.
14.In the Define the Field(s) to Summarize grid, remove the Count summarization type, and select:

Summarization Type Summarization Field Format Options

Sum Ledger/Budget Debit #,##0 Create Drill-To Report
minus Credit Link
15.On the Create Drill-To Report Link task, enter:
Option Description
Drill-To Report Name Ledger Account Details
Label Ledger Account Details
16.In the grid, select:

Prompt Value Type Field/Parameter

Ledger Account Type Use value from axis dimension Ledger Account Type
Company Use prompt value from source Company
report
Year Use prompt value from source Year
report
17.Click OK.
18.Click OK.

Result
You can run the Ledger Account Detail report for the summarization value of each ledger account type in
the Ledger Account Summary report.
Related Information
Tasks
Create Drill-To Report Links on page 118

Composite Reports

Setup Considerations: Composite Reports

You can use this topic to help make decisions when planning your configuration and use of composite
reports. It explains:
• Why to set them up.
• How they fit into the rest of Workday.
• Downstream impacts and cross-product interactions.

• Security requirements and business process configurations.

• Questions and limitations to consider before implementation.
Refer to detailed task instructions for full configuration details.

What They Are

With composite reports, you can combine data from multiple sources into a single report. You can use
report data sources to collate data from these types of subreports:
• Advanced
• Matrix
• Trending

Business Benefits
Composite reports enable you to:
• Consolidate and compare data across multiple data sources and time periods.
• Format reports for browsers, Microsoft Excel, mobile devices, and PDFs.
• Reduce or eliminate manual Excel intervention by incorporating style options directly in the report
designer.

Use Cases
• Deliver a detailed financial statement that compares plan and actual data.
• Measure the health of your organization by comparing headcount and turnover.
• Prepare comprehensive payroll documents.
• Track internal metrics for your organization.

Questions to Consider

Questions Considerations
Which report type should you use as your • Advanced reports enable you to include
subreport? dynamic data rows. When you use advanced
reports, Workday maintains any sort order
defined in the reports in your composite report.
• Matrix reports enable you to summarize and drill
down on data in your composite report.
• Trending reports enable you to analyze trends in
financial and employee data.

Which business objects should you enable for The business objects that you enable for filtering
filtering and grouping? and grouping determine the:
• Data you can reference in your composite
report.
• Filter criteria you can use on rows.
• Groupings you can use on columns.
Each subreport must reference all enabled
business objects as primary or related business
objects.

How should you define prompt values for Prompts might not display to report runners in
subreports? subreports. You can configure prompts by defining
prompt values:

Questions Considerations
• Directly in the subreports.
• In the composite report so report runners can
easily run the report without needing to provide
prompt values each time.
You can use custom or Workday-delivered prompt
sets to configure populated values for prompts to
avoid creating duplicate prompts in your composite
report.

Recommendations
Use:
• A consistent naming convention across your subreports to help you find your subreports more easily.
Example: Add Subreport to the name of each subreport.
• A lookup date rollup calculated field to compare trended data across different time dimensions when
using trending subreports.
• Fewer filters on your subreports so you can access and manage data from the composite report.
• Hierarchies to define the filter criteria when using business objects with hierarchical structures. Workday
updates the filter criteria as you update the hierarchy.
• Matrix subreports because you can drill down on and summarize your data.

Requirements
• All subreports that use the trending report type must use the same time dimension.
• The Group by Field on your subreports must use the same related business object as the control field
column on your composite report.
• Use the Table output option on all subreports so that your data displays properly when used on the
composite report. You can configure other output options on the composite report.

Limitations
• You can incorporate changes to your organizational hierarchies using effective dates, but not all
hierarchies are date effective.
• You can't:
• Apply outline structures when you use multiple control field columns.
• Configure column outlining for repeating column groups when a conditional value already exists on a
cell.
• Create composite reports on mobile devices.
• Export charts to Excel.
• Include control field columns in repeating column groups.
• Retain column width and row height when you export to PDF.
• Use advanced, matrix, or trending reports with filter aggregations as subreports.
• Use matrix or trending reports with text-based count distinct summarization fields or only percentile
summarization fields as subreports.
• View conditional formatting or all formatting styles on mobile devices.

Tenant Setup
No impact.

Security

Domains Considerations
Custom Report Creation domain in the System Enables you to create and manage custom reports.
functional area.
Custom Report Management domain in the System Enables you to delete, edit, and view custom
functional area. reports you own.
Formatting Style Management domain in the Enables you to create, manage, and view
System functional area. formatting styles.
Maintain Excel Template domain in the System Enables you to attach an Excel template to a report
functional area. definition.
Manage: All Custom Reports domain in the System Enables you to delete, edit, and view all custom
functional area. reports in your tenant, including reports owned by
other individuals.
Outline Structure Management domain in the Enables you to manage outline structures for
System functional area. composite reports.
Report Prompt Set Management domain in the Enables you to create, delete, and edit prompt sets.
System functional area.

Workday determines composite report security based on the security settings of the subreports. If you don't
have access to the composite report and subreport, Workday dynamically modifies the report so you view
only the fields you have access to.

Business Processes
No impact.

Reporting

Reports Considerations
Report Definition Usages Displays how often you use a subreport.
Validate Composite Report Displays anomalies, exceptions, and warnings for
composite reports so you can take action on them.

Integrations
No impact.

Connections and Touchpoints

Workday offers a Touchpoints Kit with resources to help you understand configuration relationships in your
tenant. Learn more about the Workday Touchpoints Kit on Workday Community.
Related Information
Concepts
Concept: Composite Reports on page 144
Concept: Formatting Styles on page 145
Reference
Reference: Reporting Limits
The Next Level: Composite Reporting Overview

The Next Level: Composite Reporting for HCM

The Next Level: Financial Reporting

Steps: Create Composite Reports

Prerequisites
Create the advanced, matrix, or trending reports you want to use as subreports.
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can use composite reports to combine 2 or more reports into a single report. Example: You can create
a report that displays the gender of all active employees and contingent workers across your organization.
You can also create an income statement that compares the actuals and plan data so that you can drill
down on the data by ledger account and region.
Unique functionalities for composite reports include:
• Dragging and dropping columns and rows to change their placement in the report.
• Performing cell, column, and row calculations.
• Setting up cells, columns, and rows with unique formatting and reporting options.

Steps
1. Create Custom Reports on page 29.
Create a custom composite report.
2. (Optional) Select a Prompt Set.
See Concept: Prompt Sets for Composite Reports on page 145.
3. Enable Business Objects for Filtering and Grouping on page 129.
Select the business object that you want to use for filtering and grouping your subreport data.
4. Set Up Composite Report Columns on page 130.
5. Set Up Composite Report Rows on page 133.
6. Set Up Composite Report Cells on page 135.
7. Set Up Additional Options for Composite Reports on page 137.
8. Set Up Output Options for Composite Reports on page 139.

Next Steps
Test the report to ensure Workday displays the data correctly.
When you test a report, Workday displays the first 10 results. When the report includes a:
• Filter, Workday applies the filter to all instances of the primary business object and displays the first 10
results.
• Subfilter, Workday applies the subfilter to the 10 filtered instances and displays the results.
Related Information
Tasks
Steps: Create Advanced Reports on page 106
Steps: Create Matrix Reports on page 112
Steps: Create Trending Reports on page 162

Enable Business Objects for Filtering and Grouping

Prerequisites
• Create a custom composite report.
• Create the advanced, matrix, or trending reports you want to use as subreports in your composite
report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can enable business objects that filter and group your subreport data, in addition to determining the:
• Data you can reference in your composite report.
• Filter criteria you can use on rows. Example: You can define the filter criteria on lookup data rows using
a business object enabled for filtering and grouping.
• Groupings you can use on columns.

Steps
1. Access your composite report from the Edit Custom Report task.
2. As you complete the Business Object Enabled for Filtering and Grouping grid, consider:
Option Description
Business Object Select the business object that matches the
dimensions setup in all subreports used in the
composite report. Each subreport must reference
all enabled business objects as primary or related
business objects.
Your selection determines the available values for
the:
• Control field column.
• Data column.
• Lookup data row.

Hierarchy Structure (Available when the business object has a

hierarchical structure.) Specify a hierarchy
structure that you can use when you define the
filter criteria on a:
• Data cell.
• Data column.
• Lookup data row.
Example: You can define the filter criteria on a
lookup data row in terms of all the values in the
Corporate: All Accounts hierarchy structure.
Workday references only the primary hierarchy for
the outline structure.

Hierarchy Effective Date Select the effective date that Workday uses to
retrieve the hierarchies in the hierarchy structure
for filtering. Example: You undergo a company-

Option Description
wide reorganization at the beginning of next
month. You can use the first day of next month to
reference the reorganized hierarchy structure.
Consider that:
• Depending on the field, your selection might be
the end date associated with the report period.
• Not all hierarchies are date effective.

Next Steps
Set up the composite report columns.

Set Up Composite Report Columns

Context
You can configure these column types on your composite report:
• Calculation columns display the result of calculations applied on other columns.
• Control field columns set the common dimension across your report.
• Data columns display aggregated data from a subreport.
• Empty columns display empty space between other columns.
• Lookup field value columns display attributes of a control field.
You can create your reports more efficiently by duplicating columns with calculation or data cells. Workday
retains the configuration of the cell, including the:
• Cell label.
• Options selected for the cell.
• Subreports used in the cell.
• Style formatting selected.

Steps
1. Access the Edit Custom Report task.
2. Set up a control field column by selecting Define > Control Field from the menu of an undefined
column.
3. (Optional) As you complete the Outline Data section, consider:
Option Description
Outline Structure Select an outline structure to use in lookup data
rows, such as the Ledger Account Outline outline
structure. When you use the outline structure in

Option Description
lookup data rows, you can expand and collapse
nested groupings of ledger accounts.
Default Outline Structure Select the check box to use the outline structure
as the populated value in the Outline Structure
field in lookup data rows.
Expand on Initial Display Select an option from the prompt to enable
expanding second- and third-level data from the
primary hierarchy. Microsoft Excel maintains
these report settings when you export the
composite report.
Outline Effective Date Workday uses Today when you don't select an
option.
Summary Data Below Select the check box to display the summary
or total lines for data rows with outlining at the
bottom of the rows.
4. Set up a data column by selecting Define > Data from the menu of an undefined column.
5. As you complete the Sub Report section, consider:
Option Description
Sub Report Name You can't select matrix or trending subreports that
use:
• Only percentile summarization fields.
• Text-based count distinct summarization fields.

Map Sub Report Prompts Select values to configure each prompt field when
the:
• Composite report uses a prompt set.
• Subreport uses prompts.

Map Fields For Join Select the Group by Field as the Join Field that
corresponds to the business object used for the
Control Field column. The grid enables multiple
business objects to be available as dimensions on
the same report. Example: The Group by Field
Ledger Account and Ledger Account by Name
use the same Ledger Account related business
object and would be available on the same report.
To identify and fix exceptions when joining
subreports for the Map Fields For Join grid,
access the Validate Composite Reports report
and click Fix.

6. (Optional) Select a value on the Field to Aggregate prompt in the Data Item section.
Available options depend on the Summarization Type that you configure on the subreport.
7. (Optional) Set up a lookup field value column by selecting Define > Lookup Field Value from the menu
of an undefined column.
8. In the Lookup Type section, select Control Field Column to display the data in rows sorted by the
Return Field value. The Return Field value must be an attribute of the business object associated with
the control field column.

9. (Optional) Set up a calculation column by selecting Define > Calculation from the menu of an
undefined column.
As you complete the task, consider:
Option Description
Reverse the Sign Select Yes to reverse the natural sign of a value.
You can create a row category and reverse the
sign of cells in rows associated with that category.
Drill Down Layout Override Select a value from the prompt to enable report
runners to drill down on data in calculation
columns.
Note: Workday doesn't support drilling down on
custom fields.
You can configure drill-down options and access
the Create Composite Calculation Drill Down
Definition task. In the Drill Down Measures grid,
you can specify the columns from your composite
report to use in your drill-down layout. Configure
detail drilling in the Custom View Details grid by
specifying the business objects to use when you
select View Details or the drillable value on the
column.

10.(Optional) Set up an empty column by selecting Define > Empty from the menu of an undefined
column.
11.(Optional) Set up a Repeating Column Group on a defined column to enable a column or a series of
columns to repeat based on a value.
Example: Plan and Actuals columns can repeat for each company or cost center.
Workday supports repeating column groups for all column types except control fields.
12.As you configure the Repeating Column Group option, consider:
Option Description
Repeating Field Select a value from the prompt that's a valid
dimension in all subreports referenced by the data
columns.
Sort Repeating Field Select a value from the By Value prompt to sort a
cell value in ascending or descending order.
Outline Data Select an option from the prompt to enable
column outlining. You can expand and collapse
various levels of data when the report results
display.
Note: Workday disables column outlining when
a conditional value already exists on a cell. If you
configure column outlining first, then Workday
limits configuring conditional values to calculation
cells.

13.(Optional) Select Delete on a defined column to view up to 3 levels of cell dependencies for the column
before deleting it from the report.

Related Information
Concepts
Concept: Analytic Indicators on page 62
Tasks
Steps: Create Matrix Reports on page 112
Reference
The Next Level: Composite Reporting - Control Columns

Set Up Composite Report Rows

Prerequisites
• Create a custom composite report with at least 1 column defined.
• Create the advanced, matrix, or trending reports you want to use as subreports in your composite
report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can set up these row types on your composite report:
• Calculation rows display the result of calculations that reference other rows.
• Combine data rows display all rows from the control field columns for all subreports. You can then apply
calculations to create a Total row.
• Dynamic data rows filter for instances based on the results of an advanced subreport.
• Empty rows provide empty space between rows of data.
• Lookup data rows determine the data to display based on filter criteria. You can use this row type to
apply row outline structures.
You can create your report more efficiently by duplicating rows with cells. When you duplicate rows,
Workday retains the setup of the cell, including the:
• Cell label.
• Options selected for the cell.
• Subreports used in the cell.
• Style formatting selected.

Steps
1. Access the Edit Custom Report task.
2. (Optional) Set up a lookup data row by selecting Define > Lookup Data from the menu of an undefined
row.
As you complete the task, consider:
Option Description
Filter Criteria Workday populates the Filter Data in Sub Report
grid based on the control field columns in the
report. This determines the rows to include in the
report in addition to the filter criteria used for the
entire row.
Outline Structure In the Outline Options section, Workday
populates the field based on the selection on the

Option Description
control field column. The outline structure sets up
the hierarchy in the report that groups data.
Workday doesn't support outlining on multiple
control field columns.

Expansion Level In the Outline Options section, specify the

expansion approach that displays when you
expand an outline. You can select:
• Use Row Filter Criteria to expand rows for
each hierarchy node and detail instance
defined in the Filter Criteria section for the
report row.
• Level Number to display an expansion row
for each unique value in the hierarchy for that
level.
• Use Starting Node to display the highest
organization or organization node a user has
permission to view.

Starting Node (Available when you select Use Starting Node

as the Expansion Level.) Specify the highest
node to display for the current user based on the
hierarchical level of the field.
Include Nodes with No Data In the Outline Options section, select the check
box to include and enable expansion on nodes
that don't have data.
3. (Optional) Set up a combine data row by selecting Define > Combine Data from the menu of an
undefined row.
4. (Optional) In the Sort section, select a value from the By Value prompt to sort the data by total for
columns and rows, or logically for control field columns.
5. (Optional) Set up a dynamic data row by selecting Define > Dynamic Data from the menu of an
undefined row.
As you complete the task, consider:
Option Description
Map Sub Report Prompts Set up each prompt field if the:
• Composite report uses a prompt set.
• Subreport uses prompts.

Filter Data from Sub Report Set up the grid to filter rows from the advanced
subreport. Workday keeps the sort order
configuration for the subreport when you run the
composite report.
6. (Optional) Set up a calculation row by selecting Define > Calculation from the menu of an undefined
row.
7. (Optional) Set up an empty row by selecting Define > Empty from the menu of an undefined row.

8. (Optional) As you complete the Options prompt in the Advanced section of a defined row, consider:
Option Description
Hide Analytic Indicator On the Options prompt in the Advanced section,
select the check box to hide analytic indicators
configured on columns that impact your row.
Create Conditional Formatting Override Access the task to set up styles and visibility
options that apply to true or false conditions.
9. (Optional) Select Delete on a defined row to view up to 3 levels of cell dependencies for the row before
deleting it from the report.
Related Information
Concepts
Concept: Logical Sort Order on page 63

Set Up Composite Report Cells

Prerequisites
• Create a custom composite report.
• Configure the columns, rows, and subreports for the composite report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can configure:
• Calculation cells that display the result of calculations applied to other cells.
• Data cells that display data from a matrix or trending subreport.
• Label cells that display text items on the report, such as headers and titles.
• Style cells that apply style formatting to selected cells.
You can duplicate columns and rows with calculation or data cells to create columns more easily. When
you duplicate cells, Workday retains the configuration of the cell, including the:
• Cell label.
• Options selected for the cell.
• Subreports used in the cell.
• Style formatting you select.

Steps
1. Access your composite report from the Edit Custom Report task.
2. (Optional) Configure a data cell by selecting Define > Data from the menu of an undefined cell.
3. As you complete the task, consider:
Option Description
Sub Report Name Select an advanced or matrix report to add to your
composite report.
Map Sub Report Prompts Configure each prompt field when the:
• Composite report uses a prompt set.
• Subreport uses prompts.

Option Description
Filter Data in Sub Report Complete the grid to filter rows from the
advanced, matrix, or trending subreport. Workday
keeps the sort order from the subreport when you
run the composite report.
Hide Analytic Indicator Select the Hide Analytic Indicator check box on
the Options prompt to hide visual representations
configured on the columns.
4. (Optional) Configure a calculation cell by selecting Define > Calculation from the menu of an undefined
cell.
5. As you complete the task, consider:
Option Description
Hide Analytic Indicator Select the Hide Analytic Indicator check box on
the Options prompt to hide visual representations
configured on the columns.
6. (Optional) Configure a cell label on the control field column by selecting Define > Label from the menu
of an undefined cell.
7. As you complete the task, consider:
Option Description
Text Expression Enter the text that you want to display on your
report and enclose variables in brackets.
Example: Headcount in [V1].

[V1] Variable... [V4] Variable When you run the report, Workday replaces the
variable with the dynamic value in the variable
field, such as the headcount.
8. (Optional) Configure a conditional override for the cell value by selecting Define > Conditional Value
from the menu of an undefined cell.
You can override the value of an undefined cell that intersects a lookup data row and a data column.
You can configure the cell to display zero or the actual value based on whether the condition is true or
false.
9. (Optional) Configure a conditional format for the cell value by selecting Define > Conditional Format
from the menu of an undefined cell.
10.(Optional) Configure a cell style by selecting Style from the menu of an undefined cell.
11.(Optional) Duplicate a data cell configuration by selecting Duplicate from the menu of a defined cell.
You can then select the Duplicate to location by Cells, By Row, or By Column.
12.(Optional) Clear a cell configuration by selecting Clear from the menu of a defined cell.
Workday enables you to select Clear All to clear dependent report components, down to 3 levels of
depth in the dependency hierarchy for:
• Analytic indicators.
• Cells.
• Columns.
• Conditional formatting overrides.
• Drill down layouts.
• Override conditions.
• Rows.

Set Up Additional Options for Composite Reports

Context
In the composite report settings, you can set up additional options to:
• Apply styles and formatting to the composite report.
• Customize the column headings using variables.
• Manage the business objects enabled for filtering and grouping.
• Set up headers and footers on the composite report.
• Set up prompt sets.

Steps
1. Access your composite report from the Edit Custom Report task.
2. (Optional) As you complete the General tab from the settings menu on your report, consider:
Option Description
Style Select from Workday-delivered or custom
formatting styles.
Access the Create Formatting Style task to
create custom formatting for these attributes:
• Alignment
• Border
• Column Width
• Fill
• Font
• Gridlines
• Number

Business Object Select the business object that matches the

dimensions setup in all subreports used in the
composite report.
Your selection determines the available values for
the:
• Control field column.
• Data column.
• Lookup data row.

Hierarchy Structure (Available when the business object has a

hierarchical structure.) Specify a hierarchy
structure that you can use when you define filter
criteria on a:

Option Description
• Data cell.
• Data column.
• Lookup data row.
Example: You can define the filter criteria on a
lookup data row in terms of all the values in the
Corporate: All Accounts hierarchy structure.
Workday references only the primary hierarchy for
the outline structure.

Hierarchy Effective Date Select the effective date that Workday uses to
retrieve the hierarchies in the hierarchy structure
for filtering. Example: You undergo a company-
wide reorganization at the beginning of next
month. You can use the first day of next month to
reference the reorganized hierarchy structure.
Consider that:
• Depending on the field, your selection might be
the end date associated with the report period.
• Not all hierarchies are date effective.

3. (Optional) On the Header/Footer tab, set up the header and footer information for the report.
4. As you complete the task, consider:
Option Description
Text Expression Enter the text to display on your report and
enclose variables in brackets.
Example: Last updated on [V1].

[V1] Variable... [V4] Variable When you run the report, Workday replaces the
variable with the dynamic value in the variable
field, such as the date the report runs.
5. (Optional) On the Column Headings tab, specify the column headings to include in your report.
6. As you complete the task, consider:
Option Description
Generate Column Headings Select to enable Workday to add available column
headings to the grid.
Style To apply style formatting to all of the headings in
your report:
• Create your own style.
• Select from Workday-delivered or custom
styles.
To format cells:
a. Click the Popup Window icon on the Cell
Name of the Column Heading Cells grid for
the cell that you want to format.
b. From the related actions menu of the View
Column Header Cell task, select Column
Header Cell > Edit.

Option Description
c. Select a style.

When creating a column heading cell, use a data column as the Column Reference so that Workday
can enable the Sub-Report Prompts option.
7. (Optional) On the Prompts tab, populate prompt values and connect prompts to a prompt set.
8. (Optional) On the Output tab, specify the output options for the report.
To set up a composite report as a chart, the report definition must:
• Contain no outlining on columns or rows.
• Contain no repeating column groups.
• Include at least 1 combined data row.
9. (Optional) As you complete the Composite Options section on the Advanced tab, consider:
Option Description
Show Hidden Rows, Columns and Cells Select to override any individual settings for cells,
columns, and rows in the report definition and
display these items unconditionally.
Show Row, Column and Cell definitions in Select to enable the cell, column, and row tabs
designer to display when you select the Report Settings
icon. You can then view these definitions using
the tab-based designer rather than the grid.
Do Not Reverse the Sign Select to override any individual sign reversals in
the report definition and display all numerical data
using the original sign value from any subreport.
Export Expansion Hierarchy to Excel Select to export the report to Microsoft Excel
using the outlining structure.

Set Up Output Options for Composite Reports

Prerequisites
• Create a custom composite report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can use the Output tab to specify these options for composite reports:
• Help text.
• Output types, such as chart, table, or layout.
• Worklets.

Steps
1. Access the Edit Custom Report task.
2. Access the Output tab from the settings menu on your report.

3. As you complete the Output Type section, consider:

Option Description
Chart You can't select Chart or Chart and Table when
your report uses:
Chart and Table
• Column outlining.
• Conditionally hidden columns or rows.
• Repeating column groups.

Layout Select to configure the KPI Card or KPI Line and

enable key performance indicators for your data.
4. (Optional) As you complete the Chart Options section, consider:
Option Description
Horizontal/Vertical Axis (Available axes depend on your Chart Type.) Set
up both axes for bubble charts. Donut charts don't
have axes.
Rows for Charting Select specific rows to chart for all chart types.
Add Secondary Axis (Available if you select Area - Overlaid, Column -
Clustered, or Line as the Chart Type.) Select the
check box to visualize changes in your data and
compare metrics with different scales using dual
axis charts. A dual axis enables you to overlay 2
of these chart types when you select 1 of them for
the Primary Axis:
• Area - Overlaid
• Column - Clustered
• Line
Select values on the Metrics to Include and
Secondary Vertical Axis Chart Types prompts
to use on the dual axis chart.

Top n Values Enter the number of top results to display on your

Sum Remaining Values Use with the Top n Values option.

Example: If you include only the top 10 locations
out of 22, you can sum the remaining 12 locations
into a single value labeled as Other on the chart.

Target Line Type Set up target line options for bar and column
charts by clicking:

Option Description
• Display one target line for all groups, which
enables you to select a tenant-wide calculated
field to use for drawing a single target line on
the chart.
• Display a separate target line for each
group using metric, which enables you to
display a unique target line for each group
displayed in a bar or column chart. Select the
specific measure or metric to use as a target
value when creating the report definition. On
the Matrix tab, include at least 1 currency or
numeric report field to summarize and to use
as a target line. To select the report field to use
as a target line, select Use as Target Line from
the Options prompt.

5. (Optional) Select the Enable As Worklet check box in the Worklet Options section to enable your
report as a worklet.
6. As you complete the section, consider:
Option Description
Available on Select the landing pages where you want to
display the composite report as a worklet.
Example: To configure a report as a worklet on
mobile devices, select Mobile Reports.

Maximize Report Options All reports that you enable as worklets display a
View More... link that enables you to click:
• Display this Worklet when Maximized.
Workday runs the report and ignores the
maximum number of rows specified for the
worklet. The report includes any columns with
the Display this Worklet when Maximized
option selected in the report definition.
• Run a Different Report when Maximized.
Workday runs the specified custom report that
you have access to.

Refresh Data Refresh report data for the worklet when you
either:
• Access the worklet.
• Sign in to Workday.
Consider more frequent refreshes when you
expect frequent changes to the report data.

7. (Optional) As you complete the Help Text section, consider:

Option Description
worklets, the text displays when you click More
Information under the gear icon.

Related Information
Concepts
Concept: Charts on page 48
Setup Considerations: Charts on page 26
Reference
Reference: Chart Types on page 50
2020R1 What’s New Post: Dual Axis and Combination Charts

Create Outline Structures for Composite Reports

Prerequisites
Security: Outline Structure Management domain in the System functional area.

Context
You can use outlining in composite reports to expand and collapse various levels of data when report
results display. Workday retains outlining when you export composite reports to Microsoft Excel, enabling
you to expand levels of data.
Outline structures set up:
• How the outline behaves when referenced by a composite report.
• The business object that you base the outline on.
You can reuse outline structures in more than 1 composite report definition because they're independent
of the report. A composite report can include up to 8 outline levels, but they don't support enforced
hierarchies that skip levels.

Steps
1. Access the Create Outline Structure task.
2. As you complete the Primary Hierarchy section on the Outline Structure tab, consider:
Option Description
Business Object Select the business object that matches the
dimension configuration for the Control Field.
Outline Approach (Available options depend on the business object
that you select.) You can select Use Field Value
or Use Hierarchy when the business object
contains a hierarchy. When the business object
doesn't contain a hierarchy, Workday selects Use
Field Value.
Hierarchy Type (Available when you select Use Hierarchy as the
Outline Approach.) Select the hierarchy type of
the business object that matches the control field
column of the composite report.
Top Level Node (Available when you select Use Hierarchy as the
Outline Approach.) Select the top-level node of
the business object that matches the control field
column of the composite report.

Option Description
Last Level (Available when you select Use Hierarchy as the
Outline Approach.) Select the level number or
leaf node that is the last level for the hierarchy.
Node Value Display Field Override Select a field to override the populated label
for the node that displays when the report
runs. Example: Instead of displaying the node
Corporate: Salary & Benefits for a hierarchy
outline, you can select Ledger Account Identifier
or Ledger Account Summary ID to display the
unique ID for the node.
When you override the populated value, you can't
access the related actions menu or drill into the
node.

Detail Value Display Field Override Select a field to override the populated label
for the leaf that displays when the report runs.
Example: Instead of displaying populated values
for each leaf in the Corporate: Salary & Benefits
node, you can have these leaves display their
Identifier:
• 6000
• 6010
• 6020
When you override the populated value, you can't
access the related actions menu or drill into the
leaf.

3. (Optional) Set up hierarchies associated with the business object on the Expansion Hierarchies grid.
Once you reach the desired level in the primary hierarchy, you can configure subsequent hierarchies to
expand the hierarchy.
4. (Optional) From the First Level prompt, select the level number or leaf node that starts the hierarchy.
5. (Optional) On the Expansion Path tab, configure the subsequent expansions to use once you reach
the desired level on the primary hierarchy.
As you complete the tab, consider:
Option Description
Business Object Enabled Select the business object used in each
subreport.
Business Object Hierarchy Select the business object that corresponds to
the business object selection in the Expansion
Hierarchies grid.
Expansion Field Select a field related to the business object.

Next Steps
You can use the outline structure in your composite report to set up:
• Column outlining in the control field column.
• Filtering using the business object hierarchy.
• Row outlining in a lookup data row.

You can view the outline structure usage in your tenant by accessing the View Outline Structure report.
Related Information
Reference
The Next Level: Composite Reporting - Outline Structures

Concept: Composite Reports

Composite reports use subreports to combine data from multiple data sources into a single report where
you can configure:
• Cells, columns, and rows to perform calculations.
• Conditional formatting overrides.
• Display options for columns and rows.
• Drill-down options on calculation columns.
• Formatting.
• Hierarchies to consolidate levels of data.
• Outline structures to better filter data.
• Prompts and prompt sets to specify criteria before running a report.
• Repeating column groups that sort logically or by value.
• Rows for charting.
• Sorting options for combine data rows.
• The report as a chart or worklet.
Composite reports also provide unique configuration and functionality options. You can:
• Deploy the reports as worklets on dashboards.
• Drag and drop columns and rows to change their placement on the report.
• Duplicate columns, data cells, and rows.
• Duplicate columns and rows with calculation or data cells while retaining the cell data and setup.
• Schedule reports to run in the background individually or as part of a report group.

Fixing Errors in Composite Reports

The Clean Up Custom Report task enables you to disassociate unused custom subreports and their
summarization fields from composite reports so you can delete them. You can access the task from the
Report Definition option on the related actions menu of custom reports.
Administrators with access to these domains in the System functional area can run this task:
• Custom Report Administration
• Custom Report Management
• Manage: All Custom Reports
The Validate Composite Reports report enables you to find and take action on:
• Anomalies
• Exceptions
• Warnings
Administrators with access to the Custom Report Management and Manage: All Custom Reports domains
in the System functional area can run this report.
You can click Fix to enable Workday to take action on invalid reports. Example: Clicking Fix enables
Workday to remove a duplicate reference to a Web Service ID or fix exceptions when joining subreports for
the Map Fields For Join grid.
For all other reports that don’t display Fix, manually update the report.

Related Information
Concepts
Concept: Advanced Reports on page 111
Concept: Matrix Reports on page 120
Concept: Trending Reports on page 168
Tasks
Steps: Create Advanced Reports on page 106
Steps: Create Matrix Reports on page 112
Steps: Create Trending Reports on page 162
Reference
The Next Level: Composite Reporting Overview
The Next Level: Other Report Types and Analytic Indicators

Concept: Formatting Styles

You can create formatting styles or use styles provided by Workday to gain more control over the look of
the cells, columns, and rows in your composite report. You can apply formatting to composite reports you
export to Excel or view in your browser.
When you export the report to PDF, Workday retains all formatting styles for the report, except column
width and row height. Workday supports row outlining in PDFs if you expand the rows on the initial display.
In addition to formatting styles, you can:
• Control other display options in the report, such as hiding columns or rows.
• Include blank columns or rows.
• Override the style and visibility of a column, row, or cell, including calculation, data, or empty cells.
• Use analytic indicators.
When using formatting styles, you can't:
• Apply numerical formatting because Workday treats numerical characters in the control field column as
text.
• Create report-specific styles.
• View conditional formatting or all formatting styles on mobile devices.
Related Information
Concepts
Concept: Analytic Indicators on page 62

Concept: Prompt Sets for Composite Reports

Prompt sets are groups of interdependent fields that add more flexibility when running reports. You can use
custom or Workday-delivered prompt sets to set up populated values for prompts used in:
• Composite reports and subreports, which tie together prompts for subreports that use different report
data sources.
• Custom dashboards, which apply to all worklets on the dashboard.
• Report groups, which make it easier to populate prompt values for report groups without having to
configure prompts for each report.
You can set up the fields in the prompt set for:
• Data cells.
• Data columns.
• Dynamic data rows.
Access the View Prompt Set report to view detailed information on prompt set fields. You can also drill
into the instances that use the prompt set from the Prompt Set Usages field.

Related Information
Tasks
Create Prompt Sets on page 61

Reference: Composite Report Columns

Workday provides these column types for use in composite reports:

Column Description
Control Field Sets up the:
• Combine data row calculation of control field
rows.
• Common business object used across multiple
data sources in subreports.
• Control field used in lookup data rows and
lookup field value columns.
A report must have at least 1 control field column,
but reports with multiple control field columns can't
display results in an outline.
Workday doesn't support control fields in repeating
column groups.

Data Sets up the data pulled from the subreport. A report

must have at least 1 data column, dynamic data
row, or lookup data row.
Workday aggregates and displays the results of the
subreport using the:
• Aggregation field configured for the data
column.
• Lookup data for the row as filter criteria.
You can enable multiple business objects to be
available as dimensions on the same report.
Example: The fields Ledger Account and Ledger
Account by Name use the same Ledger Account
related business object. You can map fields for
joining so they become available on the same
report.

Lookup Field Value Enables you to include additional data associated

with the business object of the control field column.
This column type doesn't support fields with built-in
prompts.

Calculation References other columns based on these

calculation types:
• Difference
• Divide
• Multiply
• Percent Increase
• Percent Remaining
• Sum

Column Description
• Sum Range
You can configure drill-down options to specify
detail drilling on calculation columns.

Empty Provides spacing between columns with data.

Workday restricts data from the column unless it's
overwritten with cell data.
Repeating Column Group Sets up a column or a series of contiguous columns
to repeat based on a value, such as repeating by a
company or cost center.
You can use repeating column groups on all
column types, except control fields.
Repeating column groups enable you to:
• Map subreport dimensions for data cells and
columns.
• Reference calculation cells and columns in
repeating column groups.
• Sort a cell value in ascending or descending
order.
• Use column outlining to expand and collapse
various levels of data when the report results
display.

Related Information
Reference
The Next Level: Composite Reporting - Control Columns

Reference: Composite Report Rows

Workday enables you to create these row types in composite reports:

Row Description
Lookup Data Enables you to display rows based on filter criteria.
The row type works with the business object of
the control field columns to determine the data to
include in the row. You can associate each control
field column with a different business object so
you can configure multiple lookup data rows with
different Filter Criteria.
Example: To display Revenue, configure the lookup
data row to include all revenue data, such as All
Ledger Accounts.
Use Outline Options to configure outline structures
so you can expand and collapse various levels
of data when the report runs. Workday preserves
outlining when you export composite reports to
Microsoft Excel, enabling you to expand levels of
data.

Row Description
Combine Data Enables you to display all rows from the control
field column so you can apply calculations to the
rows.
Configure the By Value prompt in the Sort section
to sort the data by total in ascending or descending
order. If your By Value selection contains a control
field column, you can sort the data logically.
Example: For financial reports, you can understand
how your data changes over time by sorting the
months logically, such as January, February, and
so on.

Dynamic Data Enables you to use the results of an advanced

subreport in your report.
Workday populates the Map Sub Report Prompts
grid with prompts from the subreport, and you can
configure Additional Filter Criteria using data from
the subreport.

Calculation Enables you to configure calculations that reference

other rows, such as:
• Difference: Computes the difference between 2
rows.
• Divide: Divides a row by another row or a
numeric constant.
• Multiply: Multiplies a row by another row or a
numeric constant.
• Percent Increase: Computes the change in
percentage of values within the same data
source.
• Percent Remaining: Computes the remaining
percentage of values within different data
sources.
• Sum: Sums data from any contiguous or
noncontiguous row.
• Sum Range: Sums a range of contiguous rows.
You can select the Return Zero on Error check
box to determine if the formula is erroneous when
the report runs on these calculation types:
• Divide
• Multiply
• Percent Increase
• Percent Remaining

Empty Enables you to provide spacing between rows of

data or label sections of data.

Workday displays these 3 prompts in the Advanced section when you edit any row type:

Prompt Description
Style Enables you to add formatting to the rows in
your report. You can select from custom styles,
Workday-delivered styles, or create a style using
the Create Formatting Style task.
Category Enables you to configure the row category, such as
Income or Expense Line, or create a style using the
Create Composite Row Category task.
For rows using calculation columns, you must
select For Row Category in the Reverse the Sign
section.

Options Enables you to configure display and style options.

You can:
• (Unavailable for empty rows.) Select the Hide
Analytic Indicator check box to hide analytic
indicators configured on columns that impact
your rows.
• Hide rows.
• Reverse number signs.
• Use the Create Conditional Formatting
Override task to assign styles to true/false
conditions.

Related Information
Concepts
Concept: Logical Sort Order on page 63

Reference: Composite Report Cells

You can set up these cell types in your composite report to increase the depth and focus of your report.
The contents of the intersecting column and row types determine the actions available in each cell.

Cell Description
Data Enables you to retrieve data from your subreport at
the intersection of a:
• Calculation column and calculation row.
• Calculation column and empty row.
• Data column and calculation row.
• Data column and empty row.
You can:
• Apply additional filter data for subreports.
• Map subreport prompts.
• Select the Hide Analytic Indicator check box to
hide analytic indicators configured on columns
that impact your cells.
Executing subreports for each data cell might
impact the performance of the composite report.

Cell Description
Calculation Enables you to use calculation and data columns in
your report to set up calculation cells that reference
other cells.
You can use calculation cells with outlining.
Select the Hide Analytic Indicator check box to
hide analytic indicators configured on columns that
impact your cells.

Label Enables you to set up labels, such as Total Number

of Employees, at the intersection of a control
column and empty row.
You can define labels using text expressions and
variables. Workday replaces the variables in the
text expressions with the values of the variables
when the report runs. Example: Workday replaces
[V1] with the date in the text expression Last
updated on [V1].

Conditional Value Enables you to override the value of an undefined

cell at the intersection of a lookup data row and
data column. You can set up the cell to display zero
or the actual value based on whether the condition
is true or false.
Conditional Format Enables you to override the style and visibility of an
undefined cell.

Example: Create a Report on the Gender Breakdown of Active Workers

This example illustrates how to report on multiple data sources by creating a composite report.

Context
You want to create a report that displays the gender of all active employees and contingent workers. You
want to use that data so you can publish a statement on the gender breakdown within your organization.

Steps
1. Access the Create Custom Report task.
Create a matrix report for the gender breakdown of all active employees.
a) Enter Active Employees Matrix Subreport on the Report Name field.
b) Select Matrix from the Report Type prompt.
c) Clear the Optimized for Performance check box.
d) Select All Active Employees from the Data Source prompt.
e) Click OK.
f) On the Matrix tab, select Gender from the Group by Field prompt on the Row Grouping grid.
g) Click OK.
h) Click Done.

2. Access the Create Custom Report task.

Create a matrix report for the gender breakdown of all contingent workers.
a) Enter Contingent Workers Matrix Subreport on the Report Name field.
b) Select Matrix from the Report Type prompt.
c) Clear the Optimized for Performance check box.
d) Select All Contingent Workers from the Data Source prompt.
e) Click OK.
f) On the Matrix tab, select Gender from the Group by Field prompt on the Row Grouping grid.
g) Click OK.
h) Click Done.
3. Access the Create Custom Report task.
Create a composite report for the gender of all active employees and contingent workers.
a) Enter Gender Breakdown Composite Report in the Report Name field.
b) Select Composite from the Report Type prompt.
c) On the Business Object Enabled for Filtering and Grouping grid, select Gender on the Business
Object prompt.
d) Click OK.
e) From the menu of the C1 column, select Define > Control Field.
f) Enter Gender in the Column Name field.
g) Click OK.
h) From the menu of the C2 column, select Define > Data.
i) Enter Employees on the Column Name field.
j) In the Sub Report section, select Active Employees Matrix Subreport from the Sub Report Name
prompt.
k) Click OK.
l) From the menu of the C3 column, select Define > Data.
m) Enter Contingent Workers in the Column Name field.
n) On the Sub Report section, select Contingent Workers Matrix Subreport from the Sub Report
Name prompt.
o) Click OK.
p) Click Run.

Result
Workday displays a composite report with the gender breakdown of all active employees and contingent
workers. Each gender row displays a count for each worker type that you can drill into and view additional
details on.
Related Information
Tasks
Steps: Create Matrix Reports on page 112

Example: Composite Reports for Income Statements

Example: Create an Income Statement Using a Composite Report
These examples illustrate how to set up a composite report and common composite report features.

Context
You want to create an income statement that compares the actuals and plan data, and drill down on the
data by ledger account and region. You also want to set up the income statement so that you can quickly
interpret the variance between the actuals and plan data.

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Steps
1. Create an actuals matrix subreport.
See Example: Create a Matrix Report for Actuals Data on page 152.
2. Create a plan matrix subreport.
See Example: Create a Matrix Report for Plan Data on page 154.
3. Create an income statement.
See Example: Create an Income Statement Composite Report on page 156.
4. Set up a column outline structure with a repeating column group.
See Example: Set Up a Column Outline Structure on page 157.
5. Set up a row outline structure.
See Example: Set Up a Row Outline Structure on page 158.
6. Set up analytic indicators to help identify negative variance data.
See Example: Set Up Analytic Indicators on page 159.
7. Set up a prompt set to connect individual subreport prompts.
See Example: Set Up a Prompt Set on page 160.
8. Set up custom column headings.
See Example: Set Up Column Headings on page 161.

Result
Workday displays an income statement that compares the actuals and plan data, including the variance
for regions and ledger accounts. You can drill down on the columns and rows to view more data. Workday
also displays custom column headings and formatting.
Related Information
Concepts
Concept: Composite Reports on page 144

Example: Create a Matrix Report for Actuals Data

Context
You want to create a matrix report that filters for actuals data that you can view on an income statement.

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Steps
1. Access the Create Custom Report task.
2. Enter [Subreport] Actuals in the Report Name field.

3. Select:
Option Description
Report Type Matrix
Data Source Journal Lines for Financial Reporting
4. Click OK.
5. In the Row Grouping section on the Matrix tab, select:

Group by Field Sort Rows

Cost Center Alphabetical - Ascending
Fiscal Period - Actual Alphabetical - Ascending
Ledger Account Alphabetical - Ascending
Region Alphabetical - Ascending
6. In the Define the Field(s) to Summarize section, delete the values on the populated row.
7. Select:

Summarization Type Summarization Field Format

Sum Ledger/Budget Debit minus #,##0.00;(#,##0.00)
Credit
8. In the Filter on Instances section on the Filter tab, select:

And/Or Field Operator Comparison Type Comparison

Value
And Accounting Date greater than or Value from Time Series Start
equal to another field Date
And Accounting Date less than or equal Value from Time Series End
to another field Date
9. On the Prompts tab, select the Populate Undefined Prompt Defaults check box.
10.On the Prompt Defaults grid, select:

Field Default Type Default Value Do Not Prompt at

Runtime
Company Specify default value 500.1 Global Modern
Services, Inc. (USA)
Amount Type Specify default value Activity Select the check box.
Ledger Specify default value Actuals Select the check box.
Period Specify default value 2013 - Mar
Time Period Specify default value Current Period YTD
Time Series End Date Determine default value Fiscal Time Period End Select the check box.
at runtime Date
Time Series Start Date Determine default value Fiscal Time Period Start Select the check box.
at runtime Date
11.For each remaining row, select the Do Not Prompt at Runtime check box.
12.On the Share tab, click Share with all authorized users.

13.Click OK.

Result
When you run the matrix report, Workday displays the actuals data by the row groupings.
Related Information
Concepts
Concept: Matrix Reports on page 120
Tasks
Lookup Date Rollup
Steps: Create Matrix Reports on page 112
Reference
Reference: Calculated Field Functions

Example: Create a Matrix Report for Plan Data

Context
You want to create a matrix report that filters for plan data that you can view on an income statement.

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Steps
1. Access the Create Custom Report task.
2. Enter [Subreport] Plan in the Report Name field.
3. Select:
Option Description
Report Type Matrix
Data Source Plan Lines for Financial Reporting
4. Click OK.
5. In the Row Grouping section on the Matrix tab, select:

Group by Field Sort Rows

Cost Center Alphabetical - Ascending
Fiscal Period - Budget Alphabetical - Ascending
Ledger Account Alphabetical - Ascending
Region Alphabetical - Ascending
6. In the Define the Field(s) to Summarize section, delete the values on the populated row.
7. Select:

Summarization Type Summarization Field Format

Sum Ledger/Budget Debit minus #,##0.00;(#,##0.00)
Credit

8. In the Filter on Instances section on the Filter tab, select:

And/Or Field Operator Comparison Type Comparison

Value
And Plan Period Start greater than or Value from Time Series Start
Date equal to another field Date
And Plan Period End less than or equal Value from Time Series End
Date to another field Date
And Cost Center any in the Value specified in 20.0 Finance
Hierarchies selection list this filter
30.0 Human
Resources
40.0 Information
Technology
50.0 Operations
60.0 Sales &
Marketing

9. On the Prompts tab, select the Populate Undefined Prompt Defaults check box.
10.On the Prompt Defaults grid, select:

Field Default Type Default Value Do Not Prompt at

Runtime
Company Specify default value 500.1 Global Modern
Services, Inc. (USA)
Plan Structure Specify default value Budget Select the check box.
Amount Type Specify default value Activity Select the check box.
Period Specify default value 2013 - Mar
Time Period Specify default value Current Period YTD
Time Series End Date Determine default value Fiscal Time Period End Select the check box.
at runtime Date
Time Series Start Date Determine default value Fiscal Time Period Start Select the check box.
at runtime Date
Ledger Account/ Specify default value Corporate: Income Select the check box.
Summary Statement
11.For each remaining row, select the Do Not Prompt at Runtime check box.
12.On the Share tab, click Share with all authorized users.
13.Click OK.

Result
When you run the matrix report, Workday displays the plan data by the row groupings.
Related Information
Concepts
Concept: Matrix Reports on page 120
Tasks
Steps: Create Matrix Reports on page 112

Example: Create an Income Statement Composite Report

Context
You want to create an income statement that compares the actuals and plan data in Workday by
referencing data from your matrix subreports. You want to interpret the variance by creating a column that
calculates the difference between the data from the subreports.

Prerequisites
• Create actuals and plan subreports.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Steps
1. Access the Create Custom Report task.
2. Enter Income Statement in the Report Name field.
3. Select Composite from the Report Type prompt.
4. On the Business Object Enabled for Filtering and Grouping grid, select Ledger Account from the
Business Object prompt.
5. Click OK.
6. From the menu of column C1, select Define > Control Field.
7. Enter Ledger Account in the Column Name field.
8. Click OK.
9. From the menu of column C2, select Define > Data.
10.Enter Actuals in the Column Name field.
11.Select [Subreport] Actuals from the Sub Report Name prompt.
12.Click OK.
13.From the menu of column C3, select Define > Data.
14.Enter Plan in the Column Name field.
15.Select [Subreport] Plan from the Sub Report Name prompt.
16.Click OK.
17.From the menu of column C4, select Define > Calculation.
18.Enter Variance in the Column Name field.
19.Select:
Option Description
Calculation Type Difference
Column A C3 (Plan)
Column B C2 (Actuals)
20.Click OK.
21.Click Run.

Result
Workday displays an income statement that includes the actuals and plan data, including the variance for
ledger accounts.

Related Information
Concepts
Concept: Composite Reports on page 144
Tasks
Steps: Create Composite Reports on page 128

Example: Set Up a Column Outline Structure

Context
You want to set up an income statement that enables you to drill into data by using a:
• Repeating column group that displays the data for each region.
• Drillable column outline structure so you can view data by region.

Prerequisites
• Create actuals and plan subreports.
• Create an income statement composite report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Steps
1. Access the Edit Custom Report task.
2. Select Income Statement from the Report Name prompt.
3. Click OK.
4. Select columns C2 to C4.
5. From the menu of column C4, select Repeating Column Group.
6. Enter Repeat by Region in the Repeating Column Group Name field.
7. Select Region from the Repeating Field prompt.
8. From the Outline Structure prompt, select Create > Create Outline Structure.
9. Enter Region Outline Structure in the Name field.
10.In the Primary Hierarchy section, select:
Option Description
Business Object Region
Outline Approach Use Hierarchy
Hierarchy Type Regional Hierarchy
Top Level Node Global Modern Services Regions
Last Level Leaf Node
11.Click OK.
12.Confirm that the populated value in the Outline Structure prompt is the outline structure you created.
13.Click OK.
14.Click Run.

Result
When you run the report, Workday displays a drillable column where you can view actuals, plan, and
variance data by region.
Related Information
Tasks
Create Outline Structures for Composite Reports on page 142

Example: Set Up a Row Outline Structure

Context
You want to set up an income statement with a row outline structure that can expand and collapse to view
groupings of ledger accounts.

Steps
1. Access the Edit Custom Report task.
2. Select Income Statement from the Report Name prompt.
3. Click OK.
4. From the menu of column C1, select Edit.
5. From the Outline Structure prompt, select Ledger Account Outline.
6. Select the Default Outline Structure check box.
7. Click OK.
8. Access the settings menu on your report.
9. On the Business Object Enabled for Filtering and Grouping grid, select Ledger Account Outline
from the Hierarchy Structure prompt for the Ledger Account Business Object.
10.Click OK.
11.From the menu of row R1, select Define > Lookup Data.
12.Enter Row Outline in the Row Name field.
13.In the Filter Criteria section, select:

And/Or Business Object Operator Value

And Ledger Account in the hierarchy Corporate: All Accounts
14.Click OK.
15.Click Run.

Result
Workday creates a report with a row that you can expand to view actuals, plan, and variance data by
specific groups of ledger accounts.

Related Information
Tasks
Create Outline Structures for Composite Reports on page 142

Example: Set Up Analytic Indicators

Context
You want to interpret the variance between the actuals and plan data on your income statement. You
want to set up analytic indicators to use colors and shapes so you can quickly identify zero, positive, and
negative numbers on the variance column.

Prerequisites
• Create actuals and plan subreports.
• Create an income statement using a composite report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Steps
1. Access the Edit Custom Report task.
2. Select Income Statement.
3. Click OK.
4. From the menu of column C4, select Edit.
5. From the Options prompt, select Create > Create Analytic Indicator for Report.
6. Enter Negative Analytical Indicator in the Display Option Name field.
7. Select:
Option Description
Visualization Type Status - Green/Yellow/Red
Default Visualization No visualization
8. On the Display Conditions grid, select:

Column Reference Condition Visualization

C4 Variance greater than Red diamond
C4 Variance equal to Yellow triangle
C4 Variance less than Green circle
9. Click OK.
10.Confirm that the analytic indicator option is correct and click OK.
11.Click Run.

Result
When the report runs, Workday displays analytic indicators on the composite report based on the variance.
When the variance is:
• Positive, Workday displays a red diamond.
• Zero, Workday displays a yellow triangle.
• Negative, Workday displays a green circle.

Related Information
Concepts
Concept: Formatting Styles on page 145

Example: Set Up a Prompt Set

Context
You want to set up a prompt set that doesn't notify you more than once for the company and period
prompts on the subreport. You also want to specify the prompt order and populated prompt values so you
can run the report more easily.

Steps
1. Access the Edit Custom Report task.
2. Select Income Statement from the Report Name prompt.
3. Click OK.
4. Access the settings menu on your report.
5. On the General tab, select Financial Composite Reports for Company from the Prompt Set prompt.
6. Click OK.
7. From the menu of column C2, select Edit.
8. On the Map Sub Report Prompts grid, select:

Prompt Field Value Type Value

Company Use Value From Prompt Set Company
Period Use Value From Prompt Set Period
Time Period Specify Value Current Period YTD
9. Click OK.
10.From the menu of column C3, select Edit.
11.On the Map Sub Report Prompts grid, select:

Prompt Field Value Type Value

Company Use Value From Prompt Set Company
Period Use Value From Prompt Set Period
Time Period Specify Value Current Period YTD
12.Click OK.
13.Access the settings menu on your report.
14.On the Prompts tab, select the Populate Undefined Prompt Defaults check box.

15.On the Prompt Defaults grid, select:

Field Default Type Default Value Do Not Prompt at

Runtime
Company for Financial Specify default value 500.1 Global Modern
Reports Services, Inc. (USA)
Period Specify default value 2013 - Dec
Plan Structure No default value Select the check box.
Translation Currency No default value Select the check box.
Account Translation No default value Select the check box.
Rule Set
16.Click OK.
17.Click Run.

Result
When you run the composite report, Workday displays the Company and Period prompts and maps the
values to the prompt on each subreport.
Related Information
Concepts
Concept: Prompt Sets for Composite Reports on page 145

Example: Set Up Column Headings

Context
You want to create an income statement with variables on the column headings so that you can quickly
scan and interpret the data on the report.

Steps
1. Access the Edit Custom Report task.
2. Select Income Statement from the Report Name prompt.
3. Click OK.
4. Access the settings menu on your report.
5. On the Column Headings tab, select the Generate Column Headings check box.
6. On the Column Heading Cells grid, click the Popup Window icon for Actuals in the Cell Name
column.
7. From the related actions menu of the View Column Header Cell report, select Column Header Cell >
Edit.
8. Enter Actuals YTD - [V1] in the Text Expression field.
9. Select Year from the [V1] Variable 1 prompt.

10.Click OK.
11.Click Done.
12.Return to your composite report.
13.On the Column Heading Cells grid, click the Popup Window icon for Plan in the Cell Name column to
access the View Column Header Cell report.
14.From the related actions menu of the View Column Header Cell report, select Column Header Cell >
Edit.
15.Enter Plan YTD - [V1] in the Text Expression field.
16.Select Year on the [V1] Variable 1 prompt.
17.Click OK.
18.Click Done.
19.Return to your composite report.
20.On the Column Headings tab, click OK.
21.Click Run.

Result
Workday updates the column headings with the year of the actuals and plan data.
Related Information
Tasks
Set Up Additional Options for Composite Reports on page 137

Trending Reports

Steps: Create Trending Reports

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can create a trending custom report to analyze trends in financial and worker data, such as headcount
and attrition. You can also use 1 or more trending reports as subreports in composite reporting.

Steps
1. Create Custom Reports on page 29.
Create a custom trending report.
2. Set Up Trending Reports on page 163.
3. Set Up Drill Down for Custom Reports on page 32.
4. Set Up Filter Options for Custom Reports on page 36.
5. Set Up Prompt Options for Custom Reports on page 38.
6. Set Up Output Options for Custom Reports on page 39.
7. Set Up Share Options for Custom Reports on page 42.
8. Set Up Advanced Options for Custom Reports on page 43.

Next Steps
Test the report to ensure Workday displays the data correctly.
When you test a report, Workday displays the first 10 results. When the report includes a:
• Filter, Workday applies the filter to all instances of the primary business object and displays the first 10
results.
• Subfilter, Workday applies the subfilter to the 10 filtered instances and displays the results.
Related Information
Concepts
Concept: Trended Workers Report Data Source on page 175
Concept: Trending Reports on page 168
Tasks
Steps: Set Up Tenants for Trended Worker Reporting on page 171
Set Up the Trended Workers Report Data Source on page 172

Set Up Trending Reports

Prerequisites
• Create a custom trending report.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can configure the basic options for a trending report on the Trending tab, including:
• Fields to display and summarize in your report.
• Time period for trended data.
You can use trending reports as subreports in composite reporting unless the trending report includes text-
based count distinct summarization fields.

Steps
1. Access the Edit Custom Report task.
2. As you complete the Define the Time Period section on the Trending tab, consider:
Option Description
Time Field Select a date or time field from the report data
source (RDS) that forms the foundation of the
trending report.
Example: For reports that use the Trended
Workers RDS, select Record Date as the time
field.

Group by Time Period Field Select the initial field for summarizing data into
the rows, which can be any date field.
You can also select Create Time Period for
Report to enter a time period and apply a
calendar- or fiscal-based format, such as Year-
Quarter.

Option Description
Your format must match the format of the
Trending Period. Example: When you configure
the Trending Period for a fiscal period, the
Group by Time Period Field must also be a
fiscal period.

Label Override Enter a value to override the name of the Group

by Time Period Field prompt that displays in the
report header.
Display Time Period Fields as Select an option to change the orientation of the
report by making the time period fields display as
either the columns or the rows.
If you select:
• Columns, add at least 1 Group by Field value
in the Row Grouping grid.
• Rows, you can add up to 2 Group by Field
values in the Column Grouping (Optional)
grid.

3. As you complete the Column Grouping (Optional) or the Row Grouping section, consider:
Option Description
Sort Columns/Rows Select an option so that values sort in ascending
or descending:
• Alphabetical order based on the Group by
Field value.
• Order based on the column or row total.
Sorting isn't case-sensitive.
When enabled, Workday uses the logical sort
order for the field specified in the Group by Field
value.
The Other column or row and the Total column
or row always display as the right-most column or
row in the report results.

Indexed Workday selects the check box when you select:

• An indexed data source.
• A Group by Field indexed for grouping.
If the Indexed check box is clear for a row, your
report might run slowly. Consider replacing the
Group by Field with a field indexed for grouping
so that your report can run faster.
Maximum Number of Columns/Rows Enter a value to specify the maximum number
of column or row results. When the number of
columns or rows exceeds the limit, Workday
displays an Other column or row that summarizes
the remaining values.
Workday displays more than 1 Other when:

Option Description
a. You select the Sum Remaining Values check
box on the Output tab.
b. The data exceeds the number of Top n
Values that you specify.

4. In the Define the Field(s) to Summarize grid, specify how Workday should aggregate the data.
As you complete the grid, consider:
Option Description
Summarization Type Specify the aggregation method used for the field.
The results of the aggregation method display
in the report cells or chart element, such as a
column or donut segment.
Select:
• Calculation to create a custom calculation
based on an arithmetic expression or to look
up a prior value.
• Count Distinct to drill into and view the distinct
number of instances based on a field or row in
your report results.

Summarization Field This field is inactive when the Summarization

Type is Count.
Select a currency, instance, numeric, or text field
for 1 of these Summarization Type options:
• Average
• Calculation
• Count Distinct
• Maximum
• Minimum
• Percentile
• Sum
Workday indexes report fields on Prism RDSs, but
might not index all fields on standard RDSs. To
select text fields for count distinct on a standard
RDS, clear the Optimized for Performance
check box on the Advanced tab.
For a Calculation Summarization Type, select
Create > Create Summarization Calculation
for Report or Create > Create System-Wide
Summarization Calculation to:

Option Description
• Create a summary calculation based on an
arithmetic expression.
• Look up a prior value based on:
• Average x time periods.
• Prior rollup period.
• Prior time period.
• Sum x time periods.
Note: To create tenant-wide summarization
calculations, configure the System-Wide
Summarization Calculation Management domain
in the System functional area.
You can create fields calculated from values in
report-specific or tenant-wide calculated fields.
For faster report performance, limit the number of
calculated fields you include in the report.

Format The format applies to:

Options Specify options that control how the field data

Option Description
• Show Currency Symbol: Workday displays
Invalid on fields that aggregate values in
different currencies.
• Use as Target Line: Creates 1 or more target
lines for each data group based on numeric or
currency fields. You can configure target lines
on the Output tab.
You can also select the Create prompt to create
these custom display options:
• Create Analytic Indicator for Report, which
creates a report-specific analytic indicator. To
create an analytic indicator for use in other
reports, access the Create Analytic Indicator
task.
• Create Detail Data Override. Workday
generates a detail data override for your
summarization field when your report uses
the Trended Workers RDS. You can enter a
unique drill-down layout for the field. The detail
data that you specify overrides the selections
on the Drill Down tab. You can select these
display options for the columns:
• Display format.
• Drill down window columns displayed.
• Field label overrides.
• The sort order.
When you complete the Create Detail Data
Override task, you can select Translate
from the related actions menu of the Detail
Data Override. The Translate Detail Data
Override task enables you to specify an
override to translate and a language for
translation.
You can also control which fields to sort on
and the sort direction to use.
• Create Percentile for Report, which enables
you to create custom percentiles up to 2
decimal places to use in your report. Workday
uses an approximate value for currency and
numeric fields in the percentile (PCTL).
If you configure your trending report to include
a bar or column chart, you can create 1 or more
target lines. To use a field as a target line, select
the Use as Target Line option. For multiple target
lines, you must include at least 1 currency or
numeric field to summarize and 1 currency or
numeric field to use as a target line.

Indexed Workday selects the check box based on the

indexed RDS, indexed data source filter, and the

Option Description
indexed field you select. The check box indicates
if your report has the potential to run faster.

Related Information
Concepts
Concept: Reports as a Service (RaaS) on page 211
Concept: Report-Specific Calculated Fields
Reference
Reference: Field Options on page 64

Concept: Trending Reports

Trending reports are similar to matrix reports because you can aggregate, group, and interactively drill
across dimensions of your data. Trending reports, however, require you to configure a time period as either
the column or row grouping. The time period determines what data Workday includes in the report.
Workday enables you to report on trends in workforce data, such as compensation, headcount, and span
of control so you can:
• Analyze important trends in your workforce directly in Workday without needing a third-party analytical
tool.
• Compare data to discern patterns and trends over time.
• Create detail data overrides for your summarization fields.
• Drill and take action on your data.
You can use 1 or more trending reports in composite reporting as subreports unless the trending report
includes text-based count distinct summarization fields.
Related Information
Tasks
Steps: Create Trending Reports on page 162
Steps: Set Up Tenants for Trended Worker Reporting on page 171
Reference
Reference: Reporting Limits
The Next Level: Other Report Types and Analytic Indicators

Setup Considerations: Trended Workers Report Data Source

You can use this topic to help make decisions when planning your configuration and use of the Trended
Workers report data source (RDS). It explains:
• Why to set it up.
• How it fits into the rest of Workday.
• Downstream impacts and cross-product interactions.
• Security requirements and business process configurations.
• Questions and limitations to consider before implementation.
Refer to detailed task instructions for full configuration details.

What It Is
The Trended Workers RDS is an indexed, Workday-delivered RDS that captures workforce activity and
headcount data. You can compare data to discern patterns and view trends that occur over time in your
organization.

Business Benefits
Creating reports in Workday with the Trended Workers RDS enables you to:
• Eliminate the extra effort of using multiple platforms to manipulate and analyze worker data.
• Keep worker data more secure by reducing the need to export it to outside applications.
• Make better-informed headcount decisions based on workforce trends over time.
• Quickly create summary dashboards that display important trends in your workforce.

Use Cases
You can use the RDS to create custom dashboards and reports or use Workday-delivered standard reports
to view staffing events in your organization. When you need to:
• Gain insights into the terminations across your organization, run the Terminations by Type and
Quarter standard report.
• Report on the compensation, headcount, and turnover rate for each quarter, create a report that
displays the data in a chart or table for each organization.
• View the potential of a worker, use the Performance and Potential workforce composition dashboard
so that supervisors can quickly view the data on their landing page.

Questions to Consider

Questions Considerations
How far back do you need to track data? Consider capturing the worker data that you need
so that Workday doesn't process unnecessary
information. Example: You can start collecting:
• Data from the date your company started using
your Workday production tenant, if the date is
fewer than 36 periods.
• Only the data you need by limiting the time
periods.
• Up to 36 periods of production tenant data.

How often does Workday collect, delete, or update Workday:

your worker data?
• Collects the current period of data plus 36
periods.
• Updates the Trended Workers RDS weekly
for nonproduction tenants (Implementation and
Sandbox), and either nightly or every Monday
for production tenants depending on your
retroactive period selection.
• Purges data older than 36 periods from the
RDS.

Recommendations
For best report performance, use only indexed calculated fields, indexed report fields, and built-in prompts
instead of defining filters on the report.
Enabling trended worker data in your tenant can result in processing and storing large amounts of data.
When managing your data, consider:
• Running the Create Worker Trending Data task to synchronize data that you created more than 6
periods ago. Run this task during nonpeak hours when collecting or updating your data. Doing so
conserves processing resources for day-to-day activities or other resource demands in your tenant.

• Running the Fix Worker Trending Data task to fix corrupted indexed data and resynchronize the RDS
with the reports in your tenant.
• Running the Update Worker Trending Data task to synchronize data that you created fewer than
6 periods ago. Run this task during nonpeak hours when collecting or updating your data. Doing so
conserves processing resources for day-to-day activities or other resource demands in your tenant.
• Selecting a date that is less than a year ago when you debug or troubleshoot for performance. Doing so
can help you find performance impacts much quicker than parsing through unnecessary data.

Requirements
No impact.

Limitations
• Because Workday processes and stores large volumes of data, Workday purges data that is older than
36 periods from the RDS.
• You can't use trending reports with text-based count distinct summarization fields as subreports in
composite reporting.

Tenant Setup
You can enable trended worker data by accessing the Edit Tenant Setup – Reporting and Analytics task
and selecting the check box in the Worker Trending section. You can view the status of this change by
accessing the Status tab on the Maintain Trended Workers task.

Security

Domains Considerations
Custom Report Administration in the System Enables you to perform administrative tasks on
functional area. reports and tasks.
Set Up: Tenant Setup - Reporting and Analytics in Enables you to configure trended worker data
the System functional area. in your tenant and provides access to configure
conditions for using reporting and analytics.
Trended Worker Data in the Staffing functional Provides access to all trended worker data.
area.

Business Processes
No impact.

Reporting

Reports Considerations
Maintain Trended Workers On the Status tab, Workday displays the recent run
history for trended jobs and the status when you
enable worker trending data in your tenant.
Worker Trending Audit View all activity and snapshot data Workday
captures for each period. You can assess the
information and adjust the information you capture
as your needs change.

Integrations
You can enable custom advanced reports that use the Trended Workers RDS as web services and use
them in integrations. You can import employee hire data into Workday using an Enterprise Interface Builder
(EIB) integration.

Connections and Touchpoints

Workday offers a Touchpoints Kit with resources to help you understand configuration relationships in your
tenant. Learn more about the Workday Touchpoints Kit on Workday Community.
Related Information
Concepts
Concept: Trended Workers Report Data Source on page 175
Concept: Advanced Reports on page 111
Concept: Matrix Reports on page 120
Concept: Trending Reports on page 168
Reference
Reference: Reporting Limits
Reference: Reporting on the Trended Workers Report Data Source on page 176
The Next Level: Trended Worker
The Next Level: Custom Worker Trending FAQs
The Next Level: Move up the Workday Maturity Curve: Considerations in Defining an Analytics Strategy
The Next Level: Workforce Composition Dashboards
The Next Level: Workforce Analytics: Trended Worker/Custom Worker Trending - FAQ
Workday Community: Custom Worker Trending: FAQs
Preconfigured Content: HCM Delivered Configurations

Steps: Set Up Tenants for Trended Worker Reporting

Prerequisites
Security: Set Up: Tenant Setup - Reporting and Analytics domain in the System functional area.

Context
You can enable your tenant for worker trending data to report on calculated metrics, headcount data, and
workforce activity.

Steps
1. Access the Edit Tenant Setup – Reporting and Analytics task.
2. Select the Enable Worker Trending check box in the Worker Trending section.
To view the status of this change, access the Status tab on the Maintain Trended Workers task.
3. Access the Domain Security Policies for Functional Area report to edit permissions for the Trended
Worker Data domain in the Staffing functional area.
See Edit Domain Security Policies.
4. Set Up the Trended Workers Report Data Source on page 172.
5. Access the Create Worker Trending Data task to create trending data and run the task whenever you
make changes to configurations on the Maintain Trended Workers task.
Workday recommends you run the task during nonpeak hours to minimize the impact on performance
and conserve processing resources for day-to-day activities in your tenant.

Related Information
Concepts
Concept: Trending Reports on page 168
Concept: Custom Fields in Custom Reports and Calculated Fields
Tasks
Steps: Create Trending Reports on page 162
Reference
Reference: Edit Tenant Setup - Reporting and Analytics

Set Up the Trended Workers Report Data Source

Prerequisites
• Enable worker trending in your tenant.
• Security: Set Up: Tenant Setup - Reporting and Analytics domain in the System functional area.

Context
You can update configuration settings for your trended data when using the Trended Workers report data
source, including:
• Adding up to 5 boolean, 5 numeric, or 5 single instance report fields from the Position, Worker, and
Worker Business Process business objects.
• Adding Workday-delivered report fields and creating calculated fields.
• Mapping up to 10 organization types to trended worker report fields.
• Securing report fields that you add to additional security domains.
• Selecting if numeric report fields you add are semiadditive measures, which don’t sum over multiple
periods.
• Viewing report field usages in reports and worker trending job processing statuses.

Steps
1. Access the Maintain Trended Workers task.
2. (Optional) On the Status tab, view the run history for recent trended jobs and the statuses for report
fields enabled for worker trending data in your tenant.
3. As you complete the Configuration tab, consider:
Option Description
Trending Start Date Select the earliest date for Workday to capture
worker trending data. Example: You can collect:
• Data from the date your company started using
your Workday production tenant, if the date is
fewer than 36 periods.
• Only the data you need by limiting the time
periods.
• Up to 36 periods of production tenant data.

Number of Retroactive Periods Enter the number of historical periods calculated

by the incremental update process.
You can enter:
• 1, 2, or 3 to recalculate the data nightly
for production tenants and weekly for
nonproduction tenants.

Option Description
• 4, 5, or 6 to recalculate the data weekly on
each Monday for production tenants and
weekly for nonproduction tenants.

Trending Period Select a calendar month or fiscal period.

Your Trending Period selection must match
your Group by Time Period Field selection.
Example: If your Trending Period is calendar-
based, then the Group by Time Period Field
must be calendar-based.
You can use calendar month and fiscal period
simultaneously if the last day of the fiscal period
in the fiscal schedule is always the last day of a
calendar month.
If you trend by fiscal period, you can't use
Workday-delivered reports because the reports
trend by calendar month. Instead, copy the report
and reconfigure it to use fiscal periods.

Fiscal Schedule Select a fiscal schedule, as defined on the Create

Fiscal Schedule task.
Include Terminations on Period End Date Select to include workers terminated on the last
day of the period in the ending headcount. When
selected, Workday counts worker termination
events 1 day after the termination effective date.
If you change this option, regenerate your
trending data using the Create Worker Trending
Data task to apply the new ending headcount
calculation.

Use International Assignments as Primary Select to use the worker's primary position for
Position for Trended Worker worker trending data. Clear the check box to
capture host position data.

You can access the Update Worker Trending Data task to manually synchronize your data as a
background process to:
• Capture added retroactive changes for up to 6 periods.
• Recompute for the most recent event.
You must have access to the Custom Report Administration domain in the System functional area
to access the task. Workday runs this task weekly for nonproduction tenants (Implementation and
Sandbox), and either nightly or every Monday for production tenants depending on your retroactive
period selection. You can view the Recent Run History on the Status tab on the Maintain Trended
Workers task.
4. As you complete the Organizations tab, consider:
Option Description
Report Field Select the single instance organization report field
to map to the Organization Type.
Organization Type Select up to 10 organization types to report on for
trended worker data and assign multiple types to

Option Description
workers. Workday selects 1 if you don't specify a
top-level organization.
Top Level Organization Specify the top-level organization that maps to the
organization type you select.
5. As you complete the Additional Fields tab, consider:
Option Description
Source Select the:
• Position business object to capture position
data.
• Worker business object to capture snapshot
data.
• Worker Business Process business object to
capture activity data.

Field Type Configure up to 5 report fields for each of these

report field types:
• Boolean
• Numeric
• Single Instance

Field Select a report field associated with the business

object of the Source or access the Create
Calculated Field task.
A field is suitable if Workday displays the same
result each time the field executes. The criteria for
when a field becomes unsuitable includes if it:
• Changes the result based on the security
configuration of the report runner.
• Derives instances, such as a lookup date
rollup calculated field.
• Retrieves an image.
• Runs a query for data.
• Uses prompts.
Note: Access the Field Suitability for Business
Objects report to view the indexing suitability for
fields on a business object.
Consider the impact on performance when using
calculated fields.

Domain Select the security domain to secure to the report

fields.
Semi Additive Measure Select if a numeric report field is a semiadditive
measure, which doesn’t sum over multiple
periods.
Field Usage Click to view usages for a report field. You can't
remove a trended worker report field until you
remove the usages in reports.

Related Information
Concepts
Concept: Custom Fields in Custom Reports and Calculated Fields
Reference
The Next Level: Overview of Primary Position Designation Impact

Concept: Trended Workers Report Data Source

The Trended Workers report data source (RDS) is an indexed, Workday-delivered RDS that captures
headcount data and workforce activity. You can create custom dashboards and reports or use Workday-
delivered standard reports to view staffing events in your organization. You can't create nBox or search
reports with the RDS.
The RDS reduces the effort required to gain insights into your data by enabling you to gather accurate and
current workforce data more efficiently. You don't need to export your data to Microsoft Excel or external
applications to perform complex data analysis. This keeps your data more secure.
Workday updates the RDS weekly for nonproduction tenants (Implementation and Sandbox), and either
nightly or every Monday for production tenants depending on your retroactive period selection. Workday
collects up to 36 periods of data and automatically purges data older than 36 periods from the RDS.

Activity Data, Snapshot Data, and Calculated Metrics

The RDS contains report fields that collect worker data over time and includes activity data, snapshot data,
and calculated metrics. You can distinguish between activity and snapshot data by using the Record Type
field in reports.
When processing events that occur on the last day of the period, Workday processes all activity data first,
then captures the snapshot data. Workday also snapshots the results at the end of the period and takes
into account retroactive changes up to 6 periods, which could impact your data.
Activity data includes these types of events, captured based on the Effective Date of the event:
• Addition or deletion of additional jobs.
• Hires.
• International assignments.
• Organization changes.
• Promotions.
• Staffing changes.
• Terminations.
• Transfers.
Workday tracks the Effective Date of the event as the Record Date.
Snapshot data includes worker data captured as of the last second of the last day of each period, such as:
• Biographical data.
• Compensation data.
• Headcount.
• Worker data.
Workday captures snapshot data on the first day of a new period but sets the Record Date as the last day
of the period. Example: Workday captures snapshot data on 2018-09-01T12:01, but the Record Date is
2018-09-30.
Calculated metrics are a combination of activity and snapshot data. You can:
• Aggregate calculated metrics as drillable report fields in your trending report.
• Average, sum, or build additional calculations to determine rolling averages, spans of control, or
turnovers.

Related Information
Concepts
Concept: Advanced Reports on page 111
Concept: Matrix Reports on page 120
Concept: Trending Reports on page 168
Reference
The Next Level: Other Report Types and Analytic Indicators

Reference: Reporting on the Trended Workers Report Data Source

Workday-Delivered Standard Reports

You can use these Workday-delivered standard reports that use the Trended Workers report data source
(RDS) to gain insight into staffing events in your organization:

Standard Reports Description

Promotion Rate View promotion rates.
Hires and Terminations by Quarter View hires and terminations for each quarter and
compare the data in a chart or table.
Quarterly Turnover Rates View involuntary and voluntary turnover rates for
each quarter.
Headcount and FTE by Month View the total headcount and number of full-time
employees for each month and compare the data in
a chart or table.
Employee Movement - Transfer Sub Report View where transfers occur within your supervisory
organization.

Maintaining the Trended Workers RDS

You can use these reports and tasks to create or manage trended data in your tenant:

Reports or Tasks Considerations

Create Worker Trending Data You can create trended data and run the
task to recreate all 36 periods of data in your
tenant. Because Workday processes and
stores large volumes of data, consider the
impacts on performance when using this task.
Workday recommends you run the task during
nonpeak hours whenever you make changes to
configurations on the Maintain Trended Workers
task.
Update Worker Trending Data You can manually synchronize your data as a
background process to:
• Capture added retroactive changes for up to 6
periods.
• Recompute for the most recent event.
Workday runs this task weekly for nonproduction
tenants (Implementation and Sandbox), and either
nightly or every Monday for production tenants
depending on your retroactive period selection. You

Reports or Tasks Considerations

can view the Recent Run History on the Status
tab on the Maintain Trended Workers task.
If you manually synchronize your data as a
background process to recompute for the most
recent event, Workday recommends you run the
task during nonpeak hours.

Maintain Trended Workers You can update configuration settings for your
trended data.
On the Status tab, Workday displays the recent
run history for trended jobs. You can drill down on
values on the Additional Fields Executed column
to view indexing times for report fields added to
your Trended Workers RDS.

Fix Worker Trending Data You can fix corrupted indexed data and
resynchronize the RDS with the reports in your
tenant.
Workday runs this task periodically to reload your
data.

Purge Worker Trending Data You can delete or disable the ongoing collection
of all worker trended data. Run this task before
changing the settings on the Configuration tab on
the Maintain Trended Workers task.
Example: To switch the trending period from
calendar month to fiscal period:
1. Purge the data using the Purge Worker
Trending Data task.
2. Change the configuration settings using the
Maintain Trended Workers task.
3. Create the data again using the Create Worker
Trending Data task.

Worker Trending Audit You can view all activity and snapshot data
captured for each period. You can assess the
information and troubleshoot any issues.

Workforce Composition Dashboards

These workforce composition dashboards enable you to make well-informed decisions more efficiently and
gain insight across your organization:

Workforce Composition Dashboards Description

Distribution Trends and Analysis View workforce distribution by key segments.
Diversity View gender and ethnicity composition.
Headcount Movement View hire, termination, and transfer movements.
Performance and Potential View employee performance data.
Structure Dynamics View span of control and organizational structure.

Related Information
Concepts
Concept: Trending Reports on page 168
Reference
Reference: Workforce Composition Dashboards
The Next Level: Workforce Composition Dashboards

Transposed Reports

Steps: Create Transposed Reports

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can create a transposed report where rows display as columns for side-by-side comparisons of data.

Steps
1. Create Custom Reports on page 29.
2. Set Up Rows for Transposed Reports on page 178.
3. Set Up Sort Options for Custom Reports on page 33.
4. Set Up Filter Options for Custom Reports on page 36.
5. Set Up Prompt Options for Custom Reports on page 38.
6. Set Up Output Options for Custom Reports on page 39.
7. Set Up Share Options for Custom Reports on page 42.
8. Set Up Advanced Options for Custom Reports on page 43.

Next Steps
Test the report to ensure Workday displays the data correctly.
When you test a report, Workday displays the first 10 results. When the report includes a:
• Filter, Workday applies the filter to all instances of the primary business object and displays the first 10
results.
• Subfilter, Workday applies the subfilter to the 10 filtered instances and displays the results.
Related Information
Concepts
Concept: Transposed Reports on page 180
Concept: Custom Reports on page 12
Concept: Business Objects, Data Sources, and Fields on page 13

Set Up Rows for Transposed Reports

Prerequisites
• Create a custom transposed report.

• Security: These domains in the System functional area:

• Custom Report Creation
• Manage: All Custom Reports

Context
You can configure column headings and fields to display as rows on transposed reports.

Steps
1. Access your transposed report from the Edit Custom Report task.
2. (Optional) As you complete the Column Heading section on the Rows tab, consider:
Option Description
Heading Line 1 - Field Select the field to use as the first line of the
column heading. Example: Succession Plan
Candidate.
Field Select the field to use as the column heading for
Heading Line 2. Example: Current Position.
Format Select a format if you selected a currency or
numeric Field.
Options Available options depend on your field type.
You can also select the Create prompt to create
these custom display options:
• Create Analytic Indicator, which enables you
to use the indicator in other reports throughout
your tenant.
• Create Analytic Indicator for Report, which
enables you to use the indicator only in the
current report.
• Create Percentile for Report, which enables
you to create custom percentiles up to 2
decimal places to use in your report. Workday
uses an approximate value for currency and
numeric fields in the percentile (PCTL).

Image Field Select an image to include. Example: Candidate

Photo.
3. As you complete the Rows grid, consider:
Option Description
Row Type Select Group to indicate that the row represents
a header between fields. You can expand and
collapse the subsequent rows for each group.
Label Override Enter a value to:
• Give your Group a label.
• Override the name of the Field selected for the
Row Type.

Left Justify All Fields Clear the check box to right-justify currency and
numeric fields.

Related Information
Concepts
Concept: Report-Specific Calculated Fields
Reference
Reference: Field Options on page 64

Concept: Transposed Reports

Transposed reports enable you to set up report rows as columns so you can:
• Display an image. Example: When comparing workers, you might want to display a profile picture.
• Display numeric fields as left justified, if needed.
• Group the rows within a column under collapsible headings.
• Perform side-by-side data comparisons.
You can transpose up to 100 rows of data to a columnar format. If the report returns more than 100 rows, a
More link at the top of the report enables you to view all data in a nontransposed format.
You can build transposed reports using either standard or indexed report data sources.
Related Information
Tasks
Compare Workers
Reference
The Next Level: Other Report Types and Analytic Indicators

Search Reports

Steps: Create Search Reports

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
Search reports enable you to interactively filter report results using facet filters and a search bar. You can
also select search results and perform mass actions on them. Example: Use the Workday-delivered Find
Workers search report to search for workers and add them to a talent pool.
Use an indexed data source to create search reports.
The Search Results tab isn't available when you create search reports using these Learning data
sources:
• Courses
• Learning Content
You can't:
• Export search reports as spreadsheets or PDFs, or use them to tag workers.
• Print reports that you run as a mass action from a search report using a business form layout.

Steps
1. Create Custom Reports on page 29.

2. On the Edit Custom Report task, set up Search Results options.

You can select these Options for certain types of fields:
Option Description
Attachment Field Includes links to the attachments in the report
results.
This option is only available for fields with a
related business object of Attachment.

Icon Field Displays the field as an icon in the report results.

This option is only available for fields with a
related business object of Icon.

Image Field Display the field as an image in the report results.

This option is only available for fields with a
related business object of Image.

Detail Result Field Display the field in an expandable section of each

report result. If the first field with Detail Result
Field selected is a multi-instance field, it also
displays when you collapse the results.
You can select this option for up to 6 fields per
search report.

3. (Optional) Set Up Sort Options for Custom Reports on page 33.

4. (Optional) Set Up Filter Options for Custom Reports on page 36.
5. (Optional) Set Up Prompt Options for Custom Reports on page 38.
6. (Optional) Set Up Output Options for Custom Reports on page 39.
7. (Optional) Set Up Share Options for Custom Reports on page 42.
8. (Optional) Set Up Advanced Options for Custom Reports on page 43.

Next Steps
Test the report to ensure Workday displays the data correctly.
When you test a report, Workday displays the first 10 results. When the report includes a:
• Filter, Workday applies the filter to all instances of the primary business object and displays the first 10
results.
• Subfilter, Workday applies the subfilter to the 10 filtered instances and displays the results.
Related Information
Concepts
Concept: Business Objects, Data Sources, and Fields on page 13
Concept: Custom Reports on page 12
Concept: Indexed Data Sources and Fields on page 15

Example: Export Workers Using a Search Report

This example illustrates how you can export more than 50 workers using a mass action on a search report.

Context
You want to view all current workers on an Excel spreadsheet so you can export the data and identify each
worker's full legal name, location, and position.

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Steps
1. Access the Create Custom Report task and enter:
Option Description
Report Name Export Template
Report Type Advanced
Data Source Workers for HCM Reporting
2. Click OK.
3. In the Columns tab, enter:

Business Object Field

Worker Full Legal Name
Worker Location
Worker Position
4. In the Filter tab, add a filter with these values:

Field Operator Comparison Type Comparison Value

Worker in the selection list Prompt the user for the Default Prompt
value
5. In the Prompts tab, click Populate Undefined Prompt Defaults.
6. On the Prompt Defaults section, specify:

Field Do Not Prompt at Runtime

Worker
Contingent Worker Type Select the check box.
Employee Type Select the check box.
Worker Types Select the check box.
7. Click OK.
8. Access the Find Workers report.
9. Select Standard Report > Copy from the related actions menu.
10.Click OK.
11.In the Advanced tab, add a row in the Mass Actions section.
12.Select Create Custom Mass Action from the Mass Action prompt and enter:
Option Description
Name Find Worker Export to Excel
Executes Report Export Template
13.Click OK.

14.On the Mass Actions section, specify:

Option Description
Mass Action Find Worker Export to Excel
Name Export Workers
Output to Excel / Output to PDF Output to Excel
15.Click OK and Run.
16.Select all workers and click Export Workers.

Result
Workday exports all workers to an Excel spreadsheet with the columns on the advanced report.
Related Information
Tasks
Set Up Advanced Options for Custom Reports on page 43

nBox Reports

Steps: Create nBox Reports

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can create an nBox report with an indexed data source that counts your data and displays the results
on a 2-dimensional matrix. Column and row groupings enable you to compare and visualize objects on the
matrix.

Steps
1. Create Custom Reports on page 29.
Create a custom nBox report.
2. Set Up Matrix Options for nBox Reports on page 184.
3. (Optional) Set Up Drill Down for Custom Reports on page 32.
4. (Optional) Set Up Filter Options for Custom Reports on page 36.
5. (Optional) Set Up Prompt Options for Custom Reports on page 38.
6. (Optional) Set Up Output Options for Custom Reports on page 39.
7. (Optional) Set Up Share Options for Custom Reports on page 42.
8. (Optional) Set Up Advanced Options for Custom Reports on page 43.
9. Select N Box Cell > Setup nBox Report from the related actions menu of the report definition.
Security: Custom Report Administration domain in the System functional area.
10.Select the field values that define each column and row.

Next Steps
Test the report to ensure Workday displays the data correctly.

When you test a report, Workday displays the first 10 results. When the report includes a:
• Filter, Workday applies the filter to all instances of the primary business object and displays the first 10
results.
• Subfilter, Workday applies the subfilter to the 10 filtered instances and displays the results.
Related Information
Concepts
Concept: Business Objects, Data Sources, and Fields on page 13
Concept: Custom Reports on page 12
Concept: Indexed Data Sources and Fields on page 15

Set Up Matrix Options for nBox Reports

Prerequisites
Security: These domains in the System functional area:
• Custom Report Management
• Manage: All Custom Reports

Context
You can use the Matrix tab to select the fields you want to group into columns and rows on your nBox
report.

Steps
1. Access the Edit Custom Report task.
2. As you complete the Row Grouping and Column Grouping grids on the Matrix tab, consider:
Option Description
Group by Field Select 1 of these field types:
• Boolean
• Date
• Single instance

Label Override Don’t use. Instead, access the Set Up nBox

Report task to configure the report columns and
Sort Rows/Sort Columns
rows.
Options
Maximum Number of Rows/Maximum Number
of Columns

3. As you complete the nBox Display section, consider:

Option Description
Image Field Select an image to display.
Example: You can select Candidate Photo to
display an image of a candidate.

Display Option Select whether Workday should display the image

only or include text with the image.

Next Steps
• Set up the rest of the tabs on the report definition.
• Access the Set Up nBox Report task to configure the columns and rows on the report.

Worklets and Dashboards

Steps: Set Up Custom Dashboards

Prerequisites
Enable or create the security domains you want to use to secure your dashboard.

Context
You can create a custom dashboard so that users can access related worklets in 1 place.
As you create the dashboard, you can:
• Enable users to add or remove worklets.
• Map a prompt set to the dashboard.
• Set up domain security access.
You can set up a Dashboard Run History report to analyze dashboard usage statistics. This report can
display up to 6 months of dashboard run history results.

Steps
1. Create Custom Dashboards on page 186.
2. Access the Enable Worklet for Dashboards task.
Select a worklet, then select the dashboard you created.
Security: Set Up: Tenant Setup - Worklets domain in the System functional area.
3. For custom reports you want to add to the dashboard as worklets, set up the Worklet Options section
on the Output tab of the report definition.
You must share the report with the security groups you want to access the dashboard before you can
add the worklet to the dashboard.
See Set Up Output Options for Custom Reports on page 39.
4. Configure Dashboard Content on page 187.
5. (Optional) Save Custom Prompt Values for Worklets on page 190.
6. (Optional) Access the Maintain Dashboards report.
Click Edit and access the Announcements tab to set up announcements for the dashboard. You can
also add a photo, image, or video URL to the announcement.
Security: Set Up: Tenant Setup - Worklets domain in the System functional area.
7. (Optional) To enable the Dashboard Run History report, access the Edit Tenant Setup - Reporting
and Analytics task and select the Enable Access to Dashboard Run History check box.
Workday begins capturing dashboard run history after you enable the feature and therefore might not
initially display any data on the Dashboard Run History report. The report also tracks dashboard tab
executions.
Related Information
Concepts
Concept: Dashboards

Reference
The Next Level: Delivered and Custom Dashboards
The Next Level: Elevate Users' Experience with Dashboards
The Next Level: Report Administrator Dashboard
The Next Level: Reporting Housekeeping

Create Custom Dashboards

Prerequisites
Security: Set Up: Tenant Setup - Worklets domain in the System functional area.

Context
You can create a custom dashboard that groups together related worklets.
You can also display custom dashboards as worklets on landing pages.

Steps
1. Access the Create Custom Dashboard task.
2. As you complete the task, consider:
Option Description
Domains Select 1 or more domains that include the security
groups who need access to the dashboard.
If a Workday-delivered domain doesn't include all
the security groups you need, you can create up
to 200 custom domains.

Dashboard Icon Select an image to represent your dashboard on

the Home page.
Dashboard Tabs Enables you to add up to 6 tabs to the dashboard.
Max Worklets Allowed Select the maximum number of worklets that you
can add to each dashboard tab.
You can add up to 6 worklets to each dashboard
tab, for a total of 36 worklets.

Next Steps
• Enable reports as worklets so you can add them to the dashboard.
• Access the Maintain Dashboards report to add worklets to the dashboard.
Related Information
Concepts
Concept: Dashboards
Tasks
Steps: Set Up Custom Dashboards on page 185

Configure Dashboard Content

Prerequisites
• Enable 1 or more reports as worklets and:
• Make them available on your custom dashboard.
• Share them with the appropriate security groups.
• Security: These domains in the System functional area:
• Custom Report Creation
• Custom Report Management
• Set Up: Tenant Setup - Worklets

Context
After you create a custom dashboard, you can:
• Add required or optional worklets to the dashboard.
• Select default values for each prompt set field on the dashboard tab and map them to report prompt
fields.
Users can't add or remove required worklets, but they can add or remove optional worklets.
To improve dashboard performance, limit the number of worklets you add to a dashboard tab. The more
worklets on a dashboard tab, the longer the load time. When you run the report, the dashboard displays
the first 6 worklets in the order they display in the Worklets list.

Steps
1. Access the Maintain Dashboards report.
2. Click Edit for the dashboard you want to configure.
3. On the Content tab, click Add to create a dashboard tab.
Create at least 1 tab. You can create up to 6 tabs for each dashboard.
4. As you complete the tab, consider:
Option Description
Configurable By User Enable users to add or remove optional worklets
from the dashboard tab. You can't select this
check box if you select a Prompt Set for the
dashboard tab.
Prompt Set Select a prompt set that can pass prompt values
to all worklets on the dashboard tab. Example: If
you want to run each worklet on the dashboard
tab for the same supervisory organization,
you can use the Workday-delivered Workforce
Composition prompt set.
If you select a prompt set for the dashboard tab,
you can't select Configurable By User. You also
can't add optional worklets to the dashboard tab.
You can't:
• Add calculated fields to a prompt set.
However, if Workday enables the calculated
field for prompts, you can use the calculated
field as the Default Value for the prompt.
Then, you can add that prompt to a prompt set.

Option Description
• Change the prompt set for the dashboard tab
after you create it.

5. (Optional) As you complete the Prompts section, consider:

Option Description
Default Type Select the source of the value for the Prompt
Field.
Default Value If you select Specify default value as the Default
Type, select a default prompt value.
6. In the Worklets section, create a row for each worklet you want to add.
7. As you complete the section, consider:
Option Description
Worklet You can only select custom reports that you
enable as worklets and that you share with 1 or
more security groups.
Required for Groups Workday recommends removing security groups
that don't need access to this dashboard. Include
at least 1 security group.
Workday displays the list of security groups who
can access the report definition for the worklet.

Required? Select to prevent users from removing the worklet

from the dashboard.
If you don't select this check box, the worklet is
optional for dashboard users.

Worklet Size To increase the size of a worklet and display it

first in order, select 2X. The default worklet size is
1X.
Worklet Title Enter an alternate title for the report that displays
when you run the worklet on a dashboard.
Map Prompts This button is only available if the dashboard tab
has a prompt set and the worklet has prompts.
When you click Map Prompts, Workday
automatically maps worklet prompt fields to
prompt set fields of the same field type. However,
Workday recommends that you manually confirm
that the prompt field mappings are what you
intend.
To fix incorrect mappings between worklet prompt
fields and prompt set fields:
a. Click Map Prompts.
b. On the Value Type prompt for the prompt
field you want to map, select Use Value from
Dashboard Prompt.
c. On the Field prompt, select a field from the
dashboard prompt set.

Option Description
Invalid Landing Page Admin Configuration If there's a conflict between the security domain
for the dashboard and for the worklet, this column
displays an error message.
Fix Click to resolve security group conflicts between
the worklet and the dashboard.
8. (Optional) Add a menu to your dashboard.
Related Information
Concepts
Concept: Dashboards
Concept: Custom Worklets on page 190
Tasks
Add Dashboard Menus
Reference
The Next Level: Report Security Overview

Enable Reports for Related Worklets

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports

Context
You can embed related worklets to deliver contextual information to users as they perform actions in your
business processes. Before you can embed worklets, you must enable the reports for related worklets.

Steps
1. Access the Edit Custom Report task.
2. Select Enable As Worklet on the Output tab.
3. Enter Embedded on Tasks for the Available on section on the Output tab.
4. Share the report with required authorized groups on the Share tab.
5. On the Filter tab, add a filter condition with these settings:
Option Description
Field Select a field that the business process definition
can map to.
Operator Select in the selection list as the operator.
Comparison Value Select Prompt the user for the value as the
comparison value.

Next Steps
Make the worklets available on your custom dashboard and share them with the appropriate security
groups.
Embed the related worklets in your business processes.

Related Information
Concepts
Concept: Related Worklets in Business Processes
Tasks
Embed Related Worklets in Business Processes
Steps: Display a Quicklinks Worklet on a Dashboard on page 209
Configure Dashboard Content on page 187

Save Custom Prompt Values for Worklets

Context
On dashboards that don't use prompt sets, Workday enables you to save custom prompt values for
worklets.
You can't save custom prompt values for worklets when you access them on mobile devices. However,
Workday recognizes the prompt values you select in the desktop browser when you run the worklet on
mobile devices. If you don't enter values for required prompts through your desktop browser, the worklet
doesn't display on mobile devices. Use the Mobile Reports report to set up prompt values for a worklet
that is available only on the Mobile Reports landing page.

Steps
1. Run a dashboard that doesn't use a prompt set.
2. Click the Gear icon on a worklet and select Edit Settings.
3. Enter the prompt values you want.
You can select Restore Default Settings from the Gear icon of the worklet to restore the default
prompt values.

Result
Each time you run the dashboard, the worklet runs with the prompt values that you set. However, if you
click View More on a worklet more than 1 minute after the dashboard loads, you must enter the prompt
values again.

Concept: Custom Worklets

You can deploy these types of custom reports as worklets on dashboards or landing pages:
• Advanced
• Composite
• Matrix
• nBox
• Transposed
• Trending

Design Considerations
Workday recommends that you design worklets to load quickly so that they don't time out on a dashboard.
For reports with prompts, Workday recommends that you configure required prompts so that report results
display as soon as the dashboard loads:
• Select Do Not Prompt at Runtime for required prompt fields.
• Set default prompt values for all required prompt fields.
To maximize available space for a worklet, Workday recommends that you:

• Select the Display this Worklet When Maximized option for nonessential fields in the report definition.
• Sort and filter the report to display the most essential data.
• Use charts to visualize and display more data in a worklet.

Sharing Options
When you share a report that you enable as a worklet, users can add the report as a worklet to available
dashboards. Example: You can build a headcount report, enable it as a worklet on an HR dashboard,
and share it with the HR Partner group. HR Partners can then view the report as a worklet on the HR
dashboard.
When you share a report with specific users:
• You can't add it as a worklet to a dashboard.
• Your Setup Administrator can't add it as a required or recommended worklet to a landing page.

Optional and Required Worklets

You can add a custom report to a dashboard as:
• Optional worklets, which users can remove from the dashboard. They can also add optional worklets
back to the dashboard.
• Required worklets, which users can't remove from the dashboard.
If there's a conflict between required and optional options for a worklet, the required option always takes
precedence.

Worklet Management
You can't hide or delete a worklet unless you remove it from all dashboards and administrator and user
configurations.
You can use the Remove Worklet from Dashboards task to remove a worklet from dashboards and
configurations.
The Remove Worklet from Dashboards task also includes a confirmation page, which enables you to drill
down on worklet usage details for user and administrator configurations.

iPad Considerations
When displaying custom reports and worklets on an iPad, Workday ignores options for:
• 3D charts.
• Hiding table borders and column headings.
• Maximizing reports.
• Refreshing data. The data refreshes every time you access the report or worklet.
Related Information
Concepts
Concept: Custom Reports on page 12
Concept: Mobile Devices and Features
Tasks
Set Up Output Options for Custom Reports on page 39
Set Up Share Options for Custom Reports on page 42
Reference
The Next Level: Report Security Overview

Concept: Worklet Performance

Optimizing Worklet Performance

For optimal report performance, Workday recommends that you:
• Share worklets with the fewest user groups necessary.
• Use data sources secured to domains with the fewest possible security groups.
• Use the smallest possible data source for the intended users.
Example: For worklets for managers, use a data source such as My Direct and Indirect Workers
instead of All Workers.
• Use an indexed data source.
• Use user-based security groups instead of job-based security groups.
This approach reduces the complexity of the security evaluation required and improves performance of
the worklet.

Matrix Worklet Performance

Displaying matrix reports as worklets on the Home page can increase the page load time. The more rows
that the report evaluates and summarizes, the longer it takes for the worklet to load.
Instead of using matrix reports as worklets on the Home page, consider:
• Building a report of key custom reports and deploying it as a worklet to your users. The reports on the
worklet only execute when the user selects Run from the related actions menu.
• Displaying the worklet on the My Team dashboard. The worklet only runs when the user selects it from
the dashboard.

Worklet Caching
You can store temporary copies of data for certain worklets instead of running the worklet each time the
page refreshes. Workday stores and displays cached worklet data for the remainder of your browser
session and each time you refresh the page. Workday recalculates the worklet data when you:
• Select Refresh from the Gear icon on the worklet.
• Sign in to Workday again.
Related Information
Concepts
Concept: Indexed Data Sources and Fields on page 15

Custom Metrics and Scorecards

Steps: Create Custom Metrics and Scorecards

Prerequisites
• Create fiscal schedules for use with any custom scorecards you create.
• Select Enable Scorecarding check box in the Scorecarding section on the Edit Tenant Setup -
Reporting and Analytics task.
• Security: Metric Management domain in the System functional area.

Context
You can build custom metrics and analytic scorecards to make key information available from a dashboard
or home page.

Steps
1. Set Up Analytic Scorecard Profiles and Metric Sets on page 193.
You can create a metric set to group custom metrics for a scorecard.
2. Create Custom Metrics on page 195.
3. Access the Create Custom Dashboard task and create a custom dashboard for displaying your
scorecard.
Include Metrics Published as the Domain for your dashboard.
4. Set Up Custom Reports for Scorecards on page 196.
5. Process Metrics on page 198.
You can process metrics for the current period.
6. (Optional) Initialize metric values for historic periods. On the Initialize Metric Values task, you can:
• Add a new metric and process for historic periods.
• Reprocess an existing metric for historic periods.
7. (Optional) Schedule calculation of metric values for multiple historic periods on the Calculate Metric
Values task.
Related Information
Concepts
Concept: Workday Scorecards on page 199
Tasks
Steps: Set Up Custom Dashboards on page 185
Set Up Organization Chart Metrics
Reference
Reference: Edit Tenant Setup - Reporting and Analytics
Reference: Metric Calculation Time Periods
Reference: Metric Calculations for Financials
Reference: Metric Calculations for Dependent Metrics on page 204
Reference: Metric Calculations for HCM
The Next Level: Scorecards

Set Up Analytic Scorecard Profiles and Metric Sets

Prerequisites
Security: Metric Management domain in the System functional area.

Context
You can create an analytic scorecard profile and metric set to group associated metrics for inclusion in a
scorecard.
You can create a metric set with up to 20,000 organizations. Workday calculates the number of
organizations based on the options you select for:
• Organization type.
• Content nodes, if using a hierarchic organization type.
• Node levels.

Steps
1. Access the Maintain Analytic Scorecard Profiles and Metric Sets report.
2. Click Create Analytic Scorecard Profile.

3. As you complete the task, consider:

Option Description
Name Enter a name for the metric set.
Organization Type Select the type of organization for the metric set.
Top Level Node Select the top-level organization associated with
the metric set.
Fiscal Schedule Select the time interval for the metric set.
Example: Standard Corporate Schedule, which
uses a monthly interval.
4. From your analytic scorecard profile, click Metric Set Details.
5. Click Edit.
As you complete the task, consider:
Option Description
Inactive Inactivate the metric set and disable publishing.
Skip Review Disable the review process for the metric set.
Include Content For hierarchic organization types, include any
hierarchic content nodes in the levels you
select in Top Level Node and Levels from
Top. Example: For a metric set based on an
Organization Type of Cost Center Hierarchy,
selecting this option includes the content nodes in
the hierarchy.
Metric Calculation Scope Include subordinate nodes in the metric set.
Levels From Top Define which organizations to include in the metric
set.
Example: If you enter 0, the metric set includes
only the organizations you select as Additional
Nodes. If you enter 1, the metric set includes
only the organization you select as the Top Level
Node. If you enter 2, the metric set includes the
top-level organization as well as its immediate
subordinates.

Additional Nodes Select any nodes in addition to the Top Level

Node to include in the metric set, and the
specified levels below that node.
Published Period Select the period for which you want to retrieve
data. For your initial metric set setup, select the
period before the first period you want to process.
Run as Scheduled User For metric calculations based on a matrix report,
run the calculation as the user who runs or
schedules the Calculate Metric Values task.
Run as Integration User For metric calculations based on a matrix report,
run the calculation as a named integration system
user you select.

Next Steps
Create custom metrics for your metric set.
Related Information
Reference
Reference: Metric Calculations for Financials

Create Custom Metrics

Prerequisites
• Create a metric set.
• For metrics calculations sourced from Workday Benchmarking data, create a custom matrix report
based on the Benchmark Values As a Source for Scorecard report.
• For metrics sourced from matrix reports, share the reports with authorized groups or users.
• Security: Metric Management domain in the System functional area.

Context
You can create custom metrics to include in scorecards that provide business performance information for
a specific organization or user group. For each custom metric you create, you can add:
• Metric sources, including Workday-delivered calculations or custom reports. You can access the View
Metric Calculation report to see descriptions of Workday-delivered calculations.
• Recommended actions for metric statuses.
• Report links for drill to detail information.
• Target benchmarks.
• Thresholds.

Steps
1. From your analytic scorecard profile, click Metrics.
2. Click Create Custom Metric.
3. Select the Workday Metric Calculation Name to use to calculate the metric. Workday displays metric
calculations options based on the organization type specified for the metric set.
You can't use a matrix report that has a Lookup Prior Value summary calculation in a metric calculation.
4. Add help text for the metric in About This Metric.
5. (Optional) In the Report Links section, you can set up hypertext links to 5 reports.
As you complete the Report Links grid, consider:
Option Description
Tag Specify a label to display instead of Report Link
1 and so on, for each Report Link you add in the
About This Metric field.
Drill To Specify the report for each Report Link you add
in the About This Metric field.
Map Prompts Click to add prompt values for a Report Link.
6. On the Metric Source tab, specify how Workday calculates the metric values.
As you complete this tab, consider:
Option Description
Track Target Click to track the target value for the metric.

Option Description
Target Source If you select Online Page as the source, you must
also:
• Set values for the metric set on the Generate
Target and Benchmark Lines task.
• Set target values for each metric on the Metric
Target Values report.

Track Benchmark Click to track the benchmark value for the metric.
Benchmark Source If you select Online Page as the source, you must
also:
• Set values for the metric set on the Generate
Target and Benchmark Lines task.
• Set benchmark values for each metric on the
Metric Target Values report.
Select WD Matrix Report to use a custom report
data as the source for metric calculations,
including Workday Benchmarking data.

7. On the Calculation Configuration tab, set up the metric calculation configuration for Workday-
delivered calculations.
When setting up Actual Amount, Target Amount, or Benchmark Amount for metrics sourced from
matrix reports, consider:
Option Description
Matrix Report Select a custom matrix report that groups by the
organization type specified for the metric set.
To include Workday Benchmarking data in your
scorecard, select a custom matrix report based
on the Benchmark Values As a Source for
Scorecard report.
Value Type Specify that you want to add a default value,
if available, or use the value from the metric
calculation.
Value Specify default values for report prompts.
Aggregation Field Select the Summarization field from the standard
or custom report used to aggregate values.

Next Steps
Set up reports and dashboards for your metrics.
Related Information
Reference
Reference: Metric Calculations for Financials

Set Up Custom Reports for Scorecards

Prerequisites
Security: These domains in the System functional area:

• Custom Report Creation

• Metric Management

Context
When you set up a scorecard, you need to use these reports types as the source for the metrics data:
• A composite report as the main report for your scorecard.
• One or more advanced subreports. Subreports calculate values on the metric rather than in the
composite report.
You can manually create custom reports for your scorecard, or you can create a composite report and
underlying subreports from your analytic scorecard profile with these predefined settings:
• Drilling.
• Layout.
• Prompt defaults.

Steps
1. From your analytic scorecard profile, click Reports and Dashboards.
2. Click Scorecard Report.
As you complete the task, consider:
Option Description
Dashboard Select the dashboard for your report, or click
Create > Create Custom Dashboard.
Metric Select a metric for your report, or click Create >
Create Custom Metric.
Formatting Style Select a formatting option for your metric.
Enable Drilling to Select to display additional information and report
links.
Target Select the target for your metric value:
• Actual Value
• Target Value

Share Option Subreports of the scorecard report inherit the

share option that you select. This share option
can impact subreports that are referenced in other
composite reports outside the scorecard report.

Next Steps
Initialize and publish metric values.
Related Information
Tasks
Steps: Set Up Custom Dashboards on page 185
Reference
Reference: Custom Scorecard Report Definition on page 201

Process Metrics

Prerequisites
Security: Metrics Management domain in the System functional area.

Context
You can run these metric processes at the end of the scorecard period to update report data for your
analytic scorecard:
• Initialize
• Reinitialize
• Calculate
• Review
• Publish

Steps
1. From your analytic scorecard profile, click Process.
2. Click:
• Initialize to process metrics for the current period.
• Reinitialize to reprocess metrics for the current period.
3. Click:
• Calculate to calculate metrics for the metric set.
• Recalculate to recalculate metrics you select for the current period.
4. (Optional) Access the Start Metric Review task.
Reviewers can comment, send back, or approve the metrics.
5. Click Publish.
6. (Optional) Click Delete to delete metric values for a specific period from the metric set.
You can also select Delete Metric Values > Run from the related actions menu of an analytic
scorecard profile to select more delete options.

Result
Workday displays up to the last 6 published periods for the metric set.

Next Steps
Click Results next to a processed period to access the Metric Processing Status by Metric and Period
report, which displays metric processing history.
Click Errors to access the Error in Details report, which displays metric job errors.

Review Metrics

Prerequisites
• The scorecard administrator runs the Start Metric Review task.
• Security: Metrics in Review domain in the System functional area.

Context
When the scorecard administrator runs the Start Metric Review task, metrics reviewers receive a
notification to review the metric set.

Steps
1. Access the Scorecard Reviewer report.
Run the report for the Metric Set, Organization, and Period you want to review.
2. On the Mark Reviewed/Comment column, click the related actions menu for each metric and select
Analytic Metric Values > Add Comment for Metric.

Next Steps
The scorecard administrator can make any adjustments as necessary and publish the metric set.

Concept: Workday Scorecards

A Workday scorecard is a snapshot of important metrics for a specific organization and time period.
Supported organization types include:
• Academic Unit and Academic Unit Hierarchy.
• Business Unit and Business Unit Hierarchy.
• Company and Company Hierarchy.
• Cost Center and Cost Center Hierarchy.
• Custom Organizations.
• Location and Location Hierarchy.
• Regional Hierarchy.
• Supervisory.
Scorecard data can include:
• Metric descriptions.
• Metric trending from the prior period to the current period.
• Review comments about individual metrics.
• Status and recommendations to address a metric.
• Target and actual values.
• The period for which data computes and aggregates, such as a particular month or quarter.
You can base each metric on a scorecard on a Workday or external data source using:
• A matrix report.
• A Workday-delivered calculation.

Scorecard Results
Calculated metric values might differ from custom matrix report results that you use as a benchmark
source for your metrics. Reports use the latest data from the data source when you run the report, while
analytic metric values are a snapshot from the time that you calculate the metrics. Analytic metric values
don't include any data that has:
• An effective date after the date of the snapshot.
• An effective date before the date of the snapshot, but hasn't been processed at the time of the
snapshot.
Scorecards also remove inactive organizations by default, while custom reports don’t. However, you can
configure your report to filter out inactive organizations.

Scorecard Roles
Scorecard roles are:
• Scorecard administrators, who have access to the Metrics Management domain and, optionally, the
Manage: Metric Values domain in the System functional area.

• Scorecard reviewers, who have access to the Metrics in Review domain in the System functional area.
• Scorecard users, who have access to the Metrics Published domain in the System functional area.

Workday-Delivered Scorecards
Workday provides preconfigured scorecards, such as:
• Executive Workforce Scorecard (for HCM).
• Financial Executive Scorecard.
Workday-delivered scorecards include:
• Composite reports and related subreports.
• Dashboards.
• Drill-to reports, when applicable.
• Metric sets and metrics.
• Prompt sets.

Custom Scorecards
In addition to using Workday-delivered scorecards, you can also create custom scorecards. If creating
custom scorecards, you must provide additional training and security configuration for roles supporting
scorecards.
Workday recommends contacting Workday Professional Services to implement custom scorecards.

Metric Calculations Report

The Metric Calculations report lists Workday-delivered metric calculations and includes:
• A detailed description.
• The metrics based on the calculations.
• The organization types supported.

Migrating Scorecards
Using Object Transporter, you can migrate scorecard components in this order:
1. Metric sets. Object Transporter automatically moves any metrics, as well as the metric configurations
and drill-to reports associated with the metrics in the metric set.
2. Composite reports. Object Transporter also migrates the associated:
• Analytic indicators.
• Prompt sets.
• Subreports.
3. Dashboards.
Related Information
Tasks
Create Custom Metrics for HCM
Reference
Reference: Metric Calculation Time Periods
Reference: Metric Calculations for Financials
Reference: Metric Calculations for HCM
The Next Level: Scorecards

Reference: Custom Scorecard Report Definition

You can create a Scorecard Report from an analytic scorecard profile, which includes a complete
composite report and underlying advanced subreport. You can also create your own custom composite
report and subreport on the Create Custom Report task.
The subreport definition for a scorecard includes these settings:

Option Description
Data Source Scorecard subreports use the All Analytic Metric
Values data source.
Data Source Filter Specifies the filter for your scorecard audience:
• All Metrics for administrators.
• Metrics for Review for reviewers.
• Published Metrics for users.

Field (Columns tab) Select Metric Value in the Field prompt in the grid.
Also add a row in the grid and select Metric in the
Field prompt.
Field (Filter tab) Select Organization in the Field prompt in the grid.
Also add a row in the grid and select Period in the
Field prompt.

The composite report definition for a scorecard includes these settings:

Tab Field Description

General Prompt Set Specifies a Workday-delivered
prompt set or a custom prompt
set.
To create a custom prompt set,
click Create > Create Prompt
Set, and include fields for:
• Metric Organization
• Metric Set
• Metric Period

General Business Object Composite reports for metric

scorecards must include the
Analytic Metric Values as
the Business Object in the
Business Object Enabled for
Filtering and Grouping grid.
Prompts Effective Date, Entry Date Specifies date and time settings
for Runtime Date Prompts.
Prompts Field Specifies these required prompt
defaults:
• Metric Organization
• Metric Set
• Metric Period

Tab Field Description

Output Output Type The KPI Line and KPI Card
layout types return the metric
value, status, trend, target, and
comment from the lookup field
value columns.
Output Enable as Worklet Enables the composite report as
a worklet for your dashboard.

The composite report definition for a scorecard also includes these column and row types:

Column Type/Row Type Description

Control Field Column Maps to the Analytic Metric Values Business
Object, and returns values based on the metrics
defined in the row and lookup values defined in the
columns.
Lookup Field Value Columns Returns fields from the Analytic Metric Values
Business Object, and returns values for each
metric defined as a row.
Dynamic Data Row Returns values for a single metric when you
filter the results of the subreport. Workday maps
prompts from the subreport to pull in metric values
for the Organization and Period specified in the
prompt set.

Reference: Scorecard Results

On the Maintain Analytic Scorecard Profiles and Metric Sets report, you can set up metric sets for an
Organization Type that is:
• Hierarchical with hierarchic content.
Examples: Location Hierarchy and Location, Academic Unit Hierarchy and Academic Unit.
• Hierarchical with nonhierarchic content.
Examples: Cost Center Hierarchy and Cost Center.
Depending on the options you select for the metric set, Workday displays varying results in the related
scorecards.

Scorecard Results for a Hierarchy with Hierarchic Content Organization Type

Organization Type Example Content Included Scorecard Results

Location Hierarchy No • Location hierarchy nodes
in the Top Level Node you
select.
• Additional Nodes you select.

Location Hierarchy Yes • Location hierarchy nodes

in the Top Level Node you
select.
• Locations explicitly included in
any of the location hierarchy

Organization Type Example Content Included Scorecard Results

nodes in the Top Level Node
you select. Workday excludes
content for subordinate
locations that aren't explicitly
in the hierarchy.
• Nodes and locations explicitly
included in the Additional
Nodes you select.

Location Not applicable • Locations explicitly included in

any of the location hierarchy
nodes within the level you
select in Top Level Node.
• Location you select in
Additional Nodes.

Academic Unit Hierarchy No • Academic unit hierarchy

nodes in the Top Level Node
you select.
• Additional Nodes you select.

Academic Unit Hierarchy Yes • Academic hierarchy nodes

in the Top Level Node you
select.
• Academic units explicitly
included in any of the
academic unit hierarchy nodes
in the Top Level Node you
select. Workday excludes
content for subordinate
academic units that aren't
explicitly in the hierarchy.
• Nodes and academic units
explicitly included in the
Additional Nodes you select.

Academic Unit Not applicable • Academic units explicitly

included in any of the
academic unit hierarchy nodes
within the level you select in
Top Level Node.
• Academic units you select in
Additional Nodes.
Since Academic Unit is role-
enabled, Workday also traverses
the Academic Unit content
hierarchy.

Scorecard Results for a Hierarchy with Non-Hierarchic Content Organization Type

Organization Type Example Content Included Scorecard Results

Cost Center Hierarchy No • Cost center hierarchy nodes
in the Top Level Node you
select.
• Additional Nodes you select.

Cost Center Hierarchy Yes • Cost center hierarchy nodes

in the Top Level Node you
select.
• Cost centers explicitly
included in any of the cost
center hierarchy nodes in the
Top Level Node you select.
• Nodes and cost centers
explicitly included in the
Additional Nodes you select.

Cost Center Not applicable • Cost centers in any part of the

cost center hierarchy level you
select in Top Level Node.
• Cost centers you select in the
Additional Nodes prompt.

Scorecard Result Discrepancies

Calculated metric values might differ from custom matrix report results that you use as a benchmark
source for your metrics. Reports use the latest data from the data source when you run the report, while
analytic metric values are a snapshot from the time that you calculate the metrics. Analytic metric values
don't include any data that has:
• An effective date after the date of the snapshot.
• An effective date before the date of the snapshot, but hasn't been processed at the time of the
snapshot.
Scorecards also remove inactive organizations by default, while custom reports don’t. However, you can
configure your report to filter out inactive organizations.

Reference: Metric Calculations for Dependent Metrics

Workday provides a number of metric calculations for use with custom scorecards. Some Workday product
areas (Example: HCM and Projects) provide Workday-delivered calculations for specific use cases.
Workday also enables you to combine the WD Simple Arithmetic calculation with other metrics to form
dependent metrics.

Workday-Delivered Description Organizations Configuration Options

Calculation
WD Simple Arithmetic Enables you to create Supervisory A, B, C, D, E, F
a metric based on other Organization (variables mapped to
metrics. You can map up existing metrics)
Cost Center Hierarchy
to 6 existing metrics to
Use Multiplication
variables named A, B, Custom Organization
C, D, E, and F to create Reverse Sign

Workday-Delivered Description Organizations Configuration Options

Calculation
new metrics. You don't Custom Organization
need to use all variables. Hierarchy
Example: You can use A
Project
and B, or A and C, or A
and E, or all 6 variables. Project Hierarchy
Workday calculates the
value of each of the
metrics A, B, C, D, E,
and F first, and then
calculates the value of
the dependent metric.
Use Multiplication
effectively changes the
division operator (/) to a
multiplication operator
(*).
Reverse Sign reverses
the positive/negative
sign of the calculation
result.
Calculation: (A - B) / (C
- D) / (E - F) or (A - B) *
(C - D) * (E - F).
Custom Metric
Examples: To create a
Revenue Per Headcount
metric, assign a
Revenue metric to A and
a Headcount metric to C.
To create a Days Sales
Outstanding metric,
assign a Revenue
metric to A, Accounts
Receivables metric to
C, and Number of Days
metric to E.

Related Information
Concepts
Concept: Workday Scorecards on page 199

Custom Data Sources

Set Up Extended Indexed Data Sources

Prerequisites
• Create the Custom Data Source Extension Approval Event business process and security policy in the
System functional area.

• Security: Manage: Custom Data Sources domain in the System functional area.

Context
You can set up an extended indexed data source that includes fields suitable for indexing.

Steps
1. Access the Maintain Custom Data Source report and click Create Custom Data Source.
2. Select the Data Source that you want to add fields to. Example: You can add fields to the Job
Applications data source.
3. (Optional) Review the Data Source Filters and Delivered Indexed Fields tabs.
4. As you complete the Additional Fields tab, consider:
Option Description
Source Field You can add fields suitable for indexing for these
field types:
• Calculated fields from your tenant.
• Custom fields from your tenant.
• Delivered fields from the primary business
object for the data source.

Usages Displays usage for the Source Field in your

tenant.
5. On the Maintain Custom Data Source report, click Submit to submit the draft data source for security
approval.

Result
Workday sends the data source approver an Inbox notification with the approval request. The approver
can review security and approve or deny the data source.

Next Steps
On the Maintain Custom Data Source report, you can click Publish to schedule publishing of an
approved, unpublished extended custom data source. You can also:
• Click Create New Version to update fields for a published extended custom data source.
• Click View next to a data source and navigate to the Status tab to view publishing history and indexing
processing time.
Related Information
Reference
The Next Level: Extended Indexed Data Sources

Concept: Extended Indexed Data Sources

Workday enables you to extend some Workday-delivered indexed data sources by adding a limited
number of these field types:
• Calculated fields from your tenant.
• Custom fields from your tenant.
• Nonindexed delivered fields from the primary business object.
Workday indexes the fields you add, enabling you to create high-performing reports for executive
dashboards and scorecards.

An extended indexed data source provides functionality similar to a Workday-delivered data source,
including:
• Drilling on summary data in reports based on the indexed data source.
• Support for all report types. Advanced and matrix reports with multiple filters yield the greatest
performance benefit from indexed data sources.
• Support for scorecards, worklets, and worksheets.
When you create a custom report based on an extended indexed data source and you include facets, you
can search on these field types in report results:
• Indexed delivered fields.
• Text fields that you add to the data source.

Field Suitability for Indexing

Security is one reason some fields aren't suitable for indexing. Example: A multi-instance field contains 3
values. If some users should only have access to 1 or 2 of the values, Workday doesn't index the multi-
instance field.
Workday displays an error message when you try to add a field to your data source that isn't suitable for
indexing. Workday also displays an alternate field, if one is available. You can also:
• Access the Field Suitability for Business Objects report, which enables you to display indexing
suitability for fields on a business object.
• Select the related actions menu for any field to check if the field is Suitable for Indexing.

Data Source Security

Workday recommends that you set up a user-based security group for the data administrator and assign
the group to the Manage: Custom Data Sources security domain.

Data Source Approval and Publishing Process

When the data administrator submits a draft version of an extended indexed data source for approval,
Workday sends a pending review action to the security administrator or approver Inbox. The security
administrator or approver reviews the security domains for the calculated fields in the extended indexed
data source. After approval, the data administrator can publish the data source.
Workday schedules an hourly background publishing process job that indexes the fields that you add to
the data source. For any calculated fields that you add, Workday creates a duplicate field with the same
name. You can use the duplicate calculated field in custom reports to ensure that your report still runs in
Optimized for Performance mode.
After indexing completes for all fields, Workday marks the data source as Published. You can click View
for a data source on the Maintain Custom Data Source to view the Status tab, which displays the details
on the background indexing job.
You can create a Custom Data Source Extension Approval Event business process for data source
approval and publishing steps.

Versioning Process
Workday supports versioning for an extended indexed data source. Only 1 version of an extended indexed
data source can be in Published status; Workday marks other versions as Historical.
The data administrator can edit the extended indexed data source to add new fields. Every new draft
version requires security review and approval.

Related Information
Reference
The Next Level: Factors Impacting Report Performance

Maintain Custom Data Source for the Worker Business Object

Prerequisites
• Create a Custom Data Source Approval Event business process and security policy in the System
functional area.
• Security: Manage: Custom Data Sources domain in the System functional area.

Context
Note: Workday recommends creating an extended indexed data source instead of a custom worker data
source. See Set Up Extended Indexed Data Sources on page 205. You can only access the Maintain
Custom Worker report if you've previously created a custom worker data source in your tenant.

Steps
1. Access the Maintain Custom Worker report.
2. Click Edit next to a draft data source.
3. On the General tab, select an Effective Date Field for Processing that Workday uses when indexing
fields.
Example: Use Termination Date as the effective date to index data records for terminated workers.
4. On the Filter tab, set up the data source filters.
As you complete the tab, consider:
Option Description
Condition Select a Boolean-type field associated with the
Primary Business Object for the custom data
source.
Domain Select 1 or more valid domains for the data
source.
Default Select to display the filter as the default for the
custom data source in a report definition. A
custom data source must always have only 1 data
source filter.
5. On the Fields tab, add a row in the Fields grid for each field you want to add to the data source.
As you complete the tab, consider:
Option Description
Source Field Select fields from the Source Business Object,
including calculated fields.
Category Select a new display category in which to place
the field you add.
Domain Select or override the domain to secure the
Source Field.
Inactive Select this check box to ensure that the Source
Field doesn't display in field prompts.

6. On the Security tab, select fields from the Securing Entity Fields prompt to set up contextual security
for the filters and fields.
Example: Add Supervisory Organization as the securing entity to ensure that a manager can access
data only for employees that they manage.

Result
Workday sends the data source approver an Inbox notification with the approval request. The approver
can review security and approve or deny the custom data source.

Next Steps
On the Maintain Custom Worker report, click Submit for Approval to submit the draft data source for
security approval.
Once approved, click Publish on the Maintain Custom Worker report. You can also:
• Click Create New Version to add more fields to a published data source.
• Click View next to a data source and navigate to the Data tab to view publishing history.

Quicklinks

Steps: Display a Quicklinks Worklet on a Dashboard

Context
Quicklinks enable you to link to external websites from Workday. You can use a Quicklinks worklet to
display collections of links, such as an internal help portal or benefits information.
You can display Quicklinks on:
• Announcements.
• Custom reports and worklets.
• Dashboards.
• Dashboard menus.

Steps
1. Access the Domain Security Policies for Functional Area report.
Select the System functional area. Ensure that the Quicklinks domain is enabled and that the correct
security groups have access to it.
See Edit Domain Security Policies.
2. Create or edit Quicklinks.
See Maintain Quicklinks on page 210.
3. (Optional) Access the Create Quicklink Group task.
Organize related Quicklinks into a Quicklink group.
Security: Set Up: System domain in the System functional area.
4. (Optional) If there isn't an existing dashboard you want to display the Quicklinks on, create a custom
dashboard.
See Create Custom Dashboards on page 186.
5. Create a Quicklinks Worklet on page 210.
6. Add the Quicklinks worklet to a dashboard.
See Configure Dashboard Content on page 187.

Maintain Quicklinks

Prerequisites
Security: Set Up: System domain in the System functional area.

Context
Quicklinks enable you to link to external websites from Workday. You can display Quicklinks in:
• Announcements.
• Custom reports and worklets.
• Dashboards.
• Dashboard menus.

Steps
1. Access the Maintain Quicklinks task.
2. Add a new row and enter a Name and URL.
3. (Optional) Set a Condition Rule so that the Quicklink only displays under certain conditions within a
dashboard.
Condition rules applied to Quicklinks don’t work in custom reports.
4. (Optional) Click View Details to navigate to a quicklink location and remove the link.
The View Quicklink Usage Details grid provides information on where the quicklink is used in your
tenant, including on the Edit Tenant Setup – System task. If you have security permissions to access
the location, you can click the link in the grid to navigate to the quicklink location.
We don't display the View Details button on a quicklink row when the quicklink isn't in use in your
tenant or doesn't have a relationship with other objects in your tenant. When you don't see the View
Details button on the row, you can delete the quicklink from the Maintain Quicklinks task.

Next Steps
Add the Quicklink to a:
• Custom report or worklet.
• Dashboard menu or announcement.
• Quicklink group.
Related Information
Tasks
Steps: Display a Quicklinks Worklet on a Dashboard on page 209

Create a Quicklinks Worklet

Prerequisites
• Set Condition Rules for Quicklinks.
• Create a dashboard or landing page to display the worklet on.
• Security: These domains in the System functional area:
• Custom Report Creation
• Manage: All Custom Reports
• Quicklinks

Context
You can create a Quicklinks worklet to display external website links on a dashboard.

Steps
1. Access the Create Custom Report task.
2. Select Advanced on the Report Type prompt.
3. Clear the Optimized for Performance check box.
4. Select Quicklinks on the Data Source prompt.
5. On the Columns tab, select Quicklink Item on the Field prompt.
6. (Optional) Set Up Sort Options for Custom Reports on page 33.
7. On the Filter on Instances grid on the Filter tab, select from these options:
• To display all the Quicklinks within a group, select Quicklink Group on the Field prompt. Select an
Operator value and select 1 or more groups on the Comparison Value prompt.
• To display a specific Quicklink, select Quicklink Item on the Field prompt. Select an Operator value
and select 1 or more Quicklinks on the Comparison Value prompt.
• To display only Quicklinks that a user has access to, select Valid for Worker on the Field prompt.
Select an Operator value and select the Comparison Value check box.
If you don’t set any filter conditions, the report displays all Quicklinks.
8. On the Output tab, select the Enable As Worklet check box in the Worklet Options section.
9. Select an appropriate Worklet Icon.
10.On the Available on prompt, select the dashboard where you want to display the worklet.
11.On the Share tab, select the appropriate sharing options.

Next Steps
Add the worklet you created to the dashboard you selected on the Available on prompt.
Related Information
Tasks
Steps: Display a Quicklinks Worklet on a Dashboard on page 209

Reports as a Service (RaaS)

Concept: Reports as a Service (RaaS)

Introduction to RaaS
You can enable advanced and search reports as web services. Workday Web Services enable access to
report results through URLs, which you can use in:
• Custom Workday Extend applications.
• Integrations between Workday and external business services. Example: Payroll or benefits providers.
• External reporting tools to access Workday data. Example: Microsoft Excel.
Output options for web services include:
• CSV
• GData
• JSON
• RSS
• Simple XML

• Workday XML
Before enabling a standard report as a web service, consider copying the standard report to a custom
report. To avoid any disruption to your integration processes if Workday updates a standard report, enable
the custom report as a web service instead.
GET RaaS requests fail if you enable a custom report as a web service and the username of the report
owner contains a backslash (\) character.

RaaS Namespaces
When you enable a custom report as a web service, Workday generates a unique RaaS namespace for
the report, using this format:
urn:com.workday.report/Report_Name
To minimize disruptions to integrations that use the report output, the RaaS namespace doesn’t change
when the report name or report owner changes.
You can edit the namespace for a custom report. However, consider:
• Workday doesn’t verify that a RaaS namespace is unique.
• If an integration uses the report as a web service, you must update it with the new namespace.

Web Service Output Types

Output Type Description

CSV You can use the CSV output option when you want
to import data into a spreadsheet as simply and
quickly as possible. You don't need to know XML or
schemas.
If you output data to a CSV file that uses UTF-8
encoding, append this query parameter to your web
service URL: &bom=true
This parameter ensures that other applications,
such as Microsoft Excel, can correctly interpret the
encoding and display the characters in the CSV file.
For advanced reports that have Group Column
Headings, the CSV output doesn’t retain the
column groupings or column group headings.
The columns in the CSV output might not match the
order of the columns in the report definition.

GData You can use GData output for integrations with

Google gadgets.
JSON You can use the JSON output option in system-to-
system integrations that require the JSON format.
RSS You can enable any advanced custom report as
an RSS web service, which users can subscribe to
as an RSS feed. Users can monitor updates in a
tenant through an RSS feed without logging in to
Workday.
Simple XML Simple XML simplifies Workday XML so that other
desktop applications can process it. Simple XML
changes:

Output Type Description

• Single instance fields to simple string-type
elements.
• Multi-instance fields to simple string-type
elements.
• Multi-instance fields within the primary business
object to simple string-type elements, with a
semicolon separating each value.
• Date fields that don’t contain times to dates only,
with no times or offset from GMT.
You can use simple XML for basic desktop
integrations with other reporting tools, such as
Microsoft Excel or Crystal Reports.
The Simple XML output option provides these
URLs:
• Simple XML: The simplified XML output from a
report.
• XSD: The schema definition associated with the
simplified XML.

Workday XML The Workday XML option outputs the literal XML
code from Workday. This option might be useful in
REST- or SOAP-based integrations. Workday XML
might be too complex for some integration needs.
Example: Quickly creating a refreshable report with
Microsoft Excel. In these cases, Simple XML might
be more appropriate.
The Workday XML output option provides 3 URLs:
• Workday XML: The pure XML output from a
report that might be useful for REST-based
integrations.
• XSD: The schema definition associated with the
Workday XML.
• WSDL: Web Services Definition Language,
often used with SOAP.

Related Information
Tasks
Create Workday Accounts Automatically
Edit Workday Accounts
Steps: Set Up Outbound EIB

Concept: Accessing RaaS Output

Reports as REST-Based Web Services

To access report output for a REST-based web service integration, select Web Services > View URLs
from the related actions menu of the report definition. You must enter values for required prompts before
you can access report output.
You can either:
• Download the output file.

• Right-click the output you want and select Copy URL.

Reports as SOAP-Based Web Services

To build a SOAP-based web service integration, you need access to the Web Services Definition
Language (WSDL) definition underlying the report. Using the WSDL, you can define integrations from
external applications that need to access Workday report data.
To access the WSDL definition, select Web Services > View URLs from the related actions menu of the
report definition. You must enter values for required prompts before you can access report output.
You can either:
• Click the WSDL link and copy the definition.
• Right-click WSDL and select Copy URL.
Some XML reporting tools support specifying a schema with a data source to help interpret and validate
the data. To access the schema associated with a report:
1. From the related actions menu of the report definition, select Web Service > View WSDL.
2. Select all the XML from the opening <xsd:schema> tag to the closing </xsd:schema> tag.
3. Copy the XML or save it to a file, as your reporting tool requires.

Report Output URL

The URL for report output follows this pattern:
https://<workday-
url>/<tenant>/<username>/<report_name>?<prompt_1>=<prompt_1_value>&<prompt_2>=<prompt_2_v

URL Parameter Description Example

<workday-url> The URL of your Workday tenant. www.myworkday.com
<tenant> The name of your Workday gms
tenant.
<username> The user running the report. lmcneil
<report_name> The name of the report with Organization_Headcount
spaces replaced by underscores.
<prompt_1> The Label for Prompt XML Alias Organization
value of the report prompt, which
<prompt_2> Include_Subordinate_Organizations
you can view on the Prompts tab
of the report definition.
<prompt_1_value> For report prompts that take a Prompts that take a single
single instance value, the URL instance value: Organization
<prompt_2_value>
parameters follow this pattern: %21WID=cb550da820584750aae8f807882fa
<prompt>%21WID=<WID> .
Prompts that take multiple
For report prompts that take instance values: Location
multiple instance values, the URL %21WID=d951e85593ad4daf88dc1bfabf069
parameters follow this pattern: f5799b99ca2246d9bcf405fbc0a96b1d
<prompt>%21WID=<WID_1>!<WID_2>
All other prompts:
.
Include_Subordinate_Organizations=1
Otherwise, the URL
parameters follow this pattern:
<prompt>=<prompt_value> .

<format> The format of the report output. json

URL Parameter Description Example

Valid values for format include:
• csv
• gdata
• json
• rss
• simplexml

Example: https://www.myworkday.com/gms/lmcneil/Organization_Headcount?
Organization
%21WID=cb550da820584750aae8f807882fa79a&Include_Subordinate_Organizations=1&format=json
Related Information
Tasks
Steps: Set Up Outbound EIB

Concept: Reports as RSS Feeds

You can view a report as an RSS feed using a feed reader that permits SSL/HTTPS or HTTP basic
authentication.
To copy the RSS URL for a standard report:
1. Click the RSS feed icon. A new page opens.
2. Copy the URL from the browser address bar. Workday might prompt you to sign in before the page
displays.
To copy the RSS URL for a custom report:
1. On the report definition, select Web Services > View URLs from the related actions menu and enter
any required prompt values.
2. Right-click the RSS link and select Copy URL.
If the feed reader prompts you to sign in, you can use your Workday username and password.

Workday Query Language (WQL)

Concept: Workday Query Language (WQL)

Workday Query Language (WQL) enables you to use SQL-like syntax to access Workday data using data
sources and fields instead of reports. WQL enables you to query Workday for data and explore:
• Data sources.
• Data source filters.
• Fields.

Enabling WQL
WQL requires you to register an API client for your tenant. Register it in your tenant using the Register API
Client for Integrations task. You don't have to register an API client when you're using WQL in a Workday
Extend app.
When you register the API client for WQL, select System from the Scope (Functional Areas) prompt.
When you manage the refresh token, select a Workday account that has access to execute reports. The
API calls use this account.

Security
To use WQL, you need access to the Workday Query Language domain in the System functional area.
You can only view and use data sources and fields that you have security access to within a WQL query.

WQL and RaaS Usage Metrics Report

You can use this report to monitor usage trends for API requests over time. The report displays WQL and
Reports as a Service (RaaS) executions for outbound integrations. It returns counts for a rolling 90 days by
dimensions, such as time and source of request.
Note: You can only view report results in your Production tenant.
Related Information
Tasks
Register API Clients for Integrations
Reference
2022R2 What's New Post: Workday Query Language (WQL)
2022R1 What's New Post: Workday Query Language (WQL)
2021R2 What's New Post: Workday Query Language (WQL)
Reference: WQL REST API on page 219

Convert Reports to WQL Queries

Prerequisites
Security: Workday Query Language domain in the System functional area.

Context
You can convert advanced and matrix reports to Workday Query Language (WQL) and use the resulting
WQL query in integrations to extract data from Workday.

Steps
1. Access the Convert Report to WQL report.
2. Select a report to convert.
You can only select reports you have access to.
3. Complete any prompts that the report contains, as required.

Result
Workday displays the WQL query and indicates whether the query is valid. Some report definitions might
have configurations that prevent the report from creating a valid WQL query.
When advanced or matrix reports contain values in the Column Heading Override column, Workday
includes the value as an alias in the converted WQL query. When a report contains fields from related
business objects, Workday uses the value in the Group Column Heading column as the alias in the
converted WQL query.
Workday displays a table listing any components of the report that you can't convert to WQL.

Next Steps
Insert the WQL query into the query parameter of the WQL GET /data API call.
When your query exceeds 2,048 characters, insert the query into the request body of the POST /data API
call.

Related Information
Reference
Reference: WQL REST API on page 219

View WQL Query Results

Prerequisites
Security: Workday Query Language and WQL for Workday Extend domains in the System functional area.

Context
You can test Workday Query Language (WQL) queries in your tenant as an alternative to testing them in
third-party applications. Workday returns up to 500 rows of results, providing you with a response you can
use to continue developing your query.

Steps
1. Access the View WQL Query Result report.
2. Enter a WQL query for which you want to view sample results.
Workday truncates the results to 500 rows when you enter a query:
• Without a limit.
• With a limit greater than 500.
3. (Optional) To save the query for later use, enter a name for it and click Save.
You can access the Manage My Saved Filters report later to retrieve the saved query.

Example
When you enter this query:

SELECT location, count()

FROM allWorkers
GROUP BY location
ORDER BY count ()
LIMIT 4

Workday returns this table of results:

Location Count
Main Campus 419
Pleasanton 1042
San Francisco 1103
London 1172

To sort the results in descending order, specify:

ORDER BY count () desc

Related Information
Reference
Reference: Reporting Limits
Reference: WQL Result Limits on page 223

Concept: Related Business Objects in WQL

You can access fields from a related business object (RBO) in the SELECT clause using curly bracket {}
notation.
You can also filter query results by RBO fields using the WHERE ON clause. In WHERE ON clauses, omit the
curly bracket {} notation for the RBO fields.

Syntax

SELECT field1{relatedBusinessObjectField1, relatedBusinessObjectField2}

FROM dataSource

Example: SELECT dependents{age} FROM allWorkers

You can reference a single field or multiple, comma-separated fields from an RBO field.
You can also assign a custom alias to an RBO field. Example: dependents{age} as DependentsAge

Examples
Return the worker and multiple fields from the Dependents RBO in 1 group:

SELECT worker, dependents{legalName_FirstName, legalName_LastName, age}

FROM allWorkers

Return the worker and multiple fields from the Dependents RBO as separate groups:

SELECT worker, dependents{legalName_FirstName} as FirstName,

dependents{legalName_LastName} as LastName, dependents{age} as Age
FROM allWorkers

When you call multiple fields separately from the same lookup field, use a unique field alias.

Limitations
When the lookup field for the RBO is multi-instance, Workday only supports up to 500 values for the RBO
field. Example: You specify a worker as a primary business object and worker dependents as the RBO.
When the query returns more than 500 dependents for a worker, WQL displays an error.
You can’t access fields from RBOs:
• In queries that use a GROUP BY clause.
• Outside of the SELECT and WHERE ON clauses.
When you use a third-party API client, you might need to encode the query first. Some third-party clients
don't process curly bracket {} notation.
Example query before encoding:

SELECT worker, dependents{legalName_FirstName} as FirstName FROM allWorkers

Example query after encoding:

SELECT%20worker%2C%20dependents%7BlegalName_FirstName%7D%20as%20FirstName
%20FROM%20allWorkers

Related Information
Concepts
Concept: Business Objects, Data Sources, and Fields on page 13

Reference
2022R2 What's New Post: Workday Query Language (WQL)

Concept: Pagination of WQL Query Results

When you first execute a query, the Workday Query Language (WQL) in the query parameter runs and
builds a cache that returns a maximum of 10,000 rows. You can access additional rows by paginating
through the result set using the limit and offset parameters in the REST API call for your WQL query.
Note: WQL caches page limitation requests for only the length of a user session.
To view any remaining results, use these parameters:

Parameter Description
limit Specifies the number of rows in 1 page of results.
Values must be between zero and 10,000.
offset Specifies the starting row for the result set. Used by
the limit parameter.
In the initial request for the first page of results, omit
the offset parameter or set it to zero.

Note: Workday reserves the keyword LIMIT for both a clause and a pagination parameter. The LIMIT
keyword isn't case-sensitive.
• Use the LIMIT clause to limit the number of total rows returned in a query response.
• Use the limit parameter to specify how many rows to display per page of query response.

Examples
To return 1,000 rows starting with the first row of the result set:

https://{hostname}/ccx/api/wql/v1/{tenant}/data?
limit=1000&offset=0&query=select worker, location from allWorkers

To return the next 1,000 rows, increase the offset to 1,000:

https://{hostname}/ccx/api/wql/v1/{tenant}/data?
limit=1000&offset=1000&query=select worker, location from allWorkers

Related Information
Reference
Reference: WQL Result Limits on page 223

Reference: WQL REST API

Use the WQL REST API to return:
• A list of data sources and data source filters.
• Details about a specific data source.
• Fields in a data source.
You can use the information from the response to construct a WQL request in:
• The query parameter of the GET /data endpoint.
• The request body of the POST /data endpoint.
Base URL: https://{hostname}/api/wql/{version}/{tenant}
Base URL for Workday Extend: https://api.workday.com/wql/{version}

GET /data
Returns the data from a WQL query. Use this request for queries with less than 2,048 characters. You can
only view data you have security access to. You execute WQL using the query parameter.
Example: {baseURL}/data?query={myquery}
Example JSON response:

{
"total": 152,
"data": [
{
"location": {
"descriptor": "Academic Location WATS 1",
"id": "5403216f5ef810381796f3bb216504f5"
},
"max(yearsOfService)": "20"
},
...
]
}

Workday clears cached WQL query results after 15 minutes. To clear the cache manually, you can add
offset=0 to your query. Example:

{baseURL}/data?offset=0&query=SELECT firstName, location FROM allWorkers

POST /data
Returns the data from a WQL query. Use this request for queries between 2,048 and 16,000 characters.
You can only view data you have security access to. You execute WQL using the query parameter. Place
the query parameter and query in the request body of the API call.
Example: {baseURL}/data/
Example request body:

{
"query" : "SELECT firstName, location FROM allWorkers"
}

Example JSON response:

{
"total": 152,
"data": [
{
"location": {
"descriptor": "Academic Location WATS 1",
"id": "5403216f5ef810381796f3bb216504f5"
},
"max(yearsOfService)": "20"
},
...
]
}

GET /dataSources
Returns a collection of data sources for use in a WQL query.

Example: {baseURL}/dataSources
Example JSON response:

{
"total": 1722,
"data": [
{
"id": "6d34556ff015100012a60a4bb1ce0b92",
"descriptor": "Student Applications",
"alias": "studentApplications",
"description": "Accesses the Student Application object and
returns one row for each application. Includes data source filters with
built-in prompts. You can use this data source to list student applications
and related data."
},
...
]
}

GET /dataSources/{ID}
Returns a data source for the specified ID for use in a WQL query.
Example: {baseURL}/dataSources/1edd77f5e9754d71872102b5a5f2cd8
Example JSON response:

{
id*: string, // wid / id / reference id
descriptor: string, // A description of the instance
alias: string, // data source alias for WQL query
description: string,
filterIsRequired: boolean
}

GET /dataSources/{ID}/fields
Returns the fields of a specific data source for use in a WQL query.
Example: {baseURL}/datasources/1edd77f5e9754d71872102b5a5f2cd8e/fields
Example JSON response:

{
"total": 190,
"data": [
{
"id": "a2b4bca236de10001b3ee3180c190038",
"descriptor": "Academic Period",
"type": "Single instance",
"alias": "academicPeriod"
},
...
]
}

GET /dataSources/{ID}/dataSourceFilters
Returns the data source filters for a specific data source for use in a WQL query.

Example: {baseURL}/dataSources/6d34556ff015100012a60a4bb1ce0b92/
dataSourceFilters
Example JSON response:

{
"total": 6,
"data": [
{
"id": "432abca0a751100008144ff171b8000a",
"descriptor": "Student Applications for Admissions Cohort
Finalize Decisions",
"alias":
"studentApplicationsForAdmissionsCohortFinalizeDecisions",
"optionalParameters": [
{
"type": "Single Instance",
"description": "The Application Grouping for this
Student Application.",
"alias": "applicationGrouping"
}
],
"description": "Return Applications that are valid for
Publication with this Cohort\n- has an Admissions Decision\n- Decisions
Published Status is Confidential - For Internal Use Only\n- No Inactive
Status"
},
...
]
}

Related Information
Concepts
Concept: Workday Query Language (WQL) on page 215
Tasks
Register API Clients for Integrations

Reference: WQL Aliases

When you create Workday Query Language (WQL) queries, you use aliases to refer to:
• Data sources.
• Data source filters.
• Fields and calculated fields.
• Parameters (built-in prompts).
All Workday-delivered objects have a corresponding WQL alias. Workday creates aliases for calculated
fields, whether Workday-delivered or not. You can edit aliases for calculated fields.

Retrieving Aliases by REST API Calls

You can return WQL aliases by calling the appropriate REST API endpoint.
Base URL: https://{hostname}/api/wql/{version}/{tenant}
Base URL for Workday Extend: https://api.workday.com/wql/{version}

Alias REST API Endpoint

All data sources. GET {baseURL}/dataSources
Single data source. GET {baseURL}/dataSources/{WorkdayID}

Alias REST API Endpoint

All data source filters and associated prompts. GET {baseURL}/dataSources/{WorkdayID}/
dataSourceFilters
Single data source filter and associated prompts. GET {baseURL}/dataSources/{WorkdayID}/
dataSourceFilters/{WorkdayID}
Fields and calculated fields. GET {baseURL}/dataSources/{WorkdayID}/
fields

Retrieving Aliases in Workday

To retrieve aliases, you can:
• Create a custom report on the Data Sources or Fields report data source using the WQL Alias report
field. The report returns the WQL alias only for data sources that Workday has enabled for reporting.
• View WQL aliases for fields, calculated fields, or data sources from the related actions menu.

Reference: WQL Result Limits

WQL queries return a maximum of 1 million rows. Workday processes queries for up to 30 minutes, after
which they time out. Refer to this table for query and LIMIT clause behavior.

Rows Returned By Query LIMIT Clause in WQL Query Query Behavior

>1 million None Query fails.
>1 million <=1 million Query succeeds and returns a
maximum of 1 million rows. You
can view 10,000 rows at a time.
<=1 million None or <=1 million Query succeeds and returns all
rows. You can view 10,000 rows
at a time.

Reference: WQL and RaaS Comparisons

Use the tables to compare how Workday Query Language (WQL) and Reports as a Service (RaaS)
support the various ways you can extract data from Workday.

Feature Support Summary

Feature Supported by WQL Supported by RaaS

Access fields from a Global No Yes
business object.

Feature Supported by WQL Supported by RaaS

Use the percentile function as an No Yes
aggregation operator in SELECT
clauses.
Use the GROUP BY clause to Yes No
aggregate results.
Paginate results. Yes No

Use Cases

Use Case WQL Support RaaS Support

Group your extract by 1 or more Supported. Not Supported.
dimensions.
You can use the GROUP BY
clause to aggregate results by
various dimensions.

Download the results in partitions Supported. Not Supported.

instead of 1 large response.
You can paginate results 10,000
rows at a time using the LIMIT
and OFFSET parameters.

Extract data using web services. Supported with RESTful web Supported with RESTful and
services. SOAP web services.
Dynamically change the query Supported. Supported.
extract without signing in to
Because WQL requests are You can dynamically update
Workday.
string values, you can change the parameters in the URL.
request outside of Workday.

Persist the definition of an extract You can save a WQL query Supported.
to enable collaboration. outside of Workday.
RaaS is a Report as a Service
and, as such, can persist report
definitions in Workday.

Audit the extraction to identify Not Supported. Supported.

changes and revert them as
Because RaaS persists report
necessary.
definitions, you can track changes
through the Workday audit
framework.

Extract data from multiple Supported. Not Supported.

environments without having to
You can change the request URL To extract report from another
create or migrate reports across
for WQL as needed to point to tenant, you must migrate the
tenants.
any customer tenant. report to that tenant.

Extract small to moderately sized Supported. Supported.

result sets.
Up to 1 million rows. Up to 1 million rows.

Extract data within time limits. WQL queries time out at 30 RaaS processing times out at 6
seconds. hours.

Use Case WQL Support RaaS Support

Extract results in multiple formats. You can extract results in JSON. Supported. You can extract
results in these formats:
• CSV.
• GData.
• JSON.
• RSS.
• Simple XML.
• Workday XML.

Extract only the appropriate data Supported. Supported.

for the issuing user. WQL honors object and data- RaaS honors object and data-
level security based on the level security based on the
issuing user. issuing user.

Create outbound integrations Supported. You must have some knowledge

with only limited knowledge of of Workday reporting.
You don't have to understand the
Workday custom reports.
Workday Report Writer to use
WQL. WQL is similar to standard
database languages.

Start an integration from a Supported. Supported.

Workday standard report.
You can use the Convert Report You can copy and customize
to WQL report to convert standard and advanced reports
Workday advanced and matrix for outbound integrations.
reports to WQL.

Programmatically explore any of Supported. Not Supported.

these items:
WQL provides APIs for data You must create a report
• Data sources. sources, data source filters, and definition in Workday and
• Fields of data sources. fields. complete the prompts for data
• Data source filters. sources, filters, and fields.
To query any data sources, filters,
and fields in WQL, you must have
access to them in Workday.

WQL Reference
PARAMETERS
You can add a PARAMETERS clause at the beginning of a Workday Query Language (WQL) query to
specify built-in prompt values for:
• Data sources.
• Data source filters.
• Report fields.
Specify values for report fields in the PARAMETERS clause. You can specify values for data sources and
data source filters in the PARAMETERS or FROM clause, but not both.

Syntax

PARAMETERS parameter1 = value1,...parameterN

Arguments

Argument Description

parameter1, parameter2, ...parameterN The alias for a parameter.

value1, value2, ...valueN The value of the parameter that you want to query.

Comparison Operators

Operator Field Data Type Compatibility Description

= Boolean Equal.
Date
Numeric
Text

Examples
To specify the reportingDate parameter for the contractRates field and the company parameter for a
data source in the PARAMETERS clause:

PARAMETERS reportingDate = "2018-01-01", company =

cb550da820584750aae8f807882fa79a
SELECT contractRateSheet, contractRates
FROM contractRateSheetsForCompany

To specify the reportingDate parameter for the contractRates field in the PARAMETERS clause and
the company parameter for a data source in the FROM clause:

PARAMETERS reportingDate = "2018-01-01"

SELECT contractRateSheet, contractRates
FROM contractRateSheetsForCompany(company =
cb550da820584750aae8f807882fa79a)

To specify the parameters for a data source filter in the PARAMETERS clause:

PARAMETERS projectsAndProjectHierarchies =
(0c0bbf2e124810a26765415bb08406c5), includeSubordinateProjectHierarchies =
true
SELECT projectObject
FROM projects (dataSourceFilter =
projectsByProjectsProjectHierarchiesFilter)

Limitations
• You can only specify the same parameter once in the query. PARAMETERS field_1=val1,
field1=val2 is invalid.
• You must specify the dataSourceFilter in the FROM clause.
Related Information
Reference
FROM on page 228

SELECT
Returns field values from Workday data sources. Workday Query Language (WQL) requires this clause in
all queries.
You can only access fields that:
• Workday has authorized for use with the Workday Report Writer or default areas.
• The current processing Workday account has permission to access.

Syntax

SELECT field1 AS myAlias, function(field2),

field1{relatedBusinessObjectField1}, ...fieldN
FROM dataSourceAlias

Arguments

Argument Description
field1, field2, ...fieldN The WQL alias for the field you want to access.
If 2 or more fields have the same alias, WQL
returns the first field defined in Workday.

myAlias (Optional) Rename the column header in the

response.
Example: SELECT max(yearsOfService) as
Seniority
You can’t use a WQL keyword as a custom alias.
WQL doesn’t support escape character syntax.
WQL supports some special characters and spaces
in single or double quotes. Examples:
• ~
• @
• $
• *
• -
• _
• /
• ?
• :
• ;

function (Optional) You can use these aggregation functions

with fields:
• AVG(field)
• COUNT()
• COUNT(DISTINCT field)
• MAX(field)
• MIN(field)
• SUM(field)

Argument Description
COUNT() doesn't take any arguments.

relatedBusinessObjectfield1 The field of the related business object for which

you want to filter results.

Aggregation Functions

Aggregation Function Description

AVG(field) Returns the average value of a numeric field.
COUNT() Returns the number of instances matching the
query criteria.
COUNT (DISTINCT field) Returns the unique number of instances matching
the query criteria. Use only on text and single
instance fields.
MIN(field) Returns the minimum value of a field.
MAX(field) Returns the maximum value of a field.
SUM(field) Returns the total sum of a numeric field.

Example
To return worker information from a data source:

SELECT worker, fullName, location FROM allWorkers

Limitations
WQL doesn't support SELECT *.

FROM
Specifies the data source and data source filter the SELECT clause retrieves data from. Workday requires
this clause in any Workday Query Language (WQL) query.
You can only access fields that:
• Workday has authorized for use with the Workday Report Writer or default areas.
• The current processing Workday account has permission to access.

Syntax
To query data from a data source:

FROM dataSourceAlias

To query data from a data source with a data source filter:

FROM dataSourceAlias(dataSourceFilter=filterAlias, filterPrompt1=value1,

filterPrompt2=value2)

To query data from a data source using entry and effective date filters:

FROM dataSourceAlias(effectiveAsOfDate=date, entryMoment=dateTime)

Arguments

Argument Description

dataSourceAlias The alias for the data source you want to access.

dataSourceFilterAlias (Optional) The alias for the data source filter you
want to use.

effectiveAsOfDate (Optional) Run the query as of an effective date or

entry date. Only supported for Standard Workday-
effectiveAsOfMoment
delivered data sources.
entryDate
If you don't specify an effective or entry moment,
entryMoment the query returns results as of the current date and
time.
WQL supports these formats:
• Effective Date:
effectiveAsOfDate="2018-01-01"
• Effective Date and Time:
effectiveAsOfMoment="2018-01-01
11:45:08"
• Entry Date: entryDate="2019-01-01"
• Entry Date and Time:
entryMoment="2019-01-01 12:30:25Z"
WQL supports dates and datetimes in Coordinated
Universal Time (UTC) or Pacific Standard Time
(PST).
WQL returns an error if you specify an
effectiveAsOfMoment or an entryMoment
when the data source doesn't support these values.

value1, value2, ...valueN Values for the built-in data source prompts.

instance1, instance2, ...instanceN The Workday ID of the field value you want to
match.
When you run a query, Workday validates the
format of the Workday ID and fails the query when
the format is invalid.

inst_refId The reference ID type of a field in the conditional

expression.

referenceID The reference ID of the field value you want to

match.
Example: (inst_refId = referenceID)

Examples
Return worker name from the All Workers data source:

SELECT fullName FROM allWorkers

Return a student name, academic unit, and level from the Student Applications data source and by
specifying a data source filter:

SELECT firstName, academicUnit, academicLevel

FROM studentApplications (dataSourceFilter =
studentApplicationsByAcademicUnitAndAcademicLevel, academicUnit = {Workday
ID}, academicLevel = {Workday ID})

Return worker name in ascending order from the All Workers data source, using the effective moment and
entry moment of the data values.

SELECT worker
FROM allWorkers (effectiveAsOfDate="2018-01-01", entryMoment="2019-01-01
12:30:00")
ORDER BY worker ASC

WHERE
Specifies one or more conditional expressions that filter the results of the query. Workday evaluates
expressions in parentheses first in conditional expressions. Use the AND and OR logical operators to
separate conditional expressions in Workday Query Language (WQL).

Syntax

WHERE
field1 = value1
AND field2 IN (instance1, instance2)
OR field3 IN (inst_refId = referenceID)

Arguments

Argument Description

field1, field2, ...fieldN The alias for a field in the conditional expression.

value1, value2, ...valueN The value of the field you want to match.

inst_refId The reference ID type of a field in the conditional

expression.

referenceID The reference ID of the field value you want to

match.
You can filter by the reference ID with or without
double quotes.
Examples
• (inst_refId = "referenceID")
• (inst_refId = referenceID)

Comparison Operators
WQL supports dates and datetimes in Coordinated Universal Time (UTC) or Pacific Standard Time (PST).

Operator Field Data Type Compatibility Description

= Boolean Equal.
Date
Numeric
Text

> Date Greater than.

Numeric

>= Date Greater than or equal to.

Numeric

< Date Less than.

Numeric

<= Date Less than or equal to.

Numeric

!= Boolean Not equal.

Date
Numeric
Text

contains Text The comparison value is a subset

of the field value.
Case insensitive.
Example: Cat contains AT.

not contains Text The comparison value isn't a

subset of the field value.
Case insensitive.
Example: Cat doesn’t contain
dog.

endswith Text The comparison value is a subset

of field value. The last character
of the field value matches the
last character of the comparison
value.
Case insensitive.
Example: Cat ends with AT.

Operator Field Data Type Compatibility Description

in Instance The field matches 1 or more

possible values for a condition.
Text

is empty Boolean The field has no value.

Date
Instance
Numeric
Text

is not empty Boolean The field has a value.

Date
Instance
Numeric
Text

not in Instance The field doesn't match any

possible values for a condition.
Text

startswith Text The comparison value is a

subset of the field value. The
first character of the field value
matches the first character of the
comparison value.
Case insensitive.
Example: Cat starts with CA.

Date and Time Formats

Date and Time Format

Date YYYY-MM-DD
Time (24-hour clock) HH:MM:SS
Datetime with time zone PST: YYYY-MM-DD HH:MM:SS
UTC: YYYY-MM-DD HH:MM:SSZ

Examples
Return worker and location fields from the allWorkers data source where the location is San Francisco
and the Workday ID is a specific worker:

SELECT worker, location

FROM allWorkers
WHERE location in (Location_ID = San_Francisco_site) AND worker in
(3895af7993ff4c509cbea2e1817172e0)

Return billable transactions that were approved between 7:15 AM on August 1, 2020 and 7:45 AM on
August 30, 2020, using Coordinated Universal Time (UTC) by adding Z to the datetime values:

SELECT billableProject, projectCompany, approvalDate

FROM billableProjectTransactions
WHERE (approvalDate >= '2020-08-01 07:15:00Z' AND approvalDate <=
'2020-08-30 07:45:00Z')

Limitations
WHERE ON clauses must go before WHERE clauses.

WHERE ON
Specifies the fields to filter from related business objects (RBOs) in the SELECT clause. Workday
evaluates expressions in parentheses first in conditional expressions. Use the AND and OR logical
operators to separate conditional expressions in Workday Query Language (WQL).

Syntax

WHERE ON
relatedBusinessObject1 relatedBusinessObjectField1 = value1
AND relatedBusinessObjectField2 IN (instance1, instance2)
OR relatedBusinessObjectField3 IN (inst_refId = referenceID)
WHERE ON
relatedBusinessObject2 relatedBusinessObjectField1 = value1

Omit the braces { } notation for RBO fields.

Arguments

Argument Description

relatedBusinessObject1 The RBO of the fields for which you want to filter
results.

relatedBusinessObjectfield1, The fields of the related business objects for which

you want to filter results.
relatedBusinessObjectfield2, ...relatedBusinessObjectfieldN

value1, value2, ...valueN The values of the fields you want to match.

instance1, instance2, ...instanceN The Workday IDs of the field values you want to
match.
Workday fails queries with invalid ID formats.

inst_refId The reference ID type of a field in the conditional

expression.

referenceID The reference ID of the field value you want to

match.
You can filter by the reference ID with or without
double quotes.
Examples:
• (inst_refId = "referenceID")

Argument Description
• (inst_refId = referenceID)

Comparison Operators
WQL supports dates and datetimes in Coordinated Universal Time (UTC) or Pacific Standard Time (PST).

Operator Field Data Type Compatibility Description

= Boolean Equal.
Date
Numeric
Text

> Date Greater than.

Numeric

>= Date Greater than or equal to.

Numeric

< Date Less than.

Numeric

<= Date Less than or equal to.

Numeric

!= Boolean Not equal.

Date
Numeric
Text

contains Text The comparison value is a subset

of the field value.
Case insensitive.
Example: Cat contains AT.

not contains Text The comparison value isn't a

subset of the field value.
Case insensitive.
Example: Cat doesn’t contain
dog.

endswith Text The comparison value is a subset

of field value. The last character
of the field value matches the
last character of the comparison
value.

Operator Field Data Type Compatibility Description

Case insensitive.
Example: Cat ends with AT.

in Instance The field matches 1 or more

possible values for a condition.
Text

is empty Boolean The field has no value.

Date
Instance
Numeric
Text

is not empty Boolean The field has a value.

Date
Instance
Numeric
Text

not in Instance The field doesn't match any

possible values for a condition.
Text

startswith Text The comparison value is a

subset of the field value. The
first character of the field value
matches the first character of the
comparison value.
Case insensitive.
Example: Cat starts with CA.

Date and Time Formats

Date and Time Format

Date YYYY-MM-DD
Time (24-hour clock) HH:MM:SS
Datetime with time zone PST: YYYY-MM-DD HH:MM:SS
UTC: YYYY-MM-DD HH:MM:SSZ

Examples
Return results from the allWorkers data source and location RBO by workers who:
• Are over 50.

• Work more than 23 hours.

SELECT worker, location{addresses}, age FROM allWorkers

WHERE ON location addresses is NOT EMPTY
WHERE defaultWeeklyHours > 23 AND age > 50

Return results from the allWorkers data source and location and dependents RBOs by workers whose:
• Pay is a currency specified by a Workday ID.
• Dependents' last names start with the letter N.
• Age is over 50.
• Location is in 2 specific cities.

SELECT worker, location{addresses}, dependents{legalName_LastName}, age FROM

allWorkers
WHERE ON location addresses is NOT EMPTY AND currency in
(9e996ffdd3e14da0ba7275d5400bafd4)
WHERE ON dependents legalName_LastName startswith "N"
WHERE age > 50 OR location in (043e71ed793b1054de6213435945000c,
d13a7c46a06443c4a33c09afbdf72c73)

Limitations
WHERE ON clauses must go before WHERE clauses.
Related Information
Concepts
Concept: Related Business Objects in WQL on page 218
Reference
SELECT on page 227
2022R2 What's New Post: Workday Query Language (WQL)

ORDER BY
Sorts the results in ascending or descending order, based on 1 or more fields. WQL sorts data
alphabetically, not logically.

Syntax

ORDER BY
field1 ASC, field2 DESC

Arguments

Argument Description
field1, field2, ...fieldN The aliases for the fields by which you want to sort
your results.
ASC Sort results in ascending or descending
alphabetical order.
DESC

GROUP BY
Combines rows that have the same values into summary rows. Example: Group number of workers by
location.

Syntax

GROUP BY
field1, field2, ...fieldN

Arguments

Argument Description

field1, field2, ...fieldN The aliases for the fields by which you want to
group results.

Example
Return the location and the maximum years of service for a worker at that location from the allWorkers
data source:

SELECT location, max(yearsOfService)

FROM allWorkers
GROUP BY location

Limitations
You can't group by:
• Aggregated fields. Examples: SUM(field1), AVG(field1).
• Currency fields.
• Multi-instance fields.

HAVING
Filters a group or an aggregate by a search condition. You can only use HAVING with the GROUP BY
clause.
You can only access fields that:
• Workday has authorized for use with the Workday Report Writer or default areas.
• The current processing Workday account has permission to access.

Syntax

HAVING condition

Aggregation Functions
You can use these aggregation functions in a search condition:

Aggregation Function Description

MIN(field) Returns the minimum value of a field.
MAX(field) Returns the maximum value of a field.
SUM(field) Returns the total sum of a numeric field.

Example
Return the count of workers by location where the number of workers is greater than 100:

SELECT location, count() as Count_Workers

FROM allWorkers
GROUP BY location HAVING count() > 100

LIMIT
Returns records up to the maximum number that you specify.

Syntax

LIMIT integer

Arguments

Argument Description
integer The maximum number of records to return.

Example
Returns the full names for the first 10 records in the allWorkers data source:

SELECT fullName
FROM allWorkers
ORDER BY fullName ASC
LIMIT 10

Limitations
• LIMIT value must be greater than zero and less than 1 million.
• Because the LIMIT clause first retrieves the entire set of results before returning the number of records
you specify, using this clause doesn’t improve the performance of your query.

Business Form Layouts

Create Business Form Layouts with Report Designer in Workday Studio

Steps: Create a Business Form Layout

Prerequisites
Before you can prepare custom reports for use with a business form layout, you must complete these
prerequisites:

• Select .rptdesign as an enabled file type for uploading to Workday in Edit Tenant Setup - System. To
translate the static text in your report designs, you must also enable the .properties file type.
• Download and install Workday Studio, including Report Designer.
• Familiarize yourself with the Workday Studio documentation and tutorials for Report Designer.
In addition, for each report definition that you create, ensure that you're either the report owner or that the
report owner has shared the report definition with you. Also, ensure that the security for the report fields
permits all anticipated users to access the report. Otherwise, the report might display incomplete data for
some users.

Context
Creating a business form layout requires you to use both Workday and Report Designer. Perform step 1 in
Workday, and all subsequent steps in Report Designer. The steps for creating and using a business form
layout are as follows:

Steps
1. Prepare a Custom Report to Be Used with a Business Form Layout on page 239.
Prepare a custom report in Workday to use with a business form layout in Report Designer.
2. Create a business form layout for a custom report using Report Designer in Workday Studio.
See Steps: Create Business Form Layouts with Report Designer on page 248.
3. Upload a Business Form Layout and Attach It to a Custom Report on page 241.
Associate a report design (.rptdesign) file created with Report Designer in Workday Studio with a
custom report in Workday.
4. Run and Print a Custom Report that Uses a Business Form Layout on page 243.
Print a custom report using a business form layout associated with it in Workday.

Next Steps
Sign into Workday Studio and create the business form layout for the report.
Related Information
Concepts
Concept: Creating Business Form Layouts on page 244
Tasks
Create a Business Form Layout in Workday Studio on page 240
Run and Print a Custom Report that Uses a Business Form Layout on page 243
Upload a Business Form Layout and Attach It to a Custom Report on page 241
Reference
Reference: Edit Tenant Setup - System

Prepare a Custom Report to Be Used with a Business Form Layout

Prerequisites
Before you can prepare custom reports for use with a business form layout, ensure the following
prerequisites have been met:
• Select .rptdesign as an allowed file type for uploading to Workday in Edit Tenant Setup - System.
• Download and install Workday Studio, including Report Designer.
• Familiarize yourself with the Workday Studio documentation and tutorials for Report Designer.
In addition, for each report definition that you create, ensure that you are either the report owner or that the
report owner has shared the report definition with you.

Context
The following steps take place in Workday (as opposed to Workday Studio). After completing the steps
below for preparing a custom report for use with a business form layout, you can then use Workday Studio
to create a report design file (which defines the layout) for the report.

Steps
1. Sign in to Workday.
2. Identify or create the custom report for which you want to create a business form layout. The custom
report must be of the Advanced report type.
3. On the Advanced tab of the report definition, select the Enable As Web Service option.
4. Optionally, follow the steps below to save the report data (XML) and XML schema (XSD) for later use
in Workday Studio. You can browse for and use web-enabled reports that are stored in either your
Sandbox or Production tenant directly within Report Designer. So this step is necessary only if you want
to work with your report design offline in Workday studio (that is, when you are not connected, or do not
have the ability to connect to, your Workday tenant). To export the report data and schema, follow the
steps below.
a) As a related action on the report, select Web Service > View URLs.
b) Select Workday XML > REST > Workday XML. When the XML source code appears, save it as an
XML file to your local drive.
c) Select Workday XML > XSD > XSD. When the XSD source code appears, save it as an XSD file
to your local drive. (Note: Use your browser's Save Page As feature to accomplish this step. Do not
copy and paste the text from the browser. Copying and pasting is error prone, especially in cases
where characters from non-western fonts are used.)
After completing this step, you'll have 2 files (an XML file and an XSD file) on your local drive that you'll
use as a basis for creating a business form layout in Workday Studio.
Note: The Workday XML saved in step 4 contains whatever data is returned by the report definition.
Therefore, you should consider security and privacy policies when deciding where to store the XML file
and who should have access to it.

Next Steps
Sign into Workday Studio and create the business form layout the report. For more information, see Create
a Business Form Layout in Workday Studio on page 240.
Related Information
Tasks
Steps: Create Advanced Reports on page 106
Reference
Reference: Edit Tenant Setup - System

Create a Business Form Layout in Workday Studio

Prerequisites
Prepare a Workday custom report for use with a business form layout.

Context
These steps take place in Workday Studio, not Workday. After completing the steps below for creating a
business form layout, you can then deploy the report design directly from Workday Studio. You can also go
back into Workday and attach the business form layout to a custom report.

Steps
1. Sign in to Workday Studio.
2. Navigate to Report Designer.
3. When selecting your Workday Report Data Source, get the report description and report data by
connecting directly to your Workday tenant. You can also follow the documentation in Workday Studio
to import the report data (XML) and XML schema (XSD) you previously saved from Workday to create
your business form layout.
4. Either deploy the report design directly from within Workday Studio, or save the business form layout as
an .rptdesign file type on your local drive.

Result
After completing this step, you've either deployed the report design directly from Workday Studio or had an
.rptdesign file type on your local drive. If you opted to save the .rptdesign file to your local drive, you must
attach this file to a custom report in Workday.

Next Steps
If you don’t deploy your report design directly from Workday Studio, sign into Workday to upload your
business form layout and attach it to a custom report.

Upload a Business Form Layout and Attach It to a Custom Report

Prerequisites
Before uploading a business form layout and attaching it to a custom report, you must first create a
business form layout in Workday Studio using Report Designer.

Context
If you have associated a report design (an .rptdesign file) with a Workday custom report directly in
Workday Studio, then your business form layout is already attached to your custom report, and the use of
the process described in this topic isn't necessary.
These steps take place in Workday (as opposed to Workday Studio). After completing the steps below for
uploading and attaching a business form layout to a custom report, you can then run the report and use the
custom layout.
You can attach multiple custom layouts to a single report definition. However, a single custom layout can
be associated with only 1 custom report.

Steps
1. Sign in to Workday.
2. As a related action on the report to which you want to add a business form layout, select Layouts >
Manage Layouts.
3. From the Manage Layouts grid, click + (the plus icon) to add a new row for a new business form
layout.
4. Click the prompt button on the right side of the new row.
5. From the prompt, select Create > Create Business Form Layout and click OK to attach a new
business form layout.
This step opens the Create Business Forms Layout task. (You also can access the Create Business
Form Layout task directly from the Workday search bar or from the Workday menu.)
From the prompt, you also can select Active Custom Business Forms using Report Design to
select from a list of existing business form layouts that have previously been attached to this report.
Another option is to select Active Custom Business Forms using Stylesheet. You would only use
this option if you needed to attach an XSL stylesheet to define the business form layout, rather than

using a business form layout created in Report Designer. In general, this documentation assumes that
you would use Report Designer to create a business form layout, which is typically the best practice.
6. Enter a Description for the business form layout.
7. Click the Active check box to enable this business form layout to display in the Active Custom
Business Forms using Report Design prompt.
8. Enter a number of days for the Resulting Document Expiration Offset (in Days). This is the number
of days that the resulting document (the PDF printed using the business form layout) will be available in
Workday after you generate it. The maximum value allowed is 25,000.
Note: Ensure that the expiration offset you specify here complies with your organization's document
retention policy. Workday automatically deletes documents after the offset number of days. You can't
recover these documents.
9. Optionally enter a Comment for the business form layout.
10.Select Report Design and click the associated prompt button.
11.From the prompt, select Create > Create Custom Business Form Report Design Attachment.
12.Click Select files and select the .rptdesign file you created in Report Designer. You can also drag and
drop the file onto the task.
13.Click Upload to upload the selected .rptdesign file and then click OK.
14.The Apply Report Design separately to each row setting affects how Workday uses the .rptdesign
file when generating a PDF document. This is a design decision for the author of the .rptdesign file.
Consult with them before selecting the check box. More details on this setting and a description of its
implications are included in the documentation on Report Designer in Workday Studio.
15.Select the Override Streamlined Document Processing option if applicable.
16.Select the Force printed PDFs to download option to override the Force printed PDFs to download
setting in Edit Tenant Setup - System for a specific business form layout. Example: You have a large
custom report that you want to email or save.
17.Select the Custom Report to which you're attaching the business form layout.
18.Select any Tokens to be used with this business form layout.
You can upload image files to use in your business form layout, such as a company logo or a signature
image. Each image must be given a Token Name in the business form layout. Click + (the plus icon) in
the Tokens grid and enter a token name for each image that your business form layout will use. Click
OK when all required token names are created. (Don't click Close.)
If you do add tokens, then after you finish creating the business form layout, you must also configure it
as follows:
a. As a related action on the business form layout, select Business Form Layout > Configure.
b. Select a Token.
c. To the right, click Browse and select an image file from your local drive or network. Images can be
in BMP, GIF, JPEG, or PNG format.
d. Click Upload to upload the image to Workday.
e. You can optionally add a Comment to clarify the nature of the image (example: logo or signature).
You can return to Configure Business Form Layout if you need to delete or change an image.
f. Click OK; then click Close.
Note: Tokens are needed only if the report design created in Workday Studio requires them. If you're
unsure if tokens are needed, consult the person who created the .rptdesign file.
19.(Optional) Specify your translation preferences for the business form. You can upload translation
properties files to provide translations of static text in your business form layouts. This enables you to
output business forms in multiple languages from a single report design. Specify .properties as a valid
upload file type in the File Type Setup Instructions section of the Edit Tenant Setup - System task.
Then specify any previously uploaded Translations properties files (or create new ones) as follows:
• Select a User Language and an associated Custom Business Form Report Design Translation
Attachment. Each attachment should correspond to a translation properties file that you've

uploaded. You have the option to create a new translation attachment directly from this task, in
which case you can browse for and upload a translation properties file from your computer.
• Select Default Translation to set the default translation language. This is the language that will be
used to print the business form if there isn't a translation available in the user's preferred language.
20.If the attached business form layout is to be the default layout, then as a related action on the report,
select Layouts > Manage Layouts and select the business form layout as the Default Print Layout.
Specify a default print layout even if there's only a single business form layout attached to the report.

Result
After completing this step, you'll be able to achieve the final objective of printing a custom report using an
attached business form layout, since a relationship between these 2 objects has now been established.

Next Steps
The final step is to print the custom report using the business form layout you've created. For more
information, see Run and Print a Custom Report that Uses a Business Form Layout on page 243.
Related Information
Tasks
Create a Business Form Layout in Workday Studio on page 240

Run and Print a Custom Report that Uses a Business Form Layout

Prerequisites
Before printing a custom report that uses a business form layout, you must first upload a business form
layout (defined by an .rptdesign file) to Workday and attach it to the custom report.
PDFs generated for Workday custom reports may require you to install language packs when viewing
the document using Adobe Reader. Adobe Reader will prompt you and install the language pack for
you. This task only needs to be completed once. This is likely to happen if you are viewing a PDF that
includes Chinese characters on a computer that is not typically used for viewing Chinese documents. This
is normal behavior and helps to reduce the size of the PDFs by not including the required fonts in every
PDF generated.

Context
The following steps take place in Workday (as opposed to Workday Studio). This is the final step in using
a business form layout: printing a report that uses the business form layout that you've designed in Report
Designer.

Steps
1. Sign in to Workday.
2. Select and run a custom report that has a business form layout attached.
Note: You also can print a business form from the report step of a business process.
3. Print the report.
When you run a report that has a business form layout attached, a Print button appears and persists at
the bottom center of the browser window. It is always visible, even when you scroll vertically. To print
the report using the business form layout, select either:
a) The Print button described above.
b) The standard Print icon located at the top right of all custom report results.
If you schedule the report using the Schedule a Report task, and multiple business form layouts are
available for the report, you can identify exactly which business form layout to use for the scheduled
report. To do so, select the Business Form (PDF) output type on the Output tab of the Schedule a
Report task, and specify the business form layout to be used.

4. When a business form is finished processing, a message appears near your sign-in name and you
receive a notification in your Workday inbox.

Result
A PDF is generated based on the report definition and the selected business form layout. If there is only a
single business form layout for the report, then the process of generating the PDF file starts immediately
when you select to print the report. If multiple, active business form layouts are attached to the report, then
you are prompted to select which business form layout to use before the PDF is generated.
When the PDF file generation is complete, the resulting PDF file is sent to My Reports and you receive
an inbox notification. Note that if you use Process Monitor to check the status of a report that you've
attempted to print, the name of the process is Print Service Retrieve Report and Generate PDF.
If the total time required to run a custom report and generate the associated PDF document using a
business form layout exceeds 2 hours, the process terminates, and its status in Process Monitor changes
from Processing to Failed. Similarly, if the Print Layout page discussed in step 4 above is still open, it also
displays a message to alert you that the process has failed.
Related Information
Concepts
Concept: Report Step
Tasks
Upload a Business Form Layout and Attach It to a Custom Report on page 241

Concept: Creating Business Form Layouts

Workday enables you to design and use business form layouts for meeting the exact layout specifications
required by your organization. These specifications might include rich text formatting, headers and footers,
page breaks, and exact placement of labels, data, spaces, and margins. Report Designer in Workday
Studio enables you to use all these types of layout features and more. It is an easy-to-use, graphical layout
tool designed specifically for this purpose.
Note that Workday enables you to share your report designs with other Workday customers through
solutions sharing. You can upload your report designs so that other customers can use them or modify
them. Similarly, you can download and use report designs created by others.

Use Cases for Business Form Layouts

Workday delivers a number of business form layouts as part of individual Workday applications. However,
you also have the ability to create custom business form layouts as needed. There are 3 main scenarios
for which you might create a business form layout:
• You want to use a business form layout for a custom report that you've created in Workday.
• A Workday-delivered report (a standard report) has a delivered business form layout, but you want
to override the delivered business form layout with a custom business form layout. Depending on
the specific application with which the layout is used, you might have the ability to override the
delivered business form layout directly within the application as described in your Workday application
documentation. In addition, you also have the ability to copy any Workday standard report to a custom
report; you can then attach a custom business form layout to the custom report. For more information
on copying a standard report to a custom report, see Concept: Custom Reports on page 12.
• You want to use a custom business form layout for a standard report that does not have a delivered
business form layout. As with the preceding case, you'd first have to copy the standard report to a
custom report.

Business Form Layout Considerations

The following recommendations can help you be successful when creating and using custom business
form layouts:

• Use Workday's Custom Report Writer to get the data you want, and use Report Designer to
get the layout you want. Report Designer is a powerful tool, and it might be tempting to use all of its
capabilities, including the ability to filter and manipulate data. However, because it is critical that you
keep your report definition (in Workday) in sync with your custom business form layout (in Workday
Studio), it is highly recommended that you follow the approach below:
• In Workday: Use the Custom Report Writer to create an advanced report definition that completely
satisfies the data reporting requirements for a given report, including any filters, calculated fields,
and so on.
• In Workday Studio: Use Report Designer solely to manipulate the layout of the report. It's generally
best to avoid using this tool to manipulate data, filter report results, or make calculations.
Using this approach not only helps to keep your report definition and business form layout in sync, but
also makes your reporting solution easier to understand, modify, and troubleshoot.
• Keep your Workday report definition and business form layout in sync. If you delete a field from
your report definition (like Legal Name - First Name, for example) and that field is used by a business
form layout, the business form layout will replace the deleted field (Legal Name - First Name, in this
case) with a blank space. On the other hand, if you add a field to an existing report definition upon
which a business form layout is based, the business form layout ignores the new field, unless you
update the business form layout to reflect the new field.
Related Information
Concepts
Concept: Custom Reports on page 12
Reference
Reference: File Size and Printing Limits
Reference: Supported Configuration Types for Solutions

Workday Report Designer

Setup Considerations: Report Designer

Note: The solutions described in this section are not part of the Workday Service. See Legal Notice for
details.
You can use this topic to help make decisions when planning your configuration and use of Workday
Report Designer. It explains:
• Why to set it up.
• How it fits into the rest of Workday.
• Downstream impacts and cross-product interactions.
• Security requirements and business process configurations.
• Questions and limitations to consider before implementation.
Refer to detailed task instructions for full configuration details.

What It Is
Report Designer is a graphical tool for working with business form layouts. A business form layout is a
specific design that you can apply to a PDF containing the results of a Workday report.
Many Workday-delivered reports have built-in business form layouts. You can use those existing layouts
without reference to Report Designer. However, you do need Report Designer to customize them or to
create your own from scratch for use with your custom reports.

Report Designer isn't available in your Workday tenant. It's a separate tool, based on the Eclipse platform.
You must download and install the latest version of Workday Studio, before you can install Report
Designer.

Business Benefits
Report Designer gives you control over the exact layout and composition of your Workday report PDFs. It
enables you to tailor your presentation of Workday data to your exact business requirements.
You can use Report Designer to customize:
• Rich text formatting.
• Charts and graphs.
• Images and logos.
• Tables.
• Headers and footers.
• Page breaks.

Use Cases
There are 3 main scenarios in which you should use Report Designer:
• You want to override the existing business form layout for a Workday-delivered report.
• A Workday-delivered report doesn't have an existing business form layout and you want to create one.
• You want to create a business form layout for a custom report you've created in Workday.

Questions to Consider

Question Considerations
Do existing Workday report layouts meet my Report Designer is an entirely optional
needs? supplemental tool. If every Workday report you run
has a business form layout that meets your needs,
you don't need to use Report Designer.
Do I have an existing Workday Studio installation? Workday Studio is an integration-building tool.
It contains a menu option that enables you to
download Report Designer. However, you need
to install the latest version of Workday Studio first.
When the process is complete, Studio and Report
Designer are separate perspectives in your Eclipse
installation.
Do I have a Java Development Kit installed? Workday Studio requires a Java™ Development
Kit (JDK) that's compatible with Java version 8.
Install a suitable JDK before you can install Studio.
And you must install Studio before you can install
Report Designer.

Recommendations
Although Report Designer is an application of the Eclipse Business Intelligence and Report Tools (BIRT)
project, don't install the BIRT engine separately. The Install Report Designer option under Studio's
Workday menu provides everything you need.
You can preview your report design PDFs in Report Designer, but you should always perform final testing
in Workday.

Requirements
Before installing Report Designer, you must download and install Workday Studio. Studio requires a Java™
Development Kit (JDK) that's compatible with Java version 8.
Before using Report Designer, you must select .rptdesign as an allowed file type for uploading to Workday
in the Edit Tenant Setup - System task.

Limitations
Report Designer can only work with Advanced custom reports. You can't base your design on multiple
reports.

Tenant Setup
To use the custom layouts for Report Designer, you must override Workday-delivered layouts in the
relevant functional area. You can find details in the Edit Tenant Setup topic for that functional area.

Security
To generate a PDF from a report, you must have security permission to view all of its fields, so self-service
isn't always possible. Example: an Administrator might need to generate Compensation Statements
because individual workers lack security for some of the relevant fields.

Business Processes
You can use a Report Designer custom layout in a Business Process as a part of a Report step.

Reporting
You can base your report design on any single Advanced custom report.

Integrations
You can use Report Designer custom layouts to create PDFs in Studio integrations.

Connections and Touchpoints

Workday offers a Touchpoints Kit with resources to help you understand configuration relationships in your
tenant. Learn more about the Workday Touchpoints Kit on Workday Community.
Related Information
Concepts
Setup Considerations: Print Checks and Advices
Setup Considerations: Payslips
Tasks
Download and Install Workday Studio
Reference
The Next Level: BIRT: Report Designer
The Next Level: General Tips and Tricks
The Next Level: How to Get Started With BIRT
The Next Level: BIRT Resources Guide
The Next Level: BIRT Job Aids

Creating and Deploying Report Designs

Steps: Create Business Form Layouts with Report Designer

Context
Before you can create a business form layout in Workday, you must create a report design. A report design
requires a project, a design file, and data from a Workday report.

Steps
1. Create Report Design Projects on page 248.
Create a report design project to provide a framework that collects all files associated with your report
design.
2. Create Report Design Files on page 248.
Report design files are where you define the layout of your design.
3. Create Data Sources on page 249.
Provide an XSD schema that describes the custom report and an XML file that contains sample data.
4. Create Data Sets on page 250.
Configure the data available from a data source.
5. Create and preview your report design.
6. Deploy Report Designs to Workday on page 251.
You must deploy your design to Workday before you can use it as a business form layout.
Related Information
Reference
The Next Level: Build BIRT Expertise - Video Shorts

Create Report Design Projects

Prerequisites
Open the Report Designer perspective.

Context
You must create a report design project to provide a framework that collects all the files associated with
your report design.

Steps
1. Create a new project from the File menu by selecting New > Project.
2. Select Business Intelligence and Reporting Tools > Report Project.
3. Enter a Project name. Your new project displays in the Navigator view.

Create Report Design Files

Prerequisites
Create a report design project.

Context
A report design file is where you define the custom arrangement that you want to deploy to Workday as a
business form layout.

Steps
1. Create a new report from the File menu by selecting New > Report.
2. Select a project and provide a name for the report design. Report design files have the filename
extension .rptdesign.
3. Select a template to apply to your design.
Related Information
Reference
The Next Level: Report Design Files and Configurations

Create Data Sources

Prerequisites
Create a report design file.

Context
To create a report design, you must provide a description of the custom report in the form of an XSD
schema and, if you want to preview the design locally, some sample data in the form of an XML file.

Steps
1. In the Data Explorer view, right-click Data Sources and select New Data Source.
2. You must first specify the custom report XSD schema that you would like to use with your report design.
Accept the default selection of Create from a data source type in the following list. From the list of
data source types, select Workday Report Data Source.
3. Enter a Data Source Name.
4. If you are not already connected to your Workday environment, click Update Your Connection
Details. Specify your connection details.
5. To select a report description from your Workday tenant, click From Workday. If you have previously
downloaded an appropriate XSD schema, click Local Description File to select it from your local
machine.
6. If you click From Workday, the Report Browser dialog box opens on the Filter Custom RaaS
Reports section. Here you can use the Environment drop-down list and the Reports owned by me
check box to filter the reports that Studio offers for your selection. You can also enter the report name,
or part of it, in the Report name field.
7. From the list of filtered reports in the Select Report section, select the one that you want to use in your
report design.
8. If you wish to preview your design locally without deploying to Workday, you must specify sample data
for the report design. To select sample data from your Workday tenant, click From Workday. If you
have previously downloaded an appropriate XML file, click Local Data File to select it from your local
machine.
9. If you click Download from Workday, the Download Sample XML Report dialog box opens. Specify
the report design Project you're working on and enter a File name for the sample data XML file. Note
that by default, the Download Report Subset check box is selected, which limits the downloaded
report to 10 entries. Click Download.

10.After you specify the XML schema and sample XML for your Workday Report Data Source, click Test
Connection. Report Designer checks that the XSD and XML files exist, the XSD schema file is valid,
and the sample XML is valid.
11.The new data source displays in the Data Explorer view.
Note: One efficient way to unit test is to download a custom report run's data and schema (XML and
XSD files, respectively) and assign them as the data source for a BIRT report design. Doing so enables
you to assess the result as you add each data element to the design. You can test various scenarios by
adding new fields (update both the XSD and XML files) or by manipulating the XML data.

Create Data Sets

Prerequisites
Create a report design data source.

Context
Data sets define which data is available to a report design from a data source.

Steps
1. In the Data Explorer view, right-click the Data Sets folder and select New Data Set. The New Data
Set wizard opens.
2. Under Data Source Selection, select a data source. You can filter the available data sources by
entering text in the filter field.
3. Enter a Data Set Name, then click Finish to open the Edit Data Set window.
4. As you complete the task, consider:
Option Description
Data Source Displays the data source that the data set is
based on. You can only use 1 data source in
Report Designer, so there are no options in the
Select Data Source drop-down list.
Output Columns Displays the XML schema element values for
each of the columns that you added as rows to
your custom report in Workday. Select an output
column and click Edit to change Type, Alias,
Display Name, or Display Name Key.
Computed Columns Displays each of the computed columns that
you added as rows to your custom report in
Workday. Select a computed column and click
Edit to change its Column Name, Data Type,
Expression, Aggregation, or Filter. You can
also click New to add new computed columns but
this is bad practice. Always add new computed
columns in Workday.
Filters Displays any filters you defined in Workday to
reduce the number of rows included in the output
document. Select a filter and click Edit to change
its Expression, Operator, or Value. You can
also click New to add a new filter but this is bad
practice. Always add new filters in Workday.

Option Description
Settings Enables you to change the number of rows that
Report Designer retrieves from the report data
source. By default, it retrieves every row. To set a
limit, clear the Fetch all rows from data source
check box and enter your preferred maximum
number of rows in the Max number of rows to
fetch from data source field.
Preview Results Enables you to preview the data set results that
Report Designer retrieves from the specified data
source.
5. The newly created data set displays in the Data Explorer view, with 1 element for each of the fields in
the relevant custom report. Expand the data set element to view the data fields that it contains.

Deploy Report Designs to Workday

Prerequisites
Ensure that your tenant is configured to upload files with the .rptdesign extension to Workday.

Context
When you've finished work on your report design, you must deploy it to Workday before you can use it as a
business form layout.

Steps
1. In the Navigator view, right-click your report design file and select Deploy > Deploy to Workday.
2. In the Deploy Report Design to Workday dialog box, click Select Custom Report to specify the
relevant custom report in Workday. The correct custom report might already be named in the Custom
Report field.
3. In the Create or Select a Business Form Layout for which to Deploy this Report Design section,
the Create Business Form Layout check box is selected by default. To specify a business form layout
for which you've already deployed the report design, select the Select Business Form Layout check
box and select from the associated drop-down list.
4. As you configure the business form layout, consider:
Option Description
Description Use this field to enter a description for the
business form layout.
Active This check box, which is selected by default,
activates the layout for the custom report.
Document Expiration Use this field to enter the number of days until the
resulting PDF document expires. If you need to
access the PDF after expiration, you can rerun
the report.
Comment (Optional) Use this field to enter a comment.
Apply per row This check box, which is selected by default, tells
Workday to apply the report design to each row of
the relevant custom report. If you clear the check

Option Description
box, Workday applies the report design to the
report's data as a whole.
Use as the Default Business Form Layout This check box is only enabled if there's already
a report design associated with the custom report
in Workday. If there is, select the check box to set
the current design as the default business form
layout for printing the custom report.
5. Click Deploy.

Concept: Report Designer Overview

When you run a report, Workday displays the results and enables you to download a PDF version. You can
associate this PDF with a specific design called a business form layout. Report Designer is a graphical tool
that enables you to create your own designs. Then you can deploy them as business form layouts in your
Workday tenant.
There are 3 main scenarios in which you might use Report Designer:
• You want to create a business form layout for a custom report you've created in Workday.
• Workday provides a standard report with a delivered business form layout, but you want to customize
the business form layout.
• You want to use a customized business form layout for a standard report because it doesn't have a
Workday-delivered business form layout. For this use case, make sure to first copy the standard report
to a custom report.
Workday provides Report Designer as part of the Workday Studio Eclipse development environment and
uses the open-source Business Intelligence and Reporting Tools (BIRT) software. Ensure that you have
the latest version of the Workday Studio.
Report Designer gives you control over a number of useful design factors, including these elements:
• Rich text formatting.
• Charts and graphs.
• Images and logos.
• Tables.
• Headers and footers.
• Page breaks.
Related Information
Reference
The Next Level: BIRT: Report Designer
The Next Level: General Tips and Tricks

Concept: Data Sources, Data Sets, and Tables

When creating a report design, you must provide a description of the report's structure and some sample
data. Together, these are known as the design's data source.
Note: If you wish to apply your design to a custom Workday report, the report must be enabled as a web
service. The Enable as Web Service option is only available on Advanced custom reports.
You use the Report Designer Data Source wizard to retrieve the report's structure in the form of its XML
Schema and sample data in the form of an XML file.
Report Designer displays the data structure of the source Workday report as Data Sets. Each data set
displays the fields that were defined for a business object in the report.

A Workday report can contain fields from secondary business objects that are related to the primary
business object. Report Designer displays fields from any secondary business objects as additional data
sets. A report can also contain individual fields that occur multiple times. Report Designer displays these
fields as additional data sets too.
In Report Designer, you use tables to present the data taken from a Workday report. You can create tables
by dragging whole data sets into your report design. Each row in the report has a corresponding column in
the table.
Note: It is best practice, when possible, to base your report design on a single table or grid.

Reference: Data Type Mapping

Workday supports a fixed set of data types in its reports. Report Designer data types can differ slightly.
This table describes how Workday data types map to Report Designer data types.

Workday Data Type Report Designer Data Type Notes

Text String
Decimal Decimal
Boolean Boolean By default, Boolean data type
values display as true or false
in a report's PDF. However, you
can add logic to the report design
(using a JavaScript expression,
for example) to have it display
yes or no in the PDF instead.
Date Date
DateTime Timestamp
Currency Decimal Workday provides a Show
Currency Code Column option
for currency values. If you select
this option when creating or
editing a custom report, Workday
displays an additional Currency
column when you run the report.
In Report Designer, this selection
translates to an additional
Currency field in the data set.
Multi-instance Secondary Data Set Multi-instance type fields
represent the one-to-many
relationship a primary business
object has with a related business
object. A multi-instance field can
contain multiple values, with each
value representing an instance in
the related business object that
is linked to the primary business
object.
Reference ID String A Reference ID is a unique
identifier for a specific instance of
a business object in Workday.

Workday Data Type Report Designer Data Type Notes

Rich Text String Report Designer treats rich text
values as strings. However,
these values can contain HTML
tags. To display the formatted
text in a PDF, rather than the
HTML tags, use the Dynamic
Text component from the Report
Designer palette.

Designing and Formatting Reports

Add Labels to Report Designs

Prerequisites
Create a report design file.

Context
Use labels for static text that will need to be translated.

Steps
1. Drag a Label report item from the Palette to the required position on the Layout tab of the main view.
An empty text field displays.
2. In the empty text field, enter text for the label.
3. Use the Properties tab of the Property Editor view to configure the properties of the label. Note that
you can apply formatting to a label as a whole but you can't format individual words.

Add Text Blocks to Report Designs

Prerequisites
Create a report design file.

Context
Use text blocks for longer pieces of text. Text blocks can contain plain text, HTML, or inline expressions.

Steps
1. Drag a Text report item from the Palette to the required position on the Layout tab of the main view. An
empty text box displays.
2. Enter your text in the large blank space.
3. To tell Report Designer how to interpret your text, select the relevant option from the content type drop-
down list:
• Auto
• HTML (default)
• Plain

4. When entering HTML, you can add tags manually or use the tag shortcuts on the toolbar. To use
the shortcuts, highlight the relevant text and click a tag in the toolbar. Report Designer adds the tags
around the selected text.
5. To change the type of tags that are displayed in the toolbar, select from the category list on the left of
the toolbar. The options are:
• Formatting
• Layout
• Content
• Lists
• Dynamic Text
Report Designer interprets dynamic text as JavaScript. Select this option when you want to use an
expression to manipulate data before the report displays it.You can edit the text box again at any time
by double-clicking it.

Add Dynamic Text to Report Designs

Prerequisites
Create a report design file.

Context
Use dynamic text to create expressions using a combination of literal values, fields, operators, variables,
and functions that evaluate to a single value.

Steps
1. Drag a Dynamic Text report item from the Palette to the required position on the Layout tab of the
main view.
2. Enter your expression in the Expression field. Enclose literal text in double quotation marks. Use the
shortcut buttons to quickly add operators. Add terms by making selections in the Category and Sub-
category lists, then double-clicking in the Double click to insert list.
3. If you're adding dynamic text to a table that's bound to a data set, the Available Column Bindings
option displays in the category list, showing rows from that data set.

Add Rotated Dynamic Text to Report Designs

Prerequisites
Create a report design file.

Context
You can add rotated text to your report designs using angles of 90, 180, or 270 degrees. Report Designer
treats rotated text as an image and might not always render it perfectly, so you should use this feature only
when strictly necessary.

Steps
1. To add rotated text to your report design, drag the Rotated Dynamic Text item from the Palette view to
the required position on the Layout tab of the main view.
2. To add literal text, enter it between quotation marks in the Text Content field.
3. To add an expression, click Invoke Expression Builder. Enter your expression in the Expression
field. Enclose literal text in double quotation marks. Use the shortcut buttons to add operators quickly.

Add terms by making selections in the Category and Sub-category lists, then double-clicking in the
Double click to insert list.
4. From the Rotation Angle drop-down list, select 0, 90, 180, or 270 degrees.

Add Data Sets and Data Set Fields to Report Designs

Prerequisites
Create a report design file.

Context
Data sets define which data from a report is available to a report design. You can add an entire data set to
a design to form a table or you can add data set fields individually.

Steps
1. To add an entire data set to a report design, drag the data set node from the Data Explorer view to the
required position on the Layout tab of the main view.
2. Select the Workday report columns that you want to bind to columns in the report design, then click OK.
Report Designer adds the data set to your design in the form of a table.
3. To add an individual data set field to a report design, drag the field node from the Data Explorer view to
the required position on the Layout tab of the main window.

Add Images to Report Designs

Prerequisites
Create a report design file.

Context
You can add 2 types of images to your report designs: images that are part of a layout, such as company
logos, and images that Workday returns as reports results data.

Steps
1. Drag an Image report item from the Palette to the required position on the Layout tab of the main view.
2. Select a source for your image. As you do so, consider:

Option Description
URI This option enables you to specify a web link to
an image. You can also specify tokens, which you
create in the Workday application by uploading
images to the business form layout configuration.
Using tokens means that you don't have to update
your report design when you change an image in
Workday. Report Designer displays a placeholder
for token images, rather than the image itself.
Embedded image This option enables you to browse to an image
file. Report Designer embeds the image in the
report design.
Dynamic image This option enables you to include images that
are returned as report results data.

3. To add a URI, enter the web link or token in the Enter URI field.
4. To add an embedded image, click Add Image and browse to the file that you want to add.
5. To add a dynamic image, click Select Image Data. The Select Data Binding window displays.
6. From the Data Set drop-down list, select the data set from which to retrieve the image.
7. Select the check box beside the row that contains the image. Click OK. The dynamic image expression
is inserted into the Enter dynamic image expression field.
Report fields that were defined using the Base64 Image Data field display as images within PDF
documents only.

Add Background Images to Master Pages

Prerequisites
Create a report design file.

Context
In the Master Page view, you can add background images to your report design as tokens or as
embedded images.

Steps
1. To add a background image to the master page, on the Property tab of the Property Editor - Master
Page view, select the Advanced tab.
2. If your image is web-based, select URL from the Value drop-down list of the Background image type
property. Enter the URL in the Value field of the Background image property.
3. Alternatively, if your image is stored locally, select Embedded Image from the Value drop-down list of
the Background image type property. Click the browse icon next to the Value field of the Background
image property and select the image.
4. Use other fields in the Background section on the Advanced tab to specify the background image’s
size and position, and whether it’s displayed once or in a repeating pattern.

Add Grids to Report Designs

Prerequisites
Create a report design file.

Context
You can add grids to your report design to help you arrange items. Unlike tables, grids are simple layout
devices. They don't iterate through the data rows that a data set returns. Grids are typically used to display
a single instance object field value.

Steps
1. To add a grid to your report design, drag the Grid item from the Palette view to the required position on
the Layout tab of the main view.
2. Specify the number of columns and rows that you want to see in your grid. You can now drag data set
items from the Data Explorer view or report items from the Palette view to each cell in the grid.

3. Adjust the size and appearance of your grid’s cells on the General tab of the grid's Properties view.
Grid cells have no default height or width values. Workday recommends that you don't impose any.
Adding height and width values can cause the generated PDF to have unwanted line breaks.
If you add a grid within a grid, avoid truncating values by ensuring that the column width of the outer
grid is greater than the column width of the inner grid.
4. By default, grid cell borders are invisible. To adjust border visibility, edit the Values under the Box
heading on the Advanced tab of the cell’s Properties view.
5. You can create nested grids by dragging a new grid to a cell of an existing grid.

Add Lists to Report Designs

Prerequisites
Create a report design file.

Context
You can add lists to your report design to help you present items in Header, Detail, and Footer rows.

Steps
1. To add a list to your report design, drag the List item from the Palette view to the required position on
the Layout tab of the main view. Report Designer displays Header, Detail, and Footer rows.
2. Drag data set items from the Data Explorer view or other layout items from the Palette view to the list’s
rows.

Add Tables to Report Designs

Prerequisites
Create a report design file.

Context
Tables are at the heart of most report designs. They lay out information in row and column form but they're
more than simple grids - tables iterate through all the data rows that a data set returns. Tables are typically
used to display multi-instance object field values.

Steps
1. To add a table to your report design, drag the Table item from the Palette view to the required position
in the Layout tab of the main view.
2. From the Data Set drop-down list, select the data set that contains the columns you want to bind, then
select the columns. You can adjust the table's binding on the Binding tab of the Property Editor -
Table view. By default, a table returns all entries within a data set.
3. Specify the number of columns and details rows that you want to see in your table.
4. (Optional) Specify the order your results are returned in on the Sorting tab of the Property Editor -
Table view. You can use any field in the data set bound to the table as a sorting key. The sorting field
doesn't have to be part of the table's output.
5. (Optional) Specify 1 or more conditions that must be met for an entry to be output in a table on the
Filters tab of the Property Editor - Table view. If you specify multiple conditions, the entry is only
returned if they evaluate to true.

6. (Optional) Adjust the appearance of your table's cells on the General tab of the table's Property Editor
view. Table cells have no default height or width values. Workday recommends that you don't impose
any. Adding height and width values can cause the generated PDF to have unwanted line breaks.
If you add a table within a table, avoid truncation of values by ensuring that the column width of the
outer table is greater than the column width of the inner table.
7. (Optional) Improve readability by assigning a color to every other table row. On the Highlights tab of
the Property Editor - Table view:
a) In the Condition section, specify row.__rownum%2 Not Equal to 0.
b) Select the Background Color of your choice.

Add Charts to Report Designs

Prerequisites
Create a report design file.

Context
Charts are a useful way to represent data or the relationships between sets of data. Report Designer offers
a variety of ways to chart your data, and it is important that you choose the correct type. For example, a
particular set of data might work best when presented as a bar chart.

Steps
1. To add a chart to your report design, drag the Chart report item from the Palette view to the required
location on the Layout tab of the main view.
2. On the Select Chart Type tab of the New Chart dialog box, choose the type of chart that you would
like to use. Different options are available for different chart types. For example, charts may offer
multiple Y axes or 3D views.
Note: Charts with an Output Format set to SVG do not render when a PDF is generated on Workday's
servers, so ensure that you select PNG, JPG, or BMP.
3. On the Select Data tab, specify the 2 types of data that Report Designer needs to create your chart:
the Category series and the Value series. Think of these as your chart's X and Y axes. To add a series,
drag a column heading from the Data Preview section to the Category (X) Series or Value (Y) Series
field.
Note: Some chart types use slightly different names for the Category and Value fields, but the
principle is always the same.
4. On the Format Chart tab, edit the chart's formatting properties to your liking. Select a chart element
from the Chart Area or Series categories on the left of the tab and adjust its properties on the right.

Add Barcodes to Report Designs

Prerequisites
Create a report design file.

Context
You can encode information in a variety of barcode formats and add them to your report designs.

Steps
1. Drag a Dynamic Text report item from the Palette to the required position on the Layout tab of the
main view.

2. In the Expression Builder, select the BIRT Functions category and the IDAutomation subcategory,
then double-click the barcode encoder you want to use. Example: Code128c.
Report Designer adds an expression in the Expression Builder.
3. Select the data you want to encode from the Available Column Bindings or Available Data Sets
categories and their subcategories, then double-click it to enter. Report Designer adds it to the
expression.
To encode a string literal, add it in quotation marks between the parentheses in the expression.
4. From the Font drop-down list on the General tab of the Properties view, select a barcode font that's
supported by your selected encoder.

Next Steps
Preview your report design.

Group Report Data

Prerequisites
Create a report design file.

Context
Report Designer enables you to group a set of rows within a report by the values of one particular column.
For example, the grouping feature allows you to:
• Aggregate and summarize a grouping and add this information to the report.
• Add titles or other text to the beginning of each group.
• Add averages, counts, subtotals, and other summary information to the beginning or end of each group.
• Insert a page break before or after each group.
Note:
If you need to group custom report data, wherever possible use the grouping functionality that Workday
provides for custom report configuration before creating your report design.
In addition, due to performance issues inherent in BIRT, Workday recommends that you don't use Report
Designer's group-by feature for data sets where the custom report data exceeds 10 MB.

Steps
1. Bind the primary data set to a table within the main body of the report. In the Property Editor - Table
view, select the Binding tab, then select the primary data set from the Data Set drop-down list.
Note: The Workday runtime has to make at least one complete scan of a data set to find all the values
for the column it's grouping on. The runtime must also store the grouped-by data in memory until it has
rendered the complete data set. Keep this factor in mind when you're considering using this feature. We
recommend using grouping only on data sets that are relatively small and never when you are using the
Apply report design separately for each row option.
2. In the Outline view, expand the Body > Table > Groups node. Right-click Groups and select Insert
Group.
3. As you specify the group's properties, consider:
Option Description
Name The group name.
Group On The data set column to group on.
Expression The data binding expression for the column.

Option Description
Sort direction Ascending or descending.

Note:
After grouping has occurred, a display row number might not match the row order of the initial data,
leading to incorrect joining of primary and secondary data sets. If you want to add a secondary data set
binding to a report with a grouped primary data set, you must set thePrimaryRowNumber parameter
from the primary data set using a new column named Row_Number, which is added automatically.
To do so, click Data Set Parameter Binding in the Property Editor - Table view and give the
PrimaryRowNumber parameter the value row["Row_Number"].
Be aware that the expression row.__rownum was used in Report Designer for Workday 17 and
Workday 18. It is important to understand the difference between these 2 expressions:
• The new row["Row_Number"] expression is a column placed in the data set by the Workday
extensions. It indicates the row order of the report data item in the report data coming from the
server.
• The former row.__rownum expression was a special expression that indicated the row number at
display time of the data set item.
4. To add text or other report items to the end or beginning of every grouping, use the group header and
footer. Example, you can add an aggregation of one of the fields, based on the grouping. First add a
column binding for the aggregation, then add that to the table group footer.

Edit Master Pages

Prerequisites
Create a report design file.

Context
You can make adjustments that are reflected on every page of your report design by editing its master
page.

Steps
1. To edit the master page of report design, select the Master Page tab in the main view.
2. Drag report items from the Palette view to the master page’s header or footer.
Note:
The master page footer automatically includes the current date and time, which it retrieves using the
JavaScript new Date() function.
3. Use the Properties tab of the Property Editor – Master Page view to adjust properties such as header
and footer dimensions, text size, and background color.

Prevent Broken Image Links from Displaying

Prerequisites
Create a report design file.

Context
Report Designer displays a broken image link when it can't locate an image specified in a Workday report.
You can prevent the broken link symbol from appearing in generated reports by adjusting the properties of
the image.

Steps
1. Select an image or image place-holder.
2. On the Visibility tab of its Properties view, select the Hide Element check box.
3. In the Expression field, enter row["Photo.Photo"]== null, where Photo is the column heading
value for the image field in your report. Example: EmployeeHeadshot.EmployeeHeadshot. This
expression checks if the image is present, and hides it for all outputs if it's missing.

Display Multiple Labels on the Same Line

Prerequisites
Create a report design file.

Context
By default, report items display on successive lines. But there are many situations in which you need
items to display side by side on the same line. Example: you might want to begin a form letter with 'Dear'
followed by a name.

Steps
1. To display successive items on the same line within a grid or table, select one of them and open its
Property Editor view.
2. Select the General tab.
3. From the Display drop-down list, select Inline.
4. Repeat steps 1 through 3 for each item that you want to display on the same line.

Display Rich Text Data in Tables

Prerequisites
Create a report design that uses Workday data of the type Rich Text.

Context
When you drag a data set into a report design to form a table, each cell contains a Data report item, by
default. These treat text as a simple string and lose any rich text formatting that might have been applied in
the associated Workday custom report. To display the correctly formatted text within your generated PDF,
replace the cells' Data report items with Dynamic Text report items.

Steps
1. Delete the Data report item from the cell in the table.
2. Drag a Dynamic Text report item from the Palette view to the same cell.
3. In the Expression Builder, select Available Column Bindings from the Category list.
4. Select the Table element that corresponds to the appropriate data set from the Sub-Category list.
5. Double-click the data set row that you require. Expression Builder inserts the appropriate expression in
the Expression field.

6. Click OK. Report Designer displays the expression within the dynamic text report item in the cell.

Apply Global Formatting

Prerequisites
Create a report design file.

Context
Although you can edit the formatting options for each item in your report design individually, you might
sometimes wish to apply the same formatting style to an entire layout.

Steps
1. To apply formatting to an entire report design, open the Outline view.
2. Expand the Styles node.
3. Right-click Report and select Edit Style.
4. In the Edit Style dialog box, edit formatting options such as font size and color.

Use JavaScript to Conditionally Alter Layout

Prerequisites
Create a report design file.

Context
You can use JavaScript expressions to conditionally alter the layout of your report design. For example,
you might want to change the font color in a particular field, based on values in the report.

Steps
1. On the Layout or Master tab of the main view, select the report item to which you want to apply
conditional formatting.
2. Open the item's Property Editor view and select the Highlights tab.
3. Click Add to create your new formatting rule. The rule has 2 parts: a condition and a format. When the
condition is met, Report Designer applies the format.
4. In Condition section of the New Highlight dialog box, set the condition that you want to test for. In
the field on the left, specify the first part of the conditional expression. Click Fx to enter JavaScript
expressions in the Expression Builder.
5. In the central drop-down list, select an operator.
6. In the field on the right, specify the final part of the conditional expression. Example completed
conditional expression: row["OrderTotal"] Greater Than 1000.
7. In the Format section, specify the formatting that should apply if the condition is met. Example: set the
font color to red.
Related Information
Reference
The Next Level: Javascript Sample Code

Insert Page Breaks

Prerequisites
Create a report design file.

Context
When creating a design for a multipage report, you might want to specify page breaks to better organize
the material. For example, a report might contain subreports that would look better on separate pages.

Steps
1. To add a page break after a report item, select the item and open its Properties Editor view.
2. On the Page Break tab, from the After drop-down list, select Always.

Create Report Design Templates

Prerequisites
Create a report design project.

Context
The Report Designer New Report wizard includes a number of predefined design templates. You can also
create templates of your own for inclusion in the wizard.

Steps
1. Create a new template from the File menu by selecting New > Template.
2. Select a project and provide a name for the report design. Report design templates have the filename
extension .rpttemplate.
3. In the Display Name field, enter the name that will be visible to users in the New Report wizard.
4. (Optional) You can also enter a Description and select an image to associate with the new template.
5. After you create the new template, you must register it with the New Report wizard to make it available
to others. To do so, select File > Register Template with New Report Wizard...
Note: To remove a custom template from the New Report wizard, you must delete it from the Report
Designer custom templates folder. To locate this folder, select Window > Preferences and navigate to
Report Design > Template.

Result
The template you created is now available from the New Report wizard, using the display name you
provided. If you included a description and a specific image, they too are displayed in the wizard.

Navigate Report Designs Using the Outline View

Prerequisites
Create a report design file.

Context
By default, the Outline view is displayed in the lower left-hand corner of the Report Design perspective,
beside the Navigator view. This tree-structure view is useful for navigating complex layouts in your report
design.

Steps
1. In the Outline view, expand your report design, then expand the Body node.
2. Select a report item. Report Designer highlights the corresponding item on the Layout view.
You can expand grid report items in order to display their rows and cells. You can also expand lists,
tables, and cross tabs to display their contents.

Update Report Designs to Match Custom Report Changes

Prerequisites
Create a report design file.

Context
If you modify a custom report in Workday after you've created a report design, you must update the report
design file to reflect the changes.

Steps
1. In the Data Explorer view, right-click the data source for your report design, then select Edit.
2. Click From Workday, then enter the report name.
3. Select the report, then click Finish.
4. Double-click a data set to open the Edit Data Set window. Click OK to update the data set for your
report design. Repeat for each data set in your report design.
5. Preview the report by selecting Run > View Report > In Web Viewer.
6. Click Export Report. Select PDF from the Export Format drop-down list. Click OK to display a list of
fields that are no longer valid in your report design.
7. Update any fields listed in the error messages.
Example: If a field has been renamed, double-click the field in the Layout view of Report Designer to
open the Edit Data Binding window. Click the JavaScript Syntax button, then use the Expression
Builder to select the new field from the available data sets.

Debug JavaScript in Report Designs

Prerequisites
Create a report design containing JavaScript.

Context
Before you can use Eclipse's debugging tools with JavaScript that's part of a report design, you need to
perform some extra steps.

Steps
1. In the Script view, place a breakpoint on the line that you're interested in debugging. To do so, double-
click the margin to the left of the script.
2. In the Navigator view, right-click the .rptdesign file, then select Debug As > Debug
Configurations....
3. In the left navigation pane of the Debug Configurations dialog box, select Report, then click New in
the toolbar.
4. In the Output section, select PDF from the Format drop-down list. Then select the Open generated
file when finished check box.

5. Click Apply, then click Debug.

6. Select Window > Open Perspective > Other and open the Debug perspective.
7. Debug using the standard Eclipse debugging tools.
Note: Right-clicking the report design, then selecting Report > Debug Report uses default settings
only, and attempts to print to an HTML file without displaying the output. Don't use this option.

Concept: Applying a Report Design Separately to Each Row

On the Layout > Manage Layouts page in Workday, the Apply report design separately to each row
check box controls how Workday applies your report design to the custom report data.
• If you select the check box, Workday breaks the data from the report into individual rows. It then applies
the report design individually to each row of data, generates multiple individual PDF documents, and
merges them together into a single PDF document.
• If you don't select the check box, Workday applies the report design to the data returned by the report
as a whole.
Selecting the Apply report design separately to each row check box allows you to make assumptions
when creating a report design.
• If you select Apply report design separately to each row, you can assume that there will only ever be
a single row of data. This can be useful when dealing with complex layouts, or where the report design
includes headers and footers. You can also assume that the page numbers will be reset for each row.
• If you don't select Apply report design separately to each row, you can assume that your report
design should contain a table for the primary data set.

Concept: Report Designer Fonts

In Report Designer, the Font drop-down list displays only fonts that are available on the Workday server.
Workday provides these font families to the report design at runtime:
• IDAutomationOCR-A
• IDAutomationOCR-A6LPI
• IDAutomationOCR-AIII
• IDAutomationOCR-AIV
• IDAutomationOCR-B
• IDAutomationOCR-BIII
• IDAutomationOCR-BIV
• Roboto Light
• Roboto Regular
• Roboto Medium
• SansSerif
• Serif
For barcodes, Workday provides these font families:
• IDAutomationC128L
• IDAutomationC128M
• IDAutomationC128S
• IDAutomationC128XL
• IDAutomationC39L
• IDAutomationC39M
• IDAutomationC39S
• IDAutomationC39XL
• IDAutomationHC39L
• IDAutomationHC39M

• IDAutomationHC39S
• IDAutomationHC39XL
• IDAutomationUPCEANL
• IDAutomationUPCEANM
• IDAutomationUPCEANS
For check printing, Workday provides IDAutomationMICR.

Unicode and Internationalization of Text in Report Designs

Unicode is a computing industry standard for the consistent encoding, representation, and handling of text
in most of the world's writing systems. Each Unicode character can be represented by a different character
encoding, also known as a code point, the most commonly used being UTF-8 and UTF-16.
A computer font is an electronic data file containing a set of glyphs, characters, or symbols where each of
the glyphs, characters, or symbols is a visual representation of a character encoding. There are now many
fonts based on Unicode, for example, TrueType and OpenType. These font formats map Unicode code
points to glyphs, characters, or symbols.
Unicode-based fonts typically focus on supporting only basic ASCII, or particular sets of characters or
symbols. These are the reasons for this approach to font design:
• Applications and documents rarely need to render characters from more than one or two writing
systems.
• Fonts tend to demand resources in computing environments.
• Designing a consistent set of rendering instructions for tens of thousands of glyphs, characters, or
symbols constitutes a massive task.

FAQ: Font Issues in Report Designs

Why won't any text render in my report design?
If the text doesn't render at all in your report, it might mean that one of these elements doesn't cover all the
code points for all the characters in your locale:
• A Font property you've selected for a report item.
• A Font style setting for the entire report.
• A default Font Workday runtime has selected for your report.
If this is the case, check your data (including translation labels) and select Arial Unicode MS as the new
Font value where appropriate. Once completed, print your report with the new report design.
Why will most of the text render, but certain characters are corrupted or missing?
If some text renders, but certain characters are corrupted or missing, it might mean that one of these only
partially covers some of the code points used by the text in your report:
• A Font property you've selected for a report item.
• A Font style setting for the entire report.
• A default Font Workday runtime has selected for your report.
If this is the case, check your data (including translation labels) and select Arial Unicode MS as the new
Font value where appropriate. Once completed, print your report with the new report design.
What do I do when the text appears to be truncated on the page?
If the text appears truncated, you need to examine the space that you've allocated for the text to be
rendered in your report design. Ensure that the text area is large enough to fully display the text in the
selected font.
What do I do when traditional Chinese characters render incorrectly in PDFs viewed in Chrome?

You might find that a Workday-generated PDF containing traditional Chinese characters doesn’t render
properly when viewed in Chrome. If this is the case, use another browser or PDF viewer to display the
PDF. Alternatively, install the PDF Viewer extension from the Chrome Web Store in order to view the PDF
in Chrome.

Sharing Report Designs

Export Report Design Projects

Prerequisites
Create a Report Designer project.

Context
You might wish to share projects with other Report Designer users. To do so, export the project to an
archive file. Other users can then import the project into Report Designer and modify the design, if
required.

Steps
1. Right-click the project in the Navigator view and select Export...
2. Expand the General folder and select Archive File.
3. On the Archive file screen, select which of the project's files you wish to export. All of the contents are
selected by default.
4. Click Browse and navigate to the folder you'd like to export to, then specify a filename for the archive
file.

Import Report Design Projects

Prerequisites
Have access to an exported Report Designer project archive file.

Context
Another Report Designer user might wish to share a project with you. When they have exported the project
as an archive file, you can then import it.

Steps
1. Right-click in the Navigator view and select Import....
2. Expand the General folder and select Existing Projects into Workspace.
3. On the Import Projects screen, select the Select archive file option.
4. Click Browse beside Select archive file and navigate to the archive file you'd like to import. Once
imported, the project displays in the Navigator view.

Concept: Workday Solution Sharing and Report Designs

When you share a custom report with other Workday users, you also automatically share any report
designs associated with it, as well as any configured translations. Workday users of the importing tenant
can print the custom report in exactly the same way as users of the exporting tenant.
If you don't want to share a report design with a custom report, make a copy of the report and remove the
design from the business form layout. Share the copy rather than the original.

Translation Support

Steps: Translate Labels Using Resource Files

Prerequisites
Create a report design file.

Context
Report Designer can automatically translate label text using user-configured locale-based resource
files. When you generate a PDF, Report Designer selects the relevant resource file, based on the user's
preferred language setting, and performs the translation. This means that different users who need to
generate documents in their own language can use the same business form layout.

Steps
1. Create a Translation Resource File for the Default Locale Language on page 269
Provide a resource file for the default locale's language even though you aren't translating the label text
into that language.
2. Create Translation Resource Files for the Target Languages on page 270
Provide resource files for each target language that you wish to offer as a translation option.
3. Associate Labels with Resource File Key Pairs on page 271
Associating a label with a resource file key pair in the default locale language enables Report Designer
to match the same key pair in the target language.
4. Preview a Translated Report Design on page 272
You can preview a translated report design before deploying it to Workday by changing your locale
preference.
Related Information
Reference
The Next Level: BIRT Translations
The Next Level: Translating BIRT Output

Create a Translation Resource File for the Default Locale Language

Prerequisites
Create a report design file.

Context
You must provide certain resource files to enable automatic label translation in Report Designer. One of
these is a file that associates a resource key with some text in the default locale language. Other resource
files provide text for that same key in a target language. Report Designer can then swap the default locale
language text for the target language text when it encounters the key that they have in common.

employment with our Company includes the following agreed upon terms: . Give
each new key its own line in the text file.
Note: Resource file keys can't contain spaces.
3. Save the text file in the relevant project folder with the filename translations.properties.
Note: The translation resource file for the default locale doesn't have a locale suffix such as en_US or
fr_FR. Translation resource files for target languages do have these suffixes.
4. You must now associate the resource file with the report design file. To do so, open the design file and
select the Resources tab of the Property Editor - Report view.
5. In the Properties Files section, add the translation.properties file you just created.

Example
The following text is an example of a translation.properties resource file's contents:
Dear=Dear
Congratulations=Congratulations on joining our team. We're excited to have you!
Terms=Your employment with our Company includes the following agreed upon terms:
Date_Of_Hire=Date of Hire:
Business_Title=Business Title:
Manager_Name=Manager Name:
Organization=Organization:
Location=Location:
Base_Pay_Amount=Base Pay Amount:
Hire_Advice=Please be advised that your employment with the Company will be "at-will", which means that
either you or the Company may terminate your employment at any time, for any reason or no reason, with
or without notice. There is no promise by the Company that your employment will continue for a set period
of time or that your employment will be terminated only under peculiar circumstances.
Sincerely=Sincerely,

Create Translation Resource Files for the Target Languages

Prerequisites
Create a report design file.

Context
To enable automatic label translation in Report Designer, you must create a resource file that associates
keys with text in the default locale language. You also require resource files that provide text for those keys
in your target languages. Each target language must have a resource file.

Steps
1. To create a resource file, select File > New > Other.... Expand the General node and select Untitled
Text File.
2. Add keys to the text file in the format Key=Value, where Key is the name you want to give to the
resource key and Value is the appropriate text in the target language. Give each new key its own line
in the text file.
Note: You must provide a key pair for each key pair in the original language, as defined in
translations.properties.

3. Save the text file in the relevant project folder with the filename
translations_[locale_id].properties, where [locale_id] is the IEFT code for the target
language. Example: translations_fr_FR.properties.
Note: You don't need to associate target language resource files with your report design. When
you add the source language resource file translations.properties file, Report Designer
automatically picks up the others.

Example
The following text is an example of a translation_fr_FR.properties resource file's contents:
Dear=Cher
Congratulations=Félicitations pour rejoindre notre équipe. Nous sommes ravis de vous avoir!
Terms=Votre emploi avec notre société comprend les éléments suivants modalités convenues:
Date_Of_Hire=Date d'embauche:
Business_Title=Titre Affaires:
Manager_Name=Nom du gestionnaire:
Organization=Organisation:
Location=Emplacement:
Base_Pay_Amount=Montant du Salaire de Base:
Hire_Advice=S'il vous plaît noter que votre travail avec la Société sera «à volonté», ce qui signifie que
vous ou la Société peut mettre fin à votre contrat de travail à tout moment, pour n'importe quelle raison ou
sans raison, avec ou sans préavis. Il n'ya pas de promesse par la Société que votre emploi se poursuivra
pendant une période de temps définie ou que votre emploi sera terminé que dans des circonstances
particulières.
Sincerely=Sincèrement,

Associate Labels with Resource File Key Pairs

Prerequisites
Create a translation resource file for the default locale language.

Context
When you have created a translation resource file for the default locale language, you must then associate
its labels with key pairs in that file.

Steps
1. Select a label in your report design. In the Property Editor - Label view, select the Localization tab.
2. Click Browse. The Select Key dialog box shows all of the key pairs that you defined in your
translations.properties resource file.
3. Add the pair that is appropriate for your label.

4. Repeat steps 1 through 3 for each label that requires translation.

Note:
• The first properties file in the list is the default properties file. The Layout view uses it to display the
report design's label content.
• Report Designer previews use the properties file associated with the locale that you select in
Preferences > Preview to display the label content and translate the text.
• After you deploy a report design with translation resource files to Workday, the server runtime
selects the properties file whose suffix corresponds to the user's Preferred Display Language. If a
language-specific file isn't available, it selects the default properties file.

Preview a Translated Report Design

Prerequisites
Create a report design file and the resource files that enable the translation of its labels.

Context
Report Designer uses your locale preference to determine which language to use when previewing a
translated report. You must have created a translation resource file for any language you want to preview
in.

Steps
1. To set the locale preference, select Window > Preferences.
2. Expand the Report Design node and select Preview.
3. From the Choose your locale drop-down list, select a locale.
4. To preview the report, select Run > View Report > As PDF.
After you deploy a report design with translation resource files to Workday, the server runtime selects
the properties file automatically, based on the .properties suffix string included in the filename that
corresponds to the user's preferred display language, or the default properties file, if a language-specific
file isn't available. The first properties file in the list is the default file for the business form layout that
uses the report design.

Result
Report Designer previews the report with its label text translated into the language specified in the locale
preference.

Conditionalize Label Translation with JavaScript

Prerequisites
Create a report design file and the resource files that enable the translation of its labels.

Context
You can use an onCreate JavaScript to override the translation context on a report design. This enables
Report Designer to translate label text based on a specified condition, rather than the language preference
of the user running the print task.

Steps
1. To add an onCreate script, select a label on the Layout tab of your report design, then select the
Script tab.

2. From the Script drop-down list, select onCreate.

3. In the text pane, add the appropriate JavaScript.

Example
This example overrides the default language and provides appropriate translation if the locale is fr_CA:

importPackage(Packages.java.util);
if(row["Locale"]=="fr_CA")
{
var lc = new Locale("fr_CA");
this.text = reportContext.getMessage("Dear", lc);}

Troubleshooting: Translation Issues on Custom Reports

Cause Solution
You didn't upload translation resource files to the Make sure you set up Workday Report Designer to
report design. translate from resource files.
See Steps: Translate Labels Using Resource Files
on page 269.

If the worker associated with the report doesn't 1. Access the Transfer Ownership of Custom
have a preferred display language, Workday Reports task.
translates the report based on the worker's locale.
Assign yourself as the owner of the report.
Security: These domains in the System
functional area:
• Custom Report Administration
• Manage: All Custom Reports
2. Access the Change Preferences task.
Select a preferred display language or preferred
locale. Workday translates the report based on
the preferences you select.
Security: The Core Navigation domain in these
functional areas:
• Adaptive Insights for Financial Plans
• Adaptive Insights for Headcount Plans
• Tenant Non-Configurable
3. Preview a Translated Report Design on page
272.

Related Information
Concepts
Concept: Country-Specific Information, Locales, and Languages
Tasks
Run and Print a Custom Report that Uses a Business Form Layout on page 243

Previewing and Printing

Preview Report Designs as PDFs

Prerequisites
Create a report design file.

Context
You should always test the PDF output of your design within the Report Designer environment before you
deploy it to Workday.

Steps
1. Select Run > View Report > In Web Viewer. This action doesn't immediately generate a PDF. First, it
produces a paginated HTML view.
2. To display the PDF output, click Export Report. Select PDF as the Export Format. The Fit To option
is set to Auto by default. In some cases, this default setting doesn't paginate the PDF correctly and
selecting Actual Size achieves a better result.
Note: The PDF that this method generates is the closest match for the layout that the report design
generates after it deploys to Workday. You can also generate a PDF by selecting Run > View Report
> As PDF. This option immediately generates a PDF document that is quite close to the output that
the Workday runtime generates. For example, it displays page breaks, allowing you to view the output
for multi-page reports as individual pages within the PDF. However, report designs that include page
numbers and JavaScript that depends on the use of event handlers might not display exactly as they
would when deployed to Workday.

Print Custom Reports after Design Deployment

Prerequisites
Create a report design file and deploy it to Workday for use as a business form layout.

Steps
1. Sign in to your Workday tenant and search for the custom report.
2. Click Print to generate a PDF that applies the new report design. The Print Layout page displays with
a message indicating that the print job has been submitted for processing.
You can't print in Proxy mode.
3. Click Refresh. Workday displays a link to the generated PDF file.
A link to the PDF is also available in the My Reports area, as indicated by the Status message.
4. Click the link to the PDF file, then click OK to open the file.
PDFs generated for Workday custom reports might require you to install language packs when viewing
the document using Adobe Reader. You only need to complete this task once. This is likely to happen
if you're viewing a PDF that includes Chinese characters on a computer that isn't typically used for
viewing Chinese documents. This is normal behavior and helps to reduce the size of the PDFs, by not
including the required fonts in every PDF generated.
Always print checks at 100% scale to ensure that the MICR line appears correctly.

Examples

Example: Create a Report Design with a Single Data Set

This example illustrates how to create a simple report design based on a custom report with a primary
business object only.

Context
Your workplace activities committee often needs to send letters to San Francisco-based workers,
announcing corporate activities. They ask you to create a report design for this purpose using placeholder
text. First, you need to create a custom report in Workday to select employees located in San Francisco.
The custom report employs a primary business object only, resulting in a single Report Designer data set.

Steps
1. Sign in to your Workday GMS tenant.
2. Access the Create Custom Report task.
3. Configure these values:

Option Value
Report Name Activity Announcement
Report Type Advanced
Data Source All Active Employees
Enable As Web Service Select this check box.
4. On the Columns tab, configure these values:

Business Object Field Column Heading Override

XML Alias
Employee Legal Name - First Name First_Name
Employee Full Legal Name Full_Name
Employee Primary Address - Full Address
Employee Current Worker Signatory
5. On the Filter tab, add a filter condition with these values:

Option Value
And/Or And
Field Location
Operator in the selection list
Comparison Type Value specified in this filter
Comparison Value San Francisco
6. Open Report Designer in Workday Studio.
7. Create a report project named Activity Announcement. In that project, create a report file named Activity
Announcement.rptdesign.

8. Create a Workday data source and download some sample data:

a) Create a new Workday Report Data Source named Activity Announcement Data.
b) Download the report description for the Activity Announcement custom report from Workday.
c) Download sample report data from Workday and name the file Activity Announcement Sample.xml.
9. Create a new data set with these values:

Option Value
Data Source Selection Activity Announcement Data
Data Set Type Workday Primary Report Data Set
Data Set Name Employees
10.Add a table to the layout:
a) Drag a Table report item to the Layout tab of the main window.
b) Specify 1 column and 1 details row.
c) Select Employees from the Data Set drop-down list.
d) Select all available binding columns.
e) Delete the header and footer rows.
f) Drag the detail row border to increase its size.
g) On the General tab of the table's Property Editor view, enter Employees in the Name field.
11.Add a local image file of your company logo to the layout:
a) Drag an Image report item to the Employees table.
b) Select the Embedded image check box and click Add Image... to locate your image file.
12.Drag these items in this order to the Layout view from either the Employees data set or the Palette:

Item Location Text Actions

Full Name Employees data set N/A On the Padding tab
of the field's Property
Editor view, configure
the Top padding to 12
points.
Address Employees data set N/A N/A
Data Palette N/A • Configure the
Display Name as
Preparation Date,
and select Date from
the Data Type drop-
down list.
• Enter new Date()
in the Expression
field. Configure the
Top padding to 12
points.

Label Palette Dear • Ensure that you add

a space after Dear.
• On the General
tab of the label's
Property Editor
view, select Inline

Item Location Text Actions

from the Display
drop-down list.
• Configure the Top
padding to 20 points.

First Name Employees data set N/A Configure the Display

as Inline.
Label Palette , Configure the Display
as Inline.
Text Palette [REPLACE THIS TEXT Configure the Top
WITH DETAILS OF padding to 6 points.
YOUR EVENT]
Sincerely,

Signatory Employees data set N/A Configure the Top

padding to 30 points.
13.Delete the date expression from the footer in the Master Page view.
14.Save and preview your design.

Next Steps
Deploy your design to Workday for use as a business form layout.

Example: Create a Report Design with Multiple Data Sets

This example illustrates how to create a report design based on a custom report that includes primary and
secondary business objects, as well as multi-instance fields.

Context
Your HR department asks you to create a report design for a letter outlining employee benefit enrollments.
You need to create a Workday custom report that includes a secondary business object and a multi-
instance field. This means that you need to create a data set for the primary business object, another for
the secondary business object, and a third for the multi-instance field.

Steps
1. Sign in to your Workday GMS tenant.
2. Access the Create Custom Report task. Configure these values:

Option Value
Report Name Employee Benefit Enrollments
Report Type Advanced
Data Source All Active and Terminated Workers
Enable As Web Service Select this check box.

3. On the Columns tab, enter these values:

Business Object Field Column Heading Column Heading

Override Override XML Alias
Worker Legal Name - Last Last Name Last_Name
Name
Worker Legal Name - First First Name First_Name
Name
Worker Employee ID Employee ID Employee_ID
Worker Supervisory Organization Supervisory_Organization
Organization
Worker First Day of This Benefit Enrollment Date Benefit_Enrollment_Date
Calendar Year
Worker Current Worker Signatory Signatory
Worker Work Address - Full Work Address Work_Address
Benefit Elections Benefit Type Benefit Type Benefit_Type
Benefit Elections Benefit Provider Benefit Provider Benefit_Provider
Benefit Elections Coverage Coverage Coverage
Benefit Elections Dependents Dependents Dependents
Benefit Elections Current Election Current Election Effective_Date
Coverage Begin Date Coverage Begin Date
Benefit Elections Group Number Group Number Group_Number
4. Add a Group Column Heading for the secondary business object. Enter Benefit Elections in both the
Business Object and Group Column Heading fields.
5. Open Report Designer in Workday Studio.
6. Create a report project named Employee Benefit Enrollment Letter. In that project, create a report file
named Employee Benefit.rptdesign.
7. Create a Workday data source and download some sample data:
a) Create a new Workday Report Data Source named Employee Benefit Enrollments Data.
b) Download the report description for the Employee Benefit Enrollments custom report from
Workday.
c) Download sample report data from Workday and name the file Employee Benefit Enrollments
Sample.xml.
8. Create the data set relating to the primary business object, Worker, with these values:

Option Value
Data Source Selection Employee Benefit Enrollments Data
Data Set Type Workday Primary Report Data Set
Data Set Name Worker

Report Designer displays XML schema element values and names for the columns that you added as
rows to your custom report for the Worker business object in Workday. Note that Report Designer adds
a Row_Number column automatically to support grouping.

9. Create the data set relating to the secondary business object, Benefit Elections, with these values:

Option Value
Data Source Selection Employee Benefit Enrollments Data
Data Set Type Workday Secondary Report Data Set
Data Set Name Benefit Elections
Business Object Benefit Elections

Report Designer displays the XML schema element values for each of the columns that you added
as rows to your custom report for the Benefit Elections business object in Workday, and their display
names. It also displays a warning message about an empty PrimaryRowNumber input parameter
value. You'll configure this later, so dismiss the message.
10.Review the fields in your custom report in Workday. You will find that Dependents is a multi-instance
field, as indicated by the multi-instance icon.
11.Create another secondary data set relating to the Dependents multi-instance field in your custom
report:

Option Value
Data Source Selection Employee Benefit Enrollments Data
Data Set Type Workday Secondary Report Data Set
Data Set Name Dependents
Business Object Benefit Elections/Dependents

Report Designer displays the XML schema element value for the Dependents multi-instance field, and
its display name. Again, it also displays a warning message about an empty PrimaryRowNumber input
parameter value. As before, dismiss the message.
12.Add a table to the layout:
a) Drag a Table report item to the Layout tab of the main window.
b) Configure 1 column and 1 details row.
c) Select Worker from the Data Set drop-down list.
d) Select all available binding columns.
e) Delete the header and footer rows.
f) Drag the detail row border to increase its size. Doing so makes its rows a fixed size, which could
result in truncated data. To ensure that the table can grow to accommodate the data displayed within
it, select the guide cell for the table's only row. On the General tab of the row's Property Editor
view, delete the value from the Height field.
g) On the General tab of the table's Property Editor view, add Worker in the Name field.
13.Add a local image file of your company logo to the layout:
a) Drag an Image report item to the Worker table.
b) Select the Embedded image check box, then click Add Image... to browse to an appropriate image
file.
14.Add the Work Address field to the layout:
a) Drag the Work Address field from the Worker data set to the Worker table in the Layout view.
b) On the Padding tab of the Work Address item's Property Editor view, configure the Top and
Bottom values to 12 points.

15.Add the current date to the layout:

a) Drag a Data item to the Worker table, and position it below the previous item.
b) Enter Preparation Date as the Display Name and select Date from the Data Type drop-down list.
c) Click JavaScript Syntax. Select Native JavaScript Functions > Date, then double-click Date() to
enter the new Date() expression.
16.Add a salutation to the layout:
a) Drag a Dynamic Text item to the Worker table, and position it below the previous item.
b) Configure this expression in the Expression Builder: "Dear " + row["First_Name"] + "
" + row["Last_Name"] + ",". You can enter the row parts of the expression by selecting
Available Column Bindings > Table - Worker, then double-clicking First_Name or Last_Name.
c) Configure the salutation item top and bottom padding to 6 points.
17.Add introductory text to the layout:
a) Drag another Dynamic Text report item to the Worker table, and position it below the previous item.
b) Configure this expression in the Expression Builder: "Thank you for completing
the Benefit Enrollment process. We are very pleased to present your
Benefits Statement. You are enrolled in the following plans as of " +
row["Benefit_Enrollment_Date"] + "."Expression Builder You can enter the row part
of the expression by selecting Available Column Bindings > Table - Worker, then double-clicking
Benefit_Enrollment_Date.
c) Configure the introductory text item top and bottom padding to 6 points.
18.Add the Benefit Elections data set to the layout as an embedded table and configure the
PrimaryRowNumber input parameter value:
a) Drag the Benefit Elections data set to the Worker table, and position it below the previous item.
Select all available binding columns.
b) Name the new table Benefits.
c) On the Binding tab of the Benefits table's Property Editor view, click Data Set Parameter
Binding.
d) Select the PrimaryRowNumber parameter, then click Edit.
e) Click JavaScript Syntax. Select Available Column Bindings > Table - Worker, then double-click
RowNum to enter the row.__rownum expression. This expression returns the current row number,
so that the corresponding benefit election details are returned for each worker.
f) Delete the footer row in the Benefits table.
19.Add the Dependents data set to the layout as an embedded table and configure both the
PrimaryRowNumber and SecondaryRowNumber input parameter values:
a) Add a new column to the right of the Coverage column.
b) Drag the Dependents data set from the Data Explorer view, and position it within the detail row of
the column you just created. The data set has just one available binding column. Select it.
c) Drag the Dependents column heading into the heading row between Coverage and Effective Date.
d) Delete the header and footer rows in the embedded Dependents table.
e) Name the new embedded table Dependents.
f) On the Binding tab of the Dependents table's Property Editor view, click Data Set Parameter
Binding.
g) Select the PrimaryRowNumber parameter, then click Edit.
h) Click JavaScript Syntax. Select Available Column Bindings > Table - Worker, then double-click
RowNum to enter the row._outer.__rownum expression. Note that the expression is formed this
way because the Dependents table is nested within the Worker table.
i) Select the SecondaryRowNumber parameter, then click Edit.
j) Click JavaScript Syntax. Select Available Column Bindings > Table - Benefits, then double-click
RowNum to enter the row.__rownum expression.

20.Add a closing paragraph to the layout:

a) Drag a Label item to the Worker table, and position it below the previous item.
b) Add this text to the label: If you have any questions or find your enrollment in
error, please contact the Benefits Department.
c) Configure the closing paragraph item top and bottom padding to 6 points.
21.Add a sign-off to the layout:
a) Drag another Label item to the Worker table, and position it below the previous item.
b) Add this text to the label: Sincerely,
c) Configure the sign-off item top and bottom padding to 6 points.
22.Add a signatory to the layout:
a) Drag the Signatory field from the Worker data set to the Worker table in the Layout view, and
position it below the previous item.
b) To make room for a signature, configure the signatory item top padding to 40 points.
23.Include a page break after each letter:
a) In the Worker table's Property Editor view, select the Page Break tab.
b) From the After drop-down list, select Always.
24.Change the background color of the Benefits table. Make the text in its header row bold and left-
justified:
a) On the General tab of the table's Property Editor view, click Background color, and select a
suitable color.
b) Select the guide cell for the table's header row. On the General tab of the row's Property Editor
view, click B and click Left.
25.Delete the date expression from the footer in the Master Page view.
26.Save and preview your design.

Next Steps
Deploy your design to Workday for use as a business form layout.

Example: Create a Report Design with Resource-Based Translation

This example illustrates how to create a report design that uses resource files to translate label text based
on the user's location.

Context
A colleague asks you to create a report design for a high-level summary of the current employment
situation at Global Modern Services, using resource files to enable translation. You need to create a
custom report in Workday to select the relevant data. The design uses a single data set. The default locale
language for the report is English. The target language is German.

Steps
1. Sign in to your Workday GMS tenant.
2. Access the Create Custom Report task. Configure these values:

Option Value
Report Name Positions Vacant
Report Type Advanced
Data Source Companies
Enable As Web Service Select this check box.

3. On the Columns tab, configure these values:

Business Object Field Column Heading Column Heading

Override Override XML Alias
Company Name Name Name
Company Position Count - Total Positions - Total Positions_-_Total
including Subordinate
Organizations
Company Positions Filled - Count Positions - Filled Positions_-_Filled
Company Position Count - Fillable Positions - Vacant Positions_-_Vacant
Company Average Age Average Employee Age Average_Age
4. Open Report Designer in Workday Studio.
5. Create a report project named Positions Vacant. In that project, create a report file named Positions
Vacant.rptdesign.
6. Create a Workday data source and download some sample data:
a) Create a new Workday Report Data Source named Positions Vacant Data.
b) Download the report description for the Positions Vacant custom report from Workday.
c) Download sample report data from Workday and name the file Positions Vacant Sample.xml.
7. Create the data set relating to the primary business object, Company:

Option Value
Data Source Selection Positions Vacant Data
Data Set Type Workday Primary Report Data Set
Data Set Name Positions

Report Designer displays XML schema element values and names for the columns that you added as
rows to your custom report for the Worker business object in Workday.
8. Create a table using the Positions data set:
a) Drag the Positions data set to the Layout tab of the main window.
b) Select all available binding columns.
c) Delete the footer row.
d) On the General tab of the table's Property Editor view, enter Positions in the Name field.
9. Create a translation resource file for the default locale language and associate it with the report design
file:
a) Select File > New > Other.... Expand the General node and select Untitled Text File.
b) Add keys to the text file. Use the format Key=Value, where Key is the name you supply for the
resource key and Value is the appropriate text in English. Give each key its own line in the text file:

Key Value
Name Name
Total Positions - Total
Filled Positions - Filled
Vacant Positions - Vacant

Key Value
Age Average Age
c) Save the text file in the Positions Vacant project folder with the filename translations.properties.
d) On the Resources tab of the report design file's Property Editor view, add the
translations.properties properties file.
10.Create a translation resource file for the target language:
a) Select File > New > Other.... Expand the General node and select Untitled Text File.
b) Add keys to the text file. Use the format Key=Value, where Key is the name you supply for the
resource key and Value is the appropriate text in German. Give each key its own line in the text file:

Key Value
Name Name der Firma
Total Positionen - Total
Filled Positionen - Gefüllt
Vacant Positions - Frei
Age Durchschnittsalter
c) Save the text file in the Positions Vacant project folder with the filename
translations_de_DE.properties.
11.Associate column headings with resource file key pairs:
a) Select the Name column heading.
b) On the Localization tab of its Property Editor view, click Browse.
c) Select the Name key pair.
d) Repeat substeps a through c for each column heading.
12.Delete the date expression from the footer in the Master Page view.
13.Preview the translation in Report Designer.
a) Save your design and preview it as normal by selecting Run > View Report > As PDF. The table's
header row displays in English.
b) Change Report Designer's locale by selecting Window > Preferences > Report Design > Preview
and then selecting German (Germany) from the Choose your locale drop-down list.
c) Preview the design again. The table's header row displays in German.

Next Steps
Deploy your design to Workday for use as business form layout.

Discovery Boards

Steps: Set Up Tenant for Discovery Boards

Context
Set up your tenant for discovery boards to gain insights for informed business decisions by:
• Exploring your data using interactive visualizations.
• Sharing business insights by creating a dashboard-like experience for end users.

Workday reserves the right to suspend a customer's access to Discovery Boards on Workday-delivered
data sources if required to maintain tenant performance and stability. Workday will work with the affected
customer to address issues in order to resume their access to Discovery Boards.

Steps
1. Set up your tenant for Drive.
See Steps: Set Up Drive.
2. Create User-Based Security Groups.
Create an unconstrained security group, such as a user-based security group, for your discovery board
users, and assign users.
Note: Ensure that every user who has access to the Discovery Boards: Create domain also has
access to the Drive domain.
Example: You can define or update these security groups (administered by the Security Configurator
group):

Group Name Group Type

Discovery Board Administrator User-Based
Report Writer User-Based
3. Edit Domain Security Policies.
Create or edit a security policy for these domains in the System functional area:
• Discovery Boards: Administration
• Discovery Boards: Create
• Discovery Boards: Manage Curated Data Source Field List
Workday suggests that you use the security groups you created and edited along with the System
Auditor group.

Domain Security Groups Task Permissions

Discovery Boards: Discovery Board Administrator View and Modify
Administration
System Auditor View only

Discovery Boards: Discovery Board Administrator, Report Writer View and Modify
Create
System Auditor View only

Discovery Boards: Discovery Board Administrator View and Modify

Manage Curated Data
System Auditor View only
Source Field List
Discovery Boards: Discovery Board Administrator View and Modify
Manage Curated Data
System Auditor View only
Source List
Discovery Boards: Discovery Board Administrator View and Modify
Manage Drilling Field
System Auditor View only
Lists
Discovery Boards: Discovery Board Administrator View and Modify
Manage Delivered
System Auditor View only
Discovery Boards

Domain Security Groups Task Permissions

Discovery Boards: Set Discovery Board Administrator View and Modify
Up Discovery Board as
System Auditor View only
a Worklet
4. Activate Pending Security Policy Changes.
Related Information
Reference
The Next Level: Enable Discovery Boards in Your Tenant

Steps: Create a Discovery Board

Prerequisites
These domains in the System functional area:
• Discovery Boards: Create
• Drive

Context
Discovery boards enable you to perform drag and drop analysis by iteratively asking questions around
data in a data source. Use a discovery board to create 1 or more visualizations, which are graphical
representation of certain data fields selected from a data source.

Steps
1. Access the Drive Home page.
2. Select New > Discovery Board.
You can also duplicate an existing discovery board by right-clicking it and selecting Make a Copy.
3. Enter a name.

Result
Workday creates a discovery board and adds it to your list of documents on the My Files view in Drive.
The discovery board contains 1 empty visualization to begin your analysis.

Next Steps
You can:
• Enter an explanatory description below the board title to help viewers understand the board's purpose
and scope.
• Open the discovery board and edit the empty visualization, and add more visualizations as desired.
• Add your discovery board as a worklet on the Home page.
• Share the board with other users and assign their access to the board.
• Permanently delete discovery boards by accessing the Drive Permanent File Delete task.
Related Information
Tasks
Permanently Delete Drive Items
Set Up Discovery Boards as Home Page Worklets on page 292
Reference
The Next Level: Discovery Boards Guidance

The Next Level: Quick Sheet: Create Discovery Boards

Steps: Create Visualizations

Prerequisites
Security: These domains in the System functional area:
• Drive
• Discovery Boards: Create

Context
You can explore and analyze data in a data source interactively by using a visualization (viz) in a discovery
board.

Steps
1. Access Drive.
You can also access your discovery board as a worklet from the Home page.
2. Select the discovery board you want to edit.
3. (Optional) To enable live updates, select Automatically Update from the related actions menu of the
discovery board. When you disable the automatic update, you can manually update the viz by clicking
Update Now.
4. Set Up the Viz Data Source on page 287.
5. On the Builder panel, select a viz type.
See Concept: Visualization Types on page 302.
6. Drag and drop fields into the drop zones to analyze the data.
7. (Optional) To display only the fields administrators configured in curated field lists, enable Show only
curated fields from the related actions menu of the discovery board. When you disable the curated
field list, Workday displays all available fields to discovery board users.
Discovery board administrators can configure curated field lists for the primary business object of the
data source.

Next Steps
You can:
• Add a description to the viz by selecting Add Description from the related actions menu of the viz.
• Change how Workday displays your vizzes by dragging the viz to a new location on the sheet to
reposition it.
• Modify your viz to change how Workday displays data.
• Duplicate the viz by selecting Duplicate from the related actions menu.
Related Information
Concepts
Concept: Discovery Board Workspace on page 305
Concept: Using Drop Zones in a Viz on page 307
Concept: Interactive Viz Queries on page 306
Tasks
Steps: Modify Visualizations on page 311
Set Up Curated Field Lists on page 290
Set Up Discovery Boards as Home Page Worklets on page 292

Reference
The Next Level: Discovery Boards Guidance
The Next Level: Quick Sheet: Create Discovery Boards

Set Up the Viz Data Source

Prerequisites
These domains in the System functional area:
• Drive
• Discovery Boards: Create

Context
Every visualization (viz) in a discovery board analyzes data in a data source.
When you create a discovery board, you select the data source to analyze in the first viz. When you add a
new viz or duplicate an existing viz, Workday automatically selects the same data source as the previously
selected viz. You can change the data source used in a viz by using the Data Source panel.
If your tenant has Prism Analytics enabled, Workday lists both Prism data sources and the supported
Workday-delivered data sources you have access to.
For Workday-delivered data sources, you have more options to configure for the data source, such as data
source filters and prompts built into data sources or fields.

Steps
1. Select a viz in a discovery board.
2. Click the data source panel icon on the left side of the discovery board workspace.
3. Select a data source from the list when creating a new discovery board.
Workday displays data sources that you have permission on. If your Discovery Boards administrator
curated the list of data sources, then Workday lists the data sources you have permission on from that
curated list. To view all data sources that you have permission on, disable Show only curated data
sources from the discovery board related actions.
4. (Optional) Click the left arrow next to the data source name to select a different data source.
5. (Workday-delivered data sources) Select all required and any optional data source filters and prompts.

Result
Workday applies the selected data source and displays the builder panel so you can analyze the data in
the data source.

Set Up Prompt Values for Discovery Boards

Prerequisites
These domains in the System functional area:
• Drive
• Discovery Boards: Create

Context
The data sources used in a discovery board might include prompts that are built-in to the data source or
fields. Built-in prompts can:
• Filter down the data in your data source. Example: Worker Type prompt built-in to the Trended Workers
data source.
• Be a parameter that influences data results. Example: Currency and Account Translation Rule Set
prompts built-in to the Translated Debit Amount field.
You can select the values for the built-in prompts when you edit a discovery board. Built-in prompts are
either required or optional.
You can select values for most built-in prompts. Workday supports prompts that use any field type
supported in discovery boards except for:
• Currency
• DateTime
• Numeric
• Text
When you configure a prompt in a discovery board, by default:
• You select a static value for the prompt.
• The prompt value applies to all vizzes on a sheet that use the same combination of the selected data
source and data source filter.
• The prompt is visible in edit mode only.

Steps
1. Select a viz that uses the combination of data source and data source filter you want to configure.
2. Select the data source panel icon on the left side of the discovery board workspace.
3. In the Sheet Prompts section, select 1 or more values for a built-in prompt.
4. (Optional) Select the prompt menu and select an option to change the properties of the prompt:
Option Description
Determine Value Dynamically Use this option to change the prompt from static to dynamic,
meaning that Workday determines the prompt value based on
some context, such as the current date or current user.
When you update a prompt to be dynamic, select a field that
determines the prompt value dynamically. These fields are on the
Global business object. These Global fields aren't available:
• Fields with built-in prompts.
• Calculated fields with these functions:
• Date Constant
• Lookup Field with Prompts
• Numeric Constant
• Prompt for Value
• Text Constant
Example: In a date prompt's input, you select the field First Day of
This Month. When you view the discovery board, Workday:
• Determines the first day of the current month.
• Uses that value for the prompt.
• Displays data in the viz based on that prompt value.

Option Description
In view mode, dynamically determined viewer-exposed prompts
display the resulting values, not the field on the Global business
object.

Override at Viz Use this option to override the value of the prompt for the selected
viz.
When you override a sheet-level prompt at the viz-level, Workday
moves the prompt from the Sheet Prompts section to the Viz
Overrides section on the data source panel.
You can remove a viz override by selecting Clear Override from
the prompt menu in the Viz Overrides section.

Create Control and Link Use this option to create a control and link it to the prompt, giving
viewers control over the data returned.
When you select a value in a control, Workday applies that value
as the input to the linked prompt.
Any changes you make to the values of a control in view mode
only apply to view mode in your current session. Example: You
are in view mode and select different values for the control, and
then switch to edit mode. Workday reverts the control values to the
saved version of the discovery board.
See Concept: Discovery Board Controls on page 308.

Related Information
Concepts
Concept: Discovery Board Controls on page 308
Reference
2023R1 What's New Post: Discovery Board Controls
2022R1 What's New Post: Discovery Boards Prompts
2021R2 What's New Post: Viewer Access for Discovery Boards

Set Up Curated Data Sources

Prerequisites
Security: Discovery Boards: Manage Curated Data Source List subdomain in the System functional area.

Context
You can curate the data sources to display on the Data Source panel in discovery boards. This list makes
it easier for discovery board users to view the data sources available to them. By default, when you create
a data source list, Workday only displays the data sources in that list. Users can also display all data
sources.

Steps
1. Access the Maintain Data Source List for Discovery Boards report.
2. Click Add Data Sources.
Select the data sources to display on your discovery board. The Data Sources to Add grid only
displays the data sources supported in discovery boards.

3. Click Enable in Discovery Boards.

Once you enable a data source list, you can disable it by clicking Disable in Discovery Boards.
4. (Optional) To modify the list, click Add Data Sources or Remove Data Sources. The Data Sources to
Remove grid displays the data sources currently on the curated data sources list.

Result
When you create a discovery board, Workday displays the list of curated data sources in the Data Source
panel.

Set Up Curated Field Lists

Prerequisites
Security: These domains in the System functional area:
• Discovery Boards: Manage Curated Data Source Field List
• Discovery Boards: Manage Drilling Field Lists

Context
You can configure curated field lists so that it's easier for discovery board editors to find the right fields
to use when building visualizations. For all visualizations except tables, you can perform better ad hoc
analysis and reporting by configuring fields to drill into and view details for.

Steps
1. Access the Maintain Field Lists for Discovery Boards report.
2. Select a Business Object to base the curated field list on.
All data sources with the primary business object you select share the same curated field list.
3. As you complete the Data Source Fields tab, consider:
Option Description
Enable in Discovery Boards (Available after you add fields to the curated
field list.) Click to enable the curated list that you
configured in discovery boards. Once clicked, you
can click Disable in Discovery Boards to disable
the curated field list.
From the related actions menu of the discovery
board, you can click Show only curated fields:
• Off to display all available fields.
• On to display only the fields configured in the
curated field list.

Add Fields Click to access the Add Fields to Data Source

Field List for Discovery Boards task. The
Fields to Add grid displays all fields available to
populate the curated field list.
Remove Fields (Available after you add fields to the curated field
list.) Click to access the Remove Fields from
Data Source Field List for Discovery Boards
task. The Fields to Remove grid displays the
fields currently on the curated field list.

Option Description
Selected Fields The grid displays all fields added to the
curated field list that users view when creating
visualizations.
The Where Used column displays a usage
count for each curated field. The count includes
Workday internal development usages.

4. On the Drill By Fields tab, click Edit Drill By Field List to access the Edit Drill By Field List for
Discovery Boards task. You can manage the fields you use to drill into visualization measure data.
If you don't configure fields on the Drill By Fields tab, Drill By won't display on visualizations.
5. As you complete the tab, consider:
Option Description
Enable in Discovery Boards Click to enable the drill by field list that you
configured in discovery boards. Once clicked, you
can click Disable in Discovery Boards to display
all available drill by fields for the business object
you selected.
Selected Grouping Fields The grid displays all fields added to the drill
by field list that users view when creating
visualizations. You can select the Default Sort for
each field that determines the display order for the
drill by fields. Example: When you select a drill by
field in a visualization, Workday displays a new
table. The new table displays the Default Sort
you selected for the drill by data.

Discovery boards don't support drilling on:

• Blank or Other values.
• Fields that you can't filter on.
• Lookup prior value calculated fields.
6. On the Show Details Fields tab, click Edit Show Details Field List to access the Edit Show Details
Field List for Discovery Boards task. You can manage the fields Workday displays when you view the
details of a data point to the transaction level.
If you don't configure fields on the Show Details Fields tab, Show Details won't display on
visualizations.
7. As you complete the tab, consider:
Option Description
Enable in Discovery Boards Click to enable the show details field list that you
configured in discovery boards. Once clicked, you
can click Disable in Discovery Boards to disable
the show details field list.
Selected Fields The grid displays all fields added to the show
details field list that users view when creating
visualizations. You can select the Default Sort
for each field that determines the display order for
fields when you view details. Example: When you
click Show Details on a visualization data point,
Workday displays a new table. The new table

Option Description
displays the Default Sort option you selected for
the show details data.
To change the order of the Show Details fields
displayed in a visualization, remove the fields,
then add them in the desired order.

Result
Workday displays:
• Curated fields when you build discovery board visualizations if the data source has a primary business
object with a curated field list configured.
• Options on the visualization to drill into and view details for your data.

Next Steps
You can drill into or view details for visualizations and display the resulting data in a pivot table or table.
You can then click:
• Add to Sheet to add a visualization to a sheet. Each sheet can display up to 10 visualizations. Workday
disables Add to Sheet if the visualization you drill into or view details for includes a lookup date rollup
calculated field.
• Export as a Report to export a visualization to the Report Writer. Workday disables Export as a
Report if:
• The visualization you drill into or view details for includes a lookup date rollup calculated field.
• You don't have access to the Custom Report Creation domain in the System functional area.
Related Information
Reference
The Next Level: Enable Discovery Boards in Your Tenant

Set Up Discovery Boards as Home Page Worklets

Prerequisites
Enable People Experience to customize the Home page.
Security: These domains in the System functional area:
• Discovery Boards: Set Up Discovery Board as a Worklet
• Set Up: Tenant Setup - Worklets

Context
You can add discovery boards as worklets on the Home page. This enables users to access their most
commonly used discovery boards without needing to go to Drive.

Steps
1. Access the Maintain Dashboards report.
2. Click Edit in the Home dashboard row.
3. In the Content tab, add a worklet row in the Worklets grid.

4. As you complete the grid, consider:

Option Description
Worklet Select the Discovery Boards folder and then
select the discovery board that you want to set as
a worklet.
Required for Groups Select the security groups that you want to have
access to the discovery board worklet.
Required Select the check box to set the discovery board
worklet as Required.
5. (Optional) For users in security groups that don't require the discovery board worklet:
a) Access the Configure My Worklet Landing Pages task.
b) Select the Home landing page.
c) In the Optional Worklets section, select the discovery board to display.

Result
The discovery board worklet displays on the Home page.
Related Information
Tasks
Steps: Set Up People Experience
Reference
2022R2 What's New Post: Discovery Boards Worklets on the Home Page
Reference: Home Page Sections

Reference: Supported Fields in Discovery Boards

When you create or edit a discovery board, Workday lists the supported fields in the field list.
For Prism data sources, Workday supports:
• Every field in the Prism data source.
• Tenant-wide summarization calculations.
• The global calculated field functions supported in Prism data sources.
For Workday-delivered data sources, Workday supports:
• Workday-delivered fields.
• Tenant-wide summarization calculations.

• Tenant-wide calculated fields that use these functions:

• Aggregate Related Instances
• Arithmetic Calculation
• Build Date
• Concatenate Text
• Convert Currency
• Convert Text to Number
• Count Related Instances
• Date Constant
• Date Difference
• Evaluate Expression
• Evaluate Expression Band
• Extract Multi-Instance
• Extract Single Instance
• Format Date
• Format Number
• Format Text
• Increment or Decrement Date
• Lookup Date Rollup
• Lookup Field with Prompts
• Lookup Hierarchy
• Lookup Hierarchy Rollup
• Lookup Organization
• Lookup Organizational Roles
• Lookup Range Band
• Lookup Related Value
• Lookup Translated Value
• Lookup Value As Of Date
• Numeric Constant
• Substring Text
• Sum Related Instances
• Text Constant
• Text Length
• True/False Condition
Workday doesn't support:
• Fields on the Global business object.
• Fields that use these field types:
• DateTime
• DateTimeZone
• Rich Text
• Time
If you use a Self-referencing Instance field in a viz, it displays as a Single Instance field.
Note: Use optimized fields whenever possible to improve performance. When creating or editing a viz,
Workday displays a blue dot and tip text messages on fields optimized for performance. Data source
fields might be optimized for different purposes. You can achieve better performance when you use fields
optimized for grouping, aggregation, or filtering. Workday optimizes all fields in Prism data sources, and
some fields in indexed Workday-delivered data sources.

Related Information
Concepts
Concept: Prism Data Sources on page 331
Reference
2023R1 What's New Post: Multi-Instance Fields on Discovery Boards

Reference: Reporting Limits

• Data Sources on page 295
• Prism Data Sources on page 296
• Financial Modeled Data Source on page 296
• Processing on page 296
• Discovery Board Visualizations on page 296
• Scheduled Report Output on page 298
• Reports Run in the Browser on page 298
• Displaying Report Designer in the Browser on page 300
• Exporting to Excel on page 301
• Report Performance Logs on page 301
• Mobile Devices on page 301

Report Criteria Returned Instances Limit

Indexed RDS 3 million
Prefiltering

Indexed RDS 3 million

Postfiltering

Nonindexed RDS 3 million

Prefiltering

Nonindexed RDS 1 million (for grouping only)

Postfiltering
Pregrouping

Nonindexed RDS 3 million

Postfiltering
Indexed report fields

Prism Data Sources

Financial Modeled Data Source

Workday limits the data it puts in the financial modeled data source when you set up the financial reporting
data model.

Description Limit
Time duration of journal line data Up to 3 years, rolling (current year plus 2 years
prior)
Maximum number of optional dimensions 15
Maximum number of values per dimension 100,000

Workday returns up to 1,000,000 cells that contain data in the query response.

Discovery Board Visualizations

Viz Type Results

Area Chart Workday returns up to:
• 100 values on the x-axis.
• 250 color groupings per x-axis value, plus the
Other group.

Viz Type Results

• 40 million cells, whether or not the cell contains
data. Empty cells don't display in a chart viz
like they do in a pivot table viz. However, this
limitation still applies.

Bar Chart Workday returns up to:

Chart Workday returns up to:

Donut Chart Workday returns up to 250 color groupings, plus the

Other group.
Heatmap Workday returns up to:
• 100 values on the x-axis, plus the Other group.
• 100 values on the y-axis, plus the Other group.

Line Chart Workday returns up to:

Pivot Table Workday returns up to:

• 50,000 data rows.
• 12,000 row groupings (rows displayed in the
pivot table).
• 250 column attribute groupings.
• 40 million cells, whether or not the cell contains
data.

Scatterplot Workday returns up to 250 color groupings, plus the

Other group.
Table Workday returns up to 50,000 data rows.

When you filter on a field that contains more than 5,000 values, Workday returns up to 5,000 distinct
values in the Filter panel.

Scheduled Report Output

Number of Rows Supported Formats Results

Between 500,000 and 1 million Text (CSV) Workday generates the report in
Text (CSV) format.
More than 1 million Not supported Workday doesn't generate a
report.

You can use the Process Monitor report to determine if Workday switched to another supported format, or
if Workday didn't generate the report.

Reports Run in the Browser

Report Type Results

All • The file size limit for report results is 50 MB and
15 GB for scheduled reports.
• The XML string limit is 2 GB.
• Workday limits tabular data processing to 5
seconds.

Advanced Workday returns up to:

• 1,000 instances.
• 10,000 rows for nonsupported pagination.

Report Type Results

Composite Workday returns up to:

Matrix Workday returns up to:

nBox Workday enables up to 100 images for each nBox

cell.
For reports with drill-down, Workday returns up to:
• 50,000 rows for supported pagination.
• 10,000 rows for nonsupported pagination.

Report Type Results

Workday returns up to 50,000 rows for reports
using Prism data sources.

Search Workday returns up to 2,000 instances.

The limit doesn't affect mass actions within search
reports.

Simple Workday returns up to:

• 1,000 instances.
• 50,000 rows.

Transposed Workday returns up to:

• 1,000 instances.
• 50,000 rows.

Trending For reports with drill-down, Workday returns up to:

Displaying Report Designer in the Browser

Browser Rows Displayed Columns Displayed

Internet Explorer 11 50 20
All other browsers 200 50

Exporting to Excel
Workday adheres to these Microsoft Excel 2007 or newer limitations when exporting a composite report
with outlining:

Type Limit
Cells 1,000,000
Columns 16,384
Rows 1,048,576

Report Performance Logs

You can use report performance logs to troubleshoot performance issues in your reports.

Reference
The Next Level: Breaking Through With Mobile
The Next Level: Breaking Through with Mobile

Discovery Board Concepts

Concept: The Discovery Board Workflow

Workday makes some Workday-delivered data sources available for use in discovery boards. If you
configure your tenant for Workday Prism Analytics, you can also use Prism data sources.
A discovery board is your starting point for data analysis, similar to a project workspace. The discovery
board is the canvas for discovering and sharing data insights.
You can create discovery boards from Workday Drive and opening the document opens the workspace in
Workday where you can create visualizations.

Visualizations
A visualization (viz) is a graphical or textual representation of certain fields selected from a data source.
Vizzes might be charts, tables, or more. Use vizzes to explore and analyze your data interactively.
Discovery boards have 1 or more sheets, and each sheet can display up to 10 vizzes. The individual vizzes
on a sheet can be:
• Related, meaning they use the same underlying data source and data source filter.
• Unrelated, meaning they use different data source and data source filter.
To create a viz on your discovery board, select a data source. To display data in a viz, drag and drop fields
into the various drop zones. Vizzes display inside panels (or boxes) in the workspace area of a discovery
board sheet.
The drill panel gives you more control over your vizzes by enabling you to:
• Add vizzes to a sheet, and each sheet can display up to 10 vizzes.
• Display the details of a data point to the transaction level.
• Export vizzes to the Report Writer.
• Use different dimensions to drill into viz measure data.
Related Information
Reference
The Next Level: Discovery Boards Guidance

Concept: Visualization Types

Visualizations enable you to display data from a data source either graphically or textually. The viz type
determines the drop zones in the Builder panel and how the data is visually displayed in the viz.
Workday provides several viz types that enable you to decide how to explore and display the data. Some
viz types are compatible with custom reports, enabling you to export the viz to either a Matrix or Advanced
report. Other viz types are optimized for use in discovery boards and can't be exported to custom reports.

Viz Type Description

Chart A Chart is a viz type that displays data graphically, representing each point
(Matrix report- of data as a mark on the chart. Chart vizzes support several mark types,
compatible) enabling you to create different types of charts, such as bars, lines, points, and
more.

Viz Type Description

A chart display summarized (aggregated) data grouped and filtered by the
selected attribute fields.
You can think of a chart in a discovery board as a recipe with these
components:
• Attribute and summarization fields
• Axis placement (X-Axis and Y-Axis)
• Appearance encodings (such as Color and Size)
• Mark type (such as Point, Line, and Bar)
When you export this viz type to a custom report, Workday creates a Matrix
report.

Donut Chart A Donut Chart is a viz type that displays a circle divided into sectors, but
(Matrix report- the center of the circle has a blank center (hole). Each sector illustrates a
compatible) percentage of the total.
Donut chart vizzes show relative sizes at a glance. The human eye can't easily
distinguish between sectors that have similar sizes, especially if there are
many very small sectors (marks). Workday recommends using a donut chart
viz under these circumstances:
• You only have 1 summarization field to display in the viz.
• All values to display in the viz are positive (no zero or negative values).
• The attribute values to display represent part of a whole.
• The number of attribute values to display is low, such as less than 10. You
can sort and filter an attribute field to reduce the values displayed.
Donut chart vizzes can't display negative or zero values in the Angle drop
zone. When a summarization field contains those values, Workday displays a
warning icon in the upper right corner of the viz. Click the warning icon to learn
how many values do and don't display in the viz.
When you export this viz type to a custom report, Workday creates a Matrix
report.

Pivot Table A Pivot Table is a viz type that displays attribute and summarized data in a
(Matrix report- tabular format. Pivot tables have complex headers that are ideal for comparing
compatible) multiple fields against one another.
Pivot tables are similar to tables, but with the added feature of adding grouping
to rows and columns. Due to their detailed headers, pivot tables are useful for
comparing data that contains subcategories, so you can access several levels
of detail in 1 place.
You might want to create a pivot table if you want to see the raw data
comprising the points on a chart viz, instead of a graphical representation of it.
When you export this viz type to a custom report, Workday creates a Matrix
report.

Table A Table is a viz type that displays the data in a tabular, spreadsheet format.
(Advanced report- A table is a viz with attribute fields only in the Columns drop zone. Its format is
compatible) closest to what you might see in a CSV file. Tables are optimal for when you'd
like a granular, simple display of data that has several attribute fields in it.

Viz Type Description

When you export this viz type to a custom report, Workday creates an
Advanced report.

Area Chart An Area Chart is a viz type that displays metrics connected by line segments
as a continuum, filling in the space between the lines with color. Similar to Line
Charts, Area Charts typically display trends over time.
Area Charts provide more options for grouping the categories than Chart
vizzes.
You can't export this viz type to a custom report.

Bar Chart A Bar Chart is a viz type that displays metrics for categories of data as either
vertical or horizontal bars.
Bar Charts provide more options for grouping and orienting the categories
than Chart vizzes.
You can't export this viz type to a custom report.

Heatmap A Heatmap is a viz type that compares 2 attributes by a common metric (a

summarization field).
Heatmaps enable you to use color to see variations in the data.
You can't export this viz type to a custom report.

KPI Chart A KPI Chart is a viz type that displays a measure and its progress toward a
specified target.
Use a KPI viz on aggregated numeric or currency data. When you create or
edit a KPI, you can display:
• The base measure.
• An optional comparison measure.
• The variance (difference) between the base measure and the comparison
measure.
• A visual cue that indicates the progress toward the target.
You can't export this viz type to a custom report.

Line Chart A Line Chart is a viz type that displays metrics connected by line segments as
a continuum, typically as a trend over time.
You can't export this viz type to a custom report.

Scatterplot A Scatterplot is a viz type that compares 2 metrics (summarization fields),

grouped by a set of common attributes (color and size).
Scatterplots show how a metric correlates to another metric. Example: You
can use a Scatterplot to show the relationship between population size and
income.
You can't export this viz type to a custom report.

Waterfall A Waterfall is a viz type that displays the incremental transitions of quantitative
values that increase or decrease.

Viz Type Description

Use a Waterfall viz to visualize and understand the progression of a specific
value and how it's influenced by positive and negative factors. Example: Use a
Waterfall to display how headcount is influenced by hiring and terminations.
You can use either Numeric or Currency metrics in a Waterfall viz.
By default, Waterfalls display the Total (the end value), which summarizes
all values and calculates how all the increments affect the starting value.
Optionally, you can hide the Total.
You can create a Waterfall viz using either of these methods:
• One field each in the Measures and Dimensions drop zones. Workday
displays how the values of a dimension field incrementally increase or
decrease the value of a measure field. Example: You can perform expense
analysis by the categories defined in a single dimension field.
• Multiple fields in the Measures drop zone. Workday displays each field in
order on the x-axis, using the top field as the starting value.
You can't export this viz type to a custom report.

Related Information
Reference
The Next Level: Discovery Board Visualization Examples

Concept: Discovery Board Workspace

When you open a discovery board, Workday opens the workspace in View mode. View mode enables
you to view the discovery board, but not make any changes. If you have Can View or Can Comment
permission on the discovery board, you view the discovery board in view mode.
If you're the owner or if you have Can Edit permission on the discovery board, you can click Edit to switch
to Edit mode. Edit mode enables you to make changes to the discovery board and save it.
You see these workspace components in edit mode:

1. Panels for editing a viz. The left side panel is where you navigate between the data source panel,
builder panel, filter panel, and formatting panel to edit and configure a viz. Click an icon to hide or open
a particular panel. You might want to hide a panel to see more of the workspace.
2. Board title and description. Click in either field to enter or edit text.
3. Menu options for the board.
4. Share button. Click to share a board with an individual user or a security group.
5. Undo and redo buttons.
6. Builder panel. The builder panel contains the options for configuring the selected viz in the workspace.
You select the type of viz to create, such as Chart or Pivot Table, drag fields into the drop zones, and
configure any drop zone or field options. You can narrow the list of fields by filtering the field list.
7. Data source used in the selected viz. You can change the data source in the viz by clicking the data
source panel.
8. Field list. Expand a category to see the fields in that category. All summarization fields for a particular
Numeric or Currency field are grouped under the field. Hover over the Numeric or Currency field and
click the double chevron icon to expand it to see the related summarization fields.
9. Drop zones and drop zone options. The available drop zones and options vary by viz type.
10.Visualization.
11.Sheet controls.
12.Control panel. The control panel displays the controls linked to the prompts and filters that viewers and
editors can use to provide input values.
13.Viz type options.
14.Select a dual or merged Y-axis (Area Chart, Bar Chart, Chart, and Line Chart vizzes only).
15.Select mark type (Chart viz only).
16.Back to Drive button.
The left side panel includes these icons:
• Data source panel. View or change the data source for the selected viz.
• Builder panel. Build the viz by selecting the fields and configuring options for the selected viz.
• Filter panel. Filter the data in the selected viz or all vizzes on the sheet.
• Formatting panel. View or change formatting options for the selected viz or all vizzes on the board, such
as changing the assigned color.

Concept: Interactive Viz Queries

When you build a visualization in a discovery board, you're actually creating queries against a data source.
The act of dragging a field to a drop zone creates a query that is sent to the data source, fetches the
requested data, and then visually renders the results as a chart or table.
By default, the viz automatically updates the data when you make a change. However, you can temporarily
turn off live, automatic updates of the data for all vizzes in the board. You might want to disable automatic
updates to improve performance if the board contains many vizzes with a lot of data. To turn off the live
updates, select Automatically Update from the discovery board menu. When you change a viz, such as
changing a field in a drop zone, Workday displays an empty viz until you click Update now in a viz.
When some people think of queries, they think of SQL (the structured query language used to access data
stored in a relational database). Viz queries aren't written in SQL, they're constructed by your actions in the
discovery board. However, it might help to understand how data is requested and returned if we make a
comparison with SQL.
If a viz query were expressed in SQL, it would look something like this statement (the clauses are listed in
the order that they're processed):

SELECT <attributes in builder>, <summarizations in builder>

FROM <data source>
WHERE <attributes in filters>
GROUP BY <attributes in builder>

ORDER BY <attribute sort options>

LIMIT <attribute limit options>

Note that the query is constructed based on the field role (summarization or attribute), and where the fields
are placed in the drop zones.

Concept: Using Drop Zones in a Viz

To analyze data in a visualization, you place (drag and drop) fields from the list of fields into the drop zones
(such as X-Axis) in the builder panel. The fields and their locations determine the placement and visual
appearance of the data in your viz.
Workday automatically selects the best visual representation for the combination of summarization and
attribute fields you add to the drop zones.
When you select a field from the panel and start to drag it over, the appearances of the drop zones change
to help guide your placement of the field in the builder panel. Drop zones permit either summarization and
attribute fields. A grayed out drop zone means that the drop zone doesn't apply to the selected field. A
highlighted drop zone means that the drop zone is available for the selected field.
As you work with drop zones, consider:
• Some drop zones permit multiple fields and some limit the number of fields. As you drag and drop
fields, the drop zones provide instructional text and highlighted drop zone areas to help you build your
viz.
• The position of attribute fields in drop zones, such as X-Axis and Columns, determines the grouping
order in the viz.
• You can remove a field from a drop zone by clicking the X next to the field name.
• You can drag a new field directly on top of an existing field to replace it.

Concept: Chart Viz Mark Types

In a Chart visualization, Workday displays the data as a collection of marks. A mark is the visual
representation of a metric value calculated for a group of input rows.
The mark type controls the shape of data in a Chart viz, and how data points are visually represented.
When you create a Chart viz in a discovery board, you can select the mark type from the Marks drop-down
menu.
How Workday renders a particular chart depends on the mark type along with the placements of
summarization and attribute fields in the drop zones.

Mark Type Description

Bar Workday displays each mark as a rectangular bar with its length
proportional to the value it represents.
Point Workday displays each mark as a dot, with its position determined by
the values on the 2 axes (Cartesian coordinates).
Line Workday displays each mark as an end point of a straight line, with a
straight line connected between marks.
You might use a line chart to visualize a trend in summarization data
over time with the line drawn chronologically.

Area Like a line chart, Workday displays each mark as an end point of a
straight line, but fills the space between the marks and the horizontal
axis with a color.
Similar to a line chart, an area chart typically displays summarization
data over time, and is typically used to compare 2 or more quantities.

Mark Type Description

However, unlike lines, area charts are typically used to represent
cumulative totals rather than individual totals.
You might use an area chart to illustrate how the member of an
attribute contributes to an overall trend.

Auto Workday selects the best mark type based on the fields in the drop
zones.

Concept: Discovery Board Controls

When you create or edit a discovery board, you can give discovery board viewers some control over the
data returned in the board by creating controls. A control is a configurable input that provides viewers some
lightweight data analysis capabilities over the discovery board that they view.
Each control is associated with and linked to a controllable, either a prompt or a filter. When editors or
viewers select a value in a control, Workday applies that value as the input to the associated controllable.
To create a control, select the Create Control and Link option from either a prompt menu or filter menu.
When you select Create Control and Link for a controllable, Workday:
• Creates a control and links it to the controllable.
• Displays a control panel on the right side of the discovery board workspace. Workday displays the
control panel in both edit mode and view mode.
• Places the control at the bottom of the control panel. Workday creates 2 controls when you configure a
filter that uses the is between operator.
You can create a control for any prompt, and for filters that:
• Use static values.
• Use an operator that accepts a filter value, such as the operator is greater than or is in list. You can't
create a control for filters that don't accept values, such as filters with the operator is empty or is not
blank.
When you create a control, you can:

Control Action Notes

Change the name of the control. Select Rename from its menu in the control panel.
Workday uses the prompt or filter name as the control name
automatically. Because some prompts and fields have the same
name, you can create multiple controls with the same name.
Note that when you create a control from a filter that uses the in
between operator, Workday creates 2 controls and uses both the field
name and control operator to define the control name.

Change the order in the control Drag and drop a control in the control panel to change its order.
panel.
By default, Workday displays the controls in the control panel in
the order you create them. The order of the controls doesn’t affect
the data because Workday applies an AND condition between all
controls. However, you might want to change the order to group
together similar controls.

Remove the control. Select Remove from its menu in the control panel.
When you remove a control, Workday:
• Removes the control from the control panel.

Control Action Notes

• Retains the associated controllable in the data source panel or
filter panel, but removes the link.
• Moves any input value currently defined in the control input to the
controllable input.
Additionally, Workday automatically removes a control when you
perform an action on its associated controllable that renders the
control obsolete. Example: The controllable is a filter and you update
the filter, or disable the filter.

Related Information
Tasks
Set Up Prompt Values for Discovery Boards on page 287
Filter Data in a Viz on page 318
Reference
2023R1 What's New Post: Discovery Board Controls

Concept: Sharing Discovery Boards

You can share a discovery board with an individual user or a security group. You share a discovery board
by:
• Clicking the Share button from the board.
• Using Workday Drive.
Consider these requirements:
• To share a discovery board, you must be the owner or have Can Edit permission if the owner enables
editors to share.
• To share a discovery board with a security group:
• Your tenant must be set up for group sharing on Drive using the Configure Group Sharing in Drive
task.
• Discovery boards must be shareable with the security group.
• You can give users and groups Can View or Can Edit permission.
• To give Can View permission, the user or group you share with must have permission on at least 1 data
source used in the discovery board.
• To give Can Edit permission, the user or group must have access to the Discovery Boards: Create
domain.

Concept: Discovery Board Security

Workday enforces security when someone views or edits a discovery board. To view a discovery board,
you must have permission on at least 1 data source used in it.
Each viz in a discovery board uses a single data source. To see a viz when editing or viewing a discovery
board, you must have permission on that data source. Workday enforces contextual security, which
determines what data displays for each user.
How Workday displays the discovery board depends on your data source access and board permission:

Discovery Board Permission Details

Can Edit When you edit a discovery board, Workday:
• Displays a placeholder for every viz, but only displays the data if
you have permission on the data source.

Discovery Board Permission Details

• Displays every sheet even if you don't have permission on any
data source used in the sheet.

Can View When you view a discovery board, Workday:

• Hides a viz if you don't have permission on the data source.
• Reorganizes the vizzes on a sheet if you don't have permission on
1 or more vizzes.
• Hides a sheet if you don't have permission on at least 1 data
source used in the sheet.

Reference: Summarization and Attribute Viz Fields

Discovery board visualizations use attribute and summarization fields to control how Workday analyzes
and groups data.

Field Type Considerations and Examples

Attribute An attribute field describes a property of an entity.
The data answers who, what, when, and where
questions and can be any field type on a data
source.
Summarization A summarization field enables you to analyze
the attributes as categories. You can analyze the
aggregated data in summarization fields from
different perspectives to derive meaning from the
data.
Workday creates summarization fields for each
currency and numeric field in the data source. You
can make the data in those fields less granular by
using a summarization field.
You can use:
• Currency or numeric fields to aggregate numeric
data from multiple rows by selecting AVG, MAX,
MIN, or SUM.
• Single instance or text fields to aggregate data
by selecting COUNT DISTINCT.
Workday ignores case-sensitivity and groups
values with special characters and different
spellings. Example: Workday, workday, and
W0rkday group as 2 distinct instances because of
the misspelling of the third instance.

You can place attribute and summarization fields only in some drop zones in a viz depending on the viz
type. Some viz types, such as Chart and Pivot Table, must contain at least 1 summarization field. If you
don’t use a summarization field in a drop zone, Workday uses the Count summarization in the viz, which is
a count of all records.
The values in a currency and numeric attribute field are individual, finite, discrete values. The values in a
currency and numeric summarization field are infinite within a range of continuous values. You can use
some numeric data as both an attribute and summarization field, such as length. However, some numeric
data isn't continuous and you should use them only as an attribute, such as USA zip codes.

Workday-Delivered Discovery Boards

Copy Workday-Delivered Discovery Boards

Prerequisites
• Set up your tenant for Drive.
• Security: Discovery Boards: Manage Delivered Discovery Boards domain in the System functional area.

Context
You can use Workday-delivered discovery boards as a starting point when configuring discovery boards.
You can make copies of Workday-delivered discovery boards and share them using Drive.
You can customize copied discovery boards by:
• Adding visualizations to the discovery board.
• Editing the copied discovery boards in Drive.
• Removing visualizations.
Changes Workday makes to Workday-delivered discovery boards don't apply to copies.

Steps
1. Access the Delivered Discovery Boards report.
2. Select the discovery board you want to copy.
3. Click Make a Copy.

Result
Workday displays a link to the discovery board copy in Drive.

Next Steps
You can:
• Customize the discovery board by adding visualizations.
• Share the discovery board with users.
Related Information
Reference
2021R2 What’s New Post: Buyer Manager Insights with Discovery Boards
2021R2 What's New Post: Delivered Discovery Boards

Modifying Visualizations

Steps: Modify Visualizations

Prerequisites
Security: These domains in the System functional area:
• Drive
• Discovery Boards: Create

Context
You can change discovery board visualizations (vizzes) to control the way Workday displays viz data.

Steps
1. Access the viz in a discovery board.
2. (Optional for Area Chart, Bar Chart, Chart, and Line Chart viz types) To compare metrics with different
scales, select Dual on the Y-Axis drop zone to enable the Y-Axis (Left) and Y-Axis (Right) drop zones.
Drag and drop summarization fields in both Y-Axis drop zones to display values on opposite axes of the
chart.
3. (Optional for Bar Chart or Waterfall viz types) Select a horizontal or vertical Orientation for the marks
on the viz.
4. (Optional for Area Chart and Bar Chart viz types) Select the Grouping of the marks on the viz, such as
Cluster, Overlay, Stack, or Stack to 100.
5. (Optional for the Chart viz type) Select the type of Marks for each y-axis, such as area, bar, or line.
When you create a dual axis chart, you can make a combination chart by selecting different mark types
for each y-axis.
6. (Optional) Adjust Mark Size in a Viz on page 312.
7. (Optional) Change Viz Colors on page 313.
8. (Optional) Group Data by Color in a Viz on page 313.
9. (Optional) Change Field Options for Visualizations on page 314.
10.(Optional) Change the Formatting of a Numeric Summarization in a Viz on page 314.
11.(Optional for the KPI viz type.) Set Up KPI Viz Options on page 315.
12.(Optional for the Waterfall viz type.) Set Up Waterfall Viz Options on page 316.
13.(Optional) Filter Data in a Viz on page 318.
14.(Optional) Sort Data in a Viz on page 320.
15.(Optional) Limit Viz to the Top N Values on page 321.
Related Information
Concepts
Concept: Discovery Board Workspace on page 305
Concept: Using Drop Zones in a Viz on page 307
Tasks
Steps: Create Visualizations on page 286

Adjust Mark Size in a Viz

Prerequisites
Security: Discovery Boards: Create domain in the System functional area.

Context
You can adjust the size of Point mark types in Chart and Scatterplot visualizations. To adjust the size
based on the field value per mark, add a summarization field to the Size drop zone.

Steps
1. Select a Scatterplot viz or a Chart viz with Point as the mark type.
2. Drag a summarization field from the field panel to the Size drop zone.

Group Data by Color in a Viz

Prerequisites
Security: Discovery Boards: Create domain in the System functional area.

Context
For some viz types, you can add a field to the Color drop zone to encode the marks so the groups are
visually differentiated.
Most viz types, such as Chart and Donut Chart, accept an attribute field in Color, which creates additional
groupings in the viz. Heatmap vizzes accept a summarization field in Color.

Steps
1. (Area Chart, Bar Chart, Chart, and Line Chart viz) Select a viz with at least 1 attribute field in the X-Axis
drop zone.
2. (Donut Chart viz) Select a Donut Chart viz with a summarization field in the Angle drop zone.
3. (Heatmap viz) Select a Heatmap viz.
4. Place a field in the Color drop zone.
Suppose you have a Chart viz, and you place the worker field in X-Axis, Count in Y-Axis, and the
gender field in Color. The viz groups the workers by gender and uses a different color for each gender.
Related Information
Concepts
Concept: Color in Discovery Boards on page 317
Tasks
Change Viz Colors on page 313

Change Viz Colors

Prerequisites
Security: These domains in the System functional area:
• Drive
• Discovery Boards: Create

Context
You can select color palettes to use for your discovery boards and assign color options at the viz level.

Steps
1. Open a discovery board and click the Formatting panel.
2. Select a color palette to use for the board and any board-level color overrides.
3. To override board-level palettes and overrides, select a viz and set any field value overrides for the viz.
When you override a palette color, Workday assigns the next color in the palette to the next field value,
and so on, if multiple overrides exist.
4. Clear any overrides that you no longer need.
Related Information
Concepts
Concept: Color in Discovery Boards on page 317

Tasks
Group Data by Color in a Viz on page 313

Change Field Options for Visualizations

Prerequisites
Security: Discovery Boards: Create domain in the System functional area.

Context
You can change field names and how Workday displays summarization data for fields in your viz. You can
also override the display name of drop zones.
For KPI and Waterfall viz types, click Viz Options to configure the display name.

Steps
1. (Optional) On the Builder panel, access the drop zone menu and select the Override display name
check box in the Display name section.
You can enter a unique display name for these viz types:

Viz Type Drop Zones

Area Chart X-Axis, Y-Axis
Bar Chart X-Axis, Y-Axis
Bubble Chart X-Axis, Y-Axis
Chart X-Axis, Y-Axis
Donut Chart Angle, Color
Heatmap X-Axis, Y-Axis, Color
Line Chart X-Axis, Y-Axis
Scatterplot X-Axis, Y-Axis
2. (Available for all viz types except KPI and Waterfall.) Select a field in a drop zone and select Field
Options.
3. (Available for Pivot Table vizzes.) From the Display As drill down menu, you can display the
summarization field as a percentage of a total.
Overall Total is unavailable when the pivot table includes rows only.
4. (Optional) In the Field Display Name field, enter a unique display name.
Related Information
Tasks
Set Up Waterfall Viz Options on page 316
Set Up KPI Viz Options on page 315

Change the Formatting of a Numeric Summarization in a Viz

Prerequisites
Security: Discovery Boards: Create domain in the System functional area.

Context
You can specify the number format for Numeric summarization fields displayed in a viz. When you edit a
KPI or Waterfall viz, the number formatting you specify applies to every summarization field.

Steps
1. Select a viz that includes a summarization field.
2. Hover over a summarization field in a drop zone and select Formatting.
3. Select the desired formatting option, such as Percent.

Set Up KPI Viz Options

Prerequisites
Security: Discovery Boards: Create domain in the System functional area.

Context
When you create or edit a KPI viz, you can configure some KPI-specific options, such as:
• The variance (difference) between the base measure and the comparison measure. To display the
variance, you must include a field in the Comparison Measure drop zone.
• A visual cue that indicates the progress toward the intended result. The visual cues use an icon and/or
prominent background color to indicate progress. You can add rules that define when the current value
is expected, a warning, or critical.

Steps
1. Select a KPI viz.
2. Click Viz Options.
3. On the Comparison tab, define the Target options:
Option Description
Display name The label to display in the viz next to the target
value when the viz includes a comparison
measure.
4. (Optional) To display the difference between the base and comparison measures as a value, select
Show variance and define the variance options:
Option Description
Show as percentage Displays the variance as a percentage of the
target instead of a number. Select the number of
Decimal Places to display.
Calculation How to calculate the variance using the base and
comparison measure values.
Display name The label to display in the viz next to the variance
value.

5. (Optional) Select the Indicators tab, and add 1 or more rules that define progress toward the intended
result.
a) Select which value to evaluate against in each rule, either the Base measure value or Percentage
of target.
b) In the first rule, define the rule conditions by selecting the comparison operator, comparison value,
and the visual indicator to display.
c) (Optional) Click Add Rule to add another rule.
d) To change the order of rules, click the handle on the right side of a rule and drag into the desired
position.
Workday evaluates the rules in order starting at the top. The viz displays the indicator for the first
matching rule.
Related Information
Reference
2021R2 What's New Post: KPI Viz Type for Discovery Boards

Set Up Waterfall Viz Options

Prerequisites
Security: Discovery Boards: Create domain in the System functional area.

Context
When you create or edit a Waterfall viz, you can configure how to display the data and labels in the viz.
You can create a Waterfall viz using either of these methods:
• One field each in the Measures and Dimensions drop zones. Workday displays how the values of a
dimension field incrementally increase or decrease the value of a measure field. Example: You can
display headcount (measure field) by fiscal period (dimension field). You can change the sort order of
the dimension field values.
• Multiple fields in the Measures drop zone. Workday displays each field in order on the x-axis, using the
top field as the starting value. You can change the order of the measure values in the viz by changing
the order of the fields in the Measures drop zone.
The method you use to create a Waterfall viz determines the viz options you can configure.

Steps
1. Select a Waterfall viz.
2. Select Viz Options.
3. As you complete this step, consider:
Option Description
Show data labels Display the data value as text above each incremental increase or
decrease.
Hide Start Value By default, Workday uses the first value on the x-axis as the start
value and applies the Start color displayed in the viz legend to the
first value. When you enable this option, Workday:
• Hides the Start label from the viz legend.
• Changes the color of the first value on the x-axis to use either
the Increase or Decrease assigned color according to the field
value.

Option Description
Hide total Hide the total value, which displays the cumulative effect of all
increments in the last bar using a separate color.
Sort Order (Dimension drop zone only) Select how to sort the values from the
field in the Dimensions drop zone.
You can sort the data alphabetically, logically, or numerically in
ascending or descending order.

Limit (Dimension drop zone only) You can apply a limit on the number of
field values displayed on the axis with the dimension field.
For more information on limiting data, see Limit Viz to the Top N
Values on page 321.

Axis display names Override the default names that display on the x-axis and y-axis of
the viz.
Measure display names Override the default display names for each field in the Measures
drop zone.
When the viz has multiple fields in the Measures drop zone,
Workday uses these display names for the first measure and each
incremental measure.

Label display name Override the default display name for the total value (if included).

Related Information
Reference
2022R2 What's New Post: Waterfall Viz Type for Discovery Boards

Concept: Color in Discovery Boards

You can use color in discovery boards to apply more meaning to your vizzes. We provide a variety of color
palettes to help differentiate data across vizzes. Use the Formatting panel to make color selections for:
• Board level: Select a palette and specify any field value overrides.
• Viz level: Select a viz and specify any field value overrides.

Palettes and Overrides

You pick a color palette for a board and then assign colors that are meaningful. Example: You could assign
colors to represent specific products or functional areas: a beverage company could use the branding
colors of the top 5 competitors on its vizzes to quickly identify each product while analyzing the data (such
as red for Coke and blue for Pepsi).
You can change the overall color aesthetic on discovery boards without having to change each viz
manually. You can select from a variety of color palettes, including ones that are color-blind friendly or high
contrast to differentiate colors more easily.
You can override field value colors for most viz types:

Viz Type Overrides Available

Bar Chart Yes
Line Chart Yes
Area Chart Yes

Viz Type Overrides Available

Scatterplot Yes
Heatmap No
KPI NA
Waterfall Yes
Chart Yes
Donut Chart Yes

Color Assignment Rules and Considerations

• Colors from the selected palette are assigned dynamically, so the color assignment might change
based on the data in the viz. If you want to apply a specific color to a data value, assign the color
manually as an override to persist the color. Color assignments made by the system are based on
the legend items returned in the viz query, which takes instance-level and cell-level security into
consideration.
• Color assignments for measures apply to all data sources used on the board. Color assignments for
dimensions are specific to the data source and can be different.
• Color assignments depend on whether there's a field in the Color drop zone on the Builder panel. Until
there’s a dimension in the Color drop zone, color assignments are driven by measures.
• Color assignments are persisted when switching between chart types that support color assignments.
• For Waterfall charts, there's a 4-color palette that represents the start, increase, decrease, and total
data values. You can swap the increase and decrease colors from the palette to make those selections
more meaningful. Example: For a decrease that is actually a positive trend, assign a color that visually
represents the trend (green instead of red).
Related Information
Tasks
Group Data by Color in a Viz on page 313
Change Viz Colors on page 313
Reference
2022R2 What's New Post: Color in Discovery Boards

Filtering and Sorting Data in Visualizations

Filter Data in a Viz

Prerequisites
These domains in the System functional area:
• Drive
• Discovery Boards: Create

Context
You can constrain data in a viz by filtering on an attribute field. Viz filters enable you to filter data in a single
viz, while sheet filters enable you to filter data on all vizzes in the sheet that use the same data source.
As you filter data in a viz, consider:
• Some filter operators will be slower than others.

• Workday applies the filter in the order that they’re listed in the filter panel. Consider placing filter
conditions that constrain the largest amount of data toward the top of the filter panel for better
performance.

Steps
1. Access your discovery board from Drive.
You can also access your discovery board as a worklet from the Home page.
2. Select a viz that uses the combination of data source and data source filter you want to filter.
3. Select the filter panel on the left side of the discovery board workspace.
4. Add a filter to the Sheet Filters or Viz Filters section.
5. As you complete the task, consider:
Option Description
Field Select the field that you want to filter.
Workday doesn't support lookup date rollup
calculated fields on sheet or viz filters.

Filter Operator Workday displays the operators available for the

selected field.
Filter Values Available options depend on the selected field
and filter operator.
6. (Optional) Select the filter menu and select an option to change the properties of the filter:
Option Description
Determine Value Dynamically Use this option to change the filter from static to dynamic, meaning
that Workday determines the filter value based on some context,
such as the current date or current user.
When you update a filter to be dynamic, select a field that
determines the filter value dynamically. These fields are on the
Global business object. These Global fields aren't available:
• Fields with built-in prompts.
• Calculated fields with these functions:
• Date Constant
• Lookup Field with Prompts
• Numeric Constant
• Prompt for Value
• Text Constant
Example: In a date filter's input, you select the field First Day of
This Month. When you view the discovery board, Workday:
• Determines the first day of the current month.
• Uses that value for the filter.
• Displays data in the viz based on that filter value.
You can't create a control linked to a dynamically determined filter.

Move to Sheet and Move to Viz Use this option to change which vizzes the filter applies to.
A viz filter applies to the selected viz, and a sheet filter applies to all
vizzes on the sheet that use the same data source and data source
filter.

Option Description
Create Control and Link Use this option to create a control and link it to the filter, giving
viewers control over the data returned.
When you select a value in a control, Workday applies that value
as the input to the linked filter.
Any changes you make to the values of a control in view mode
only apply to view mode in your current session. Example: You
are in view mode and select different values for the control, and
then switch to edit mode. Workday reverts the control values to the
saved version of the discovery board.
See Concept: Discovery Board Controls on page 308.

Remove Deletes the filter from the discovery board.

Disable Use this option to turn off the filter temporarily without removing it.

Related Information
Concepts
Concept: Viz Filters on page 322
Concept: Discovery Board Controls on page 308
Tasks
Limit Viz to the Top N Values on page 321
Set Up Discovery Boards as Home Page Worklets on page 292
Reference
2023R1 What's New Post: Discovery Board Controls
2023R1 What's New Post: Discovery Board Filters

Sort Data in a Viz

Prerequisites
Security: Discovery Boards: Create domain in the System functional area.

Context
You can sort attribute data in a visualization to arrange the data in a meaningful order for analysis, such as:
• Alphabetically
• Chronologically
• Logically
• Numerically
You can sort the data in a Waterfall viz when there's a field in the Dimensions drop zone. For details, see
Set Up Waterfall Viz Options on page 316.

Steps
1. Select a viz with at least 1 attribute field in a drop zone.
2. (Area Chart, Bar Chart, Chart, Heatmap, and Line Chart viz) Click the drop zone options for the X-Axis
or Color drop zone.
3. (Donut Chart and Scatterplot viz) Click the drop zone options for the Color drop zone.
4. (Pivot Table viz) Click the drop zone options for the Columns or Rows drop zone.
5. (Table viz) Hover over an attribute field in the Columns drop zone and select Table Options.

6. Select the Sort Order.

When you add fields to a viz, Workday automatically sorts the data by Logical Sort. If Logical Sort
isn't applicable to the viz, Workday automatically sorts the data alphabetically (chronologically and
numerically for date and numeric fields) in ascending order.
For Donut Charts, the first mark in a sorted list starts at the Y-axis, which is the top half of a vertical
line going through the circle. The next mark in the sorted list displays next to the first in a clock-wise
rotation.

Limit Viz to the Top N Values

Prerequisites
Security: Discovery Boards: Create domain in the System functional area.

Context
Another way to filter data in a visualization is to apply a limit on the number of attribute values displayed.
You can limit attribute values in these viz types:
• Area Chart
• Bar Chart
• Chart
• Donut Chart
• Heatmap
• Line Chart
• Scatterplot
• Pivot Table
Workday limits the data if the number of unique values exceeds the configured limit. Workday automatically
defines different limit values depending on the viz type and drop zone. Example: Workday automatically
limits the Color drop zone in Donut Chart vizzes to 20 values. You can change the limit values of different
drop zones, up to a different maximum for each.
Limiting data in a viz works with how you sort the data. You can change how you sort the data when you
edit the limit settings.
For most viz types, you can sum all other values into a single value labeled Other. You can't sum all other
values in a Pivot Table viz.
You can limit the values in a Waterfall viz when there's a field in the Dimensions drop zone. For details,
see Set Up Waterfall Viz Options on page 316.

Steps
1. Select a viz with at least 1 attribute field in a drop zone.
2. Click the drop zone options for the X-Axis, Columns, Rows, or Color drop zone that contains an
attribute field.
When you change the orientation of a Bar Chart viz to horizontal, you can click the Y-Axis drop zone
options.
3. Select the number of values to Limit.
4. (Optional for Area Chart, Bar Chart, Chart, Donut Chart, Heatmap, Line Chart, and Scatterplot) Select
Sum Remaining Values.
Related Information
Reference
Reference: Reporting Limits

Concept: Viz Filters

You can filter on an attribute field to constrain the data Workday displays in discovery board sheets and
visualizations. Filtering on a field enables you to include records in the viz based on the values of the
selected field.
Create and edit filters on the Filter panel. You can create these types of filters:
• Viz filters, which apply only to the selected viz.
• Sheet filters, which apply to all vizzes on the sheet that use the same data source and data source filter.
You can create multiple sheet and viz filters on a field. The order of filters doesn't matter because Workday
applies an AND condition to all filters that apply to a viz.
As you create filters, consider that Workday doesn't support lookup date rollup calculated fields on sheet or
viz filters.
Related Information
Tasks
Filter Data in a Viz on page 318

Sharing Visualization Insights

Export a Viz as a Custom Report

Prerequisites
Security: These domains in the System functional area:
• Custom Report Creation
• Discovery Boards: Create

Context
You can export these viz types as a custom report in Workday:
• Chart
• Donut Chart
• Pivot Table
• Table
When you export a viz as a custom report, consider:
• Each time you export a viz, Workday creates a new report definition.
• Fields not supported in discovery boards might display in custom reports. Example: Discovery boards
don't support time field types, but Report Writer does. If you use a datetime field, Workday displays only
the date in a viz, but displays the date and time in the custom report.
• The chart and sort options you select for the viz might not display the same way in the exported custom
report.
• The drill by and show details fields you set up might differ in the custom report.
• The type of report that Workday creates depends on the type of viz you export.
• A Chart and Donut Chart viz becomes a Matrix report with the chart and table displayed.
• A Pivot Table viz becomes a Matrix report with only the table displayed.
• A Table viz becomes an Advanced report.
• For Chart and Donut Chart vizzes, color overrides aren't exported.
• Workday assigns you as the owner of the report.
• Workday sets the report definition sharing options to Don't share report definition.

• You can edit the report definition after Workday creates the report.

Steps
1. Select a viz.
2. Select Export as a Report from the viz menu in the upper right corner.
3. Enter the name of the report definition.

Result
Workday creates the report definition and runs the report. You can view the report immediately in a new
tab.

Download Visualizations

Prerequisites
Security: Discovery Boards: Create domain in the System functional area.

Context
You can download visualizations as CSV or PNG image files to your computer.

Steps
1. Select a viz.
2. (Available for all viz types except Matrix Report - Pivot Tables and Advanced Report - Tables.) Select
Download as PNG from the related actions menu of the viz.
3. (Available for Matrix Report - Pivot Tables and Advanced Report - Tables only.) Select Download as
CSV from the related actions menu of the viz.
You can also select Download as CSV from the related actions menu of Drill By and Show Details
results.
Downloading large volumes of data might impact the performance of your browser. You can't download
multiple CSV files simultaneously.

Result
Workday generates a CSV or PNG file and saves it to the directory configured in your browser. The
filename is the same as the viz name.
The viz title and description (if populated) are exported with the viz.
When you open the CSV file, consider the application you select might impose limitations different from
Workday. Example: Microsoft Excel limits the number of characters in each cell to 32,767.

Prism Analytics

Steps: Set Up Tenant for Prism Analytics

Prerequisites
You need to create a Tenant Management case with Workday and create a Tenant - Setup Feature
request to provision Prism Analytics hardware for your tenant.

Security: Security Configuration domain in the System functional area.

Context
Set up Prism Analytics to enable data administrators and data analysts to create tables and datasets for
blending Workday and non-Workday data that data analysts can analyze inside Workday.

Steps
1. Create User-Based Security Groups.
Create security groups for your data administrators and data analysts, and assign users.
Example: You can define these security groups (administered by the Security Configurator group):
• Prism Data Writer
• Prism Data Administrator
2. Create Prism Access Security Groups.
Create security groups for your data administrators and data analysts, and assign unconstrained
security groups. This security group type doesn't accept users directly. Instead, you associate 1 or more
unconstrained security groups with the group.
Example: You can define these security groups (administered by the Security Configurator group):

Group Name Unconstrained Security Group to Associate

Prism Data Writer (Prism Access) Prism Data Writer
Prism Data Administrator (Prism Access) Prism Data Administrator
Security Administrator (Prism Access) Security Administrator
Security Configurator (Prism Access) Security Configurator
3. (Optional) Create Role-Based Security Groups.
Note: When you create a role-based (constrained) security group for any of the dataset-related roles,
you must select Role has access to the positions they support for the Access Rights to Multiple
Job Workers option.
4. Access the Maintain Functional Areas task.
Select the Enabled check box for the Prism Analytics functional area.

5. Edit Domain Security Policies.

Create or edit a security policy for these domains:
• Prism Datasets: Create
• Prism Datasets: Manage
• Prism Datasets: Owner Manage
• Prism Datasets: Publish
• Prism: Manage Data Source
• Prism: Manage Relax Sharing
• Prism: Tables Create
• Prism: Tables Manage
• Prism: Tables Owner Manage
• Prism: Manage Connection
• Prism: Manage File Containers
Workday suggests that you use the security groups you created.

Domain Security Groups Task Permissions

Prism Datasets: Create Prism Data Administrator (Prism Access), Prism View and Modify
Data Writer (Prism Access)
Prism Datasets: Prism Data Administrator (Prism Access) View and Modify
Manage
Security Configurator (Prism Access), Security View only
Administrator (Prism Access)

Prism Datasets: Owner Prism Data Administrator (Prism Access), View and Modify
Manage Security Administrator (Prism Access)
Prism Datasets: Publish Prism Data Administrator (Prism Access), View and Modify
Security Configurator (Prism Access)
Prism: Manage Data Security Configurator (Prism Access) View and Modify
Source
Prism: Manage Relax Prism Data Administrator (Prism Access) View and Modify
Sharing
Prism: Tables Create Prism Data Administrator (Prism Access), Prism View and Modify
Data Writer (Prism Access)
Prism: Tables Manage Prism Data Administrator (Prism Access) View and Modify
Security Configurator (Prism Access), Security View only
Administrator (Prism Access)

Prism: Tables Owner Prism Data Administrator (Prism Access), View and Modify
Manage Security Administrator (Prism Access)

Prism: Manage Prism Data Administrator, Prism Data Writer View and Modify
Connection
Prism: Manage File Employee as Self, Contingent Employee as Self View and Modify
Containers (optional)
6. Activate Pending Security Policy Changes.
7. Set Up Dataset Sharing on page 421.
8. Set Up Table Sharing on page 419.

9. (Optional) Enable users with Dataset Viewer permission to see dataset transformations. Workday
recommends not enabling this option if you've shared a dataset that contains potentially sensitive data.
a) Access the Edit Tenant Setup - Reporting and Analytics task.
b) Select Enable Prism Dataset View Transformations in the Prism Analytics section.
10.(Optional) Enable Contextual Publishing for Datasets on page 440.
11.(Optional) Customize notification settings.
a) Access the Edit Tenant Setup - Notifications task.
b) Select the System notification group in the Notification Delivery Settings section.
c) Customize these notification settings:
• Prism Data Acquisition Notification
• Prism wBucket Complete Notification
d) Select the Prism Analytics notification group.
e) Customize these notification settings:
• Manual Dataset Publish Notifications
• Prism Data Change Notification
• Scheduled Dataset Publish Notifications
You can only mute or unmute email notifications.
See Reference: Edit Tenant Setup - Notifications.
Related Information
Concepts
Concept: Security in Prism Analytics on page 427
Tasks
Create Prism Access Security Groups
Reference
Community article: Setup Feature Tenant Request
2021R1 What's New Post: Dataset Viewer
2021R1 What's New Post: Prism Analytics Security Domains

Steps: Set Up Tenant for Analytic Data Source

Prerequisites
• Security: Security Configuration domain in the System functional area.
• Set up the tenant for Prism Analytics.

Context
Set up your tenant so you can install and configure analytic data sources, and make them available for
data analysts to use.

Steps
1. Create User-Based Security Groups.
Create security groups for your data administrators and data analysts, and assign users.
2. Access the Maintain Functional Areas task.
Select the Enabled check box for the Analytical Framework functional area.
See Steps: Enable Functional Areas and Security Policies

3. Edit Domain Security Policies.

Create or edit a security policy for the Manage: Analytic Data Sources domain. Workday suggests that
you use the security group you created and provide both View and Modify task permissions.
4. Activate Pending Security Policy Changes.
Related Information
Concepts
Concept: Workday-Delivered Analytic Data Sources on page 456
Tasks
Steps: Set Up Tenant for Prism Analytics on page 323
Steps: Enable Functional Areas and Security Policies

Concept: Prism Analytics Data Management Workflow

With Workday Prism Analytics, you can analyze your Workday and non-Workday data together without
having to export it into a separate data warehouse and BI (business intelligence) application. This makes
analysis faster, easier, more secure, and performed in a location where users can take action on it.
What are the steps involved in going from raw data (both internal and external to Workday) to
visualizations and reports in Workday? What skills do you need to perform each step? This section
explains each phase of the data workflow from transforming data to analyzing it.

Phase 1: Create Tables and Data Change Tasks to Bring in Data

The first phase in the data management workflow is to bring data into the Prism Analytics Data Catalog.
You can bring in external data or Workday transactional data. The Data Catalog is where data analysts can
see what data is available to them.
You bring in data by creating a table. A table is a Prism Analytics object that stores (materializes) data and
represents it in a tabular format. A table has a schema and contains data that's valid against the schema.
After you create a table, you create a data change task to load or change data in the table.
You can also create a base dataset to bring in data. However, Workday recommends creating tables only.
Example: You create a table to contain external operational data, and then create a data change task that
loads that data from a delimited file on an external server into the table. You create a schedule for the data
change task to run on a recurring basis.
Example: You create a table and data change task using data in a Workday custom report.
If you're familiar with ETL workflows (extract, transform, and load), tables and data change tasks together
encompass the extract logic.

Who does this phase? Data Administrators or Data Analysts.

Where can I read more details? Concept: Tables on page 333
Steps: Create a Table by File Upload on page
355
Steps: Create Table from a Workday Report on
page 357
Steps: Create a Table Manually on page 359
Edit a Table on page 384
Concept: Data Change Tasks on page 415
Create a Data Change Task on page 410

Create a Data Change Task Schedule on page

413
Concept: Data Catalog on page 338
Concept: Creating Reports to Import into Tables
and Datasets on page 330

Phase 2: Create Derived Datasets to Transform the Data

After you've brought in data into the Data Catalog, you create derived datasets based on tables and other
datasets to transform, enrich, and join the data. Create a derived dataset to describe the processing logic
that you need to prepare the data for analysis.
Derived datasets contain information on how to process, blend, and transform the data you import into
them. Transforming data is an iterative process and typically involves creating multiple derived datasets
based on other tables and derived datasets. You can:
• Create new fields by creating a Prism calculated field.
• Add 1 or more stages in a derived dataset that perform different actions, such as aggregating, joining,
or filtering. Some stage types can change either the number of records or fields in the dataset.
Example: You can create a derived dataset that aggregates data into groups using a Group By stage, and
then create another derived dataset based on this dataset that joins the aggregated data with another
dataset using a Join stage.
Example: You can create a Prism calculated field to calculate the point of sales revenue per store.
From the perspective of an ETL workflow, the derived dataset encompasses the transform logic.

Who does this phase? Data Administrators or Data Analysts.

Where can I read more details? Concept: Datasets on page 336
Concept: Dataset Workspace on page 336
Steps: Create a Derived Dataset on page 367
Add a Prism Calculated Field to a Dataset on page
389
Concept: Dataset Stages on page 342
Manage Dataset Fields on page 392
Add a Stage to a Dataset on page 391
Reference: Explode Stages on page 398
Reference: Filter Stages on page 398
Reference: Group By Stages on page 400
Reference: Join Stages on page 401
Reference: Union Stages on page 402
Reference: Unpivot Stages on page 403
View Table and Dataset Lineage on page 372

Phase 3: Apply Security to the Data

Workday applies no security to the objects inside the Data Catalog. External data doesn't have any
security applied to it, and when you bring Workday data into the Data Catalog, Workday removes the

existing security from the fields in the tables and datasets. As a result, any user who has access to a table
or dataset in the Data Catalog can see all data in the objects they have access to.
Before you make any data in the Data Catalog available for analysis, you need to apply security to the data
using the existing Workday security domains. Applying security to the data you plan to make available for
analysis enables you to take advantage of Workday's strong, configurable security model for external data
as well as Workday data.
You configure the data security by editing the data source security on the dataset or table, but Workday
applies the security to the data in the form of a Prism data source (see next phase).

Who does this phase? Security Administrators or Data Administrators.

Where can I read more details? Concept: Security in Prism Analytics on page 427
Edit Prism Data Source Security on page 424

Phase 4: Make the Data Available for Analysis

You can decide which data in the Data Catalog to make available for analysis by creating a Prism data
source from either a table or dataset. When Workday creates a Prism data source, it loads the data source
with the data from the table or dataset, and applies the appropriate security restrictions to the data source,
fields, records, and field values.
The way you create a Prism data source depends on the Data Catalog object:
• Table. Edit the table schema and select the Enable for Analysis option.
• Dataset. Publish the dataset. On the View Dataset Details report, select Quick Actions > Publish.
Workday applies the security domains configured in the data source security for the table or dataset, or it
applies the Prism: Default to Dataset Access security domain if no data source security was configured.
The Prism: Default to Dataset Access domain provides contextual access to a Prism data source based on
your access to the underlying table or dataset.
You can use Prism data sources in visualizations and reports like any Workday delivered data source.
From the perspective of an ETL workflow, enabling a table for analysis and publishing a dataset are the
load part of the process.

Who does this phase? Data Administrators or Data Analysts.

Where can I read more details? Concept: Making Prism Data Available for Analysis
on page 444
Edit a Table on page 384
Concept: Dataset Publish Schedules on page 445
Create Dataset Publish Schedules on page 442
Publish a Dataset as a Prism Data Source Manually
on page 441

Phase 5: Analyze and Visualize the Data

After a Prism data source is available, Report Writers can use it to create discovery boards and reports.
Related Information
Concepts
Concept: Security in Prism Analytics on page 427
Tasks
Steps: Create a Table Manually on page 359

Steps: Create a Dataset with External Data (SFTP Server) on page 360
Steps: Create a Dataset with External Data (Upload a File) on page 364
Steps: Create a Dataset Using Workday Data on page 365
Steps: Create a Derived Dataset on page 367
Edit Prism Data Source Security on page 424
Publish a Dataset as a Prism Data Source Manually on page 441
Create Dataset Publish Schedules on page 442
Reference
The Next Level: Prism Analytics Community Guide
The Next Level: Move up the Workday Maturity Curve: Considerations in Defining an Analytics Strategy
The Next Level: Create a Vaccine Management Solution Using Prism and Discovery Boards
The Next Level: Estimating Prism Projects - Creating an Estimator Framework
The Next Level: Scoping a Prism Project

Concept: Creating Reports to Import into Tables and Datasets

Tables and Data Change Tasks

To create a table from a Workday report, or to use a Workday report as a source in a data change task, the
report must be configured:
• As an advanced report. Tables and data change tasks don't support importing other report types, such
as matrix or composite.
• As a web service.
• For Prism Analytics. Select the Enable for Prism check box in the Advanced tab of the custom report.
Workday doesn't support selecting reports when the report includes:
• Fields from a related business object that have a many to 1 relationship with the primary business
object.
• Prompts, except for optional prompts and required prompts with a default value set.
Note: If your custom report includes a Currency field, you must select the Show Currency Column check
box in the Field Options column for the Currency field, located in the Columns tab of the report.
To optimize performance when running a data change task, consider these options:
• Use indexed data sources whenever possible.
• Use data sources that provide the smallest possible set of data that meets your needs. Example: If
you're interested in compensation-related transactions, use employee compensation events instead of
all business process transactions.

Datasets
To create a dataset from a Workday report, the report must be configured:
• As an advanced report. Tables and data change tasks don't support importing other report types, such
as matrix or composite.
• As a web service.
• For Prism Analytics. Select the Enable for Prism check box in the Advanced tab of the custom report.
Workday doesn't support selecting reports when the report includes:
• Fields from a related business object that have a many to 1 relationship with the primary business
object.

Note: If your custom report includes a Currency field, you must select the Show Currency Column check
box in the Field Options column for the Currency field, located in the Columns tab of the report.
To optimize performance, consider these options:
• Use indexed data sources whenever possible.
• Use data sources that provide the smallest possible set of data that meets your needs. Example: If
you're interested in compensation-related transactions, use employee compensation events instead of
all business process transactions.
Related Information
Tasks
Steps: Create Table from a Workday Report on page 357
Steps: Create a Dataset Using Workday Data on page 365

Concept: Prism Data Sources

A Prism data source is a type of data source that gets its data from a Prism Analytics table or dataset.
Typically, Prism data sources blend together Workday and non-Workday data.
Prism data sources are different than Workday-delivered data sources in several ways. Prism data
sources:
• Are created by a colleague at your organization.
• Have their own primary business object that isn't linked to any other business object in Workday.
• Can become inactive. When a Prism data source is inactive, it exists in the tenant, but is empty and
unavailable for querying in reports and discovery board visualizations.
• Can be deleted from your tenant. You can only remove a Prism data source when no reports or vizzes
currently use the associated Prism data source.
• Only support some report types.
• Only support some field types.
• Only support some calculated fields. Some of the supported calculated fields provide limited
functionality.
Prism data sources also have their own security. Security group access controls who can see a Prism data
source.
With the appropriate permissions, you can:
• Create a viz in a discovery board using the Prism data source.
• Create a custom report using the Prism data source.
• View a Prism data source by accessing the View Prism Data Source report.
• Make the Prism data source inactive.
• Remove the Prism data source from the tenant.

Supported Custom Reports on Prism Data Sources

You can create these types of custom reports using a Prism data source:
• Advanced. Some features aren't supported, such as Subfilters. Workday only displays features that
it supports. Also, only add a field from a related business object when necessary. Fields from related
business objects might impact report performance.
• Composite. The Prism data source must include at least 1 Instance field.
• Matrix. Most features are supported. Lookup Prior Value isn't supported.
• Simple. All features are supported.
• Transposed. All features are supported.

Supported Calculated Fields on Prism Data Sources

You can create these calculated fields using Prism data sources:
• Arithmetic Calculation
• Build Date
• Concatenate Text
• Convert Text To Number
• Date Constant
• Date Difference
• Evaluate Expression
• Format Date
• Format Number
• Format Text
• Increment or Decrement Date
• Lookup Date Rollup
• Numeric Constant
• Substring Text
• Text Constant
• Text Length
• True/False Condition
Workday only makes available calculated fields that are supported for Prism data sources.
There are some limitations when creating some calculated fields:
• Calculated fields only work on supported field types. Example: date-related functions work only on fields
of type Date.
• You can't use Instance or Multi-Instance fields in some calculated fields, such as Format Text and
Substring Text. This is because Instance and Multi-Instance fields in Prism data sources only include
the unique identifier information (also known as a WID), not the display name.
Related Information
Concepts
Concept: Prism Analytics Data Management Workflow on page 327
Concept: Deleting Prism Data on page 453
Tasks
Unpublish a Dataset on page 452
Delete Rows from a Prism Data Source on page 453
Reference
The Next Level: Prism Analytics Community Guide

Reference: External Data Limits

Workday enforces limits when you create a table or dataset using the REST API or the UI. The limits apply
when you:
• Create a table or dataset in the UI by uploading a file. Workday creates and uses a bucket.
• Create a data change task in the UI by uploading a file. Workday creates and uses a file container.
• Run a data change task in the UI by uploading a file. Workday creates and uses a file container.
• Upload a file to a file container using the REST API.
• Create a bucket using the REST API.
• Upload a file to a bucket using the REST API.
Workday enforces these limits:

Limit Value
Maximum size of a single file 256 MB compressed
Maximum number of buckets that can be created in a 24-hour rolling 1,000
period
Maximum number of data change activities and bucket completions that 1,000
can be run in a 24-hour rolling period
Maximum number of concurrent uploads using any method 10
Maximum number of files in all file containers and buckets in a 24-hour 50,000
rolling period
Maximum size of all files in all file containers and buckets in a 24-hour 125 GB compressed
rolling period

Related Information
Tasks
Steps: Create a Table by File Upload on page 355
Create a Data Change Task on page 410
Steps: Create a Dataset with External Data (SFTP Server) on page 360
Steps: Create a Dataset with External Data (Upload a File) on page 364
Upload a New File to a Dataset on page 371

Table and Dataset Concepts

Concept: Tables
A table is a Workday Prism Analytics object that stores (materializes) data and represents it in a tabular
format. A table has a user-defined schema and only contains data that's valid against the schema. The
data in tables is backed by a distributed columnar data store.
You create tables to bring in data from multiple sources and store it in a central location, the Data Catalog
(similar to a data warehouse). You can then join, transform, blend, and enrich table data using derived
datasets based on the table. Use derived datasets to prepare data for analysis.

Tables Compared to Base Datasets

A table is similar to a base dataset with important differences.

Concept Tables Base Datasets

Schema You define the table schema before Base datasets control underlying data
you load data into the table. If you’re stored in files. Dataset schemas describe
familiar with databases, this is commonly how to read (and later transform) the
referred to as schema-on-write. data stored in those files. If you’re
familiar with databases, this is commonly
You can still change the table schema,
referred to as schema-on-read.
but there are requirements and
limitations. Example: You can add/ Although you can change the dataset
remove fields at any time, but if you want schema at any time, you must make sure
to change the field type, the table must that the schema matches the data in
be empty (zero rows). Schema changes the underlying files so that it recognizes
are destructive. Example: if you remove the data correctly. If the schema doesn't

Concept Tables Base Datasets

a field, you lose all data contained in the match the file, then Prism sets value as
field. null.

Source type Tables can accept data from any type of A base dataset only accepts data from
source at any time, such as file upload, a the same source type that you used
dataset, or REST API. when you created the dataset. That is, if
you create a dataset using SFTP, it will
Create data change tasks to load data
only accept data from an SFTP server.
into and change data in a table. You
can use a different source type for each
data change task that works on the same
target table.
Example: You create 2 data change
tasks that use the same target table and
these source types:
• A delimited file that inserts data.
• A derived dataset that updates data.

Data validation When you load data into a table, When you publish a dataset, Workday
Workday validates the data against the reads the data stored on disk and
defined schema. validates it against the current schema of
the base dataset.
If the value for a field doesn’t match the
field type or other field parameters (such If the value for a field doesn’t match the
as date format), then Workday marks field type or other field parameters (such
the entire row as invalid and doesn’t as date format), then Workday marks
include the row in the table. Instead, the that field value as NULL and includes the
row is sent to an error file that you can row in the published Prism data source.
download.

NULL handling Every field allows NULL values unless Every field allows NULL values.
you configured it as required.
Workday doesn’t distinguish between
Workday distinguishes between NULL NULL values and empty string values in
values and empty string values in Text delimited files.
fields when reading a delimited source
file to load data into a table.
If a delimited file contains:
• 2 consecutive field delimiters only,
then Workday treats the field value as
NULL. Example: "Smith",,"Tom"
• 2 consecutive field delimiters with
the 2 consecutive quote characters
in between, then Workday treats
the field value as an empty string.
Example: "Smith","","Tom"

Name restrictions Tables have 2 names: Base (and derived) datasets have 2
names:
• Name. This is a display name that
displays in the Data Catalog. You can • Name. This is the name that displays
change the display name. in the Data Catalog. You can
• API Name. This is a unique name change the display name. Publishing
used to reference the table in the API. renamed datasets won’t affect reports

Concept Tables Base Datasets

You can’t change the table API name or discovery boards that use the
after you create the table. original names.
Table fields also have a display name • API Name. This is a unique name
and an API Name. You can change the used to reference the dataset in the
display name at any time. However, you API. You can't change the dataset
can’t change the API name after you API name after you create the
create the field and save the table. dataset.

Display, API, and field API names must Dataset fields only allow 1 name and you
be unique and conform to the name can change it at any time. But you must
validation rules. ensure to fix any downstream errors
that might result from changing the field
See Reference: Naming Guidelines on name.
page 376 for more details.
Display and API names must be unique
and conform to the name validation
rules.

Deleting data You can remove all rows (truncate) or You can remove all rows (truncate)
some rows (delete) from a table. from a base dataset. You can’t delete a
subset of rows.
You can selectively delete rows based
on a key field. You might want to do this
when you append data to the table and
you need to remove the rows added from
a particular load.

Make Prism data Use the Enable for Analysis option Publish the dataset to create a Prism
source when you create or edit the table data source.
schema to create a Prism data source.
Row count Workday knows exactly how many rows Workday doesn’t know how many rows
of data exist in a table, and it displays of data exist in a base dataset.
the number of rows in the Data Catalog
and on the View Table Details report.

Related Information
Concepts
Concept: Datasets on page 336
Reference
2020R1 What's New Post: Prism Analytics Tables
Reference: Naming Guidelines on page 376

Concept: Table Error File

When you load data into a table, Workday validates the data against the defined schema.
If the value for a field doesn’t match the field type or other field attributes (such as date format), then
Workday marks the entire row as invalid and doesn’t include the row in the table. Instead, Workday sends
the row to an error file that you can download.
Use the error file to get a list of all rows that failed to load into the table. You can fix the errors in the data,
remove the extra fields that Workday adds, and load the fixed data into the table.
The error file:
• Is a CSV file.

• Includes all fields defined in the table schema plus fields for troubleshooting:
• Error Code
• Error Message
• Includes all failed rows up to a maximum of 10,000 rows. If there are more than 10,000 error rows, then
Workday rejects the load with a status of Failed.
To download the error file, access either:
• The Activities tab on the View Table Details report.
• The Prism Activities Dashboard from the Data Catalog.
Click the download icon for an activity that included some errors.
Related Information
Reference
Reference: Table Error File Error Codes on page 354

Concept: Datasets
A dataset is a Prism Analytics object that controls some underlying data and describes some processing
logic to manipulate the data. A dataset is a description of the data, otherwise known as metadata. It
contains all of the data about the data, plus a subset of example rows to help you understand the data
values. You create datasets to prepare data for analysis.
A dataset can describe either Workday or non-Workday (external) data. You might want to create a dataset
using external data to blend, transform, and enrich it with Workday data. This enables you to analyze
your Workday and non-Workday data together without having to export it into a separate electronic data
warehouse and business intelligence (BI) application.
A dataset can also describe data that's output from another table or dataset by deriving the dataset from an
existing table or dataset.
You can create a:
• Base dataset. A base dataset is a dataset that is based on 1 or more source files. The source files can
come from external sources (non-Workday data) or from the output of a Workday custom report. You
create a base dataset when you create a new dataset using these options:
• from File. This option creates a dataset with external data that you upload in the browser.
• from SFTP. This option creates a dataset with external data that Workday retrieves from an SFTP
server using an integration.
• from Custom Report. This option creates a dataset with Workday data.
• Derived dataset. A derived dataset is a dataset that is based on 1 or more existing tables or datasets.
The source data of a derived dataset comes from the output of existing tables and datasets. You use
derived datasets to blend data together from different sources, such as Workday data and non-Workday
data. Some stage types, such as Join and Union, are only available to derived datasets. You create a
derived dataset when you create a new dataset using the Derived Dataset option.

Concept: Dataset Workspace

The Edit Dataset Transformations task is where you make changes to the dataset definition to
manipulate data. This task acts like a single page application, meaning you can interact with elements on
the task dynamically as if it were its own application. You can also make all the changes you want, such
as adding Prism calculated fields and stages. When you're done, click Save to save all changes to the
dataset.
If you have permission to edit a dataset, you can access the Edit Dataset Transformations task using
these methods:
• Right-click the dataset name on the Data Catalog report and select Edit Transformations.
• Select Edit Transformations from the Quick Actions on the View Dataset Details report.

• Access the Edit Dataset task and select the dataset name that you want to edit.
• When creating a dataset for the first time, the workflow leads you to the Edit Dataset Transformations
task.
When you view the Edit Dataset Transformations task, you see these components:

1. Pipeline list. (Derived datasets only.) Click Change Pipeline to view a collapsible panel that lists all
tables and datasets that you've imported into the derived dataset. Importing a table or dataset creates
a new pipeline. You can also use this panel to add a new pipeline by importing an additional table or
dataset. When you select an item in the pipeline list, the pipeline details panel displays the details for
that pipeline.
2. Pipeline details panel. This panel displays every stage in the dataset pipeline, starting with the first
stage that created the pipeline. For base datasets that can be an Import or Parse stage depending on
where the source data comes from. For derived datasets, it's an Import stage. You can:
• Add, edit, and delete stages.
• Manage dataset fields.
• View stage descriptions.
• View the number and names of Prism calculated fields in a stage.
• Collapse this panel to increase the available space in the example data table.
3. Example data table. The example data table takes up most of the space on the Edit Dataset
Transformations task. It displays the current view of the data (records and fields) for the output of the
currently selected pipeline stage.
4. Inspector panel. This panel displays when you select a field in the example data table. You can hide
this panel to increase the available space in the example data table. This panel has these tabs:
• Field Info. This tab displays detailed information about the selected field, including statistics on the
values in the field. All statistics are based on the data currently shown in the example data table.
Therefore, to get more precise numbers, increase the number of example rows.
• Functions Library. This tab displays the functions that you can use in a Prism calculated field
expression, including description, syntax, and an example. You can search for a specific function.

You can click the + icon next to the function name to insert the function at the current location in the
Prism calculated field expression.
5. Prism calculated field expression bar. Click Add field to add a new Prism calculated field, and then
enter the field expression. You can:
• Use the expression bar later to edit the field expression.
• Expand the expression builder to create and view multiline expressions.
• Edit the field name in the inspector panel.
6. Stage statistics and search bar. For a selected stage, you can see the number of:
• Fields
• Prism calculated fields
• Field-related errors
You can see the ID for stages. The stage ID is a unique ID that Workday assigns to the stage based on
the order you added the stage to the dataset. For each stage you add, the stage ID increases.
If you use Microsoft Excel, there are potential limits on the number of characters your cells can contain
when you download all values.
7. Download example data.
8. Search for a field and navigate to it directly.
9. Example data controls. Use this menu to filter the example data displayed in the dataset.
10.Table and list view. You can view the example data table as a table or a list. The field list view navigator
enables you to see distinct, null, median, and top values at a glance. When you edit a new dataset, the
default view is table view. Each time you change the view, the last view you select becomes the default
view.
11.Edit dataset details. Use the configuration icon to open a pop-up where you can:
• Change the dataset display name.
• Create and edit tags.
• Edit the dataset description.
• View the dataset API name.
12.Dataset actions menu. Use this menu to quickly access the View Dataset Details and View Dataset
Lineage reports.
Related Information
Concepts
Concept: Dataset Stages on page 342
Concept: Dataset Pipelines on page 342
Concept: Prism Expression Language on page 458
Tasks
Change the Dataset Example Rows on page 395
Reference
2021R1 What's New Post: Dataset Viewer

Concept: Data Catalog

The Data Catalog report is your starting point for using Workday Prism Analytics. The report displays the
data available to you. If you have the appropriate permissions, you can:
• Bring in and store data from multiple sources using either tables or base datasets.
• Create derived datasets to transform the data.
• Create data change tasks to change data in a table using data from a source.
You can also:
• Customize your view of datasets and tables by filtering them.

• See details for a selected object, such as a description, tags, or dependencies.

• Access details about reportable rows and Prism usage.
• Access documentation that supports your use of Prism Analytics using the Help button.
When you view the Data Catalog report, you see these components:

1. Data Catalog details panel. From this panel, you can:

• Create datasets and tables.
• Create data change tasks.
• Create connections.
• View dataset publishing activities in the Dataset Activities tab.
• View all Prism-related activities in the Prism Activities Dashboard.
• View data change activities.
• View Prism usage details.
• Open the Prism Analytics Data Management User Guide in a new browser tab. The entire
documentation is also available in the Workday Community if you have access to Community.
2. Main Data Catalog view. This view displays all the data that you have permission to view. Right-clicking
a dataset or table displays a list of actions that you can perform.
3. Inspector panel. This panel displays when you select an object in the Data Catalog. You can hide
this panel to increase the available space in the main Data Catalog view. This panel displays detailed
information about the selected object, such as if a dataset is Enabled for Analysis. If enabled
(published), you can create reports and visualizations with the dataset. If enabled and outdated, the
dataset is published but has changed since it was last published.
You can also view tags assigned to a dataset or table from the inspector panel. Clicking a tag in the
panel displays the datasets or tables filtered by the tag.
4. Search for objects to filter the list of objects in the Data Catalog.
5. The number of objects displayed.

6. Filter by tags.
You can add or edit tags to organize your data if you have editor permission when you:
• Create a dataset by file upload.
• Create a derived dataset.
• Create a table.
• View a dataset or table.
• Edit a table.
Note: Tags you create are visible to all.
If you remove a tag from a dataset or table, the tag still displays in the tag menu if another dataset or
table uses the tag.
If you change browsers or laptops, the tag filters you select in the Data Catalog report won’t persist.
Workday doesn’t store tag names but rather a randomly generated identifier for each tag. This is
consistent with how Workday stores other filters in Data Catalog.
7. Filter the Data Catalog report based on when objects were last modified.
Workday automatically applies a Last 7 days filter that you can edit or delete.
Note: If you delete the filter, Workday will reapply it when you change sessions.
If you edit the filter without deleting it, Workday persists those changes to other sessions.
Workday provides the Prism Datasets and Tables data source to help you create reports and discovery
boards about Prism Analytics tables and datasets. Although this is an indexed data source, none of the
fields in it are indexed. As a result, it behaves like a standard data source.

Concept: Dataset Schema Changes

Schemas are the structures behind how your data is organized. A dataset might consist of multiple
schemas that you define when creating the dataset. Each of these dataset components has its own
schema:
• The files containing external data that you upload into a dataset.
• The custom report you create to bring Workday data into a dataset.
• The input to a pipeline stage. For the first stage in a base dataset, this schema is determined by the
dataset source.
• The output from a pipeline stage. For the last stage in the Primary Pipeline, this schema determines the
output schema of the entire dataset.
Schema changes can happen anywhere in a dataset. Schemas change when you add new fields or
remove existing fields, such as when you:
• Add a Prism calculated field.
• Hide or expose a field.
• Add a stage that adds or deletes fields in that stage.
Schemas can also change when you:
• Upload an external file.
• Import a file from an SFTP server.
• Import data from a custom report.
Where changes occur in a dataset can affect other dataset components. Changes to dataset schemas can
break components that were based on the original schema. Where changes occur can also affect how you
manage changes.
Note: When you change the schema and Workday imports the new source file into the dataset, you must
open the dataset and save the changes. If you don’t save the dataset, Workday continues to use the old

schema definition. The next time you publish the dataset, you might get inconsistent data in the Prism data
source.
When you import data that changes the schema of your dataset from an SFTP server or custom report,
you must manually edit the dataset to incorporate the changes. If new fields are added to the dataset,
Workday hides them. Expose the new fields and save the dataset to include the fields in the dataset
schema.
Workday recommends that you ensure that the dataset is up to date and includes the fields you want. In
most cases, you use the Manage Fields stage to manage dataset schema changes.

Manage Fields
The Manage Fields stage uses the output of the previous stage as a baseline from which to monitor
changes. When this baseline changes, Workday warns you in the pipeline details panel. If the baseline
changes, in the Manage Fields stage, Workday:
• Displays all new and removed fields.
• Doesn't yet include all changes in the dataset schema.
• Displays no data in the example table.
Workday recommends that you:
• Add a Manage Fields stage at the beginning of the Primary Pipeline of a derived dataset when you want
to monitor the schema of the table or dataset from which it’s derived.
• Add a Manage Fields stage at the end of the Primary Pipeline of a dataset that you intend to publish.
This enables you to detect any schema changes that might break reports that use the Prism data
source of this published dataset.
• Add a Manage Fields stage at the end of a pipeline when you need to hide fields or expose new fields.
• Add a Manage Fields stage in a base dataset to ensure that no future integration can unintentionally
remove an existing field.
• Include no more than 2 Manage Fields stages in a single pipeline.
In some cases, Workday handles schema changes without using a Manage Fields stage. Example: When
uploading a new version of a source file into a dataset, Workday handles schema changes based on the
source file header row:

Source File Contains Header Row Result

Yes Workday uses the field names in the header row of
the dataset to determine which fields are in the new
source file.
You can add or delete fields anywhere in the
source file. If the field names in the source file
don’t change, Workday updates the schema of the
dataset into which you import the new source file.

No Workday handles changes that occur only at the

end of the source file.
You can only add new fields at the end of the
source file. If you do so, Workday updates the
schema of the dataset into which you're importing
the new source file.

Related Information
Tasks
Manage Dataset Fields on page 392

Steps: Create a Dataset with External Data (SFTP Server) on page 360
Steps: Create a Dataset Using Workday Data on page 365
Reference
The Next Level: Prism Analytics Best Practices

Concept: Dataset Pipelines

Datasets contain 1 or more pipelines. A pipeline is a container of stages that models the flow of how data
should be transformed. It consists of an ordered list of stages, each of which define how to modify the data
at that point in the pipeline. Pipelines can contain 1 or more stages.
Base datasets contain 1 pipeline, and derived datasets can contain 1 or more pipelines. Every dataset has
a Primary Pipeline.
The first stage in a pipeline brings in data from the dataset source. Stages listed after the first stage in a
pipeline take the output of the previous pipeline as the input to the current stage. If you're familiar with ETL
workflows (extract, transform, and load), each stage is 1 step in a development pipeline.
The last stage of any pipeline is the output for that pipeline. The output of the Primary Pipeline is the output
of the entire dataset. Therefore, when you publish a dataset, the output of the Primary Pipeline will be
materialized as the data in the Prism data source.
Related Information
Tasks
Add a Stage to a Dataset on page 391

Concept: Dataset Stages

A stage is a pipeline object that takes in data, transforms it in some way, and outputs modified data. A
stage performs a single computational function, such as joining data with a Join stage or parsing data from
the dataset source with a Parse stage.
Prism Analytics supports these stage types:
• Explode
• Import
• Parse
• Manage Fields
• Filter
• Group by
• Join
• Union
• Unpivot
Adding a stage can change the number of records and fields in the dataset.
Deleting a Union or Join stage disconnects but keeps the stage's pipelines. If you don't want to keep the
disconnected pipelines, delete or use them in another Join or Union stage in the Primary Pipeline.
You can't delete or add an Import stage or a Parse stage.
Related Information
Tasks
Add a Stage to a Dataset on page 391
Reference
Reference: Dataset Stages on page 353

Concept: Unpivot Stages

The Unpivot stage enables you to arrange the data in derived datasets in a way that is more meaningful
to you. You can convert fields (columns) to rows. The unpivot process consolidates data from 2 or more
similar fields into a pair of new fields:
• A field created from the original field names (referred to as Input Fields)
• A field created from the original field values (referred to as Output Values)
When you unpivot:
• Workday populates the new fields with the values you specified for the unpivot.
• Workday repeats row values in the input fields you didn’t include in the unpivot.
You can:
• Apply the unpivot to all field types.
• Rename your output values.
• Specify names for your pairs of new fields.
• Unpivot up to 150 input fields within each Unpivot stage.
• Create multiple pairs of new fields within each Unpivot stage.
• Add or delete an Unpivot stage anywhere in pipelines of a derived dataset.
Workday recommends that you create multiple pairs of new fields in a single Unpivot stage rather than 1
pair of new fields in many Unpivot stages.
Related Information
Reference
Reference: Unpivot Stages on page 403
2020R2 What's New Post: Unpivot Stage
Examples
Example: Unpivot Stock Vesting Data in a Dataset on page 406

Concept: Dataset Field Origin

You can see where a dataset field originates in pipelines for derived datasets. When tracing a field’s origin,
Workday searches for the location where the field is first introduced. Workday displays the most upstream
field that you have permission on. To see the first occurrence of a field, you must have permission to view
or edit transformations on all the datasets in the field’s lineage including its first occurrence.
Examples of original fields include:
• Fields in base datasets created from the Dataset REST API.
• Fields in the Parse stage.
• Fields in tables.
• Fields in the Unpivot and Group by stages if the field is created within the stage.
• Output fields in the Union stage.
• Prism calculated fields.
Related Information
Tasks
View Field Lineage on page 373

Concept: Field Lineage

You can see the lineage of a dataset field and all transformations involving the field across different
datasets. You can also trace the lineage of a calculated field and all dependent fields used in it. When
tracing the lineage of a field, Workday displays the stages involving the field across all datasets or tables
that you have permission on. Specific stage information for each stage is displayed in the inspector panel.

Related Information
Tasks
View Field Lineage on page 373
Reference
2022R2 What's New Post: Field Lineage for Prism Analytics

Concept: Table and Dataset Field Types

Each table and dataset field has a field type attribute. The field type is often referred to as a data type in
other data applications.
The field type determines:
• What kind of values the field can hold.
• Which functions can use the field as an argument. Example: The CONCAT function only accepts Text
fields as arguments.
When you create a table, you define the field type of each field. When you load data into a table from
a delimited file, Workday validates the data against the defined schema. If the value for a field doesn’t
match the field type or other field parameters (such as date format), then Workday marks the entire row
as invalid and doesn’t include the row in the table. Instead, Workday sends the row to an error file that you
can download.
When you create a dataset using external data, Workday attempts to guess the field type of each field by
examining some of the data. However, you can change the field type if Workday assigned the wrong field
type or if you want to apply a different field type.
Note: If you change the input field type in the last stage before a Manage Fields stage, the new field type
must be compatible with the changed field type.
When you create a dataset from a custom report, Workday maps the Workday field types to dataset field
types.
For Prism calculated fields, the expression result determines the field type for that field. If a Prism
calculated field expression is TO_INT(zipcode), then the field type for that field is Integer.
Note: Workday recommends using the Numeric field type in datasets where possible. When you
use a different numeric field type, such as Double, you risk losing precision and getting erroneous
results depending on the data and calculations in the dataset. In base datasets, set the field type as
Numeric(x,y). You can also change the field type in a derived dataset using the CAST function. Example:
CAST([salary] AS decimal(12,4))

Table and Dataset Field Types

Tables and datasets use these field types:

Table or Dataset Field Type Description Range of Values

Boolean A Workday specific field type that True, False
contains boolean values.
Currency A variable length decimal value Currency values can represent
that supports a maximum of 20 any valid positive or negative
digits before the decimal point value given the specified number
and a maximum of 6 digits after of digits before and after the
the decimal point, combined with decimal point.
a Workday-recognized, 3-digit
currency code.

Table or Dataset Field Type Description Range of Values

Date Date combined with a time of day Date range: January 1, 1753,
with fractional seconds based on through December 31, 9999
a 24-hour clock.
Time range: 00:00:00 through
23:59:59.997
Internally, Workday stores all
Date type data in UTC format
(coordinated universal time). If
you bring in external data with
time zone information, Workday
converts the data to UTC. If you
bring in external data with no
time zone information, Workday
doesn't convert the data and
stores it as UTC.

Double Double-precision 64-bit floating 4.94065645841246544e-324d to

point number. 1.79769313486231570e+308d
(positive or negative)
Instance A Workday-specific field type A hexadecimal value that
that contains Workday Instance references a WID.
values. Each field also retains
information about the business
object the Instance field is based
on. Instance fields represent a
1-to-1 relationship between 2
objects.
Integer 32-bit integer (whole number). -2,147,483,648 to 2,147,483,647
Long 64-bit long integer (whole -9,223,372,036,854,775,808 to
number). 9,223,372,036,854,775,807
Multi-Instance A Workday-specific field type Zero or more hexadecimal values
that contains a set of (zero or that reference a WID.
more) Workday Instance values.
Each field also retains information
about the business object the
Instance values are based on.
Multi-Instance fields represent a
1-to-many relationship between 2
objects.
Numeric A variable length numeric value Numeric values can represent
that supports a total of 38 digits any valid positive or negative
before and after the decimal value given the specified number
point, but a maximum of 18 digits of digits before and after the
after. decimal point.
All Numeric fields have an
associated number of digits
before and after the decimal
point (similar, but not identical, to
precision and scale).

Table or Dataset Field Type Description Range of Values

When you create a table or
dataset from a Workday report,
Workday assigns the digit values
to the Numeric field.
When you create a table or
dataset from external data, you
can specify the digit values for
Numeric fields.
Example: Numeric(19,2) can
store any value from 0.00 to
9,223,372,036,854,775,807.99
and Numeric(19,0) can only
store whole numbers from 0 to
9,223,372,036,854,775,807.

Text Variable length non-Unicode text Maximum text length of

(also known as string) data. 2,147,483,647 characters.

Mapping Report Field Types to Table and Dataset Field Types

When you create a table or dataset from a custom report, Workday:
• Creates a field in the table or dataset for every report field that uses a supported field type.
• Assigns a field type to the fields in the table or dataset.
Workday only retains report fields that have field types that tables and datasets support. Workday doesn't
include any field that uses an unsupported table or dataset field type.
After creating a table or dataset from a custom report, verify that the assigned field types are correct for
your table or dataset needs. Example: You might need to change a field type from Numeric to Integer to
match the field type when joining the dataset with another dataset.
This table explains how a report field type maps to a table or dataset field type when you create a table or
dataset.

Report Field Type Table or Dataset Field Type Notes

Numeric Numeric, Integer, or Long The field type in the table or
dataset depends on the number
of digits before and after the
decimal point in the report:
• Integer. Zero digits after, and
less than or equal to 9 digits
before the decimal point.
• Long. Zero digits after, and
greater than 9 digits and less
than or equal to 18 digits
before the decimal point.
• Numeric. All other Numeric
values.
For Numeric fields, Workday
assigns the number of digits
before and after the decimal

Report Field Type Table or Dataset Field Type Notes

point based on the values in the
custom report.

Text Text
Rich Text Not supported
Date Date
DateTimeZone Not supported
Time Not supported
Currency Currency
Boolean Boolean
Multi-Instance Multi-Instance Tables and datasets only include
Multi-Instance report fields that
are located in:
• The primary business object.
• A related business object that
has a 1-to-1 relationship with
the primary business object.

Single Instance Instance

Self-Referencing Instance Instance

Mapping Table and Dataset Field Types to Prism Data Source Field Types
When you enable a table for analysis or publish a dataset, Workday creates a Prism data source.
This table lists the field types Workday uses in a Prism data source:

Table or Dataset Field Type Prism Data Source Field Type Notes
Text Text
Boolean Boolean
Date Date Workday doesn't include any time
information in the Date field in
the Prism data source. Workday
deletes any time information in
the Date field when it creates the
Prism data source.
Currency Currency
Integer Numeric
Long Numeric
Double Numeric
Numeric Numeric Workday writes Numeric fields
with a maximum of 20 digits
before and 6 digits after the
decimal point. If a Numeric field
contains a value that exceeds

Table or Dataset Field Type Prism Data Source Field Type Notes
these maximums, then Workday
rounds down the value when it
creates the Prism data source.
Instance Single Instance Workday assigns the business
object name associated with the
Instance field in the dataset.
Multi-Instance Multi-Instance Workday assigns the business
object name associated with the
Multi-Instance field in the dataset.

Related Information
Tasks
Change Dataset Field Types on page 393
Reference
Reference: Currency Format Requirements for External Data on page 378
The Next Level: Prism Analytics Best Practices

Concept: NULL Values in Tables and Datasets

If a field value in a table or dataset is empty, it's considered a NULL value. When you enable a table for
analysis or publish a dataset, Workday replaces all NULL values with a default value in the Prism data
source. Prism data sources, discovery boards, and reports have no concept of NULL values.

How Tables Process NULL Values

A value can be NULL because the raw data from the source is missing values for a particular field.

How Datasets Process NULL Values

A value can be NULL for these reasons:
• The raw data from the source is missing values for a particular field.
• The raw data from an external data source can't be parsed for the specified field type.
• A Prism calculated field expression returns an empty or invalid result.
• The dataset contains a Join stage and:
• You configure an outer join (you include all rows from at least one of the dataset pipelines).
• There's no match from 1 pipeline to the other.
If you're familiar with SQL, this is similar to an unjoined foreign key.

Default Values by Field Type

Workday replaces NULLs with these values in a Prism data source:

Field Type Value in Prism Data Source

Boolean False
Currency 0 (with an empty currency code)
Date (Blank)
Note: If the date value in a table that is enabled for analysis
is 0000-12-31T23:59:59.999Z, then Workday displays
inconsistent result.

Field Type Value in Prism Data Source

Numeric, Double, Integer, Long 0
Instance (Blank)
Multi-Instance (Blank)
Text (Blank)

NULL Values in Prism Calculated Fields

The way datasets treat NULL values in Prism calculated fields is consistent with SQL standard. That
means:
• Arithmetic calculations on numeric fields that involve a NULL return NULL. Example: 5 + NULL returns
NULL.
• Comparison operations that result in a Boolean field that involve a NULL return NULL. Example: 5 >
NULL returns NULL.
Currency fields have 2 components to the field value (the currency code and currency value), and as a
result, they handle NULLs a little differently than numeric fields in arithmetic calculations.
• Addition and subtraction calculations on Currency fields that involve a NULL return NULL. Example:
TO_CURRENCY("5.00 USD") + NULL returns NULL.
• Addition and subtraction calculations on Currency values that use different currency codes return NULL.
Example: TO_CURRENCY("5.00 USD") + TO_CURRENCY("5.00 EUR") returns NULL.
You can't use Currency fields in comparison operations. However, you can test for NULL values by using
this syntax:

value IS NULL
value IS NOT NULL

NULL Values in Group By Stages

When you create a Group By stage, you select a dataset field for grouping and another field for
summarizing. How Workday treats NULL values depends on how you use the field:
• For grouping fields, any NULL values result in their own group.
• For summarization fields, NULL handling depends on the summarization type.

Summarization Type Description

Average Returns the average of all valid numeric values in the group. It sums
all values in the provided expression and divides by the number of
valid (not NULL) rows.
If a Currency field contains multiple currency codes, the result is
NULL.

Count Returns the number of all rows in a group (counts all values, both
NULL and non-NULL).
If a Currency field contains multiple currency codes, the result is
NULL.

Maximum Returns the greatest of all non-NULL values, and NULL if all values
are NULL.

Summarization Type Description

If a Currency field contains multiple currency codes, the result is
NULL.

Minimum Returns the lowest of all non-NULL values, and NULL if all values are
NULL.
If a Currency field contains multiple currency codes, the result is
NULL.

Sum Returns the total of all non-NULL values, and NULL if all values are
NULL.
If a Currency field contains multiple currency codes, the result is
NULL.

Related Information
Concepts
Concept: Table and Dataset Field Types on page 344
Reference
Reference: Currency Format Requirements for External Data on page 378

Concept: Prism Calculated Fields

A Prism calculated field is a user-created field that generates its values based on a calculation or condition,
and returns a value for each input row. Values are computed based on expressions that can contain values
from other fields, constants, mathematical operators, comparison operators, or built-in row functions.
Use Prism calculated fields to:
• Derive meaningful values from base fields, such as calculating someone's age based on their birthday.
• Do data cleansing, such as substituting 1 value for another.
• Compute new data values based on a number of input variables, such as calculating a profit margin
value based on revenue and costs.
Sometimes you need several steps to achieve the result that you want. You can use the result of a Prism
calculated field in the expressions of other Prism calculated fields, enabling you to define a chain of
processing steps.
When you create a Prism calculated field, the inspector panel displays for the new field. To see a list of
available functions, click the Functions Library tab in the inspector panel.
You can extract and export the expressions used in dataset pipelines as CSV files from the View Dataset
Lineage report.
Related Information
Concepts
Concept: Prism Expression Language on page 458
Tasks
Add a Prism Calculated Field to a Dataset on page 389
Reference
The Next Level: Prism Analytics Best Practices

Concept: Hiding Dataset Fields

A data administrator can control what fields of a dataset are visible. Hidden fields aren't visible further
along in the development process. Example: if you hide a field in a stage in a pipeline, that field isn't visible

in a later stage. Hidden fields aren't included in the Prism data source of a published dataset, or in an
imported dataset of a derived dataset.
You might decide to hide a field to:
• Protect sensitive data. In some cases, you might want to hide fields to protect sensitive information.
You can hide detail fields, but still allow access to summary information. Suppose that you have a
dataset containing employee salary information. You might want to hide salaries per person, but still
enable analysts to view average salary by department.
• Hide unpopulated or sparse data fields. You might have fields in your raw data that didn't have any
data collected. The data collected might be too sparse to be valid for analysis. Suppose that a web
application has a placeholder field for comments, but it was never implemented on the website so the
comments field is empty. Hiding the field prevents analysts from using a field with mostly null values
when they analyze the data.
• Use a calculated field instead of the fields that it's based on. You might add a Prism calculated field
to transform the values of the raw data. You want your users to analyze the transformed values, not the
raw values. Suppose that you have a "return reason code" field where the reason codes are numbers
(1, 2, and 3). You could transform the numbers to the actual reason information (such as Didn't Fit,
Changed Mind, and Poor Quality), so the data is more usable during analysis.
• Hide Prism calculated fields that do interim processing. As you work on your dataset to cleanse
and transform the data, you might need to add interim Prism calculated fields to achieve a final result.
These fields are necessary to do a processing step, but aren't intended for final consumption. You can
hide these working fields so they don't clutter later stages or the dataset details.
Hide a field in the Manage Fields stage by unselecting the check box for a field. Although you can also hide
a field in the inspector panel, it's a best practice to hide fields in the Manage Fields stage.
Related Information
Concepts
Concept: Prism Analytics Data Management Workflow on page 327

Concept: Dataset Integration Schedules

Schedules for dataset integrations enable you to specify when, how often, and under what criteria to import
data into a dataset. Workday enables you to import data into a dataset immediately on an ad hoc basis or
according to a preconfigured schedule.
You can schedule the integration to run:
• Once in the future.
• On a recurring basis (Example: daily, weekly, or monthly).
• Only after another Prism scheduled process completes at a status you specify.

Integration Schedule Types

Schedule Type Description

Recurring An integration schedule that runs at specified
intervals, such as daily, weekly, or monthly.
Dependent An integration schedule that depends on the
completion of another Prism scheduled process.
For your dependency criteria, you can specify:
• The process type, such as another Prism data
integration.
• The status that triggers integration, such as the
process type successfully completing.

Schedule Type Description

Example: When the Prism Data Acquisition Future
Process completes with no warnings or errors,
begin integration.
Note: A Prism Analytics integration schedule can
depend only on another Prism-related process,
such as bringing data into a dataset or publishing
another dataset.

As you create an integration schedule, consider these actions that you can perform on it:

Action Description
Activate Activate a suspended integration schedule.
Change Schedule (recurring schedules only) Edit the run frequency (daily, monthly, weekly), start
time, and date range for the integration schedule.
You can also change to another scheduled
recurring process.
Delete Permanently delete the integration schedule.
Edit Environment Restrictions Select the environment in which you want the
scheduled integration to run.
Edit (Recurring Schedules) Edit the schedule name,
recurrence criteria, and range of recurrence dates.
To change the run frequency, use Change
Schedule.
(Dependent Schedules) Edit the schedule name,
dependency, trigger status, and timed delay
configurations.

Edit Scheduled Occurrence (recurring schedules Update the schedule date and time for one
only) particular occurrence of the scheduled request.
You can also delete a particular occurrence of the
scheduled integration.

Run Now Run the integration schedule immediately on an ad

hoc basis.
Suspend Suspend use of the integration schedule. You can
activate a suspended schedule.
Transfer Ownership Transfer ownership of an integration schedule.
Every process must have an assigned owner for
the process to run.
Example: Transfer ownership if the assigned
owner becomes inactive. The person you transfer
ownership to must have the appropriate security
access.

View All Occurrences (recurring schedules only) View all future occurrences of an integration
schedule within a specified range of dates and
times.

Action Description
View Details (Recurring schedules) View schedule details,
such as recurrence criteria, error messages, the
schedule owner and creator, and the next 10
scheduled integrations if applicable.
(Dependent schedules) View schedule details, such
as the dependency configuration, the schedule
creator and owner, and the number of times run.

Related Information
Tasks
Manage Dataset Integration Schedules on page 369
Steps: Create a Dataset with External Data (SFTP Server) on page 360
Steps: Create a Dataset Using Workday Data on page 365

Reference: Dataset Stages

Prism Analytics supports these stage types:

Stage Type Description

Import The first stage in every pipeline in a derived dataset
is an Import stage. An Import stage imports data
from a source, and for derived datasets that source
is the output of a table or an existing dataset.
Workday automatically creates an Import stage
when necessary.
You can't delete or add an Import stage.

Parse A Parse stage is a type of stage that enables you

to describe the source data in a tabular format.
Workday automatically displays the Parse stage
when you create a dataset using external data.
You can't delete or add a Parse stage.

Manage Fields A Manage Fields stage is a type of stage that

enables you to view field changes, select fields, and
edit fields.
Filter A Filter stage is a type of stage that constrains rows
in a dataset based on the filter criteria you define.
Add Filter stages to limit the data in the dataset for
analysis, such as on a particular region or year.
You can add or delete a Filter stage in the middle or
at the end of a pipeline.

Group By A Group By stage is a type of stage that enables

you to summarize (aggregate) multiple values in a
dataset by specified groups. You can summarize
the values using a summarization type, such as
MIN, MAX, or SUM. Add Group By stages to get
data to the appropriate level that you need to join
the data in 1 dataset with another dataset.

Stage Type Description

You can add or delete a Group By stage in the
middle or at the end of a pipeline.

Join A Join stage is a type of stage that combines fields

from 2 dataset pipelines based on common values
that exist in each pipeline. Add Join stages to
view and use related data from different datasets.
You can add Join stages to derived datasets only.
Derived datasets are the only datasets that can use
multiple datasets as their source data.
You can add or delete a Join stage anywhere in the
Primary Pipeline of the derived dataset.

Union A Union stage is a type of stage that combines data

from similar fields in different datasets into a single
field. Add Union stages to:
• Combine datasets that have similar, but not
identical schema.
• Combine datasets with the same schema but
with source data from different locations, such
as different SFTP servers.
You can add Union stages to derived datasets only.
Derived datasets are the only datasets that can use
multiple datasets as their source data.
You can add or delete a Union stage anywhere in
the Primary Pipeline of the derived dataset.

Unpivot An Unpivot stage is a type of stage that converts

fields (columns) to rows. Add an Unpivot stage to
consolidate data from 2 or more similar fields into a
pair of new fields.
You can add Unpivot stages to derived datasets
only.
You can add or delete an Unpivot stage anywhere
in pipelines of the derived dataset.

Related Information
Concepts
Concept: Dataset Stages on page 342

Reference: Table Error File Error Codes

When you view an error file for a table load, you might see these errors:

Error Code Notes

3000 The number of fields in the source doesn’t match the number of fields
in the wBucket schema. You use wBuckets when you load data into a
table using the REST API.
3001 Invalid data - Text field

Error Code Notes

3002 Invalid data - Integer field. When the precision and scale of a Numeric
field indicates that the field should contain integer values only, you
might see this error. Example: Numeric(9,0)
3003 Invalid data - Numeric field
3004 Invalid data - Date field
3005 Invalid data - Boolean field
3006 Invalid data - Instance field
4000 The number of characters for the Text field exceeds the maximum
allowed (32,000 characters).
4003 The numeric value is too large for the defined precision and scale for
the Numeric field.
5000 This error code can correspond to either of these errors:
• The error file has reached its maximum of 10 MB and has stopped
recording new error messages.
• The number of characters for the entire row of data exceeds the
maximum allowed (500,000 characters).

Related Information
Concepts
Concept: Table Error File on page 335

Creating Tables and Datasets

Steps: Create a Table by File Upload

Prerequisites
Security: Prism: Tables Create domain in the Prism Analytics functional area.

Context
You can create a table by uploading 1 or more delimited files.
Workday:
• Uses the field information in the first file to define the table fields.
• Loads the data in the files into the table.
When you create a table by file upload, you can:
• Upload up to 100 files. All files must use the same schema.
• Modify the field type that Workday guesses for each field. Example: You can change the field type from
Numeric to Text, or from Text to Multi-Instance.
• Add other fields to the table schema.
• Create a data change task to load data from files you upload into the new table.

Steps
1. Access the Data Catalog report.

2. Select Create > Table.

3. Enter the Table Name. You can change the table name when you edit the table.
4. (Optional) Change the Table API Name.
Workday automatically selects an API name based on the table name that you enter, modifying it to
make it meet the name requirements. Click Change to change the API name. You can’t change this
name after you finish creating the table.
5. (Optional) Select Enable for Analysis to create a Prism data source using the data in this table.
Workday recommends enabling a table for analysis after:
• You apply the appropriate data source security to the table.
• The table contains the data that you want and receives new and updated data from a data change
task.
6. (Optional) Create or edit 1 or more Tags to organize the table in the Data Catalog.
7. (Optional) Add a Description to help others understand what data this table contains.
8. On the Select Schema Source step, select File Upload.
9. Select 1 or more delimited files to upload.
When you upload multiple files, each file must use the same schema. Workday supports delimited files
that are RFC 4180-compliant. For more information, see RFC 4180.
10.On the Edit Parsing Options step, define how to parse the data in the file.
See Parse External Data in a Table on page 381.
11.On the Edit Schema step, review the fields Workday created based on the parsed file, and modify the
fields if necessary.
Select a field in the list and view the field details in the inspector panel on the right side. You might want
to:
• Change the field API Name. You can’t change the API name after you save the table.
• Change the Field Type if Workday assigned the wrong field type. Example: Workday assigned
the Numeric field type to a field with zip code data because the example rows it evaluated only
contained numerals. But you know that some zip code values might contain letters or a hyphen, so
you change the field type to Text.
• Change other field attributes, such as Date Format, based on the field type.
• Define some field constraints that ensure the accuracy and reliability of the data in the table, such as
Required or Use as External ID.
See Reference: Table Field Attributes on page 385.
12.(Optional) Click Add Field to add 1 or more fields. In the inspector panel for the field, configure the field
attributes.
See Reference: Table Field Attributes on page 385.

Result
Workday creates the table and starts loading the data in the files into the table. To view the data load
progress you can go to:
• The Activities tab on the View Table Details report.
• The Prism Activities Dashboard on the Data Catalog report.
Refresh the page to get the most recent status.

Next Steps
To load data from a delimited file to the table again, create a data change task for the table.
If there were errors loading data into the table, download the error file from the data load from these
locations:

• The Activities tab of the View Table Details report.

• The Prism Activities Dashboard report on the Data Catalog report.
Related Information
Concepts
Concept: Prism Analytics Data Management Workflow on page 327
Concept: Tables on page 333
Concept: Table and Dataset Field Types on page 344
Concept: Table Error File on page 335
Tasks
Parse External Data in a Table on page 381
Reference
Reference: WPA_ Fields on page 380
Reference: Supported File Formats for External Data in Tables and Datasets on page 378
Reference: Table Field Attributes on page 385
Reference: Naming Guidelines on page 376
Reference: External Data Limits on page 332
The Next Level: Prism Analytics Data Acquisition Best Practices

Steps: Create Table from a Workday Report

Prerequisites
Security: Prism: Tables Create domain in the Prism Analytics functional area.

Context
You can create a table based on an existing Workday custom report by selecting a report as the schema
source. Workday retains only the fields with field types that tables currently support.
When you create a table from a report, you can:
• Add other fields to the table schema.
• Create a data change task to load data from the report into the new table.

Steps
1. Access the Data Catalog report.
2. Select Create > Table.
3. Enter the Table Name. You can change the table name when you edit the table.
4. (Optional) Change the Table API Name.
Workday automatically selects an API name based on the table name that you enter, modifying it to
make it meet the name requirements. Click Change to change the API name. You can’t change this
name after you finish creating the table.
5. (Optional) Select Enable for Analysis to create a Prism data source using the data in this table.
Workday recommends enabling a table for analysis after:
• You apply the appropriate data source security to the table.
• The table contains the data that you want and receives new and updated data from a data change
task.
6. (Optional) Create or edit 1 or more Tags to organize the table in the Data Catalog.
7. (Optional) Add a Description to help others understand what data this table contains.
8. On the Select Schema Source step, select Workday Report.
9. Select the Workday custom report.

10.On the Edit Schema step, review the fields Workday created based on the report, and modify the fields
if necessary.
Select a field in the list and view the field details in the inspector panel on the right side.
11.(Optional) Click Add Field to add 1 or more fields. In the inspector panel for the field, configure the field
attributes.

Result
Workday creates an empty table using the schema defined in the report.

Next Steps
Create a data change task using the same report as the source to load data into the table from the report.
Related Information
Concepts
Concept: Creating Reports to Import into Tables and Datasets on page 330
Concept: Prism Analytics Data Management Workflow on page 327
Concept: Tables on page 333
Concept: Table and Dataset Field Types on page 344
Reference
Reference: WPA_ Fields on page 380
Reference: Table Field Attributes on page 385
Reference: Naming Guidelines on page 376
The Next Level: Prism Analytics Best Practices

Steps: Create Table from an Existing Table or Dataset

Prerequisites
Security:
• Prism: Tables Create domain in the Prism Analytics functional area.
• Any of these requirements:
• Prism: Tables Manage domain in the Prism Analytics functional area.
• Table Viewer or Dataset Viewer permission on the existing table or dataset.
• Table Editor or Dataset Editor permission on the existing table or dataset.
• Table Owner or Dataset Owner permission on the existing table or dataset.

Context
You can create a table based on an existing dataset or other table by selecting an existing table or dataset
as the schema source. Workday defines the new table schema based on the output schema of the existing
table or dataset.
If the existing dataset includes a Double field, consider converting it to a Numeric field in the dataset before
creating the table.
When you create a table from an existing table or dataset, you can:
• Add other fields to the table schema.
• Create a data change task to load data from the existing table or dataset into the new table.

Steps
1. Access the Data Catalog report.

2. Select Create > Table.

Result
Workday creates an empty table using the schema that you defined.

Next Steps
Create a data change task to load data into the table.
Related Information
Concepts
Concept: Prism Analytics Data Management Workflow on page 327
Concept: Tables on page 333
Concept: Table and Dataset Field Types on page 344
Reference
Reference: Table Field Attributes on page 385
Reference: Naming Guidelines on page 376
Reference: WPA_ Fields on page 380

Steps: Create a Table Manually

Prerequisites
Security: Prism: Tables Create domain in the Prism Analytics functional area.

Context
You can create a table by manually defining each field in the table schema. When you create a table
manually, the table is empty. You can create a data change task to load data into the table.

Steps
1. Access the Data Catalog report.
2. Select Create > Table.
3. Enter the Table Name. You can change the table name when you edit the table.
4. (Optional) Change the Table API Name.
Workday automatically selects an API name based on the table name that you enter, modifying it to
make it meet the name requirements. Click Change to change the API name. You can’t change this
name after you finish creating the table.
5. (Optional) Select Enable for Analysis to create a Prism data source using the data in this table.
Workday recommends enabling a table for analysis after:
• You apply the appropriate data source security to the table.
• The table contains the data that you want and receives new and updated data from a data change
task.
6. (Optional) Create or edit 1 or more Tags to organize the table in the Data Catalog.
7. (Optional) Add a Description to help others understand what data this table contains.
8. On the Select Schema Source step, select Manual Input.
The Edit Schema step displays where you can define each field in the table schema.
9. Click Add Field to add 1 or more fields.
10.In the inspector panel for the field, configure the field attributes.
See Reference: Table Field Attributes on page 385.

Next Steps
Create a data change task to load data into the table.
Related Information
Concepts
Concept: Prism Analytics Data Management Workflow on page 327
Concept: Tables on page 333
Concept: Table and Dataset Field Types on page 344
Reference
Reference: WPA_ Fields on page 380
Reference: Supported File Formats for External Data in Tables and Datasets on page 378
Reference: Table Field Attributes on page 385
Reference: Naming Guidelines on page 376
The Next Level: Prism Analytics Best Practices

Steps: Create a Dataset with External Data (SFTP Server)

Prerequisites
Security: Prism Datasets: Create domain in the Prism Analytics functional area.

Context
You can create a dataset using external data by transferring data from an SFTP server. You might want to
create a dataset that gets its data from an external server when the server regularly collects or adds new
data. You configure how often the dataset gets new data from the server.
For integration runs that transfer data from the SFTP server to succeed:
• The number of files must be less than 5,000.
• The time to transfer the data must be less than 5 hours.
Each file from the server should be less than 1 GB compressed (less than 10 GB uncompressed
approximately).
Creating a dataset using external data creates a base dataset.

Steps
1. Access the Data Catalog report.
2. Select Create > from SFTP.
On the Create Dataset Retrieval - Configure File Retrieval task, you configure how to import the data
from the SFTP server.
3. In the Files section, enter the filename or a filename pattern that represents 1 or more files.
The filename is case-sensitive. You can use the asterisk (*) and question mark (?) characters as wild
cards to specify a filename pattern. Use the asterisk (*) to specify zero or more characters, and use the
question mark (?) to specify exactly 1 character.
4. In the Transport section, specify how to connect to the SFTP server:
Option Description
SFTP Address Use this format: sftp://domain_name or
sftp://IP_address
To specify a port number, add it to the end of the domain name or
IP address. If you don't specify a port number, Workday uses port
22.

Directory (Optional) The directory on the server that contains the files.
Directory names are case-sensitive. Include a leading slash (/) only
for a full path, not a relative path.
Use Temp File Writes the imported data to a temporary file in Workday with a
randomly generated name. After the data import is complete,
Workday automatically renames the file to the correct name.
You might want to enable this option if the data import takes a very
long time and might not finish before the next scheduled time to
import data from the same server.

Authentication Method and Select the type of security authentication that the SFTP server
Details uses:
• User Name / Password.
• SSH Authentication. This option uses secure shell key
authentication using X.509 certificates.

5. (Optional) In the File Utilities section, Consider these options:

Option Description
Delete After Retrieval Deletes the files on the SFTP server after the data is imported into
the dataset. If Workday is unable to delete the files from the SFTP
server, the data retrieval fails.
Decompress Don't enable this option for datasets.
You can transfer files that are compressed or not. For compressed
files, Workday only supports gzip compression.

Decrypt Using If you want to decrypt the imported files using Pretty Good Privacy
(PGP), select a PGP Private Key Pair.
6. (Optional) In the Environment Restrictions section, at the Restricted To prompt, select the
environment in which you want to use the settings defined in the Transport section.
If you leave this option empty, Workday applies the transport settings to each environment in which
the dataset integration runs. When a dataset integration runs in a particular environment, such as
Implementation or Production, the transport settings only work if the Restricted To option matches
the current environment. When the current environment and the configured environment don’t match,
the dataset integration fails and retrieves no files from the SFTP server. You might want to restrict the
transport settings to a particular environment to avoid inadvertently transferring test data to a non-test
endpoint.
Example: You create the dataset in an Implementation environment and select Implementation in
Restricted To. Later, you migrate this dataset to a Production environment and the next time the
dataset integration runs, the integration fails. To ensure that the dataset integration runs successfully
in the Production environment, edit the dataset integration details and either clear the Restricted To
option or change it to Production.

7. On the Create Dataset Retrieval - Schedule Request Type task, in Run Frequency, specify how
often to import data from the SFTP server.
If you're importing the data once in the future or on a schedule, specify the criteria for either on the
Create Dataset Retrieval - Schedule Integration task.
After the dataset is created, you can run the integration to bring in data to the dataset on an ad hoc
basis. From the related actions menu of the View Dataset Details report, select Dataset > Run
Integration Now.
Note: You can't bring data into the same dataset at times that overlap with each other.
8. Specify a unique name for the dataset.
The dataset name is what displays in the Data Catalog. You can change the name when you create,
edit, or copy the dataset.
9. (Optional) Change the dataset API name. Workday automatically selects an API name based on the
dataset name you enter, modifying it to make it meet the name requirements. You can’t change this
name after you finish creating the dataset.
10.(Optional) Create or edit 1 or more tags to organize the dataset in the Data Catalog.
11.(Optional) Add a description to help others understand the data in this dataset. You can change the
description when you edit the dataset.
12.Select how you want to update the data in the dataset when it receives new data from an integration
run.
Option Description
Replace Workday deletes the existing data in the dataset and replaces it with the
data it imports from the SFTP server.

Option Description
Append Workday keeps the existing data in the dataset and adds to it the new
data it imports from the SFTP server.
Workday imports all data in all files during every integration run. Append
mode is different than incrementally updating data in a dataset. Whether
the data in the dataset gets updated incrementally depends on if the
SFTP server contains only incremental updates since the last integration
run.
The file schema must meet these requirements:
• All files in every integration run must use the same parsing options
(including the header row configuration) that were used during the
first integration run.
• The fields must be in the same order in all files in every integration
run.
• If the schema in a subsequent integration run contains new fields, the
new fields must be located at the end of all previous fields.
• If the file schema in a subsequent integration run deletes one or
more fields, the deleted fields must be at the end.
• Ensure that if the schema deletes fields, no future schema adds
new fields, otherwise the integration run will fail. To ensure that all
future integrations run successfully, always keep existing fields in the
schema and only add new fields. If necessary, you can include empty
(NULL) values in existing fields.
• All files in a single integration must use the same schema.

Note: An integration fails when the schema of the new data doesn't contain a field that currently exists
in the dataset, and the removed field is used in a stage in the dataset. Example: If the dataset includes
a Manage Fields stage and the integration brings in data that is missing a field in the dataset, the
integration fails. That's because the Manage Fields stage works on every field in the dataset.
13.Click Save.
Workday creates the dataset, but it has no data until Workday imports the data and fields from the
SFTP server during the first integration run. Depending on when you scheduled the data to import, the
dataset might be empty for some time. Workday also adds 2 fields that provide information about each
integration run. See Reference: WPA_ Fields on page 380.
14.(Optional) Change the name of your integration schedule. See Manage Dataset Integration Schedules
on page 369.
15.Access the Data Catalog report, right-click the dataset you just created, and select Edit.
16.Configure how to parse the data in the files from the SFTP server.
See Parse External Data in a Dataset on page 386.
17.(Optional) Add a Stage to a Dataset on page 391.
You can add only some stage types to base datasets.
18.(Optional) Add a Prism Calculated Field to a Dataset on page 389.
You can add a Prism calculated field to any stage.
Related Information
Concepts
Concept: Dataset Workspace on page 336
Concept: Datasets on page 336
Concept: Dataset Stages on page 342
Concept: Dataset Pipelines on page 342

Reference
Reference: Supported File Formats for External Data in Tables and Datasets on page 378
Reference: WPA_ Fields on page 380
Reference: Naming Guidelines on page 376
Reference: External Data Limits on page 332
The Next Level: Prism Analytics Best Practices

Steps: Create a Dataset with External Data (Upload a File)

Prerequisites
Security: Prism Datasets: Create domain in the Prism Analytics functional area.

Context
You can create a dataset using external data by uploading a file. You might want to create a dataset by
uploading a file when the data in the file is less likely to change over time.
When you create a dataset by uploading a file, the source data in the dataset remains the same over time.
However, you can change the data in the dataset later by uploading a new file to the dataset. See Upload a
New File to a Dataset on page 371.
Creating a dataset using external data creates a base dataset.

Steps
1. Access the Data Catalog report.
2. Select Create > from File.
3. Navigate to a file on your local machine and open it.
The maximum size file you can upload is 500 MB.
4. Define how to parse the data in the file.
See Parse External Data in a Dataset on page 386.
5. Specify a unique name for the dataset.
The dataset name is what displays in the Data Catalog. You can change the name when you create,
edit, or copy the dataset.
6. (Optional) Change the dataset API name. Workday automatically selects an API name based on the
dataset name you enter, modifying it to make it meet the name requirements. You can’t change this
name after you finish creating the dataset.
7. (Optional) Create or edit 1 or more tags to organize the dataset in the Data Catalog.
8. (Optional) Add a description to help others understand the data in this dataset. You can change the
description when you edit the dataset.
9. (Optional) Add a Stage to a Dataset on page 391.
You can add only some stage types to base datasets.
10.(Optional) Add a Prism Calculated Field to a Dataset on page 389.
You can add a Prism calculated field to any stage.
Related Information
Concepts
Concept: Dataset Workspace on page 336
Concept: Datasets on page 336
Concept: Dataset Stages on page 342
Concept: Dataset Pipelines on page 342

Tasks
Upload a New File to a Dataset on page 371
Reference
Reference: Supported File Formats for External Data in Tables and Datasets on page 378
Reference: Naming Guidelines on page 376
Reference: External Data Limits on page 332
The Next Level: Prism Analytics Best Practices

Steps: Create a Dataset Using Workday Data

Prerequisites
Security: Prism Datasets: Create domain in the Prism Analytics functional area.

Context
You can create a dataset using Workday data. You do this by creating a dataset using an existing Workday
custom report as the source for the dataset.
You configure how often the dataset gets new data from the report.
Workday retains only the fields with field types that datasets currently support.
Creating a dataset from a custom report creates a base dataset.

Steps
1. Access the Data Catalog report.
2. Select Create > from Custom Report.
Workday displays reports that meet the eligibility requirements for importing into Prism. See Concept:
Creating Reports to Import into Tables and Datasets on page 330.
On the Create Dataset Retrieval - Configure Report Retrieval task, you configure how to import the
data from the custom report.
3. Select a Custom Report that has the data you want to import into this dataset.
4. In the Report Criteria table, select values for the report prompts, if applicable.
Workday filters the report data with the specified values as the report runs and before importing the
data into the dataset. As you complete this step, consider:
Option Description
Value Type This option affects how Workday determines the value for this field
prompt:
• Specify Value. Workday uses the same value that you specify
here each time it runs the report to import data into the dataset.
• Determine Value at Runtime. Workday uses the current value
in a field you specify each time it runs the report to import data
into the dataset.

Value Workday uses the value or field you select here to filter the data in
the report.
5. (Optional) In the Environment Restrictions section, at the Restricted To prompt, select the
environment in which you want to use the settings defined in the Transport section.
If you leave this option empty, Workday applies the transport settings to each environment in which
the dataset integration runs. When a dataset integration runs in a particular environment, such as
Implementation or Production, the transport settings only work if the Restricted To option matches

the current environment. When the current environment and the configured environment don’t match,
the dataset integration fails and retrieves no data from the specified custom report. You might want to
restrict the transport settings to a particular environment to avoid inadvertently transferring test data to a
non-test endpoint.
Example: You create the dataset in an Implementation environment and select Implementation in
Restricted To. Later, you migrate this dataset to a Production environment and the next time the
dataset integration runs, the integration fails. To ensure that the dataset integration runs successfully
in the Production environment, edit the dataset integration details and either clear the Restricted To
option or change it to Production.

6. On the Create Dataset Retrieval - Schedule Request Type task, in Run Frequency, specify how
often to import data from the custom report.
If you're importing the data once in the future or on a schedule, specify the criteria for either on the
Create Dataset Retrieval - Schedule Integration task.
After the dataset is created, you can run the integration to bring in data to the dataset on an ad hoc
basis. From the related actions menu of the View Dataset Details report, select Dataset > Run
Integration Now. You can't bring data into the same dataset at times that overlap with each other.
Note: An integration fails to bring in new data from the custom report when the report schema doesn't
contain a field that currently exists in the dataset, and the removed field is used in a stage in the
dataset. Example: If the dataset includes a Manage Fields stage and the integration brings in data that
is missing a field in the dataset, the integration fails. That's because the Manage Fields stage works on
every field in the dataset.
7. Specify a unique name for the dataset.
The dataset name is what displays in the Data Catalog. You can change the name when you create,
edit, or copy the dataset.
8. (Optional) Change the dataset API name. Workday automatically selects an API name based on the
dataset name you enter, modifying it to make it meet the name requirements. You can’t change this
name after you finish creating the dataset.
9. (Optional) Create or edit 1 or more tags to organize the dataset in the Data Catalog.
10.(Optional) Add a description to help others understand the data in this dataset. You can change the
description when you edit the dataset.
11.Select how you want to update the data in the dataset when it receives new data from an integration
run.
Option Description
Replace Workday deletes the existing data in the dataset and replaces it with the
data it imports from the custom report.
Append Workday keeps the existing data in the dataset and adds to it the new
data it imports from the custom report.
Workday imports all data in the report during every integration run,
resulting in duplicate data in the dataset. Select append mode for a
custom report dataset when you want a snapshot of the custom report
data to maintain history in the dataset for trending use cases.
Note: Ensure that you don’t change the Column Heading Override
XML Alias values in the custom report definition. Workday uses these
values to map fields from the custom report into the dataset.

12.Click Save.
Workday creates the dataset, but it has no data until Workday runs the report and then imports the data
and fields from the report during the first integration run. Depending on when you scheduled the data to

import, the dataset might be empty for some time. Workday also adds 2 fields that provide information
about each integration run. See Reference: WPA_ Fields on page 380.
13.(Optional) Change the name of your integration schedule. See Manage Dataset Integration Schedules
on page 369
14.Access the Data Catalog report, right-click the dataset you just created, and select Edit.
15.(Optional) Add a Stage to a Dataset on page 391.
You can add only some stage types to base datasets.
16.(Optional) Add a Prism Calculated Field to a Dataset on page 389.
You can add a Prism calculated field to any stage.
Related Information
Concepts
Concept: Dataset Workspace on page 336
Concept: Datasets on page 336
Concept: Dataset Stages on page 342
Concept: Dataset Pipelines on page 342
Concept: Creating Reports to Import into Tables and Datasets on page 330
Reference
Reference: WPA_ Fields on page 380
Reference: Naming Guidelines on page 376
The Next Level: Prism Analytics Best Practices

Steps: Create a Derived Dataset

Prerequisites
Security:
• Prism Datasets: Create domain in the Prism Analytics functional area.
• Any of these requirements:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Dataset Viewer permission on the dataset to import into the derived dataset.
• Dataset Editor permission on the dataset to import into the derived dataset.
• Dataset Owner permission on the dataset to import into the derived dataset.

Context
When you first create a derived dataset, Workday creates the Primary Pipeline. Import other datasets into
the derived dataset so you can blend data together.
You can add a stage to any pipeline in the dataset. However, some stages, such as the Join stage, can
only be added to the Primary Pipeline.
When you add a Join or Union stage to the Primary Pipeline, you must select another pipeline in the
derived dataset to blend with the Primary Pipeline. Workday uses the last stage of that pipeline as the input
to the Join or Union stage.

Steps
1. Access the Data Catalog report.
2. Select Create > Derived Dataset.
3. Select a table or dataset from the list.

4. Specify a unique name for the dataset.

The dataset name is what displays in the Data Catalog. You can change the name when you create,
edit, or copy the dataset.
5. (Optional) Change the dataset API name. Workday automatically selects an API name based on the
dataset name you enter, modifying it to make it meet the name requirements. You can’t change this
name after you finish creating the dataset.
6. (Optional) Create or edit 1 or more tags to organize the dataset in the Data Catalog.
7. (Optional) Add a description to help others understand the data in this dataset. You can change the
description when you edit the dataset.
8. Click Edit Transformations to access the Edit Dataset Transformations task.
9. The Edit Dataset Transformations task displays 1 pipeline (the Primary Pipeline) that contains an
Import stage.
10.Create 1 or more additional pipelines by importing an existing dataset.
See Import a Table or Dataset into a Derived Dataset on page 368.
11.(Optional) Add a Stage to a Dataset on page 391.
You can add any stage type to derived datasets, but you can add some stage types to the Primary
Pipeline only. To blend data from 2 pipelines, consider adding a Join stage to the Primary Pipeline.
12.(Optional) Add a Prism Calculated Field to a Dataset on page 389.
You can add a Prism calculated field to any stage in any pipeline.
Related Information
Concepts
Concept: Dataset Workspace on page 336
Concept: Datasets on page 336
Concept: Dataset Stages on page 342
Concept: Dataset Pipelines on page 342
Reference
Reference: Naming Guidelines on page 376
The Next Level: Prism Analytics Best Practices

Import a Table or Dataset into a Derived Dataset

Prerequisites
• Any of these security requirements:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Dataset Editor permission on the derived dataset.
• Dataset Owner permission on the derived dataset.
• Any of these security requirements:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Dataset Viewer permission on the dataset to import into the derived dataset.
• Dataset Editor permission on the dataset to import into the derived dataset.
• Dataset Owner permission on the dataset to import into the derived dataset.

Context
A derived dataset is based on 1 or more existing tables or datasets. Use derived datasets to blend and
combine together data from multiple sources. In order to blend and combine data from multiple sources,
you need to import multiple tables or datasets into the derived dataset. When you first create a derived
dataset, you base it on an existing table or dataset. Afterward, you must import other tables or datasets
into the derived dataset.

When you import a table or dataset into a derived dataset, Workday creates a new pipeline. The pipeline
name is the same as the table or dataset name you import. You can add stages to the new pipeline.
Once a derived dataset has multiple tables or datasets imported into it, you can add a stage, such as a
Join stage, to the Primary Pipeline to blend data with any other pipeline.

Steps
1. Access the Edit Dataset Transformations task for a derived dataset.
2. In the Pipelines panel, click Add Pipeline.
3. Select a table or dataset from the list.

Result
The Pipelines panel displays the new pipeline with the first stage being an Import stage. The pipeline
name is the same as the table or dataset you imported.

Next Steps
• (Optional) Add a stage, such as a Join stage, that blends together data from the Primary Pipeline and
the pipeline you added.
Related Information
Tasks
Steps: Create a Derived Dataset on page 367

Manage Dataset Integration Schedules

Prerequisites
Security: Prism Datasets: Manage domain in the Prism Analytics functional area.

Context
You can manage how you set up integration schedules for base datasets created from:
• SFTP
• Custom reports
You can schedule the integration to run:
• Once in the future.
• On a recurring basis (Example: daily, weekly, or monthly).
• Only if another Prism scheduled process completes at a status you specify.

Steps
1. Access the View Dataset Details report for the dataset.
2. From the related actions menu, select Dataset > Edit Integration Details.
3. (Recurring schedules) As you set up the schedule, consider:
Option Description
Catch Up Behavior Select how many times the scheduled integration
runs after maintenance issues cause errors.
Example: If you schedule an integration to run
multiple times in a week when your environment
is down for maintenance, you can limit the

Option Description
process to run once instead of catching up all
missed occurrences.

4. (Dependent schedules) As you set up the schedule, consider:

Option Description
Dependency Select a Prism-related schedule on which the
dataset integration schedule depends.
Trigger on Status Select the status of the scheduled future process
that causes the dataset integration to run.
Workday recommends using one of the
completed statuses.
Example: You select Prism Integration and an
integration schedule called Dataset Integration
Schedule: Monthly Acquisition Expenses. In the
Trigger on Status field, you select Completed.
Workday brings data into the dataset only after
the Dataset Integration Schedule: Monthly
Acquisition Expenses integration successfully
completes.

Time Delayed Configuration (Optional) Specify the number of days, hours, or

minutes to delay running the dataset integration
after the trigger. You might want to delay
integration to review the latest source files.
5. (Optional) Change the name of the schedule in the Request Name field. Workday assigns a name
to the schedule based on the name of the dataset and prepends Dataset Integration Schedule: to the
name.
6. (Optional) Perform actions such as transferring ownership of the schedule or editing 1 scheduled
occurrence.
a) Access the View Integration Details report for the dataset.
b) Find the integration schedule in the Request Name column on the Schedules tab.
c) From the related actions menu of the integration schedule, select Schedule Future Process and
then the desired action.

Result
Workday imports data into the dataset based on the criteria you specified.
You can view the status of all scheduled integration processes in the Process Monitor and Scheduled
Future Processes reports. The status includes the date and time of the last successful integration. The
last successful integration date informs you about the freshness of the data brought into the dataset.
Example: If the last successful integration date is 1 week ago, but your integration schedule is set to run
daily, this discrepancy could indicate a failure in the integration process.
Related Information
Concepts
Concept: Dataset Integration Schedules on page 351

Upload a New File to a Dataset

Prerequisites
• Any of these security requirements:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Dataset Editor permission on the dataset.
• Dataset Owner permission on the dataset.

Context
When you create a dataset by uploading a file, the data in that dataset stays the same over time. If you
have a new version of the source file, you can upload it to the same dataset. You might want to upload
a new file to update an existing dataset instead of creating a new dataset. When you update an existing
dataset, you maintain any relationships with datasets that depend on the existing dataset.
When you upload a new file, all existing data is replaced with the data in the new file.
Sometimes, the fields in the source file might change, also known as a schema change. Fields might
be added, deleted, or moved. When the schema changes and the new file is imported into the dataset,
you must edit the dataset and save it to incorporate the changes in the dataset. If you don’t save the
dataset, it'll continue to use the old schema definition. The next time the dataset is published, you might get
inconsistent data in the Prism data source.
Note: Uploading a file fails when the schema of the new file doesn't contain a field that currently exists
in the dataset, and the removed field is used in a stage in the dataset. Example: If the dataset includes
a Manage Fields stage and you try to upload a file that is missing a field in the dataset, the upload fails.
That's because the Manage Fields stage works on every field in the dataset.

Steps
1. Access the View Dataset Details report for the dataset you want to update with new data.
2. Click Upload File.
3. In the confirmation dialog, click Upload.
4. Navigate to and select the local file.
5. If Workday successfully uploads the file, navigate to the Edit Dataset Transformations task.
If the schema changed, the Save button is active.
6. If the Save button is active, click Save to apply schema changes.

Result
Workday replaces the data in the dataset with the data in the file you uploaded. It updates the fields in the
dataset if the schema in the uploaded file is different.

Next Steps
Verify that no schema changes broke any Prism calculated fields, stages, derived datasets, or Workday
reports that depend on the dataset whose schema changed.
Related Information
Concepts
Concept: Dataset Schema Changes on page 340
Tasks
Steps: Create a Dataset with External Data (Upload a File) on page 364
Reference
Reference: External Data Limits on page 332

View Prism Data Usage

Prerequisites
• Any of these security requirements:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Prism Datasets: Owner Manage domain in the Prism Analytics functional area.
• Prism: Tables Manage domain in the Prism Analytics functional area.
• Prism: Tables Owner Manage domain in the Prism Analytics functional area.
• Prism Datasets: Publish domain in the Prism Analytics functional area.
• Dataset Viewer permission on 1 or more datasets.
• Dataset Editor permission on 1 or more datasets.
• Dataset Owner permission on 1 or more datasets.
• Table Viewer permission on 1 or more tables.
• Table Editor permission on 1 or more tables.
• Table Owner permission on 1 or more tables.

Context
You can view how much Prism data your organization has used on your tenant. You might want to view
your Prism data usage to ensure you're in compliance with your purchase agreement with Workday.
Workday displays this data usage information:
• Reportable Rows. This value summarizes all rows in published datasets and tables enabled for
analysis in your tenant, including the datasets and tables that you don't have permission on.
• Table and dataset usage. This grid lists all tables and datasets that you have permission on, and
includes the disk space used and number of reportable rows per table and dataset.

Steps
1. Access the Data Catalog report.
2. Click Prism Usage.

View Table and Dataset Lineage

Prerequisites
• Any of these security requirements for dataset lineage:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Prism Datasets: Owner Manage domain in the Prism Analytics functional area.
• Prism Datasets: Publish domain in the Prism Analytics functional area.
• Dataset Viewer permission on the dataset.
• Dataset Editor permission on the dataset.
• Dataset Owner permission on the dataset.
• Any of these security requirements for table lineage:
• Prism: Tables Manage domain in the Prism Analytics functional area.
• Prism: Tables Owner Manage domain in the Prism Analytics functional area.
• Prism Datasets: Publish domain in the Prism Analytics functional area.
• Table Viewer permission on the table.
• Table Editor permission on the table.
• Table Owner permission on the table.

Context
When you bring in data and transform it in Prism Analytics, you can create complex workflows containing
multiple tables and datasets. You create a derived dataset by importing a table or dataset on which the
derived dataset is based. The derived dataset depends on the table or dataset you import into it. You can
visually see these dependencies by viewing the lineage for a table or dataset.
Viewing the lineage enables you to see dependencies, and to trace the origin of a derived dataset back to
its tables and base datasets. The lineage gives you insight into the potential consequences of changes you
make to your data (impact analysis).

Steps
1. Access the Data Catalog report.
2. Right-click a table or dataset whose lineage you want to view, and select View Lineage.
On the View Table Lineage or View Dataset Lineage report, the graph displays dependencies in both
directions from the selected object where applicable:
• Upstream and downstream dependencies. When you view the lineage of a derived dataset, the
graph displays the datasets imported into the derived dataset, and any other derived datasets that
import this derived dataset.
• Downstream dependencies only. When you view the lineage of a table or base dataset, the graph
displays any derived datasets that import this table or base dataset.
Related Information
Tasks
View Dataset Dependencies on page 374
Reference
The Next Level: Prism Performance and Troubleshooting Tips

View Field Lineage

Prerequisites
Any of these security requirements:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Prism Datasets: Owner Manage domain in the Prism Analytics functional area.
• Prism Datasets: Publish domain in the Prism Analytics functional area.
• Dataset Editor permission on the dataset.
• Dataset Owner permission on the dataset.
• Dataset Viewer permission on the dataset and the tenant is configured to have the Enable Prism
Dataset Transformations check box enabled.

Context
When you bring in data and transform it in Prism Analytics, you can create complex workflows containing
multiple transformation stages across various datasets. You can visually see the different stages and
datasets a field passed through up that point by viewing the lineage for the field.

Steps
1. Access the View Dataset Lineage report for a derived dataset.

2. Select the field whose lineage that you want to view, and select View Field Lineage.
On the View Field Lineage report, the graph displays all transformations involving data in the field up to
that point across all datasets you have access to.
When you access the View Field Lineage report, you start at the field that you selected, the root node,
and you can:
• Select a node to view details in the inspector panel on the stage represented in that node.
• Control your view of the lineage by expanding and collapsing chevrons in the graph.
• View the changes across different datasets and tables, differentiated by a colored outline
encompassing all nodes in a dataset.
• Navigate through decision nodes, where there’s a divergence in the lineage.
• View all nodes in datasets and tables that you have at least View Table or View Transformations
permissions for.
• Trace the lineage of all dependent fields for calculated fields.
Related Information
Concepts
Concept: Dataset Field Origin on page 343
Concept: Field Lineage on page 343
Reference
2022R2 What's New Post: Field Lineage for Prism Analytics

View Dataset Dependencies

Context
You create a derived dataset by importing a table or dataset on which the derived dataset is based.
The derived dataset depends on the table or dataset you import into it. You can view these dataset
dependencies.

Steps
1. Access the Data Catalog page.
2. Select a dataset to open its inspector panel.
3. Scroll down to the Imported By section to view the derived datasets that imported the selected dataset.

Reference: Supported Date Formats for External Data in Tables and Datasets
External data that you bring into the Data Catalog might contain fields with date or time values. Workday
only supports some date formats. How Workday uses the date formats depends on the object you create:

• Table. When you define a Date field in the schema of a table, you can specify any of the supported date
formats. The date values in the external data must match the specified date format in order for the row
to be valid and loaded into the table.
• Base dataset. If Workday recognizes the format of a date field in the external file, it automatically
assigns the Date field type when parsing the file.
Workday supports these date formats as well as any shortened versions of them:

Format Type Format

Date and time yyyy-MM-dd'T'HH:mm:ss.SSSZZ
yyyy-MM-dd'T'HH:mm:ssZZ
yyyy-MM-dd'T'HH:mm:ss
EEE, dd MMM yyyy HH:mm:ss Z
MM/dd/yy h:mm:ss a ZZ
MM/dd/yy h:mm:ss a
MM/dd/yy H:mm:ss ZZ
MM/dd/yy H:mm:ss
yy-MM-dd h:mm:ss a ZZ
yy-MM-dd h:mm:ss a
yy-MM-dd H:mm:ss ZZ
yy-MM-dd H:mm:ss
yyyy-MM-dd HH:mm:ss.SSS

Date only yyyy-MM-ddZZ

yy-MM-dd
yyyy-MM-dd
MM/dd/yy

Time only 'T'HH:mm:ssZZ

'T'HH:mm:ss
HH:mm:ssZZ
HH:mm:ss

Related Information
Concepts
Concept: Table and Dataset Field Types on page 344
Tasks
Change Dataset Field Types on page 393
Reference
TO_DATE on page 468

Reference: Naming Guidelines

Table and Dataset Names

Workday suggests that you follow these naming restrictions and recommendations. Workday might not
enforce all naming restrictions depending on how you create the dataset.

Name Type Table Dataset (base and derived)

Name This is the display name. This is the display name.
• Must be unique in the Data • Must be unique in the Data
Catalog. Table names are Catalog. Dataset names are
case insensitive. case insensitive.
• Can contain a maximum of • Can contain a maximum of
255 characters. 255 characters.
• Can include any character, • Can include any character,
including multi-byte including multi-byte
characters, as long as characters, as long as
all characters are UTF-8 all characters are UTF-8
encoded. encoded.
• Can't start with a space or • Can't start with a space or
WPA_. WPA_.
• Can’t end with a space. • Can’t end with a space.
For datasets created from SFTP
or custom reports, Workday
enforces only these display name
restrictions:
• Must be unique in the Data
Catalog. Dataset names are
case insensitive.
• Can contain a maximum of
255 characters.

API Name • Must be unique in the Data • Must be unique in the Data
Catalog. Table API names are Catalog. Dataset API names
case insensitive. are case insensitive.
• Can contain a maximum of • Can contain a maximum of
255 characters. 255 characters.
• Can only include • Can only include
alphanumeric and underscore alphanumeric and underscore
characters. characters.
• Must start with a letter. • Must start with a letter.
• Must end with an • Must end with an
alphanumeric character. alphanumeric character.
• Can't start with WPA_. • Can't start with WPA_.

Field Name This is the display name. This is the display name.
• Can't start with a space or with • Can’t start with ( or with
WPA_. WPA_.
Table field names are case • Must be unique within the
insensitive. dataset.

Name Type Table Dataset (base and derived)

Dataset field names are case
sensitive.

Field API Name • Must be unique in the table. Workday uses dataset API field
Table API field names are names as the dataset field display
case insensitive. names.
• Can contain a maximum of
255 characters.
• Can only include
alphanumeric and underscore
characters.
• Must start with a letter.
• Can’t end with an underscore
character.
• Can't start with WPA_.

Data Change Task Names

Data change task names:
• Must be unique in the Data Catalog. Data change task names are case insensitive.
• Can contain a maximum of 255 characters.
• Can include any character, including multi-byte characters, as long as all characters are UTF-8
encoded.
• Can't start with a space or WPA_.
• Can’t end with a space.
Data change task API names:
• Must be unique in the Data Catalog. Table API names are case insensitive.
• Can contain a maximum of 255 characters.
• Can only include alphanumeric and underscore characters.
• Must start with a letter.
• Must end with an alphanumeric character.
• Can't start with WPA_.

Connection Names
SFTP connection names:
• Must be unique.
• Are case insensitive.
• Can contain a maximum of 255 characters.
• Can include any character, including multi-byte characters, as long as all characters are UTF-8
encoded.

Prism Data Source Names

The Prism data source name comes from the dataset API name of the published dataset.

wBucket Names
• Must be unique.
• Can contain a maximum of 255 characters.

• Can only include alphanumeric and underscore characters.

• Must start with a letter.
• Can't end with an underscore character.
• Can't start with WPA_.

Reference: Supported File Formats for External Data in Tables and Datasets
To bring in non-Workday data as a table or dataset, Workday parses the data into records (rows) and
fields. All characters must be UTF-8 encoded.
Tables and datasets support these source file formats:

Format Description
Delimited Text A delimited file is a plain text file format for describing tabular data.
Comma-separated value (CSV) files are the most common delimited
files. It refers to any file that:
• Is plain text (typically ASCII or Unicode characters)
• Has 1 record per line.
• Has records divided into fields.
• Has the same sequence of fields for every record.
Records are separated by line breaks, and fields within a line are
separated by a delimiter (usually a comma character).
If the delimiter also exists in the field values, it must be escaped.
Workday supports single character escapes (such as a backslash),
as well as enclosing field values in double quotes (as is common with
CSV files).

Reference: Currency Format Requirements for External Data

External data that you bring into a table or dataset might contain fields with currency values. If Workday
recognizes the format of a Currency field, it automatically assigns the Currency field type.
For Workday to recognize a single field value as valid currency data, it must meet these requirements:
• It must contain a numeric amount.
• The numeric amount can only use a period as the decimal separator.
• The numeric amount can't use any character to separate thousands.
• It must contain a valid 3-digit currency code that Workday recognizes.
• The 3-digit currency code can occur either before or after the numeric amount.
• It can contain valid currency symbols that Workday recognizes, but it must also contain the 3-digit
currency code.
• It can't contain extraneous characters, but can contain extra spaces before or after the numeric amount
or currency code.
If a Currency field contains any value that doesn't meet these requirements, Workday treats the value as
NULL.
Example: Workday recognizes these single data values as valid currency data:
• 3000.00 USD
• $3000.00 USD
• USD 3000.00
• USD $3000.00
• -$3,000.00 USD
• ($3,000.00) USD

Related Information
Concepts
Concept: Table and Dataset Field Types on page 344
Tasks
Change Dataset Field Types on page 393
Add a Prism Calculated Field to a Dataset on page 389

Reference: Date Format Symbols

Workday recognizes specific characters as symbols to represent part of a date format when you create and
edit tables and datasets. This section describes the symbols to use and the patterns use them in when you
define your date format. The count and order of the symbols determine the date format.
Workday treats any characters in the pattern that aren't in the ranges of a-z or A-Z as quoted delimiter text.
Example: Workday treats the slash (/) and colon (:) characters delimiter text even if they aren't escaped
with single quotes.

Symbol Meaning Presentation Examples Notes

G era text AD
C century of era (0 or number 20
greater)
Y year of era (0 or year 1996 Numeric presentation
greater) for year and week
year fields are
handled specially.
Example: If the count
of 'y' is 2, the year will
be displayed as the
zero-based year of the
century, which is two
digits.
x week year year 1996 Numeric presentation
for year and week
year fields are
handled specially.
Example: If the count
of 'y' is 2, the year will
be displayed as the
zero-based year of the
century, which is two
digits.
w week number of week number 27
year
e day of week (number) number 2
E day of week (name) text Tuesday; Tue If the number of
pattern letters is 4 or
more, the full form
is used; otherwise a
short or abbreviated
form is used.
y year year 1996

Symbol Meaning Presentation Examples Notes

D day of year number 189
M month of year month July; Jul; 07 3 or more uses text,
otherwise uses a
number
d day of month number 10 If the number of
pattern letters is 3 or
more, the text form is
used; otherwise the
number is used.
a half day of day text PM
K hour of half day (0-11) number 0
h clock hour of half day number 12
(1-12)
H hour of day (0-23) number 0
k clock hour of day number 24
(1-24)
m minute of hour number 30
s second of minute number 55
S fraction of second number 978
z time zone text Pacific Standard Time; If the number of
PST pattern letters is 4 or
more, the full form
is used; otherwise a
short or abbreviated
form is used.
Z time zone offset/id zone -0800; -08:00; 'Z' outputs offset
America/Los_Angeles without a colon, 'ZZ'
outputs the offset with
a colon, 'ZZZ' or more
outputs the zone ID.
' escape character for delimiter
text-based delimiters
'' literal representation literal '
of a single quote

Reference: WPA_ Fields

When you create any table or a base dataset that uses an integration, Workday automatically creates extra
fields in the table or dataset. These fields help you to uniquely identify rows in the table or dataset from
different integration runs.

Field Name Description

WPA_LoadID This field returns a value of type Text containing a unique identifier of
the integration run or data load activity that imported the current row
of data into the dataset or table.

Field Name Description

Workday adds this field to both tables and datasets.

WPA_LoadTimestamp This field returns a value of type Date (to the millisecond) containing
the date and time of the integration run that imported the current row
of data into the dataset or table.
Workday adds this field to both tables and datasets.

WPA_RowID This field returns a value of type Text containing a unique row
identifier for each row in a data load activity or integration run.
Workday adds this field to tables.

WPA_UpdateID This field returns a value of type Text containing a unique identifier of
the data load activity that updated the current row of data in the table.
Workday adds this field to tables.

WPA_UpdateTimestamp This field returns a value of type Date (to the millisecond) containing
the date and time of the data load activity that updated the current
row of data in the table.
Workday adds this field to tables.

You can’t modify or delete these fields, but you can hide them. Use these fields with the other fields to
uniquely identify rows of data in the table or dataset from multiple integrations.
You can also use these fields to group data together from a single data load or integration. Example: you
can create a Group By stage and group on the WPA_LoadID field and Count the number of rows from
each integration run.
Related Information
Tasks
Steps: Create a Dataset with External Data (SFTP Server) on page 360
Steps: Create a Dataset Using Workday Data on page 365

Editing Tables

Parse External Data in a Table

Prerequisites
Security:
• Prism: Tables Create domain in the Prism Analytics functional area when creating a table.
• Any of these security requirements when editing a table:
• Prism Datasets: Owner Manage domain in the Prism Analytics functional area.
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Table Editor permission on the table.
• Table Owner permission on the table.
• Can Insert Table Data permission on the table.

Context
When you load a delimited file into a table, you must define how Workday parses the data. You define
the parsing options on the Edit Parsing Options step when you load data into a table, such as creating a
table by uploading a file, or when adding more rows to an existing table.
Workday supports delimited files that are RFC 4180-compliant. For more information, see RFC 4180.

Steps
1. Access the Edit Parsing Options step for loading data into a table.
2. Configure the parsing options.
As you complete this task, consider:
Option Description
Row Delimiter Specifies the single character that separates rows (or records) in
your source data files.
In most delimited files, rows are separated by a new line, such as
the line feed character, carriage return character, or carriage return
plus line feed. Line feed is the standard new line representation
on UNIX-like operating systems. Other operating systems (such
as Windows) might use carriage return individually, or carriage
return plus line feed. Selecting Any New Line causes Workday to
recognize any of these representations of a new line as the row
delimiter.

Field Delimiter Specifies the single character that separates the fields (or columns)
of a row in your source data files. Comma is the most common field
delimiter.

Field Names Specifies the default name of each field. You can change the field
names after you finish defining the parsing options.
Field names must conform to the name validation rules.
Workday automatically treats the first line in each source file as a
header row instead of as a row of data. If you don't want to use the
first line as names for your fields, clear Use values from first row.

Quote Character The character that encloses a single field value, if any.
Some delimited files use the quote character to enclose individual
data values. The quote character is typically the double quote
character (").
If a field value contains a field delimiter as data, then the field value
must be enclosed in the Quote Character, otherwise Workday
assumes that the field delimiter denotes a new field.

Option Description
If a field value contains the quote character as data, then the
field value must be enclosed in the Quote Character and it must
be escaped, either by the Escape Character or another quote
character.
If a field value contains a row delimiter (such as a new line
character) as data, then the field value must be enclosed in the
Quote Character.
Suppose that you have a row with these 3 data values:

weekly special
wine, beer, and soda
"2 for 1" or 9.99 each

If the field delimiter is a comma, the quote character is a double

quote, and the escape character is a double quote, then a correctly
formatted row in the source data looks like:

"weekly special", "wine, beer, and soda", """2

for 1"" or 9.99 each"

Comment Character Specifies the character that represents a comment at the beginning
of a line of text. Workday ignores every line in the external file
that starts with the comment character. Example: Select # as the
Comment Character to ignore lines that start with #.
When the Comment Character is empty, Workday reads all lines as
rows of data.

Rows to ignore Specifies the number of lines at the beginning of the file to ignore
when reading the source file. To use this with the Use values from
first row option, ensure that the line containing the field names is
visible and is the first remaining line.

Jagged Rows Select these options when the schema of the source file isn't an
exact match of the table schema, and you want Workday to ignore
any missing or extra fields at the end of the file schema.
Field Options These options control how to handle whitespace characters in Text
fields.
• Trim leading spaces outside quotes. This option removes
whitespace characters outside the quotes of Text fields before
the quote character.
• Trim trailing spaces outside quotes. This option removes
whitespace characters outside the quotes of Text fields after the
quote character.
• Trim leading spaces in quotes. This option removes whitespace
characters inside the quotes of Text fields at the beginning of
the field value.
• Trim trailing spaces in quotes. This option removes whitespace
characters inside the quotes of Text fields at the end of the field
value.

Related Information
Tasks
Steps: Create a Table by File Upload on page 355
Reference
Reference: Naming Guidelines on page 376

Edit a Table

Prerequisites
Any of these security requirements:
• Prism Datasets: Owner Manage domain in the Prism Analytics functional area.
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Table Editor permission on the table.
• Table Owner permission on the table.
• Table Schema Editor permission on the table.

Context
You can edit a table by changing the table display name or changing the schema.
You can change the table schema by adding fields, deleting fields, or changing field attributes, such as the
field type. However, you can only change field attributes when the table contains no data.

Steps
1. Access the View Table Details report for a table.
2. Select Edit Schema from the Quick Actions button, or from the related actions menu, select Table >
Edit.
3. (Optional) Click Add Field to add 1 or more fields. In the inspector panel for the field, configure the field
attributes.
See Reference: Table Field Attributes on page 385.
4. (Optional) Delete a field by clicking the trash can in the right-most column of a field in the list.
5. (Optional) Change the field attributes of an existing field.
a) Select a field in the list, and view the field details in the inspector panel on the right side.
b) In the inspector panel for the field, change the field attributes. You can't change the API name.
See Reference: Table Field Attributes on page 385.
6. Click Next.
7. (Optional) Change the Table Display Name.
8. (Optional) Select Enable for Analysis to create a Prism data source using the data in this table.
Workday recommends enabling a table for analysis after:
• You apply the appropriate data source security to the table.
• The table contains the data that you want and receives new and updated data from a data change
task.
9. (Optional) Create or edit 1 or more Tags to organize the table in the Data Catalog.
Related Information
Concepts
Concept: Tables on page 333
Reference
Reference: Naming Guidelines on page 376

Reference: Table Field Attributes

When you add or edit a field in a table in the Data Catalog, you define these attributes:

Field Attribute Notes

Display Name You can change this name at any time. The name must
conform to name validation rules.
API Name The API name must be unique in the table. Workday
automatically selects an API name based on the field
name you enter, modifying it to make it meet the name
requirements. Click Change to change the API name. You
can’t change the API name after you save the table.
Field Type Select the field type that the values in this field must match to
be recognized as valid data. You need to configure additional
field attributes for some field types you select.
Date Format (Required for Date fields) Select the date format that the
values in this field must match to be recognized as valid date
data.
Digits Before and Digits After (Required for Numeric fields) Enter the maximum number of
digits before and after the decimal point that the values in this
field can have to be recognized as valid numeric data. The
sum of these 2 options must be less than or equal to 38.
Business Object (Required for Instance and Multi-Instance fields) Select the
business object to associate with the values in this Instance
field.
Report Field (Optional for Instance and Multi-Instance fields) The context
information for the Instance or Multi-Instance field. To enter or
change the report field, enter the Workday ID.
Description (Optional) Add a helpful field description that explains the
meaning and data value characteristics of the field.
Required Specifies that the field must contain data. Make a field
required to ensure it doesn’t contain a NULL value when you
insert or update data in the table. When you insert or update
data in a table and this field is NULL, Workday rejects the row
and instead includes it in the error file.
Default Value Use the Default Value to define a value for a field if the
uploaded source file schema doesn't include that field. When
the source file schema doesn't include a field, Workday uses
the default value for all rows in the source file.
Note: The Default Value is only used when the source file
schema is missing a field, not when a particular field value is
NULL.

Use as External ID Use this attribute to mark a single field in a table as a key.
Specify a field as the external ID when the values in the field
uniquely identify each row from its source.
Define a field as the external ID if you want to update or
delete data in the table based on data in an external file. This
attribute is similar to a primary key in a relational database.

Field Attribute Notes

When using this attribute, consider:
• You can only define 1 field in a table as the external ID
field.
• Ensure that each field value in the external ID field
is unique. If the field values aren’t unique, you'll get
unexpected results. Workday doesn’t enforce the
uniqueness.
• You can’t define a default value for fields used as an
external ID. The field value must come from the external
source and can’t be NULL.
• Workday automatically marks the external ID field as
required.

Related Information
Concepts
Concept: Tables on page 333
Reference
Reference: Naming Guidelines on page 376

Editing Datasets

Parse External Data in a Dataset

Prerequisites
• Base dataset using external data (from uploading a file or connecting to a server) exists in the Data
Catalog.
• Security:
• Prism Datasets: Create domain in the Prism Analytics functional area when creating a dataset.
• Any of these security requirements when editing an existing dataset:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Dataset Editor permission on the dataset.
• Dataset Owner permission on the dataset.

Context
When you bring external data into a dataset, you must describe the source data in a tabular format. You do
this by describing how to parse the data.
Your data must:
• Be in plain text file format.
• Have 1 record per line.
• Have the same sequence of fields for every record separated by a common delimiter (such as a comma
or tab).
Delimited records are separated by line breaks, and fields within a line are separated by a special
character called the delimiter (usually a comma or tab character). If the delimiter also exists in the field
values, it must be escaped. Datasets support single character escapes (such as a backslash), as well as
enclosing field values in double quotes.

Steps
1. Access the Edit Dataset Transformations task for a base dataset using external data.
2. Edit the Parse stage.
As you complete this task, consider:
Option Description
Row Delimiter Specifies the single character that separates rows (or records) in
your source data files.
In most delimited files, rows are separated by a new line, such as
the line feed character, carriage return character, or carriage return
plus line feed. Line feed is the standard new line representation
on UNIX-like operating systems. Other operating systems (such
as Windows) might use carriage return individually, or carriage
return plus line feed. Selecting Any New Line causes Workday to
recognize any of these representations of a new line as the row
delimiter.

Field Delimiter Specifies the single character that separates the fields (or columns)
of a row in your source data files. Comma and tab are the most
common field delimiters.

Field Names Specifies the default name of each field. You can change the field
names in the Parse stage after you finish defining the parsing
options.
Field names must follow naming validation rules.
Workday automatically treats the first line in each source file as a
header row instead of as a row of data. If you don't want to use the
first line as names for your fields, deselect the Field Names check
box.

Escape Character Specifies the single character used to escape the Quote Character
or another instance of the Escape Character when a Quote
Character is specified. Workday reads an escape character as
data only if it's escaped with another escape character.
If your data values contain quote characters as data, those
characters must be escaped and the entire field value must be
enclosed with the Quote Character. If not, then Workday assumes
that the quote character denotes a new field.
For comma-separated values (CSV) files, it's common practice to
escape field delimiters by enclosing the entire field value within
double quotes. If your source data uses this convention, then you
should specify a Quote Character.

Quote Character Some delimited files use the quote character to enclose individual
data values. The quote character is typically the double quote
character (").
If a field value contains a field delimiter as data, then the field value
must be enclosed in the Quote Character, otherwise Workday
assumes that the field delimiter denotes a new field.
If a field value contains the quote character as data, then the
field value must be enclosed in the Quote Character and it must

Option Description
be escaped, either by the Escape Character or another quote
character.
If a field value contains a row delimiter (such as a new line
character) as data, then the field value must be enclosed in the
Quote Character and Field values contain new lines must be
selected.
Suppose that you have a row with these 3 data values:

weekly special
wine, beer, and soda
"2 for 1" or 9.99 each

If the field delimiter is a comma, the quote character is a double

quote, and the escape character is a backslash, then a correctly
formatted row in the source data looks like:

"weekly special","wine, beer, and soda","\"2

for 1\" or 9.99 each"

Rows to ignore Specifies the number of lines at the beginning of the file to ignore
when reading the source file while creating and publishing the
dataset. To use this with the From First Table Row option, ensure
that the line containing the field names is visible and is the first
remaining line.

Field values contain new lines Check this option if your source data might contain new line
characters as part of a field value.
When enabled, Workday reads the new line characters inside
quote characters as part of the field value instead of as a row
delimiter. Workday interprets any row delimiter character outside of
quote characters as a new record.
Enabling this option might impact the time to publish a dataset if
Workday reads very large source files.
Note that you might get unexpected results if you enable this option
and the source file has malformed data (such as when a field value
has either an opening or closing quote character, but not both).
Try to ensure that your source data is well formed when using this
option.

Trim trailing and leading Select this check box if you want to remove whitespace characters
whitespace characters in Text at the beginning and end of Text fields.
fields

Related Information
Tasks
Add a Stage to a Dataset on page 391
Steps: Create a Dataset with External Data (SFTP Server) on page 360
Steps: Create a Dataset with External Data (Upload a File) on page 364
Reference
Reference: Naming Guidelines on page 376

Examples
Example: Bring in International-Formatted Numeric Fields on page 408

Add a Prism Calculated Field to a Dataset

Prerequisites
• Any of these security requirements:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Dataset Editor permission on the dataset
• Dataset Owner permission on the dataset.

Context
You can transform data in a dataset by adding Prism calculated fields to the dataset. Prism calculated
fields change the number of fields in a dataset, they don't change the number of records.
A Prism calculated field contains these components:

Component Description
Name The name you specify is the field display name.
Expression The expression describes a processing step that you want to perform
on the data in other fields in the dataset. Expressions can include:
• References to other fields as input.
• Constant values as literal text, numeric, or date values.
• Functions from the Prism expression language.
• Arithmetic, comparison, and logical operators.
For more information, see Concept: Prism Expression Language on
page 458.

Field type The expression determines the return value field type.
If the expression includes a function, then the return value of the
function determines the field type.
If the expression doesn't include any function, then the operator
determines the field type:
• Arithmetic operators result in one of the numeric field types,
depending on the input field types used in the expression.
Example: Long * Integer results in a Long field, and Long *
Numeric results in a Numeric field. Workday doesn't guarantee
that each calculated field value will fit in the new field. Any
calculated value that doesn't fit in the new field type becomes
NULL. Workday automatically determines the digits before and
after the decimal for Numeric field types. Numeric fields support
a total of 38 digits before and after the decimal point, and a
maximum of 18 digits after.
• Comparison operators result in a Boolean field.
• Logical operators result in a Boolean field.

You might need to create several Prism calculated fields to achieve the result you want. You can use the
result of a Prism calculated field in the expressions of other Prism calculated fields to define a chain of
processing steps.

You might want to use a Prism calculated field to:

Field Purpose Example

Convert a field type to another Change an Integer field type to a Long field type, so that you can use
field type. the EPOCH_MS_TO_DATE function on it. Example:

EPOCH_MS_TO_DATE(TO_LONG([Date in MS]))

Perform an arithmetic calculation. Calculate the net profit based on the revenue and expenses.
Example:

[Revenue] - [Expenses]

Calculate the percent of total revenue for a particular sale. Example:

([Sale]/[Total Revenue])*100

Extract values from a different Extract the currency codes from a currency field using the
field. EXTRACT_CODE function. Example:

EXTRACT_CODE([Revenue])

Combine the values from 2 Text Combine separate fields consisting of Last Name and First Name into
fields into 1 Text field. 1 field using the CONCAT function. Example:

CONCAT([First Name], " ", [Last Name])

Test for a particular condition. Test whether the year is between 2019 and 2020, inclusive. Example:

[year] BETWEEN 2019 AND 2020

Pad the beginning of a Text field The [EEID] is a Text field containing numeric data of varying lengths,
with leading zeros. and you want to create an [Employee ID] field that is always 7
characters long, including leading zeros where needed.
Create a calculated field called [PaddedID] that adds enough zeros
to the beginning of [EEID] to create a full string, even if [EEID] is an
empty string. Example:

CONCAT(“0000000", [EEID])

Then create a calculated field called [Employee ID] that returns the
last 7 characters of the [PaddedID] field. Example:

SUBSTRING([PaddedID], (LENGTH([PaddedID])-7), 30)

Return a particular date given a The [EFF_Date] field is a Date field, and you want to calculate and
Date field. return the last day of the current month.

DATE_ADD(DATE_ADD(TRUNC([EFF_Date], "month"), 1,
"month"), -1, "day")

To delete a Prism calculated field, access the Edit Dataset Transformations task, and select the menu
for the Prism calculated field you want to remove and select Delete Field. Deleting a field might cause
errors if other Prism calculated fields refer to the deleted field.

Steps
1. Access the Edit Dataset Transformations task for a dataset.
2. Select a dataset pipeline (required for derived datasets) and stage into which to add the Prism
calculated field.
3. Select Add Field.
4. Enter an expression in the expression editor.
If you use Currency fields that contain different codes, Workday treats the result of those calculations as
NULL.
5. In the inspector panel, enter a name. Field names must follow naming validation rules.
6. Save the Prism calculated field by clicking Enter or Return on your keyboard.
Clicking another field on the page also saves the changes to the Prism calculated field.
7. (Optional) You can insert single and multiline comments into any location within a Prism expression.
Workday treats all text between these characters as comments: /* */
Note: Workday won't consider the data values as comments if you enclose these characters and the
comment within double quotation marks.
Related Information
Concepts
Concept: Prism Calculated Fields on page 350
Concept: Hiding Dataset Fields on page 350
Concept: Prism Expression Language on page 458
Reference
Reference: Naming Guidelines on page 376
The Next Level: Prism Analytics Best Practices
Examples
Example: Bring in International-Formatted Numeric Fields on page 408

Add a Stage to a Dataset

Prerequisites
Any of these security requirements:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Dataset Editor permission on the dataset.
• Dataset Owner permission on the dataset.

Context
Add stages to change your data from 1 format to another format.
One way you transform data in a dataset is by adding a stage. There are different types of stages. You can
add a new stage to the end of any pipeline in your dataset. Some stage types can only be added to derived
datasets.

Steps
1. Access the Edit Dataset Transformations task for a dataset.

2. (Required for derived datasets) Select the dataset pipeline where you want to add the stage.
Select the primary pipeline of a derived dataset for some stage types, such as Join or Union.
Base datasets have only 1 pipeline, which is the primary pipeline.
3. Click Add Stage, and select the type of stage to add.
4. Configure the stage parameters.
The parameters you define depend on the type of stage that you're adding.
5. (Optional) Add a description while editing any stage except the Import stage of a derived dataset.
Related Information
Reference
Reference: Filter Stages on page 398
Reference: Group By Stages on page 400
Reference: Join Stages on page 401
Reference: Union Stages on page 402

Manage Dataset Fields

Prerequisites
• Prism Datasets: Create domain in the Prism Analytics functional area when creating a dataset.
• Any of these security requirements:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Dataset Editor permission on the dataset.
• Dataset Owner permission on the dataset.

Context
You can use the Manage Fields stage to view field changes, select fields, and edit fields.
Note: Decide on field names before you define Prism calculated fields and stages. Changing a field name
later on will break Prism calculated field expressions and stages that rely on it.

Steps
1. Access the Edit Dataset Transformations task.
2. Add a Manage Fields stage to edit fields in the dataset.
Workday recommends that you add the Manage Fields stage at the:
• Beginning of the primary pipeline of a derived dataset.
• End of a primary pipeline that you intend to publish.
3. As you complete the Manage Fields stage, consider:
Option Description
Input Name Clear the check box to hide the field from future
stages. You can hide fields to protect sensitive
data or to use a calculated field instead of the
fields that it's based on. Hide unpopulated or
sparse fields or Prism calculated fields that do
interim processing.
Output Name Ensure that the new name:
• Doesn't start with ( or with WPA_.
• Is unique within the dataset.

Option Description
• Is unique to any potential future field names
that come from the source files.
When you change a field name in the dataset
and add a new field with the same name, you get
unexpected results in the data when the schema
updates.

Output Type The field type determines which functions can

use the field as an argument. Create a Prism
calculated field to change a field type to a Date or
Currency field type or to change a Currency field
type to a numeric field type.
For numeric types, you can specify the number of
digits that go before and after the decimal point.
For Instance and Multi-Instance types, you can
select the business object name and report
field associated with the values in the field. To
select a report field, enter the Workday ID.
Numeric field types include Integer, Long, Double,
or Numeric.

Related Information
Concepts
Concept: Hiding Dataset Fields on page 350
Concept: Prism Calculated Fields on page 350
Concept: Table and Dataset Field Types on page 344
Tasks
Add a Prism Calculated Field to a Dataset on page 389
Convert Dataset Text Fields to Date Fields on page 394

Change Dataset Field Types

Context
After importing external data into a dataset, if Workday assigned a different field type than the one you
want, then you can change the field type. You might want to change the field type to:
• Accommodate some calculations you want to do.
Example: You could change an Integer field type to a Long field type to use the
EPOCH_MS_TO_DATE function on it.

• Assign a field type to a value that Workday doesn't automatically recognize.

Example: If Workday doesn't automatically recognize an instance value, change it to the Instance field
type.
Example: If Workday doesn't automatically recognize a date value, change it to the Date field type.
Use the Manage Fields stage to change most field types. However, create a Prism calculated field to make
these field type changes:

From Field Type To Field Type Function

Text Date TO_DATE
Currency Numeric, Double, Integer, or Long EXTRACT_AMOUNT
Numeric, Double, Integer, or Long Currency BUILD_CURRENCY
Text Currency TO_CURRENCY
Instance, Multi-Instance Multi-Instance CREATE_MULTI_INSTANCE

Steps
1. Access the Edit Dataset Transformations task.
2. Select a dataset pipeline (required for derived datasets).
3. Add a Manage Fields stage.
4. Edit the Manage Fields stage by changing the field type in the Output Type drop-down menu.
Note: Every Instance field type must have a business object name. If you change the field type to
Instance, click the settings icon and enter the business object name.
Related Information
Concepts
Concept: Table and Dataset Field Types on page 344
Concept: Prism Calculated Fields on page 350
Tasks
Add a Prism Calculated Field to a Dataset on page 389
Reference
Reference: Currency Format Requirements for External Data on page 378

Convert Dataset Text Fields to Date Fields

Prerequisites
• Dataset must have a field containing date data.
• Any of these security requirements:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Dataset Editor permission on the dataset.
• Dataset Owner permission on the dataset.

Context
When you create a dataset using external data, the data might contain date or time information. When you
create a dataset, Workday reads the data to determine which field type to assign to each field. If Workday
recognizes the format of a date field, it automatically assigns the Date field type. However, Workday only
recognizes some date formats. If Workday doesn't recognize a date format, then it assigns the Text field
type to the field.

If Workday doesn't recognize a date field format, you can create a Prism calculated field to convert the
Text field type to a Date field type.

Steps
1. Access the Edit Dataset Transformations task for a dataset.
2. Select a dataset pipeline (required for derived datasets) and stage into which to add the Prism
calculated field.
3. Add a new field.
4. In the expression editor for this new field, enter an expression that uses the TO_DATE function.
When you enter the expression using the TO_DATE function, make sure that you use the Text field you
want to convert and the date format that best matches the values in that Text field. To quickly enter a
field name, type a left square bracket ( [ ).
Suppose that you have a field called start_date that contains data that looks like 25-May-2017. Use this
expression:
TO_DATE([start_date], "dd-MMM-yyyy")
5. In the inspector panel, enter a name. Field names must follow name validation rules.
6. Save the Prism calculated field by clicking Enter on your keyboard.
Clicking another field on the page also saves the changes to the Prism calculated field.

Result
Prism creates a new field and populates it by converting the data to the Date field type.
Related Information
Concepts
Concept: Table and Dataset Field Types on page 344
Concept: Prism Calculated Fields on page 350
Tasks
Change Dataset Field Types on page 393
Add a Prism Calculated Field to a Dataset on page 389
Reference
Reference: Supported Date Formats for External Data in Tables and Datasets on page 374
Reference: Naming Guidelines on page 376

Change the Dataset Example Rows

Prerequisites
• Any of these security requirements:
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Prism Datasets: Owner Manage domain in the Prism Analytics functional area.
• Dataset Editor permission on the dataset.
• Dataset Owner permission on the dataset.
• Dataset Viewer permission on the dataset and the tenant is configured to have the Enable Prism
Dataset Transformations check box enabled.

• Any of these requirements:

• Dataset Viewer permission on the source base dataset.
• Dataset Editor permission on the source base dataset.
• Dataset Owner permission on the source base dataset.
• Table Viewer permission on the source table.
• Table Editor permission on the source table.
• Table Owner permission on the source table.

Context
Workday displays a subset of dataset rows to give you insight into your source data when you edit a
dataset. Workday automatically displays the first 20,000 records starting with the first file in the dataset.
You can change the example data to select between:
• No Example
• Default
• Custom Example
You can define rules to curate what data you see and how each stage impacts it. When you apply rules
to the custom example data displayed, Workday reads the data from the files again and updates the
statistics and field information for each field in the inspector panel.
You might want to create custom example rows to get more precise statistics on each field in the inspector
panel.
You can disable all example data temporarily to improve responsiveness if your dataset has a lot of fields.
After you make some changes to the dataset, such as adding a new stage or calculated field, you can then
enable the example data by selecting the number of rows to display.
Note: If you have permissions to view the View Dataset Transformations report, then you can change
example data but won't be able to save.

Steps
1. Access the Edit Transformations task for a derived dataset.
2. Select Default Example.
This field changes to reflect the current example option selected.
3. Select Custom Example.
4. Select Add First Rule.
You can add 1 rule per base dataset or table.
5. Select a source.
Workday displays the base datasets and tables that you have permission to view.
6. (Optional) Add a Description to help others understand how the rule impacts the data.
7. Specify Conditions by creating a conditional rule for the data.
You can add 1 or more conditions.
8. (Optional) Select Convert to Advanced.
Use the Prism expression language to write a boolean expression. For more information and examples,
see Reference: Boolean Expressions on page 404.
You can convert rule conditions created in Basic mode to rule expressions in Advanced mode. If you
switch back to Basic mode from Advanced mode, you need to define rule conditions again. Workday
doesn't convert Advanced mode rule expressions to Basic mode rule conditions.
9. Apply the rule.
You can only save the rule if you have Dataset Editor permission for the current derived dataset.

10.(Optional) Download Example Data.

You can download the example data displayed to view a snapshot of how your stages impact the data
before publishing.

Result
Workday applies the rule to the example data and displays rows that meet the defined conditions.

Next Steps
You can copy and paste the rules for a base dataset to other derived datasets using the same base
dataset by selecting the related actions menu by the custom example rule.
Related Information
Reference
Reference: Boolean Expressions on page 404
2022R2 What's New Post: Custom Examples for Prism Dataset Transformations

Concept: Dataset Example Data

When you're editing dataset transformations, you can view how your changes affect an example of the
data. This view enables you to see how different stages impact your data.
You can change the data displayed by selecting any of these example options:

Example Option Description Security Requirements

No Example No data displayed. This option Dataset Editor permission or
has the fastest load time. better on the dataset.
Default Example Workday displays a subset of the Dataset Editor permission or
data, enabling you to assess how better on the dataset.
different stages affect a subset of
your data.
Custom Example This option is only available for • Dataset Editor permission or
derived datasets. You can create better on the derived dataset.
rules with different filter criteria • Any of these security
for different subsets of your data. requirements:
These rules enable you to curate
what data you see and how each • Dataset Viewer permission
stage impacts it. or better on the base
dataset.
You can add 1 rule per base
• Table Viewer permission or
dataset or table used in the
better on the table.
derived dataset. The rules you
define are specific to this derived
dataset and don’t affect other
datasets with the same base
dataset or table. When adding
a filter stage, you can add more
complex filter criteria similar to
the Filter stage.

Note: If you have permissions to view the View Dataset Transformations report, then you can change
example data but won't be able to save.
Workday displays up to 20,000 rows when you select either Default or Custom Example.

Comparing Example Data to Published Data

Workday displays example data on a limited number of records, which typically is less than the number of
records published in a dataset. If the dataset uses a Join stage and 1 or more Prism calculated fields after
the Join stage, the example data displayed might be different than the published data. The published data
is correct because it works on all data from the sources.
Example: Your dataset includes a Join stage using a right outer join and a Prism calculated field with a
CASE function that evaluates the value in a field from the secondary (right) pipeline. The example data
might not find a match and return NULL for the field value, whereas the published data finds a match and
returns a non-null value. As a result, the CASE function returns a different value in the example data than
in the published data.
Related Information
Reference
2022R2 What's New Post: Custom Examples for Prism Dataset Transformations

Reference: Explode Stages

You can convert a multi-instance field into an instance field. Workday takes each instance value in the
multi-instance field and creates a new row for each value. All other fields are persisted in every new row
created. Workday recommends using this stage in a derived dataset.

Explode Stage Option Description

Select the field to explode You can select a multi-instance field in the dataset
to explode. The selected field will be dropped from
the dataset in subsequent stages
Workday will drop any report field associated with
the multi-instance field. You can add a report field
in a Manage Fields stage.

Name of the newly created field Workday recommends using a name similar to
the original multi-instance field name to facilitate
auditing.

Related Information
Concepts
Concept: Dataset Stages on page 342
Tasks
Add a Stage to a Dataset on page 391
Reference
2023R1 What's New Post: Explode Stage for Datasets

Reference: Filter Stages

You can convert filter conditions created in Basic mode to filter expressions in Advanced mode. If you
switch back to Basic mode from Advanced mode, you need to define filter conditions again. Workday
doesn't convert Advanced mode filter expressions to Basic mode filter conditions.

Edit Mode Description

Basic This mode displays prompts to help you define filter
criteria, creating filter conditions.
This mode is useful if you don't want to learn the
details of the Prism Analytics expression language
to write a filter expression manually.

Edit Mode Description

Advanced This mode enables you to define the filter criteria by
writing an expression (the filter expression). Filter
expressions must evaluate to true or false.
This mode is useful if you want to write a filter
expression that can’t be expressed in Basic mode.

Basic Mode
Define these options when you configure Filter stages in Basic mode:

Filter Stage Option Description

If All/If Any • If All—All filter conditions must be met for a
row to remain in the output of the Filter stage.
This option works like using an AND operator
between each filter condition.
• If Any—Any filter condition can be met for the
row to remain in the output of the Filter stage.
This option works like using an OR operator
between each filter condition.

Filter Condition Click Add Filter to add a new filter condition. Select
a field and operator from the prompts, and then
enter a value in the empty text field. Workday
reads the value in the text field exactly as is. You
don't need to add any quotation marks or escape
characters for Text field types.
If the field you select is a currency field, you can
enter an amount and select a currency code or
select only a currency code.
When the filter condition is configured as desired,
click the check mark button to save the filter
condition to the Filter stage. You can change the
filter condition at any time by clicking its edit button.

Advanced Mode
In Advanced mode, use the Prism expression language to write a boolean expression. Example:
TO_STRING([zip code]) LIKE("94*")
For more information and examples, see Reference: Boolean Expressions on page 404.
You can insert single and multiline comments into any location within a Prism expression. Workday treats
all text between these characters as comments: /* */
Note: Workday won't consider the data values as comments if you enclose these characters and the
comment within double quotation marks.
Related Information
Concepts
Concept: Dataset Stages on page 342
Tasks
Add a Stage to a Dataset on page 391

Reference
Reference: Boolean Expressions on page 404
Reference: Join Stages on page 401
Reference: Union Stages on page 402
Reference: Currency Format Requirements for External Data on page 378

Reference: Group By Stages

As you complete this stage, consider:

Group By Stage Option Description

Choose Grouping Fields Select 1 or more fields by which to group values
together. If you summarize (aggregate) values in
a group that contains different currency codes,
Workday returns NULL values.
Add Summarization Fields Define 1 or more summarization types (aggregate
functions) that apply to each grouping field.

You can select from these summarization types:

Summarization Type Description

Average Average returns the average of all valid numeric
values for the specified grouping field. It sums
all values in the specified field and divides by
the number of valid (NOT NULL) rows. You can
calculate the average on any numeric field.
Count Count returns the number of rows for the specified
grouping field.
Max Max returns the largest (maximum) value from
the specified grouping field. You can calculate the
maximum on any numeric or date field.
Min Min returns the smallest (minimum) value from
the specified grouping field. You can calculate the
minimum on any numeric or date field.
Sum Sum returns the total of all values from the
specified grouping field. You can calculate the sum
on any numeric field.

Related Information
Concepts
Concept: Dataset Stages on page 342
Tasks
Add a Stage to a Dataset on page 391
Reference
Reference: Filter Stages on page 398
Reference: Union Stages on page 402
The Next Level: Prism Analytics Best Practices

Reference: Join Stages

You can include 2 datasets (dataset pipelines) in a Join stage. You can add additional Join stages in the
pipeline if you need to join multiple datasets.

Join Stage Option Description

Join Pipeline Select a dataset pipeline to join with the primary
pipeline. If there aren't any pipelines available,
select Add Another Pipeline to create a pipeline
by importing a dataset.
Match Rows Select 1 or more fields from each dataset pipeline
whose values should match each other. Select the
fields that uniquely identify rows in each dataset
pipeline. Defining the matching rows is similar to
defining a primary key/foreign key relationship in
relational database terms.
You can also select an optional suggestions link
that displays Workday recommended join keys. The
suggestions are based on the number of matching
rows between fields in the example data.

Join Type Select the join type. The join type specifies which
rows from each dataset pipeline to include in the
join result.
• Inner Join. Workday includes rows that have
matching values that exist in both pipelines. If a
row from 1 pipeline doesn't match a row in the
other pipeline, the row is omitted from the join
result.
• Left Outer Join. Workday includes all rows
in the Primary pipeline and searches for a
matching row in the other pipeline. If there's no
matching row in the other pipeline, Workday
populates each field from the other pipeline
with NULL values. When the imported pipeline
includes multiple matching rows, then Workday
includes both rows in the join result.
• Right Outer Join. Workday includes all rows
in the imported dataset pipeline and searches
for a matching row in the Primary pipeline. If
there's no matching row in the Primary pipeline,
Workday populates each field from the Primary
pipeline with NULL values. When the Primary
pipeline includes multiple matching rows, then
Workday includes both rows in the join result.
• Full Outer Join. Workday includes all rows from
both pipelines. If a row from 1 pipeline doesn't
match a row in the other pipeline, Workday
populates each field from the nonmatching
pipeline with NULL values. When there are
multiple matching rows, Workday includes all
rows in the join result.

Join Stage Option Description

Note that Workday replaces all NULL values with
default values when you publish the dataset.

Select Fields Select which fields from each pipeline to include

in the join result. Any field you don't include is
dropped from that stage in the pipeline and all later
stages.

Related Information
Concepts
Concept: Dataset Stages on page 342
Tasks
Add a Stage to a Dataset on page 391
Reference
Reference: Filter Stages on page 398
Reference: Group By Stages on page 400
The Next Level: Prism Performance and Troubleshooting Tips
2023R1 What's New Post: Join Stage Suggestions

Reference: Union Stages

You can include 2 datasets (dataset pipelines) in a Union stage, and add additional Union stages in
the pipeline if you need to combine multiple datasets. If you're familiar with SQL, the Union stage is the
equivalent of a UNION ALL operator.
Define at least 1 set of matched fields (field mapping) in a Union stage before saving it. If you don't specify
a field in an input dataset for a field mapping, Workday will use a NULL value in that field from that input
dataset.

Union Stage Option Description

Union Pipeline Select a dataset pipeline to combine with the
primary pipeline. If there aren't any pipelines
available, select Add Another Pipeline to create a
pipeline by importing a dataset.
Match Fields—Union Output The name of the field that will be output from the
Union stage for each field mapping.
Match Fields—Primary Pipeline The field from the primary pipeline to match with a
field from the union pipeline.
Match Fields—Union pipeline name The field from the union pipeline to match with a
field from the primary pipeline.
Rematch Click this button if you want to discard all field
mappings and return to the default field mappings
that Workday detects and configures.
Clear All Click this button to discard all field mappings. Then
define at least 1 field mapping in the Union stage
before saving it.
Include All Click this button to create a field mapping for each
field in the input dataset pipeline. Then you can
select which fields to match from the other input
dataset pipeline.

Preparing Fields from Input Datasets

The datasets you want to combine in a Union stage might not have the same schema. Example: One
dataset might have first name and last name information in a single field, and the other has that information
in 2 fields. When this is the case, you can create Prism calculated fields for each input dataset so that you
can combine them in a Union stage.
You can create Prism calculated fields for input datasets in these locations:
• In the original dataset. Any Prism calculated field you create in a dataset is available to both that
dataset and any derived dataset that imports it as an input dataset.
• In the dataset pipeline of the derived dataset. Any Prism calculated field you create in a pipeline stage
of a derived dataset is available only to that derived dataset. It doesn't get pushed back to the original
input dataset. You might want to create a Prism calculated field in the pipeline of an imported dataset if
you need a field to use a different field type, but you don't want to change the field type of the original
dataset. Example: You could create a Prism calculated field to change a zip code field from Integer to
Text to match it with a Text zip code field in another input dataset.
Related Information
Concepts
Concept: Dataset Stages on page 342
Tasks
Add a Stage to a Dataset on page 391
Reference
Reference: Filter Stages on page 398
Reference: Group By Stages on page 400
Reference: Join Stages on page 401

Reference: Unpivot Stages

For Workday to convert fields (columns) to rows in derived datasets, follow these requirements:

Requirement Description
Number of Input Fields Select at least 2 input fields to unpivot.
Enter the same number of input fields for every
group of input fields that you unpivot in a single
Unpivot stage.
Example: If you select 5 input fields to unpivot,
each subsequent group of input fields that you
unpivot in the stage must contain 5 input fields.
If you unpivot multiple groups of input fields, the
total number of input fields you can use for all
groups together in a single Unpivot stage is 150.

Input Field Types Select input fields that are the same field type, such
as Text or Numeric. You can unpivot all field types.
If you select input fields consisting of Instance or
Multi-Instance fields, these input fields must use the
same business object.
If you select input fields consisting of Numeric
fields, these input fields must have the same
number of digits specified before and after the
decimal point.

Requirement Description
Output Field Names Enter unique names for all pairs of new fields
created from unpivoting.

Related Information
Concepts
Concept: Unpivot Stages on page 343
Reference
2020R2 What’s New Post: Unpivot Stage
Examples
Example: Unpivot Stock Vesting Data in a Dataset on page 406

Reference: Boolean Expressions

A boolean expression is an expression that evaluates to true or false. You can use the Prism expression
language to write boolean expressions in:
• Filter expressions. Use Advanced mode when configuring a dataset Filter stage.
• Custom example rule expressions. Use Advanced mode when configuring a rule for the dataset custom
example.
• Prism calculated fields. Example: Use a boolean expression in the CASE function.
The typical format of a boolean expression is:

field_name comparison_operator comparison_value

The comparison value must be of the same field type as the field in the expression.
You can also use logical operators (such as AND and OR) or arithmetic operators (such as + or /) to define
more complex expressions.
When the field name includes a space or a special character, enclose the field name in square brackets:
[ticker symbol].
When the comparison value is for a Text field type, enclose the value in double quotes (""). Example:

[Zip Code] = "94111-5224"

Comments in Expressions
You can insert single and multiline comments into any location within a Prism expression. Workday treats
all text between these characters as comments: /* */
Note: Workday won't consider the data values as comments if you enclose these characters and the
comment within double quotation marks.

Text Field Examples

[movie title] LIKE ("* and the*")

[contingent workers] IN ("Larry", "Curly", "Moe")

schedule NOT IN ("Saturday", "Sunday")

status IS NOT NULL

Numeric and Currency Field Examples

TO_STRING([zip code]) LIKE("94*")

[sale price] < 50.00

age >= 21

((EXTRACT_AMOUNT([Total Sales]) > 1000) AND (EXTRACT_CODE_TEXT([Total

Sales]) == "USD"))

Date Field Examples

[purchase date] BETWEEN 2019-06-01T00:00:00.000Z AND

2019-07-31T00:00:00.000Z

[graduation] >= 1990-01-01

Instance and Multi-Instance Field Examples

INSTANCE_IS_SUPERSET_OF([Cost Center - Manager], [Cost Center])

[Cost Center] IS EMPTY

[Journal Lines] IS NOT NULL

[Cost Center 1] != [Cost Center 2]

NOT INSTANCE_EQUALS([Cost Center 1], [Cost Center 2])

INSTANCE_CONTAINS_ANY([Regions], "070b0d082eee44e1928c808cc739b35f",
"f4c49debb3dc483baa8707dfe683503c")

Boolean Expressions on Date Type Fields

Boolean expressions on Date type fields must be in either of these formats:

yyyy-MM-ddTHH:mm:ss:SSSZ
yyyy-MM-dd

Don't enclose comparison values for Date fields in quotation marks or use any other punctuation. If the
date value is in Text format rather than Date format, the value must be enclosed in quotes like all text
values.
When specifying a range of dates, always write the earlier date first.
If the boolean expression is a shortened version of the full format, then any values not included are
assigned a value of zero (0). Example: the expression BETWEEN 2019-06-01 AND 2019-07-31 is
equivalent to this expression:

BETWEEN 2019-06-01T00:00:00.000Z AND 2019-07-31T00:00:00.000Z

The expression above doesn't include any values from July 31, 2019. To include values from July 31,
2019, use BETWEEN 2019-06-01 AND 2019-08-01.

Boolean Expressions on Currency Type Fields

Currency type fields in boolean expressions must be in a format recognized by Workday. If a Currency field
contains any value that doesn't meet these requirements, Workday treats the value as NULL.

You can use multiple currency codes. Example:

((EXTRACT_CODE_TEXT([Annual Salary]) == "EUR") AND (EXTRACT_AMOUNT([Annual

Salary]) >= 90000))
OR
((EXTRACT_CODE_TEXT([Annual Salary]) == "USD") AND (EXTRACT_AMOUNT([Annual
Salary]) >= 100000))

Related Information
Concepts
Concept: Prism Expression Language on page 458
Tasks
Change the Dataset Example Rows on page 395
Reference
Reference: Filter Stages on page 398
Comparison Operators on page 460

Example: Unpivot Stock Vesting Data in a Dataset

This example illustrates how to create an Unpivot stage in a dataset to transpose fields (columns) of data
into rows of data.

Context
You have a CSV file of stock vesting data for your workers. The workers' stock vests in 3 installments, with
a different number of shares on each date. The file contains 1 row of data for each worker, and a separate
field for each vesting date and the number of shares that vested on each date.
The CSV file contains these rows and fields:

Name Vest Date 01 QTY Vest 01 Vest Date 02 QTY Vest 02 Vest Date 03 QTY Vest 03
Dominique 04/01/2020 80 07/01/2020 85 10/01/2020 92
Desmond 02/01/2021 70 05/03/2021 65 08/02/2021 79
Stacey 02/01/2021 90 05/03/2021 80 08/02/2021 90

You need to transpose the data so that you have:

• A field that contains all vesting dates for each worker.
• A field that contains the number of shares that vested on each date for each worker.

Prerequisites
Create a table by uploading a CSV file using the data in this example. See Steps: Create a Table by File
Upload on page 355.
Create a derived dataset from the table. See Steps: Create a Derived Dataset on page 367.
Security: Prism Datasets: Manage domain in the Prism Analytics functional area.

Steps
1. From the View Dataset Details report of the derived dataset, click Edit.
2. Click Add Stage, and select Unpivot.
First, we'll unpivot the 3 date input fields, Vest_Date_01, Vest_Date_02, and Vest_Date_03.
3. Click the plus sign next to Output Values so you have a total of 3 pairs of prompts.

4. Select these values in the Input Fields and Output Values prompts:

Input Fields Output Values

Vest_Date_01 Vesting Date 01
Vest_Date_02 Vesting Date 02
Vest_Date_03 Vesting Date 03
5. In Field Names from Input, enter Vesting Schedule.
6. In Values from Output, enter Vesting Dates.
7. Click Preview to see the results of the settings you've made so far.
On the Output Fields tab, Workday displays the results of the changes you defined in the Unpivot
stage. Workday:
• Removes the input fields you selected.
• Displays the 2 new fields using the field names you defined.
• Displays the new rows created using data from the removed input fields. In this example, Workday
displays 9 rows total.
8. Click the plus sign in the upper right corner of the Unpivot stage panel. Clicking the plus sign creates
another group of input fields that you can unpivot into rows.
Next, we'll unpivot the 3 quantity input fields, QTY_Vest_01, QTY_Vest_02, and QTY_Vest_03.
9. Click the plus sign next to Output Values so you have a total of 3 pairs of prompts.
10.In the Input Fields and Output Values prompts, enter these values:

Input Fields Output Values

QTY_Vest_01 Quantity Vesting 01
QTY_Vest_02 Quantity Vesting 02
QTY_Vest_03 Quantity Vesting 03
11.In Field Names from Input, enter Quantity Schedule.
12.In Values from Output, enter Number of Shares.
13.Click Preview to see the results of the settings you've made so far.
On the Output Fields tab, Workday displays the results of the changes you defined in the Unpivot
stage.
14.Click Done, and click Save.

Result
The output of the Unpivot stage contains these rows and fields:

Name Vesting Schedule Vesting Dates Quantity Number of Shares

Schedule
Dominique Vesting Date 01 04/01/2020 QTY Vesting 01 80
Dominique Vesting Date 02 07/01/2020 QTY Vesting 02 85
Dominique Vesting Date 03 10/01/2020 QTY Vesting 03 92
Desmond Vesting Date 01 02/01/2021 QTY Vesting 01 70
Desmond Vesting Date 02 05/03/2021 QTY Vesting 02 65
Desmond Vesting Date 03 08/02/2021 QTY Vesting 03 79

Name Vesting Schedule Vesting Dates Quantity Number of Shares

Schedule
Stacey Vesting Date 01 02/01/2021 QTY Vesting 01 90
Stacey Vesting Date 02 05/03/2021 QTY Vesting 02 80
Stacey Vesting Date 03 08/02/2021 QTY Vesting 03 90

Next Steps
(Optional) Add a Manage Fields stage after the Unpivot stage to hide the Quantity Schedule field. In this
example, the Quantity Schedule field contains data that is redundant with the Vesting Schedule field.
Related Information
Concepts
Concept: Unpivot Stages on page 343
Reference
Reference: Unpivot Stages on page 403
2020R2 What’s New Post: Unpivot Stage

Example: Bring in International-Formatted Numeric Fields

This example describes how to use Prism Analytics to bring in external data that includes a numeric field
containing International-formatted numbers.

Context
Your company has a delimited file with numeric data formatted using periods to separate thousands and
commas to separate decimals. You want to bring this data into Prism Analytics as a Numeric field so that
you can perform calculations on the data. However, Workday only recognizes data in an external file as
valid numeric data when it:
• Uses a period as the decimal mark.
• Doesn't use any character to separate thousands.
You have a comma delimited (CSV) file with this data:

Key,Amount
1,"9.000,1222-"
2,"11.111,2333"
3,"9.999.999,34-"
4,"7.777.777,45"
5,"8.888,56"

In your file, no value has more than 4 digits after the decimal mark.

Prerequisites
Create a table by file upload, using the CSV file to define the source schema. The table should have these
fields:
• Key of type Numeric
• Amount of type Text
Create a derived dataset based on the table, and use DDS Intl as the dataset name.
Security:
• Prism: Tables Create domain in the Prism Analytics functional area.
• Prism: Manage File Containers domain in the Prism Analytics functional area.

• Prism Datasets: Create domain in the Prism Analytics functional area.

• Prism Datasets: Manage domain in the Prism Analytics functional area.

Steps
1. Access the Edit Dataset Transformations task for the DDS Intl dataset.
2. Create a Prism calculated field that removes the thousands separators by replacing any period with an
empty string.
a) Select Add Field.
b) Enter this expression in the expression editor, and press Enter or Return on your keyboard:

REGEX_REPLACE([Amount],"\.","")
c) In the inspector panel, enter this as the field name: Amount no thousands
3. Create a Prism calculated field that replaces the decimal comma with a decimal period.
a) Select Add Field.
b) Enter this expression in the expression editor, and press Enter or Return on your keyboard:

REGEX_REPLACE([Amount no thousands],",",".")
c) In the inspector panel, enter this as the field name: Amount decimal period
4. Create a Prism calculated field that adds any negative sign that exists at the end of the value to the
front of the value.
a) Select Add Field.
b) Enter this expression in the expression editor, and press Enter or Return on your keyboard:

CASE WHEN SUBSTRING([Amount decimal period], LENGTH([Amount decimal

period])-1, LENGTH([Amount decimal period])) = "-"
THEN CONCAT("-",REGEX_REPLACE([Amount decimal period],",",""))
ELSE [Amount decimal period]
END
c) In the inspector panel, enter this as the field name: Amount minus sign
5. Create a Prism calculated field that removes any minus sign at the end of the value.
a) Select Add Field.
b) Enter this expression in the expression editor, and press Enter or Return on your keyboard:

CASE WHEN SUBSTRING([Amount minus sign], LENGTH([Amount minus sign])-1,

LENGTH([Amount minus sign])) = "-"
THEN SUBSTRING([Amount minus sign], 0, LENGTH([Amount minus sign])-1)
ELSE [Amount minus sign]
END
c) In the inspector panel, enter this as the field name: Amount final
6. Create a Prism calculated field that converts the [Amount final] Text field to a Numeric field.
a) Select Add Field.
b) Enter this expression in the expression editor, and press Enter or Return on your keyboard:

CAST([Amount final] AS Decimal(20,4))

c) In the inspector panel, enter this as the field name: Amount Numeric
7. Select Add Stage and then select Manage Fields.

8. Hide these fields by clicking the eye icon:

• Amount
• Amount no thousands
• Amount decimal period
• Amount minus sign
• Amount final
9. Select Done.
10.Save your dataset.

Result
The dataset contains these fields:
• Key as type Numeric
• Amount Numeric as type Numeric, with 20 digits before the decimal and 4 digits after.

Changing Data in Tables

Create a Data Change Task

Prerequisites
Security:
• Prism: Manage File Containers domain in the Prism Analytics functional area when uploading a file.
• Any of these security requirements:
• Prism: Tables Owner Manage domain in the Prism Analytics functional area.
• Prism: Tables Manage domain in the Prism Analytics functional area.
• Table Owner permission on the table.
• Table Editor permission on the table.
• Can Delete Table Data permission on the table.
• Can Insert Table Data permission on the table.
• Can Truncate Table Data permission on the table.
• Can Update Table Data permission on the table.

Context
You can change the rows of data in a table by creating and running a data change task. You can:
• Insert new rows.
• Update specific rows based on a key field.
• Delete specific rows based on a key field.
• Insert new and update existing rows in the same activity, known as an upsert operation.
How you change the rows in the table depends on the operation you select, such as upsert or delete, and
the source data. The source you specify must contain the rows you want to change in the table, such as
new rows to insert, or existing rows to update or delete.
To create, edit, or view a data change task on a target table, you must have permission on the target table.
Example: To create a data change task using the upsert operation, you must have both insert and update
permission on the target table.

Steps
1. Access the Data Catalog report.
2. Select Create > Data Change Task.
You can change the data change task name at the top of the left side panel.
3. On the Source step, select the source that contains the data you want to change in the target table.
Workday uses the file upload source type by default. Click Change Connection to select a different
source type. As you select a source type, consider:
Option Description
Data Catalog Select an existing dataset or table.
File Upload Select 1 or more delimited files.
When you upload multiple files, each file must use
the same schema. Workday supports RFC 4180-
compliant delimited files. For more information,
see RFC 4180.
When you select file upload as the source type,
configure the Source Options to define how to
parse the file.

SFTP Select an SFTP connection that connects to an

SFTP server containing 1 or more delimited files.
When the SFTP connection contains multiple
files, each file must use the same schema.
Workday supports RFC 4180-compliant delimited
files. For more information, see RFC 4180.
For SFTP sources, you must also upload 1 local
delimited file that uses the same schema as
the files on the SFTP server. Workday uses the
uploaded file to determine how to parse the SFTP
files. Workday doesn't load the data from the
uploaded file to the table.
When you select SFTP as the source type,
configure the Source Options to define how to
parse the uploaded file.

Workday Report Select an existing Workday custom report.

Workday displays reports that meet the eligibility
requirements for importing into tables. See
Concept: Creating Reports to Import into Tables
and Datasets on page 330.

4. On the Source Options step, define how to parse the data in the files you uploaded for file upload or
SFTP sources.
a) Parse External Data in a Table on page 381.
b) Review the fields Workday created based on the parsed file, and modify the fields if necessary.
Select a field in the list and view the field details in the inspector panel on the right side. You might
need to:
• Change the Field Type when Workday assigns the wrong field type. Workday assigns the field
type based on the first few rows only. Example: Workday assigns the Numeric field type to a field
with ZIP code data because the example rows that it evaluates only contain numerals. However,

based on your knowledge of the source data, you know that some ZIP code values contain letters
or a hyphen, so you change the field type to Text.
• Change other field attributes based on the field type to ensure that Workday correctly parses the
data, such as Digits Before, Digits After, or Date Format.
See Reference: Table Field Attributes on page 385.
5. On the Target step, select the target table that contains the data you want to change.
6. Select the target operation to perform on the target table using the source data.
Option Description
Insert Workday keeps the existing data in the table and adds the new
data in the source. This operation is also known as Append.
Truncate and Insert Workday deletes the existing data in the table and replaces it with
the data in the source. This operation is also known as Replace.
Delete Workday deletes a row from the table when it matches a row in the
source.
Update Workday updates a row in the table when it matches a row in the
source.
To select this operation, you must use a table where you
configured 1 field as the external ID.

Upsert Workday updates a row in the table when a matching row already
exists and inserts the row when it doesn’t exist.
To select this operation, you must use a table where you
configured 1 field as the external ID.

7. On the Mapping step, select a field in the target table to use as the operation key for delete, update, or
upsert operations.
You can specify 1 of these target table fields:
• The field configured as the external ID in the table: You can use this field for delete, update, or
upsert operations.
• WPA_LoadID: You can use this field for delete or update operations only.
• WPA_RowID: You can use this field for delete or update operations only.
8. Select a source field for each target field that you want to modify. Workday requires that you map any
field used as the operation key.
Workday lists the source fields that are compatible for a specific target field. If Workday doesn't list
a source field you want, verify the source field attributes, such as the digits before, digits after, or
business object. You can navigate to the Source Options step to change the field attributes for file
upload and SFTP sources.
You can click Reset Matches to revert all mappings you changed to the simple match algorithm that
Workday uses by default. The simple match algorithm:
• Is case insensitive.
• Ignores spaces.
• Ignores underscore characters.
• Matches on the field API name.
• Won't match fields with different field types.
9. On the Review step, verify the information. You can go back to any previous step and make any
correction if necessary.
10.Click Finish and select Run Without Saving, Save and Run Now, or Save.

Result
When you save the data change task, Workday creates the data change task object and displays it on the
Data Change Tasks tab of the Data Catalog report.
When you run the data change task, Workday starts a data change activity to change the data in the table
based on the data in the source. You can view the data change activity progress and history on:
• The Activities tab of the View Table Details report. To fix errors on a table following a data change,
download the error file from the data change activity. Workday only creates an error file for data change
activities that use a file upload as the source.
• The Data Change Activities tab of the Data Catalog report.
• The Prism Activities Monitor report. You can view a detailed list of all types of Prism-related activities
for a given date range.
• The Prism Activities Dashboard report. You can view an active dashboard of all Prism-related
activities for the last 180 days. You can also see live updates to the status of activities and their run
times.

Next Steps
To fix errors on a table following a data change, download the error file from the data change activity on
the Activities tab of the View Table Details report. Workday only creates an error file for data change
activities that use file upload or SFTP sources.
Related Information
Concepts
Concept: Data Change Tasks on page 415
Concept: Mapping Fields in Data Change Tasks on page 416
Concept: Creating Reports to Import into Tables and Datasets on page 330
Tasks
Create an SFTP Connection on page 416
Reference
Reference: Table Field Attributes on page 385
Reference: External Data Limits on page 332
2022R1 What's New Post: Report Sources for Data Change Tasks
2022R1 What's New Post: SFTP Sources for Data Change Tasks
2021R2 What's New Post: Prism Analytics Data Management

Create a Data Change Task Schedule

Prerequisites
Security:
• Prism Datasets: Owner Manage domain in the Prism Analytics functional area.
• Prism Datasets: Manage domain in the Prism Analytics functional area.
• Table Editor permission on the table.
• Table Owner permission on the table.
• Can Delete Table Data permission on the table.
• Can Insert Table Data permission on the table.
• Can Truncate Table Data permission on the table.
• Can Update Table Data permission on the table.

Context
You can create a schedule for running a data change task. You can:

• Create a schedule for data change tasks that use any source type other than file upload.
• Create 1 active schedule per data change task.
• Define schedules to run on a recurring basis (Example: daily, weekly, or monthly).
• Define schedules to run only if another Prism scheduled process completes at a status you specify.

Steps
1. Access the View Data Change Task report for the data change task you want to create a schedule for.
2. Select Data Change Task > Create Schedule from the related actions menu.
3. In Run Frequency, specify how often to run the data change task.
The choices include creating a dependent schedule.
4. Select the criteria for the schedule.
5. (Recurring schedules) As you configure the schedule, consider:
Option Description
Priority Unavailable for data change task schedules.
Catch Up Behavior Select how many times the scheduled data
change runs after maintenance issues cause
errors.
6. (Dependent schedules) As you configure the schedule, consider:
Option Description
Dependency Select a Prism-related schedule on which the data
change task schedule depends.
Trigger on Status Select the status of the scheduled future process
that causes the data change task to run.
Workday recommends using one of the
completed statuses.

Time Delayed Configurations (Optional) Specify the number of days, hours, or

minutes to delay running the data change task
after the trigger.

Result
Workday runs the data change task based on the criteria that you specify, creating a data change activity.
View the status of all scheduled processes on the:
• Data Change Activities tab of the Data Catalog report.
• Prism Activities Monitor report.
• Prism Activities Dashboard report.
Workday assigns a name to the schedule based on the name of the data change task and prepends
Execute Data Change Schedule: to the name. You can change the name of the schedule in the Request
Name field when you edit the schedule. Workday displays this name in the Prism Activities Monitor,
Prism Activities Dashboard, Process Monitor, and Scheduled Future Processes reports to help you
identify a specific process request.

Next Steps
From the related actions menu of the data change task, you can:
• View the schedule details.
• Edit the schedule.

• Expire the schedule.

Related Information
Reference
Reference: External Data Limits on page 332
2021R2 What's New Post: Data Change Tasks

Concept: Data Change Tasks

A data change task is a Prism Analytics object that defines how to change the data in a Prism Analytics
table using data from a specified source. You can save data change tasks and run them at any time.
Create a data change task to output the transformed data from a derived dataset into a table. Example:
You have a base dataset with data from a custom report, and you have a derived dataset that transforms
the data in the base dataset. You can create a data change task that uses data from the derived dataset
and loads it into a table.
You specify a data operation type, such as insert or delete, that instructs how to use the data in the source
to change the table rows. You can create 1 or more data change tasks per table.
You create, edit, and manage data change tasks from the Data Catalog. Access the Data Change Tasks
tab on the Data Catalog report to view all data change tasks you have permission on.
To create, view, or edit a data change task for a specific table, you must have permission to modify data in
that table. Example: To create a data change task on the Claims table using the upsert operation, you must
have permission to insert and update data in the Claims table.
You can:
• Run a data change task on a schedule, or manually on an ad hoc basis.
• Edit the data change task, such as change the operation type or field mapping, before you run it.
• Delete the data change task.
• View the data change activities to see the number of rows affected by the data change task and to
download any failed rows.
You can use data change tasks to define these components:

Component Description
Source The object that contains the data that you want to load into the target
table. Example: A delimited file that you upload, or an SFTP server,
or a Data Catalog object, such as a dataset.
Depending on the source type, you might need to define additional
source options, such as parsing options.

Target table The table with the data you want to change using the source data.
You can only create a data change task using an existing table in the
Data Catalog.

Target operation The data operation to perform on the target table using the source
data. Workday lists the operations supported for the selected source
type.
You can specify:
• Insert
• Delete
• Truncate and Insert
• Update

Component Description
• Upsert

Mapping The specifications for matching source fields to the target table fields.
You can match a source field to 1 or more target table fields.

Data Change Activities

When you run a data change task, Workday generates a data change activity. Each data change activity
modifies the data in the table, based on the operation specified in the data change task and the data in the
source.
You can view previously run data change activities on:
• The Data Change Activities tab on the Data Catalog report. The Data Change Activities tab displays
all activities for all data change tasks and tables.
• The Activities tab on the View Table Details report. The Activities tab displays all activities for that
table, both from data change activities and other data load activities. Example: You might have a
different data load activity if you created the table from a file upload.
• The Prism Activities Dashboard report in the Data Catalog. The report displays all activity for the last
180 days. You can also download error reports from the report.
Related Information
Reference
2021R2 What's New Post: Prism Analytics Data Management

Concept: Mapping Fields in Data Change Tasks

When you create or edit a data change task, you define how to map fields from the source to target table
fields. When you define the field mappings:
• You can map some or all target fields.
• Workday marks the target field specified as the delete key, update key, or upsert key as required. When
the target operation is delete, the only field you need to map is the delete key field.
• Workday displays source fields that are compatible with the target field.
Numeric fields are compatible when the digits before and after the decimal in the source field are less than
or equal to the digits in the target field. Example: You can map an Integer or Numeric (8,0) source field to a
Numeric(10,0) or Numeric(12,2) target field, but you can't map a Numeric(20,6) to a Numeric(20,5).
Instance and Multi-Instance fields are compatible when the business object for both fields are the same.
Related Information
Reference
2021R2 What's New Post: Prism Analytics Data Management

Managing Connections

Create an SFTP Connection

Prerequisites
Security: Prism: Manage Connection domain in the Prism Analytics functional area.

Context
You can create a connection to an SFTP server so that you can use it as a source in a data change task to
load external data into a table. SFTP connections:
• Can be used in 1 or more data change tasks as the source.
• Define how to connect to and authenticate against the server.
• Define the files to get from the server.
When you run a data change task that uses the SFTP connection as the source, Workday connects to the
SFTP server using the configured authentication credentials and fetches the specified files. For the data
change activity to succeed:
• The number of files must be less than 5,000.
• The time to transfer the data must be less than 5 hours.
Each file from the server should be less than 1 GB compressed (less than 10 GB uncompressed
approximately).
Use the Test Prism SFTP Connection task to verify that Workday can connect to the SFTP server and
retrieve files.

Steps
1. Access the Create Prism SFTP Connection task.
You can also select Create > Connection from the Data Catalog.
2. As you complete this task, consider:
Option Description
Name Workday displays the name in the Data Catalog. You can change
the name at any time.
Description Enter a description that describes the SFTP server and configured
file pattern.
File Name/Pattern Enter the filename or a filename pattern that represents 1 or more
files.
The filename is case-sensitive. You can use the asterisk (*) and
question mark (?) characters as wild cards to specify a filename
pattern. Use the asterisk (*) to specify zero or more characters, and
use the question mark (?) to specify exactly 1 character.

SFTP Address Use this format: sftp://domain_name or

sftp://IP_address
To specify a port number, add it to the end of the domain name or
IP address. If you don't specify a port number, Workday uses port
22.

Directory The directory on the server that contains the files. Directory names
are case-sensitive. Include a leading slash (/) only for a full path,
not a relative path.
Use Temp File Writes the imported data to a temporary file in Workday with a
randomly generated name. After the data import is complete,
Workday automatically renames the file to the correct name.
You might want to enable this option if the data import takes a very
long time and might not finish before the next scheduled time to
import data from the same server.

Option Description
Host Key Fingerprint The encryption key that the SFTP server will use for SSH
communications.
Authentication Method and Select the type of security authentication that the SFTP server
Details uses:
• User Name / Password.
• SSH Authentication. This option uses secure shell key
authentication using X.509 certificates.

Delete After Retrieval Deletes the files on the SFTP server after the data is loaded into
the target table. If Workday is unable to delete the files from the
SFTP server, the data retrieval fails.
Decompress Don't enable this option for data change tasks and tables.
You can transfer files that are compressed or not. For compressed
files, Workday only supports gzip compression.

Decrypt Using If you want to decrypt the imported files using Pretty Good Privacy
(PGP), select a PGP Private Key Pair.
Restricted To Select the environment in which you want to use the settings
defined in the Transport section.
If you leave this option empty, Workday applies the transport
settings to each environment in which the data change activity
runs. When a data change activity runs in a particular environment,
such as Implementation or Production, the transport settings only
work if the Restricted To option matches the current environment.
When the current environment and the configured environment
don’t match, the data change activity fails and retrieves no files
from the SFTP server. You might want to restrict the transport
settings to a particular environment to avoid inadvertently
transferring test data to a non-test endpoint.
Example: You create the SFTP connection and a data change task
in an Implementation environment and select Implementation in
Restricted To. Later, you migrate this SFTP connection and data
change task to a Production environment. The next time the data
change activity runs, it fails. To ensure that the data change activity
runs successfully in the Production environment, edit the SFTP
connection and either clear the Restricted To option or change it
to Production.

Result
Workday creates the SFTP connection and displays it on the Connections tab in the Data Catalog.

Next Steps
Create a data change task using the SFTP connection as the source to load data into the table.
Related Information
Tasks
Create a Data Change Task on page 410
Reference
Reference: Naming Guidelines on page 376

2022R1 What's New Post: SFTP Sources for Data Change Tasks

Securing Data in Tables and Datasets

Set Up Table Sharing

Prerequisites
Security: Set Up: Assignable Roles domain in the Organization and Roles functional area.

Context
To enable sharing a table with another user or security group, you create tenant-specific roles that
correspond to the table-related Workday provided roles. Sharing tables is a way to control access to
individual tables.

Steps
1. Access the Maintain Assignable Roles task.
2. Set up roles for the table-related Workday-provided roles.
When you set up these tenant-specific roles, consider:
• The name you enter in Role Name becomes the prompt value in the Permission column on the
Edit Table Sharing task.
• The security groups you select in Role Assignees Restricted To determine which users and
groups you can share a table with.
• The security groups you select in Assigned by Security Groups determine which users can share
a table.
Add the roles in the table below, but substitute security groups that your organization needs instead of
Prism Data Writer and Prism Data Administrator:

Role Name Workday Role Enabled for Self-Assign Role Assigned

Assignees by Security
Restricted to Groups
Table Owner - 01. Table Prism Tables Yes Prism Data Prism Data
Prism Owner - Prism Writer Administrator
Prism Table
Owner
(Workday
Owned)
Security
Administrator

Table Editor - 02. Table Prism Tables Prism Data Prism Data
Prism Editor - Prism Writer Administrator
Prism Table
Owner
(Workday
Owned)
Security
Administrator

Role Name Workday Role Enabled for Self-Assign Role Assigned

Assignees by Security
Restricted to Groups
Table Schema 03. Table Prism Tables Prism Data Prism Data
Editor - Prism Schema Editor Writer Administrator
- Prism
Prism Table
Owner
(Workday
Owned)
Security
Administrator

Table Viewer - 04. Table Prism Tables Prism Data Prism Data
Prism Viewer - Prism Writer Administrator
Prism Table
Owner
(Workday
Owned)
Security
Administrator

Table Schema 05. Table Prism Tables Prism Data Prism Data
Viewer - Prism Schema Writer Administrator
Viewer - Prism
Prism Table
Owner
(Workday
Owned)
Security
Administrator

Can Truncate 06. Can Prism Tables Prism Data Prism Data
Table Data - Truncate Table Writer Administrator
Prism Data - Prism
Prism Table
Owner
(Workday
Owned)
Security
Administrator

Can Delete 07. Can Delete Prism Tables Prism Data Prism Data
Table Data - Table Data - Writer Administrator
Prism Prism
Prism Table
Owner
(Workday
Owned)
Security
Administrator

Role Name Workday Role Enabled for Self-Assign Role Assigned

Assignees by Security
Restricted to Groups
Can Update 08. Can Prism Tables Prism Data Prism Data
Table Data - Update Table Writer Administrator
Prism Data - Prism
Prism Table
Owner
(Workday
Owned)
Security
Administrator

Can Insert 09. Can Insert Prism Tables Prism Data Prism Data
Table Data - Table Data - Writer Administrator
Prism Prism
Prism Table
Owner
(Workday
Owned)
Security
Administrator

Can Select 10. Can Select Prism Tables Prism Data Prism Data
Table Data - Table Data - Writer Administrator
Prism Prism
Prism Table
Owner
(Workday
Owned)
Security
Administrator

Note: You can substitute any user-based security groups your organization has created for Prism-
related tasks instead of selecting Prism Data Writer or Prism Data Administrator.
Related Information
Concepts
Concept: Sharing Tables and Datasets on page 430
Tasks
Share a Table with Others on page 423

Set Up Dataset Sharing

Prerequisites
Security: Set Up: Assignable Roles domain in the Organization and Roles functional area.

Context
To enable sharing a dataset with another user or security group, you create tenant-specific roles that
correspond to the dataset-related Workday provided roles. Sharing datasets is a way to control access to
individual datasets.

Steps
1. Access the Maintain Assignable Roles task.
2. Set up roles for these Workday-provided roles: Prism Dataset Owner, Prism Dataset Editor, and Prism
Dataset Viewer.
When you set up these tenant-specific roles, consider:
• The name you enter in Role Name becomes the prompt value in the Permission column on the
Edit Dataset Sharing task.
• The security groups you select in Role Assignees Restricted To determine which users and
groups you can share a dataset with.
• The security groups you select in Assigned by Security Groups determine which users can share
a dataset.
Add the roles in the table below, but substitute security groups that your organization needs instead of
Prism Data Writer and Prism Data Administrator:

Role Name Workday Role Enabled for Self-Assign Role Assigned

Assignees by Security
Restricted to Groups
Dataset Owner Prism Dataset Prism Dataset Yes Prism Data Prism Data
Owner Writer Administrator
Prism Dataset
Owner
(Workday
Owned)
Security
Administrator

Dataset Editor Prism Dataset Prism Dataset Prism Data Prism Data
Editor Writer Administrator
Prism Dataset
Owner
(Workday
Owned)
Security
Administrator

Dataset Viewer Prism Dataset Prism Dataset Prism Data Prism Data
Viewer Writer Administrator
Prism Dataset
Owner
(Workday
Owned)
Security
Administrator

Tasks
Share a Dataset with Others on page 423

Share a Table with Others

Prerequisites
Any of these security requirements:
• Prism: Tables Owner Manage domain in the Prism Analytics functional area.
• Table Owner permission on the table.

Context
When you create a table, you're the table owner. Being the owner of a table means you have Table Owner
permission on the table. As a table owner, you can share it with other users and security groups. The table
sharing feature is a way to control access to individual tables.
You might want to share a table with someone else so they can edit it, or import it into a derived dataset.
Table permissions control either:
• Metadata. Example: Table Schema Editor, Table Schema Viewer.
• Data. Example: Can Delete Table Data, Can Truncate Table Data, Can Select Table Data, Can Insert
Table Data.
• Metadata and Data. Example: Table Owner, Table Editor, Table Viewer.

Steps
1. Access the View Table Details report.
2. Select Actions > Security > Edit Table Sharing.
3. Assign a user or security group to the desired Permission.
Note: When you grant someone one of the data permissions, that user must have access to view the
table schema. Example: If you want to grant Can Insert Table Data permission, you must also grant
either Table Schema Viewer or Table Viewer permission.
4. (Optional) Share the table with more users, or remove access from users listed in the table.
5. When you're done sharing the table with others, click OK.
Related Information
Concepts
Concept: Sharing Tables and Datasets on page 430
Concept: Relax Sharing Options on page 430
Concept: Sharing Datasets Using Relax Sharing Rules on page 432
Tasks
Set Up Table Sharing on page 419

Share a Dataset with Others

Prerequisites
Any of these security requirements:
• Prism Datasets: Owner Manage domain in the Prism Analytics functional area.
• Dataset Owner permission on the dataset.

Context
When you create a dataset, you're the dataset owner. Being the owner of a dataset means you have
Dataset Owner permission on the dataset. As a dataset owner, you can share it with other users and
security groups. The dataset sharing feature is a way to control access to individual datasets.
To share a derived dataset, you need owner permission on the current dataset and either:
• Relax Sharing Rules enabled and functional on the current dataset, or
• At least viewer permission on all upstream objects up until you reach the base datasets and tables, or
until you reach a dataset with Relax Sharing Rules enabled and functional.
You might want to share a dataset with someone else so they can edit it, or import it into another (derived)
dataset.
Note: If you want to share a derived dataset with someone, they must also have at least viewer
permission on all upstream objects up until you reach the base datasets and tables, or until you reach a
dataset with Relax Sharing Rules enabled and functional.

Steps
1. Access the View Dataset Details report.
2. Select Actions > Security > Edit Dataset Sharing.
3. Add a new row to the table, and select the Permission to assign to a user or security group.
You can configure these permissions:
Option Description
Dataset Viewer Users with this permission can:
• View this dataset.
• Import this dataset into a derived dataset.

Dataset Editor User with this permission can do all tasks of a

dataset viewer plus:
• Make changes to (edit) this dataset.

Dataset Owner User with this permission can do all tasks of a

dataset editor plus:
• Delete this dataset.
• Share this dataset.

4. (Optional) Share the dataset with more users, or remove access from users listed in the table.
5. When you're done sharing the dataset with others, click OK.
Related Information
Concepts
Concept: Security in Prism Analytics on page 427
Concept: Relax Sharing Options on page 430
Concept: Sharing Datasets Using Relax Sharing Rules on page 432

Edit Prism Data Source Security

Prerequisites
• Security: Prism: Manage Data Source domain in the Prism Analytics functional area.

Context
Before you make Prism data in a table or dataset available for analysis, configure the security (security
domains and securing entities) that Workday applies to the data in the Prism data source. You configure
the data source security by editing the table or dataset, but Workday applies the security to the data in the
Prism data source.
The configured securing entities work with the configured security domains and their security groups to
determine which users have access to which rows, fields, and field values in a Prism data source.
A securing entity is an Instance or Multi-Instance field that you use to constrain access to particular
instance values for reporting and analytics. A securing entity:
• Is typically a role-enabled Instance field, such as Cost Center or Supervisory Organization.
• Is the Person Instance field (secured to the Person Data: Person Reports domain) for self-service
security groups.
• Determines which instance values Workday displays to a user based on the role assigned to the user.
Use securing entities to control row-level and field value-level access in a Prism data source for users in
constrained security groups.
For a user to have access to a particular row or field value in a Prism data source, they must be a member
of 1 of these security groups:
• An unconstrained security group that has permissions on a domain configured in the data source
security.
• A constrained security group that has permissions on a domain configured in the data source security,
and the corresponding securing entity is configured.
Workday restricts user access to data in a Prism data source for these security groups:
• All unconstrained
• Role-based constrained
• Aggregation when role-based
• Intersection when role-based
Workday has tested and supports using securing entity fields that use these business objects:
• Company
• Company Hierarchy
• Cost Center
• Cost Center Hierarchy
• Person
• Location Hierarchy
• Region
• Region Hierarchy
• Supervisory Organization

Steps
1. Access the Edit Data Source Security task for the table or dataset you want to apply security to.
2. In the Domains prompt, select 1 or more security domains to use to determine who can see the Prism
data source.
If you specify a security domain that has a constrained security group, then you must specify an
appropriate securing entity.

3. (Optional) In the Securing Entities prompt, select 1 or more fields in the dataset. Workday lists the
Instance or Multi-Instance fields in the table or dataset that act as securing entities.
The securing entities work with the:
• Data Source Security domains to determine row-level access for a user.
• Field Level Security domains to determine field value-level access for a user.
Note: Workday uses any in common logic when evaluating the contextual security using a Multi-
Instance field.
Note: When you specify more than 1 securing entity that relates to the same security group, Workday
uses the OR condition between them. Depending on how your security groups are set up, a user might
see some additional rows or field values. Make sure you test the report results to ensure that the report
produces expected results for each user.
4. In the Default Domain(s) for Dataset Fields prompt, select 1 or more security domains that Workday
applies to every field in the Prism data source unless you override the domain for a particular field in the
next section.
Note: When you add new fields to the table or dataset, Workday applies this default domain to the
new fields. You might want to consider specifying a domain with more restrictive access. Then you can
override the default domain on a per field basis to allow more access as necessary.
5. (Optional) You can select different domains to apply to specific fields to override the default domains.
6. Review any Security Configuration Audit messages to learn more about any issues with the
configured securing entities and domains.
7. (Optional) Click Back to make any changes to the configured security options based on the audit
messages.
8. Select the Apply Security check box to apply your changes.
If you want to restrict access to rows using any of these security group types, Workday can't honor
those restrictions:
• Segment-based security groups
• Job-based security groups
• Manager's Manager security group

Result
Workday saves the security information. You can view the current security status by selecting Actions >
Security > View Data Source Security.

Example
Suppose that you select these domains containing these security groups. To enforce contextual security at
the row-level and field value-level, then use these fields as securing entities:

Security Domain Contains This Security Use This Securing Entity

Group
Custom Domain 28 HR Partner (By Location) Location
Custom Domain 29 Manager Supervisory Organization
Custom Domain 30 HR Administrator None required.
HR Administrator is an unconstrained
security group, so it doesn't require a
securing entity.

Public Reporting Items None. None required.

Security Domain Contains This Security Use This Securing Entity

Group
This domain provides access to all publicly
available fields and Workday-delivered data
sources.

Next Steps
Create the Prism data source by enabling the table for analysis or publishing the dataset. Workday applies
the security restrictions to the data in the Prism data source.

Concept: Security in Prism Analytics

Prism Analytics uses Workday's strong, flexible, and configurable security model to control access to data,
objects, and tasks. Which users have access to what data depends on where in the Prism data workflow
they are. For more information on the workflow, see Concept: Prism Analytics Data Management Workflow
on page 327.

Phase 1 and Phase 2: Create and Edit Tables, Datasets, and Data Change Tasks
In the first and second phases in the data management workflow, you bring data into the Prism Analytics
Data Catalog and then transform it. You create and edit these objects in the Data Catalog:
• Tables. Tables include metadata and all data rows in the table.
• Derived datasets. Datasets include metadata and a subset of data as a small collection of example
rows.
• Data change tasks. Data change tasks include a small collection of example rows from the target table,
and from the source if it's another dataset or table.
When it comes to security with tables, data change tasks, and datasets, you control access to the
metadata and data together.
Table and Dataset Security
Workday controls who can do what with tables and datasets in these ways:

Method Notes
Security administrator Your Workday security administrator can configure Workday security domains
grants access to grant groups of users to be able to create, edit, or manage tables and
datasets. Depending on how the administrator configures the security
domains, some users might be able to create, view, edit, or act as an owner
of all tables and datasets. Your Workday security administrator can configure
these Workday security domains to grant access to groups of users:
• Prism Datasets: Create
• Prism Datasets: Manage
• Prism Datasets: Owner Manage
• Prism: Manage Data Source
• Prism: Tables Create
• Prism: Tables Manage
• Prism: Tables Owner Manage

Table sharing and The user who created a table or dataset can share it with particular users and
dataset sharing grant different levels of access to each user.
When you create a table or dataset, you're the table owner or dataset owner.
Being the owner means that you have Table Owner or Dataset Owner
permission on the table or dataset. As an owner, you can grant different levels

Method Notes
of access by assigning permissions to another user. Example: You can assign
Table Viewer or Can Truncate Table Data permission to a table, or Dataset
Editor permission to a dataset.

Access to a table or dataset is unconstrained. This means that any user who can create or view a table or
dataset can view all fields and data (example data for datasets and data change tasks), regardless of the
origin of the data. When you create a table or base dataset from a Workday report, Workday removes all
security domains configured for the business objects in the table or dataset.
This unconstrained access only applies when you use these tasks and reports:
• View Table Details
• Edit Table
• View Dataset Details
• Edit Dataset Transformations
• View Dataset Transformations
• Create Data Change Task
• Edit Data Change Task
It doesn't apply to the data in a Prism data source.
Instead, you define the data source security to apply to the data in the Prism data source before making
the data available for analysis.
Data Change Task Security
You can't configure access on a data change task directly. Instead, Workday controls your access to a
data change task based on:
• Your target table permissions. Workday uses these table permission types:
• Table Viewer
• Table Editor
• Table Owner
• Can Delete Table Data
• Can Insert Table Data
• Can Update Table Data
• The specified operation type. You need permission to change data in the table that is compatible with
the specified operation type. Example: To create or edit a data change task on the Claims table using
the upsert operation, you must have permission to insert and update data in the Claims table.
• Your source access. You need permission to view the source, such as view permission on a custom
report, source dataset, or SFTP connection. You don't need view permission on the source when the
type is file upload.
Workday doesn't enable users to have view permission only on a data change task. If you have permission
to edit a data change task, then you have permission to view it.
If you meet the source access requirement, then you can perform the actions below with the specified
target table permissions:

Table Viewer Only Table Viewer and Can Table Editor or Table
Delete/Insert/Update Owner
Table Data
View a data change No Yes Yes
task.

Table Viewer Only Table Viewer and Can Table Editor or Table
Delete/Insert/Update Owner
Table Data
Create a data change No Yes, but you can only Yes
task. select an operation type
that is compatible with
your table permissions.
Edit the data change No Yes, but you can only Yes
task operation type. select an operation type
that is compatible with
your table permissions.
Edit the data change No Yes, but you need Yes, but you need
task source. permission on the new permission on the new
source. source.
Edit other data change No Yes Yes
task properties (not the
source or operation).

Phase 3: Apply Security to the Data

You define the security that Workday will apply to the Prism data source before you make the data in the
Data Catalog available for analysis. By applying security to the Prism data source, you can ensure that
both Workday and non-Workday data have the proper restrictions applied when viewed in a discovery
board or report.
You configure the data source security by editing the table or dataset, but Workday applies the security to
the data in the Prism data source.
Define the data source security after the data is ready to be exposed to other users by giving them access
to the Prism data source.
To configure the data source security, you must access to the Prism: Manage Data Source security
domain. For details, see Edit Prism Data Source Security on page 424.
You can restrict access to the data in a Prism data source at these levels:
• Data source-level. Specify 1 or more security domains that apply to the Prism data source that
Workday creates. These domains determine which users can see the Prism data source. This is
sometimes known as table-level security. If you don't configure any domain, Workday uses the Prism:
Default to Dataset Access domain.
• Row-level. Optionally, you can enforce row-level security by specifying in the Securing Entities
prompt 1 or more Instance or Multi-Instance fields in the table or dataset, such as Supervisory
Organization. The securing entities work with the configured data source-level security domains to
determine which users have access to which rows (and field values) in a Prism data source.
• Field-level. Specify 1 or more security domains to apply to the fields in the Prism data source. These
domains determine which users can see each field in the Prism data source.
• Field value-level. Workday uses any configured Securing Entities with the configured field-level
security domains to determine which users have access to which field values in a Prism data source.

Phase 4: Make the Data Available for Analysis

When you make Prism data available for analysis, Workday creates the Prism data source, loads it with the
transformed data, and applies the appropriate security restrictions to the data.
The way you create a Prism data source and the security required depend on the Data Catalog object. For
more information, see Concept: Making Prism Data Available for Analysis on page 444.

Optionally, you can create a Prism data source without any data source security configured. When no data
source security is configured, Workday applies the Prism: Default to Dataset Access security domain to the
Prism data source. The Prism: Default to Dataset Access domain provides contextual access to a Prism
data source based on your access to the underlying table or dataset.

Phase 5: Analyze and Visualize the Data

Workday controls access to data in a Prism data source according to the configured data source security.
The configured data source security determines who can see the Prism data source, and which rows,
fields, and field values each user can see when they query the Prism data source in a discovery board or
report.
Related Information
Tasks
Share a Dataset with Others on page 423
Edit Prism Data Source Security on page 424

Concept: Sharing Tables and Datasets

Workday enables you to have fine-grained control over what you can do with tables and datasets. Sharing
tables and datasets is a way to control access to individual tables and datasets.
When your tenant is set up for table and dataset sharing, table owners and dataset owners can share a
table or dataset with another user or security group. Example: You can control who can view a dataset, edit
the schema of a table, insert data into a table, or delete table data.

How Inherited Permissions Work to Enable Table and Dataset Sharing

Workday provides sharing permission control using Workday roles, Workday-owned security groups, and
inherited permissions.
Most Workday roles are tied to an organization. However, table-related and dataset-related Workday roles
are tied to an object type, the table or dataset. By tying a role to an object type, Workday enables you to
control which permissions a user inherits for a particular table or dataset.
Workday maps each table-related and dataset-related role to a Workday owned security group, and that
security group automatically inherits permissions from 1 or more security domains.
Example: Workday maps the Workday role "Table Schema Editor" to the "Prism Table Schema Editor
(Workday Owned)" security group, and that security group inherits View and Modify permissions on the
Prism: Tables Manage Schema domain.
Example: Workday maps the Workday role "Prism Dataset Editor" to the "Prism Dataset Editor (Workday
Owned)" security group, and that security group inherits View and Modify permissions on the Prism:
Datasets Manage domain.
As a result of these connections, you can enable table and dataset sharing by creating a tenant-specific
role and mapping it to a table-related or dataset-related Workday role. The tenant-specific role becomes
the table or dataset permission that you can share with others.
Related Information
Tasks
Share a Table with Others on page 423
Share a Dataset with Others on page 423

Concept: Relax Sharing Options

By default, to access the current dataset, you must have access to all upstream datasets and tables.
Example: To share a derived dataset, you must have owner permission on the derived dataset and at least
viewer permission on all upstream datasets and tables.

However, you can relax some permission requirements so that users require access on fewer upstream
datasets and tables to have access to the current dataset.
To relax the sharing restrictions with tables and datasets, Workday provides these options when you edit
dataset sharing and table sharing:

Option Name Description

Relax Sharing Rules When you enable Relax Sharing Rules on a table
or dataset:
• Owners of datasets derived from this table or
dataset only need a viewer role on this table or
dataset to share their derived dataset.
• (Derived datasets only) Owners of this dataset
can share it with other users without requiring
those users to have a role on any upstream
datasets or tables.
You can protect sensitive data in upstream datasets
and tables by eliminating the need for access by
using Relax Sharing Rules in downstream datasets.

Prevent Relax Sharing on Derived Datasets When you enable Prevent Relax Sharing on
Derived Datasets, Workday revokes the Relax
Sharing Rules functionality on all downstream
derived datasets.
You might want to enable Prevent Relax Sharing
on Derived Datasets to prevent others from sharing
derived datasets they own without requiring your
permission on this table or dataset.
Note: The Relax Sharing Rules option is only
functional when no dataset or table upstream from
it has Prevent Relax Sharing Rules on Downstream
Datasets enabled.

To configure these options, you must have access to the Prism: Manage Relax Sharing domain in the
Prism Analytics functional area.
Example: You create a table called Payrolls that contains sensitive data, and you create a derived dataset
off of it called Filtered Payrolls that filters out the sensitive data. You want Norman Chan to view the
Filtered Payrolls dataset, but not the Payrolls table. To accomplish this sharing scenario, you enable
Relax Sharing Rules on Filtered Payrolls, and then assign Norman Chan viewer permission on it. Now,
Norman can view Filtered Payrolls and create a derived dataset from it even though he doesn’t have
viewer permission on the Payrolls table. Also, he can share the derived dataset he created without having
owner permission on Filtered Payrolls or Payrolls.

To do this... You must have...

• View the current dataset details or table. At least viewer permission on the current dataset or
• Import the current dataset or table into a derived table, and either:
dataset. • Relax Sharing Rules enabled and functional on
the current dataset or table, or
• At least viewer permission on all upstream
objects up until you reach the base datasets and

To do this... You must have...

tables, or until you reach a dataset with Relax
Sharing Rules enabled and functional.

• View the current dataset transformations. At least viewer permission on the current dataset,
• Copy the current dataset (derived datasets and either:
only). • Relax Sharing Rules enabled and functional on
the current dataset or table and at least viewer
permission on each dataset or table that is
imported into the current dataset, or
• At least viewer permission on all upstream
objects up until you reach the base datasets and
tables, or until you reach a dataset with Relax
Sharing Rules enabled and functional.

Edit the current dataset or table. At least editor permission on the current dataset or
table, and either:
• Relax Sharing Rules enabled and functional on
the current dataset or table and at least viewer
permission on each dataset or table that is
imported into the current dataset, or
• At least viewer permission on all upstream
objects up until you reach the base datasets and
tables, or until you reach a dataset with Relax
Sharing Rules enabled and functional.

Share the current dataset or table (the action that is Owner permission on the current dataset or table,
specific to owners). and either:
• Relax Sharing Rules enabled and functional on
the current dataset or table, or
• At least viewer permission on all upstream
objects up until you reach the base datasets and
tables, or until you reach a dataset with Relax
Sharing Rules enabled and functional.

View the lineage of the current table or dataset. At least viewer permission on the current dataset or
table.
Note that when you view lineage, you only see the
upstream or downstream tables and dataset on
which you have viewer permission (or better).

Related Information
Tasks
Share a Table with Others on page 423
Share a Dataset with Others on page 423

Concept: Sharing Datasets Using Relax Sharing Rules

The relax sharing options work with table and dataset sharing permissions to determine which users can
access a table or dataset. The kind of access users have determines their ability to:
• View the table or dataset.
• Make a copy of the table or dataset.
• Import the table or dataset into a derived dataset.

• Edit the table or dataset.

• Share the table or dataset with other users.

Scenario 1
In the first scenario, Beth Liu made multiple tables and datasets, and shared some of them with Norman
Chan and Dawn Myers.
The Data Catalog includes these tables and datasets:

Table or Dataset Owners Viewers Relax Sharing Prevent Relax

Rules Enabled Sharing on
Derived Datasets
Enabled
Payrolls (table) bliu nchan No No
Filtered Payrolls bliu, nchan dmyers No No
Stock Grants bliu None No No
(table)
Filtered Stock bliu, nchan dmyers No No
Grants
Employee Grants bliu nchan, dmyers No No

The dataset lineage for the Employee Grants dataset looks like this:

Beth Liu, Norman Chan, and Dawn Myers have this table and dataset access:

Table or Dataset Beth Liu Norman Chan Dawn Myers

Payrolls Can share, edit, and Can view No access
view
Filtered Payrolls Can share, edit, and Can edit, can view No access
view

Table or Dataset Beth Liu Norman Chan Dawn Myers

Stock Grants Can share, edit, and No access No access
view
Filtered Stock Grants Can share, edit, and No access No access
view
Employee Grants Can share, edit, and No access No access
view

Although Norman Chan is an owner of Filtered Payrolls, he can't share it with others because he only has
View permission on the upstream dataset Payrolls.

Scenario 2
This scenario is based on the previous scenario. Beth Liu enabled the Relax Sharing Rules check box on
the Filtered Payrolls and Filtered Stock Grants datasets.
The Data Catalog includes these tables and datasets:

Table or Dataset Owners Viewers Relax Sharing Prevent Relax

Rules Enabled Sharing on
Derived Datasets
Enabled
Payrolls bliu nchan No No
Filtered Payrolls bliu, nchan dmyers Yes No
Stock Grants bliu None No No
Filtered Stock bliu, nchan dmyers Yes No
Grants
Employee Grants bliu nchan, dmyers No No

The dataset lineage for the Employee Grants dataset looks like this. The green check marks indicate that
Relax Sharing Rules is enabled.

Beth Liu, Norman Chan, and Dawn Myers have this table and dataset access:

Table or Dataset Beth Liu Norman Chan Dawn Myers

Payrolls Can share, edit, and Can view No access
view
Filtered Payrolls Can share, edit, and Can share, edit, and Can view
view view
Stock Grants Can share, edit, and No access No access
view
Filtered Stock Grants Can share, edit, and Can share and view Can view
view
Employee Grants Can share, edit, and Can view Can view
view

With Relax Sharing Rules enabled on Filtered Payrolls and Filtered Stock Grants:
• Norman can share Filtered Payrolls because he no longer needs owner permission on the upstream
object Payrolls.
• Norman can share Filtered Stock Grants because he no longer needs owner permission on the
upstream object Stock Grants, but he can't edit Filtered Stock Grants because he doesn't have viewer
permission on the upstream object Stock Grants.
• Norman can view Employee Grants because he no longer needs viewer permission on all upstream
objects.
• Dawn can view Filtered Payrolls, Filtered Stock Grants, and Employee Grants because she no longer
needs viewer permission on all upstream objects.

Scenario 3
This scenario is based on the previous scenario. Norman Chan created a derived dataset titled DDS
Norman by importing the Employee Grants dataset.
The Data Catalog includes these tables and datasets:

Table or Dataset Owners Viewers Relax Sharing Prevent Relax

The dataset lineage for the DDS Norman dataset (as viewed by a Prism Data Administrator who can view
all objects) looks like this:

Beth Liu, Norman Chan, and Dawn Myers have this table and dataset access:

Table or Dataset Beth Liu Norman Chan Dawn Myers

Norman Chan didn't share DDS Norman with Beth Liu, so Beth doesn't see it in her Data Catalog and she
doesn't know that it exists.

Although Norman created DDS Norman (he's the owner), he isn't able to share it with other users because
he only has Viewer permission on Employee Grants, not Owner permission. To share a dataset, you must
have Owner permission on all upstream objects up until you reach a dataset or table with Relax Sharing
Rules enabled and functional. On the dataset or table with Relax Sharing enabled, you only need Viewer
permission.

Scenario 4
This scenario is based on the previous scenario. Beth Liu enabled the Relax Sharing Rules check box on
the Employee Grants dataset.

Table or Dataset Owners Viewers Relax Sharing Prevent Relax

The dataset lineage for the DDS Norman dataset (as viewed by a Prism Data Administrator who can view
all objects) looks like this:

Beth Liu, Norman Chan, and Dawn Myers have this table and dataset access:

Table or Dataset Beth Liu Norman Chan Dawn Myers

Payrolls Can share, edit, and Can view No access
view
Filtered Payrolls Can share, edit, and Can share, edit, and Can view
view view

Table or Dataset Beth Liu Norman Chan Dawn Myers

Stock Grants Can share, edit, and No access No access
view
Filtered Stock Grants Can share, edit, and Can share and view Can view
view
Employee Grants Can share, edit, and Can view Can view
view
DDS Norman No access Can share, edit, view No access

With Relax Sharing Rules enabled on Employee Grants (Norman has Viewer permission on Employee
Grants), Norman can share DDS Norman with others.

Scenario 5
This scenario is based on the previous scenario. Norman Chan enabled the Relax Sharing Rules check
box on DDS Norman, and shared DDS Norman with Dawn Myers, giving her Owner permission.

Table or Dataset Owners Viewers Relax Sharing Prevent Relax

The dataset lineage for the DDS Norman dataset (as viewed by a Prism Data Administrator who can view
all objects) looks like this:

Beth Liu, Norman Chan, and Dawn Myers have this table and dataset access:

Table or Dataset Beth Liu Norman Chan Dawn Myers

With Relax Sharing Rules enabled on DDS Norman while giving Dawn Myers Owner permission, Dawn
can share, edit, and view DDS Norman. Beth Liu is unaware that DDS Norman exists and that Dawn can
share it with others.

Scenario 6
This scenario is based on the previous scenario. Beth Liu enabled the Prevent Relax Sharing on Derived
Datasets check box on Filtered Stock Grants.

Table or Dataset Owners Viewers Relax Sharing Prevent Relax

The dataset lineage for the DDS Norman dataset (as viewed by a Prism Data Administrator who can view
all objects) looks like this. The red circle with the line through it indicates the dataset that has Prevent
Relax Sharing on Derived Datasets enabled:

Beth Liu, Norman Chan, and Dawn Myers have this table and dataset access:

Table or Dataset Beth Liu Norman Chan Dawn Myers

Now that Prevent Relax Sharing on Derived Datasets is enabled on Filtered Stock Grants:
• Norman Chan can't share DDS Norman.
• Dawn Myers can't share DDS Norman.
Because Prevent Relax Sharing on Derived Datasets is enabled on Filtered Stock Grants, it cancels out
the effect of Relax Sharing Rules being enabled on both Employee Grants and DDS Norman.
Related Information
Tasks
Share a Table with Others on page 423
Share a Dataset with Others on page 423

Preparing Data for Analysis

Enable Contextual Publishing for Datasets

Prerequisites
Security: These domains in the System functional area:

• Security Activation
• Security Configuration

Context
When you create and edit datasets, you typically need to build reports and visualizations to test the data
you’re transforming in the dataset. To test your work, you must publish your dataset, which requires access
to the Prism Datasets: Publish domain.
You can set up your tenant to restrict users to publish datasets based on their contextual access to
the dataset. Contextual publishing enables dataset users to publish a dataset based on their dataset
permission, such as Dataset Owner or Dataset Editor.
You might want to enable contextual publishing to enable dataset users to test their work without giving
them unconstrained access to publish all datasets.
To enable contextual publishing, you must have already enabled dataset sharing by creating assignable
roles that correspond to dataset-related Workday roles.

Steps
1. Create a role-based (constrained) security group.
Select 1 of these roles for the Assignable Role:
• Dataset Owner
• Dataset Editor
Select Role has access to the positions they support for the Access Rights to Multiple Job
Workers option.
You can create a role-based (constrained) security group to enable users to publish datasets they have
Dataset Owner permission on. Example:

Security Group Property Example

Name Dataset Owner (role-based)
Assignable Role Dataset Owner
Access Rights to Organizations Applies To Current Organization And Unassigned
Subordinates
Access Rights to Multiple Job Workers Role has access to the positions they support
2. Edit the domain security policy for the Prism Datasets: Publish domain in the Prism Analytics functional
area.
Add the role-based (constrained) security group you created, and assign both View and Modify task
permissions.
3. Activate pending security policy changes.

Publish a Dataset as a Prism Data Source Manually

Prerequisites
• Security: Prism Datasets: Publish domain in the Prism Analytics functional area.

Context
This section describes how to publish a dataset immediately on an ad hoc basis.

Steps
1. Access the View Dataset Details report for the dataset you want to publish.
2. Click Publish, or from the related actions menu, select Publishing > Publish Dataset.
Workday:
• Reads the source data in the dataset.
• Transforms the source data using the transformation logic defined in the dataset.
• Creates a Prism data source and loads it with the transformed data. The Prism data source has the
same name as the dataset API name.
• Applies the appropriate security restrictions to the data.
3. View the publishing process status from the Publishing Activities tab on the View Dataset Details
report.
Refresh the browser to see the most current status. The status includes the date and time that Workday
last published the dataset successfully. The last successful published date informs you about the
freshness of the data in the Prism data source. Example: If the last successful publish date is 1 week
ago, but your publishing schedule is set to publish daily, this discrepancy could indicate a failure in the
publishing process.
You can also view the status of manually run publish requests in the Prism Activities Dashboard
report or the Process Monitor report.
4. (Optional) You can cancel the publishing process by clicking Cancel Publishing on the View Dataset
Details report.

Result
You can view the Prism data source by accessing the View Prism Data Source report, and selecting the
name of the dataset you published.
Related Information
Tasks
Unpublish a Dataset on page 452
Reference
The Next Level: Prism Analytics Data Acquisition Best Practices
The Next Level: Prism Performance and Troubleshooting Tips

Create Dataset Publish Schedules

Prerequisites
Security: Prism Datasets: Publish domain in the Prism Analytics functional area.

Context
You can create a publish schedule for a dataset. You can schedule the publish to run:
• On a recurring basis (Example: daily, weekly, or monthly).
• Only if another Prism scheduled process completes at a status you specify.
You can't publish the same dataset at times that overlap with each other.

Steps
1. Access the View Dataset Details report for the dataset you want to publish.
2. From the related actions menu, select Publishing > Create Schedule.
3. In Run Frequency, specify how often to publish the dataset. The choices include creating a dependent
publish schedule.

4. Select the criteria for the schedule.

5. (Recurring schedules) As you configure the schedule, consider:
Option Description
Priority Unavailable for publish schedules.
Catch Up Behavior Select how many times the scheduled publish
runs after maintenance issues cause errors.
Example: If you schedule a publish to run multiple
times in a week when your environment is down
for maintenance, you can limit the process
to run once instead of catching up all missed
occurrences.

6. (Dependent schedules) As you configure the schedule, consider:

Option Description
Dependency Select a Prism-related schedule on which the
publish schedule depends.
Trigger on Status Select the status of the scheduled future process
that triggers publishing the dataset.
Workday recommends using one of the
completed statuses.
Example: You select Publish Dataset as your
process type and a future publish schedule called
All Currencies. In the Trigger on Status field,
you select Completed.
Workday publishes the dataset only after the
scheduled All Currencies publish successfully
completes.

Time Delayed Configuration (Optional) Specify the number of days, hours,

or minutes to delay publishing the dataset after
the trigger. You might want to delay publishing to
review the latest source files.
7. (Optional) Change the name of your publish schedule.
Workday assigns a name to the schedule based on the name of the dataset and prepends Publish
Schedule: to the name. You can change the name of the schedule in the Request Name field when
you edit the schedule. Workday displays this name in the Process Monitor and Scheduled Future
Processes reports to help you identify a specific process request.

Result
Workday publishes a dataset based on the criteria that you specify. When publishing, Workday:
• Reads the source data in the dataset.
• Transforms the source data using the transformation logic defined in the dataset.
• Creates a Prism data source if it doesn't already exist and loads it with the transformed data. The Prism
data source has the same name as the dataset API name.
• Applies the appropriate security restrictions to the data.
View the status of all scheduled publishing processes on:
• The Dataset Activities tab of the Data Catalog report.

• The Prism Activities Dashboard report from the Data Catalog report.
• The Prism Activities Monitor report.
Refresh the browser to see the most current status. The status includes the date and time (UTC) that
Workday last published the dataset successfully. The last successful publish date informs you about the
freshness of the data in the Prism data source. Example: If the last successful publish date is 1 week ago,
but you set your publish schedule to publish daily, this discrepancy could indicate a failure in the publishing
process.
Related Information
Concepts
Concept: Security in Prism Analytics on page 427
Reference
FAQ: Dataset Publish Schedules on page 448
The Next Level: Prism Analytics Best Practices
Examples
Example: Create Dependent Publish Schedules for Datasets on page 447

Concept: Making Prism Data Available for Analysis

You can make Prism data in the Data Catalog available for analysis by creating a Prism data source from
either a table or dataset. When Workday creates a Prism data source, it:
• Loads the data source with the data from the table or dataset.
• Applies the appropriate security restrictions to the data source, fields, records, and field values.
The way you create a Prism data source depends on the Data Catalog object:

Prism Object Method Security Requirements

Table Use the Enable for Analysis option Any of these security requirements:
when you create or edit the table
• Prism Datasets: Owner Manage
schema. See Edit a Table on page
domain
384.
• Prism Datasets: Manage domain
• Table Editor permission on the table
• Table Owner permission on the table
• Table Schema Editor permission on
the table

Dataset Publish the dataset. You can create a Prism Datasets: Publish domain
publish schedule or publish a dataset
manually on an ad hoc basis. See
Create Dataset Publish Schedules on
page 442 and Publish a Dataset as a
Prism Data Source Manually on page
441.

Workday applies the security domains configured in the Edit Data Source Security task for the table or
dataset.
When you first create a table or dataset, no security domain is applied to the data source. However, you
can still create a Prism data source if you haven't specify a security domain for it. Workday applies the
Prism: Default to Dataset Access security domain if no domain has been configured. The Prism: Default to
Dataset Access domain provides contextual access to a Prism data source based on your access to the
underlying table or dataset.
Workday recommends making Prism data available analysis after you edit the data source security for the
table or dataset.

Related Information
Concepts
Concept: Prism Data Sources on page 331
Tasks
Unpublish a Dataset on page 452
Reference
The Next Level: Prism Analytics Best Practices
The Next Level: Prism Performance and Troubleshooting Tips

Concept: Dataset Publish Schedules

Schedules for publishing datasets enable you to specify when, how often, and under what criteria to
publish a dataset. Publish schedules differ from publishing immediately on an ad hoc basis using Run
Now.

Publish Schedule Types

You can create these types of schedules:

Schedule Type Description

Recurring A publish schedule that runs at specified intervals,
such as daily, weekly, or monthly.
Dependent A publish schedule that depends on the completion
of another Prism scheduled process. For your
dependency criteria, you can specify:
• The process type, such as bringing data into a
dataset.
• The status that triggers publishing, such as the
process type successfully completing.
Example: When the Prism Data Acquisition Future
Process completes with no warnings or errors,
begin publishing.
Note: A Prism Analytics publish schedule can
depend only on another Prism-related process,
such as bringing data into a dataset or publishing
another dataset.

After you create a publish schedule, consider these actions that you can perform on it:

Action Description
Activate Activate a suspended publish schedule.
Change Schedule (recurring schedules only) Edit the run frequency (daily, monthly, weekly), start
time, and date range for the publish schedule. You
can also change to another scheduled recurring
process.
Delete Permanently delete the publish schedule.
Edit Environment Restrictions Select the environment in which you want the
scheduled publish to run.

Action Description
Edit Schedule (Recurring Schedules) Edit the schedule name,
recurrence criteria, and range of recurrence dates.
Note: To change the run frequency, use Change
Schedule.
(Dependent Schedules) Edit the schedule name,
dependency, trigger status, and timed delay
configurations.

Expire Schedule Permanently stop the publish schedule. Expiring a

schedule doesn’t delete it.
Note: You can’t activate an expired schedule.

Run Now Publish the dataset immediately on an ad hoc

basis.
Suspend Suspend use of the publish schedule. You can
activate a suspended schedule.
Transfer Ownership Transfer ownership of a publish schedule. Every
process must have an assigned owner for the
process to run.
You might want to transfer ownership if the
assigned owner becomes inactive. The person you
transfer ownership to must have the appropriate
security access.

View All Occurrences (recurring schedules only) View all future occurrences of a publish schedule
within a specified range of dates and times.
View Schedule (Recurring schedules) View schedule details,
such as recurrence criteria, error messages, the
schedule owner and creator, and the next 10
scheduled launches if applicable.
(Dependent schedules) View schedule details, such
as the dependency configuration, the schedule
creator and owner, and the number of times run.

Related Information
Tasks
Create Dataset Publish Schedules on page 442
Reference
FAQ: Dataset Publish Schedules on page 448
The Next Level: Prism Analytics Best Practices
The Next Level: Prism Performance and Troubleshooting Tips

Concept: Coordinating Publish Schedules with Dataset Integration

The last integration that completes before publishing begins determines the freshness of data in a Prism
data source. To ensure that data is as fresh as possible, schedule enough time for an integration to
complete before a dataset publishing job begins.
As you create publish schedules for datasets that have scheduled integrations, consider how these
scenarios affect the freshness of data in the Prism data source:

Scenario Impact
Integration completes before a scheduled publish The published dataset will use the latest available
begins. data from the dataset source file.
Integration completes after a scheduled publish The published dataset will use the data from the
begins. dataset source file that existed before integration
began.

To help ensure that integration completes before publishing begins, you can create a publish schedule that
depends on the successful integration of the data.
Related Information
Tasks
Create Dataset Publish Schedules on page 442

Example: Create Dependent Publish Schedules for Datasets

This is an example of a publish schedule with a dependency.

Context
As an HR Analyst, you’re responsible for creating a weekly report that includes employee hiring and
turnover data from your New York office. You’d like the data in the report to be as fresh as possible. You
need to:
• Bring in the latest hiring and turnover data from your New York office every Monday morning.
• Make the data available for reporting only after you’ve brought in the latest data.

Prerequisites
• Create a dataset from SFTP integration. Schedule the integration to occur every Monday at 8 a.m.
EST. Name the dataset New York Hiring and Turnover Weekly. Run the integration once to enable the
publish option.
• Security: Prism Datasets: Publish domain in the Prism Analytics functional area.

Steps
1. Access the View Dataset Details report for the New York Hiring and Turnover Weekly dataset.
2. From the related actions menu of the View Dataset Details report, select Publishing > Create
Schedule.
3. In Run Frequency, select Dependent.
4. In Dependency, select Prism > Dataset Integration Schedule: New York Hiring and Turnover
Weekly.
5. In Trigger on Status, select Completed.

Result
Workday publishes the New York Hiring and Turnover Weekly dataset only after the successful integration
of data from the SFTP server.
The HR Analyst can:
• View the publish schedule request in the Process Monitor and Scheduled Future Processes reports.
• View the status of all scheduled publish processes on these reports:
• Dataset Activities
• Prism Activities Monitor
• Prism Activities Dashboard
Related Information
Concepts
Concept: Making Prism Data Available for Analysis on page 444
Concept: Dataset Publish Schedules on page 445
Tasks
Create Dataset Publish Schedules on page 442
Steps: Create a Dataset with External Data (SFTP Server) on page 360

FAQ: Dataset Publish Schedules

• How do I edit a publish schedule? on page 448
• How do I edit or delete only 1 occurrence of a recurring publish schedule? on page 448
• How do I change a recurring publish schedule? on page 448
• How do I edit environment restrictions for a publish schedule? on page 449
• How do I delete a publish schedule? on page 449
• How do I expire a publish schedule? on page 449
• How do I suspend a publish schedule? on page 449
• How do I activate a suspended publish schedule? on page 449
• How do I view the details of a publish schedule? on page 449
• How do I view all occurrences of a recurring publish schedule? on page 449
• How do I immediately run a publish schedule on an ad hoc basis? on page 449
• How do I transfer ownership of a publish schedule? on page 450

How do I edit a publish schedule? From the related actions menu of the View Dataset
Details report, select Publishing > Edit Schedule.

How do I edit or delete only 1 occurrence of a 1. From the related actions menu of the View
recurring publish schedule? Dataset Details report, select Publishing >
View Schedule.
2. From the related actions menu of the View
Scheduled Future Process report, select
Schedule Future Process > Edit Scheduled
Occurrence.

How do I change a recurring publish schedule? 1. From the related actions menu of the View
Dataset Details report, select Publishing >
View Schedule.
2. From the related actions menu of the View
Scheduled Future Process report, select
Schedule Future Process > Change
Schedule.

How do I edit environment restrictions for a 1. From the related actions menu of the View
publish schedule? Dataset Details report, select Publishing >
View Schedule.
2. From the related actions menu of the View
Scheduled Future Process report, select
Schedule Future Process > Edit Environment
Restrictions.

How do I delete a publish schedule? 1. From the related actions menu of the View
Dataset Details report, select Publishing >
View Schedule.
2. From the related actions menu of the View
Scheduled Future Process report, select
Schedule Future Process > Delete.

How do I expire a publish schedule? From the related actions menu of the View Dataset
Details report, select Publishing > Expire
Schedule.

How do I suspend a publish schedule? 1. From the related actions menu of the View
Dataset Details report, select Publishing >
View Schedule.
2. From the related actions menu of the View
Scheduled Future Process report, select
Schedule Future Process > Suspend.

How do I activate a suspended publish 1. From the related actions menu of the View
schedule? Dataset Details report, select Publishing >
View Schedule.
2. From the related actions menu of the View
Scheduled Future Process report, select
Schedule Future Process > Activate.
Note: You can only activate expired schedules.

How do I view the details of a publish schedule? From the related actions menu of the View
Dataset Details report, select Publishing > View
Schedule.

How do I view all occurrences of a recurring 1. From the related actions menu of the View
publish schedule? Dataset Details report, select Publishing >
View Schedule.
2. From the related actions menu of the View
Scheduled Future Process report, select
Schedule Future Process > View All
Occurrences.

How do I immediately run a publish schedule on 1. From the related actions menu of the View
an ad hoc basis? Dataset Details report, select Publishing >
View Schedule.
2. From the related actions menu of the View
Scheduled Future Process report, select
Schedule Future Process > Run Now.

How do I transfer ownership of a publish 1. From the related actions menu of the View
schedule? Dataset Details report, select Publishing >
View Schedule.
2. From the related actions menu of the View
Scheduled Future Process report, select
Schedule Future Process > Transfer
Ownership.

Related Information
Concepts
Concept: Making Prism Data Available for Analysis on page 444
Concept: Dataset Publish Schedules on page 445
Tasks
Create Dataset Publish Schedules on page 442

Deleting Prism Analytics Data

Truncate Data in a Table

Prerequisites
Any of these security requirements:
• Prism: Tables Manage domain in the Prism Analytics functional area.
• Prism: Tables Owner Manage domain in the Prism Analytics functional area.
• Table Editor permission on the table.
• Table Owner permission on the table.
• Can Truncate Table Data permission on the table.

Context
You can remove all data in a table by truncating the table. Truncating a table removes the data, but retains
the schema. You might want to truncate a table if the table contains some bad data.
If you've previously published a derived dataset based on this table, the associated Prism data source
still contains data. If you also want to remove the data from the associated Prism data source, then you
must publish the derived dataset again. Publishing a derived dataset from a truncated table makes the
associated Prism data source empty, but active.
If you selected the Enable for Analysis option for this table, then truncating the table also removes all
data from the associated Prism data source. The Prism data source is empty, but active.

Steps
1. Access the View Table Details report for the table you want to truncate.
2. Select Truncate Data from the Quick Actions menu.

Delete Rows of Data in a Table

Prerequisites
Security:
• Prism: Manage File Containers domain in the Prism Analytics functional area when uploading a file.

• Any of these security requirements:

• Prism: Tables Owner Manage domain in the Prism Analytics functional area.
• Prism: Tables Manage domain in the Prism Analytics functional area.
• Table Owner permission on the table.
• Table Editor permission on the table.
• Can Delete Table Data permission on the table.
• Can Truncate Table Data permission on the table.

Context
You can delete a subset of rows in a table using these methods:

Row Deletion Method Notes

By load ID You can quickly delete all rows that came from a particular data load
activity. Select Table > Delete Rows from the related actions menu
of the table. Then select Previous Loads.
By data change task You can delete specific rows that you specify using a data change
task with the delete operation.
You delete rows by specifying one these target fields as the Delete
Key:
• The field configured as the external ID
• WPA_LoadID
• WPA_RowID
To delete rows using a data change task, you need a delimited file
that contains a single field that contains the values in the delete key
field. Example: You can delete the rows for particular values of the
field configured as the external ID. Create a CSV file that contains
the values of the external ID field you want to delete. To delete some
rows from the ClaimID field, your CSV file might look like:

ClaimID
345999
345600
345601
345602

To delete specific rows using a data change task:

Steps
1. Access the View Table Details report for the table to delete from.
2. Select Quick Actions > Data Change Task.
3. (Optional) Change the data change task name that Workday created automatically at the top of the left
side panel.
4. On the Source step, select the file that contains the values of the rows you want to delete.
5. On the Source Options step, define how to parse the data in the files.
6. On the Target step, select Delete as the Target Operation.
7. On the Mapping step, select a field in the target table to use as the Delete Key.
8. Select a source field for the target field that you specified as the delete key.

Related Information
Concepts
Concept: Data Change Tasks on page 415
Tasks
Create a Data Change Task on page 410

Truncate Data in a Dataset

Context
You can remove the data in a base dataset by truncating the dataset. Truncating a dataset removes the
data from the dataset, but retains its metadata, such as schema and transformations.
You might want to truncate a dataset if:
• The dataset integration uses Append mode and after several integrations the dataset contains some
bad data.
• The dataset contains data that your organization later deems to be sensitive.
If you've previously published this dataset or a derived dataset based on this dataset, the associated Prism
data source still contains data. If you also want to remove the data from the associated Prism data source,
then you must publish the dataset again. Publishing a truncated dataset makes the associated Prism data
source empty, but active.

Steps
1. Access the View Dataset Details report for the dataset you want to truncate.
2. Select Actions > Dataset > Truncate.
Related Information
Concepts
Concept: Deleting Prism Data on page 453

Unpublish a Dataset

Prerequisites
• Prism data source exists in Workday, but no reports use it.
• Security: Prism Datasets: Publish domain in the Prism Analytics functional area.

Context
After you publish a dataset, you can unpublish it if necessary. When you unpublish a dataset, Workday
removes the Prism data source that is based on the dataset, including all data in it. You might want to
unpublish a dataset if you need to delete the dataset. You can only unpublish a dataset if no reports use
the associated Prism data source.

Steps
1. Access the View Dataset Details report for the dataset you want to unpublish.

2. Select Actions > Publishing > Unpublish Dataset.

Result
Workday removes the Prism data source and its rows.
Related Information
Concepts
Concept: Deleting Prism Data on page 453

Delete Rows from a Prism Data Source

Prerequisites
Security: Prism Datasets: Publish domain in the Prism Analytics functional area.

Context
When you publish a dataset, Workday creates a Prism data source and populates it with rows containing
the transformed data from the dataset. You can delete the rows in a Prism data source created from a
published dataset. When you delete rows in a Prism data source, the Prism data source is empty and
becomes inactive. If you need to delete rows from a Prism data source created from a table enabled for
analysis, then truncate the table.
You might want to delete the rows in a Prism data source if the rows contain incorrect data and you
don’t want analysts creating reports using the bad data. You can then edit the dataset to correct the
transformation logic and publish the dataset again. When you republish the dataset, Workday populates
the empty, inactive Prism data source with the new data.
Any reports that use an inactive Prism data source will be broken until you publish the dataset again.

Steps
1. Access the View Prism Data Source page, and select the Prism data source whose rows you want to
delete.
2. Select Actions > Prism Data Source > Delete Published Rows.

Result
Workday removes all data from the Prism data source, and changes the Prism data source status to
inactive.

Concept: Deleting Prism Data

You create tables, datasets, and Prism data sources filled with data. However, there might be times when
you need to remove data from your tenant.
You can remove data and Prism objects:

Action Notes
Make the Prism data source When a Prism data source is inactive, it exists in the tenant, but is
inactive. empty and unavailable for querying in reports and discovery board
visualizations.
You might want to make a Prism data source inactive if the data
source contains incorrect data and you don’t want analysts creating
reports using the bad data. You can make a Prism data source
inactive whether or not any reports or visualizations use it.

Action Notes
How you make a Prism data source inactive depends on the object
type it's based on:
• Table. Edit the table schema and clear the Enable for Analysis
option on the Edit Table task.
• Dataset. Delete the rows in the Prism data source. Select Prism
Data Source > Delete Published Rows from the related actions
on the View Prism Data Source report.

Delete the Prism data source You can only remove a Prism data source when no reports or vizzes
including all data in it. currently use the associated Prism data source.
How you remove a Prism data source depends on the object type it's
based on:
• Table. Delete the table from the Data Catalog. Right-click the table
from the Data Catalog and select Delete.
• Dataset. Unpublish the dataset. Select Publishing > Unpublish
Dataset from the related actions of the dataset. You might want to
unpublish a dataset to delete it from the Data Catalog.

Remove all data from a dataset You can remove the data in a base dataset by truncating the dataset.
(truncate). Truncating a dataset removes all data from the dataset. However, the
dataset retains its metadata, such as schema and transformations.
You might want to truncate a dataset if the dataset integration uses
Append mode and after several integrations the dataset contains
some bad data.
If you've previously published this dataset or a derived dataset based
on this dataset, then the associated Prism data source still contains
data. If you also want to remove the data from the associated Prism
data source, then you must publish the dataset again. Publishing a
truncated dataset makes the associated Prism data source empty,
but active.

Delete a dataset. When you delete a dataset, Workday removes the dataset definition
from the Data Catalog and removes the source data stored on disk in
your tenant.
You might want to delete a dataset to make more space available to
store data in your Data Catalog. You can only delete a dataset if it's
not currently published and isn't imported into any derived dataset.
Right-click a dataset from the Data Catalog and select Delete.

Delete rows from a table. You can delete 1, multiple, or all rows from a table. When you delete
rows from a table, the table remains in the Data Catalog.
Truncate a table. When you truncate a table, Workday removes all rows from the table,
and keeps the empty table in the Data Catalog.
If you selected the Enable for Analysis option for this table, then
truncating the table also removes all data from the associated Prism
data source. The Prism data source is empty, but active.

Delete a table. When you delete a table, Workday removes the table definition from
the Data Catalog, including all data contained in it.
You can only delete a table when:

Action Notes
• No reports or vizzes currently use the associated Prism data
source.
• No data change task is configured for the table.
Right-click the table from the Data Catalog and select Delete.

Related Information
Tasks
Truncate Data in a Dataset on page 452
Unpublish a Dataset on page 452
Delete Rows from a Prism Data Source on page 453

Managing Analytic Data Sources

Install and Schedule an Analytic Data Source

Prerequisites
Security: Manage: Analytic Data Sources domain in the Analytical Framework functional area.

Context
Install an analytic data source and define a schedule for updating the data in it.

Steps
1. Access the Tenant Setup for Analytic Data Source task.
2. Select the Analytic Data Source to install.
3. In Run Frequency, specify how often to update the data in the analytic data source.
4. Enter a name for the analytic data source schedule.
5. Select the Schedule tab, and select the criteria for the schedule.
When the analytic data source is based on data in Workday business objects that contain a very large
number of instances, we recommend that you define the schedule to run:
• During a quiet time.
• Weekly or monthly.

Result
Workday creates the analytic data source and its schedule. Workday loads data from Workday business
objects into the data source at the next scheduled time.

Next Steps
You can:
• Use the analytic data source in a discovery board or custom report.
• View the data source details using the View Analytic Data Source (Workday Owned) report.
• Edit, cancel, or view the analytic data source schedule.
Related Information
Concepts
Concept: Workday-Delivered Analytic Data Sources on page 456

Concept: Managing Analytic Data Source Schedules on page 456

Uninstall an Analytic Data Source

Prerequisites
Security: Manage: Analytic Data Sources domain in the Analytical Framework functional area.

Context
You can uninstall an analytic data source to remove all data from that data source. You might want to do
uninstall the data source if you encounter a critical error while using it.
When you uninstall an analytic data source:
• Any reports that use the data source will display no results and display an error the next time you run
the report.
• You can re-install the data source before running any existing reports that use the data source.

Steps
1. Access the Uninstall/Cleanup Analytic Data Source task.
2. Select the data source to uninstall, and click Confirm.

Concept: Workday-Delivered Analytic Data Sources

An analytic data source is a Workday-blended and delivered data source updated on a regular schedule
that can contain Workday data or external data.
Analytic data sources use Prism Analytics and are designed for high performance and analytical reporting.
Although analytic data sources can contain Workday data, the data isn't updated in real time like Workday-
delivered data sources directly based on business objects. When you install the analytic data source, you
define how often the data updates, such as daily, weekly, or monthly.
When Workday updates the data in an analytic data source, Workday:
• Runs a background job that extracts data from the Workday or external sources.
• Blends and transforms the data using Prism Analytics.
• Loads the data into the data source.
This processing takes time, depending on how much data is in your tenant and how often you schedule
the data updates. As a result, the freshness of the data in your analytic data source depends on both the
schedule frequency and the processing time required to update the data.
Related Information
Tasks
Install and Schedule an Analytic Data Source on page 455

Concept: Managing Analytic Data Source Schedules

After you install an analytic data source, you can manage the schedule you created for the data source.
You need access to the Manage Analytic Data Sources domain in the Analytical Framework functional
area to manage the schedule.
You can use these tasks and reports to manage the analytic data source schedule:

Task or Report Name Notes

Cancel Analytic Data Source Publish Schedule You can only cancel a schedule that currently
exists.

Task or Report Name Notes

Create Analytic Data Source Publish Schedule You can only create a schedule if you previously
canceled the schedule.
Edit Analytic Data Source Publish Schedule Change the schedule settings on the Schedule tab.
View Analytic Data Source Publish Schedule

Concept: Peakon Employee Voice Analytic Data Source

The Peakon Employee Voice analytic data source enables you to create custom employee engagement
reporting. It extracts non-aggregated answers from the Peakon system, enabling you to analyze your
Peakon data in more detail.
This analytic data source includes scores and comments from all question sets that you measure on your
Peakon Employee Voice survey, including these:
• Engagement
• Diversity and Inclusion
• Health and Wellbeing
• COVID-19
• All company-specific questions
Consider the sensitive nature of the Peakon scores data as you interact with this analytic data source and
its underlying dataset. All scores and comments are attached to an employee ID, making it possible to
identify the individual scores and comments left by an employee on their engagement survey. This analytic
data source is designed for companies with the appropriate safeguards.
Implementing a fully transparent survey requires a lot of trust from your employees. Ensure this trust by
securing their data through your analysis in Workday. You secure this data by:
• Configuring the security policy for the Peakon Responses Analytic Data Source domain.
• Providing users access to the Peakon Employee Voice Raw Data dataset in the Data Catalog. All users
with unconstrained access to the Data Catalog can access the data in the Peakon dataset and can
share it with Prism users who have constrained access.
Workday recommends that you only provide access to this data to highly privileged users before sharing
anonymized data with a wider audience.
Note: To install this analytic data source:
• Enable the Peakon Data Export API feature.
• Map the Workday tenant name in Peakon.

Peakon Employee Voice Raw Data Dataset

When you install this analytic data source, Workday also creates and adds a Prism Analytics dataset in the
Data Catalog containing Peakon answers data. The data in the Peakon Employee Voice Raw Data dataset
is the same as the data in the analytic data source. You can use Prism Analytics to join this dataset with
other data, such as worker or external data, further enhancing your reporting and analytics capabilities in
Discovery Boards and Report Writer.
Note: You can migrate between tenants any derived datasets, discovery boards, custom reports, or Prism
data sources that you create based on the Peakon Employee Voice Raw Data dataset. However, before
you migrate these assets to a different tenant, you must install the Peakon Employee Voice analytic data
source in the target tenant.

Security for Peakon Employee Voice Data

Workday controls access to the analytic data source and the raw data dataset using the Peakon
Responses Analytic Data Source domain.
To provide access to the data source and dataset:
1. Create or edit a user-based security group that contains the users who can use the data source and
raw data dataset.
2. Edit the domain security policy for the Peakon Responses Analytic Data Source domain, and provide
the security group both View and Modify permissions.
3. Set Up Dataset Sharing on page 421. Add the user-based security group in the Role Assignees
Restricted To column for the Prism Dataset Viewer Workday Role.
4. Activate pending security policy changes.
Note: Consider the sensitive nature of the highly confidential Peakon scores data as you configure this
domain security policy. Workday recommends that you only provide access to this data to highly privileged
users before sharing anonymized data with a wider audience.
Related Information
Concepts
Concept: Workday-Delivered Analytic Data Sources on page 456
Tasks
Install and Schedule an Analytic Data Source on page 455

Reference: Prism Expression Language

Concept: Prism Expression Language

Prism Analytics includes its own expression language that's composed of functions and operators. You use
the Prism expression language to create an expression, which you can use to create new values or filter
existing values.
An expression computes or produces a value by combining fields, constant values, operators, and
functions. An expression outputs a value of a particular field type, such as Numeric or Text values. Simple
expressions can be a single constant value, the values of a given field, or just a function. You can use
operators to join two or more simple expressions into a complex expression.
You can use expressions in datasets:
• Calculated fields. Use expressions to define calculated fields that operate on the source data. A
calculated field expression generates its values based on a calculation or condition, and returns a
value for each input row. Calculated field expressions can contain values from other fields, constants,
mathematical operators, comparison operators, or built-in row functions.
• Filter stages. Use an expression in a Filter stage to limit the scope of the source data of a dataset.
The expression builder helps you create calculated field expressions in a dataset. It displays the available
fields in the dataset, plus the list of the Prism functions. It validates your expressions for correct syntax,
input field types, and so on.

Function Inputs and Outputs

Functions take one or more input values and return an output value. Input values can be a literal value
or the name of a field that contains a value. In both cases, the function expects the input value to be a
particular field type such as Text or Integer. Example: The CONCAT() function combines Text inputs and
outputs a new Text.

This example demonstrates how to use the CONCAT() function to concatenate the values in the month,
day, and year fields separated by the literal forward slash character:

CONCAT([month],"/",[day],"/",[year])

A function return value might be the same as its input type or it might be an entirely new field type.
Example: The TO_DATE() function takes a Text as input, but outputs a Date value. If a function expects a
Text, but is passed another field type as input, the function returns an error.
Typically, functions are classified by what field type they take or what purpose they serve. Example:
CONCAT() is a text function and TO_DATE() is a field type conversion function.

Nesting Functions
Functions can take other functions as arguments. Example: You can use the CONCAT function as an
argument to the TO_DATE() function. The final result is a Date value in the format 10/31/2014.

TO_DATE(CONCAT([month],"/",[day],"/",[year]),"MM/dd/yyyy")

The nested function must return the correct field type. So, because TO_DATE() expects text input and
CONCAT() returns a text, the nesting succeeds.

Referring to Fields in the Current Dataset

Workday recommends enclosing all field names with square brackes ([]). Example:

TO_INT([sales])

TO_INT([Sale Amount])

TO_INT([2013_data])

TO_INT([count])

If a field name contains a ] (closing square bracket), you must escape the closing square bracket by
doubling it ]]. Suppose you have this field name:

[Total Sales]

You enclose the entire field name in square brackets and escape the closing bracket that is part of the
actual field name:

[[Total Sales]]]

Literal Text Values

To specify a literal or actual Text value, enclose the value in double quotes ("). Example: This expression
converts the values of a gender field to the literal values of male, female, or unknown:

CASE WHEN [gender]="M" THEN "male"

WHEN [gender]="F" THEN "female"
ELSE "unknown" END

To escape a literal quote within a literal value itself, double the literal quote character. Example:

CASE WHEN [height]="60""" THEN "5 feet" WHEN [height]="72"""

THEN "6 feet" ELSE "other" END

The REGEX() function is a special case. In the REGEX() function, Text expressions are also enclosed in
quotes. When a Text expression contains literal quotes, double the literal quote character. Example:

REGEX([height], "\d\'(\d)+""")

Literal Date Values

To refer to a Date value in a Filter stage expression, you must use this format (or any shortened version of
it) without any enclosing quotation marks or other punctuation:

yyyy-MM-ddTHH:mm:ss:SSSZ

Example:

[Order Date] BETWEEN 2016-06-01T00:00:00.000Z AND 2016-07-31T00:00:00.000Z

If the Filter expression is a shortened version of the full format, then Prism assigns any values that aren't
included a value of zero (0). Example: This expression:

[Order Date] >= 2017-01-01

Is equivalent to:

[Order Date] >= 2017-01-01T00:00:00.000Z

If the date value is in Text format rather than a Date format, you must enclose the value in quotes.
To refer to a literal date value in a calculated field expression, you must specify the format of the date and
time components using TO_DATE, which takes a Text literal argument and a format string. Example:

CASE WHEN [Order Date]=TO_DATE("2013-01-01 00:00:59 PST","yyyy-MM-dd

HH:mm:ss z")
THEN "free shipping" ELSE "standard shipping" DONE

Literal Numeric Values

For literal numeric values, you can just specify the number itself without any special escaping or formatting.
Example:

CASE WHEN [is married]=1 THEN "married" WHEN [is married]=0

THEN "not_married" ELSE NULL END

Related Information
Tasks
Add a Prism Calculated Field to a Dataset on page 389

Comparison Operators
Comparison operators are used to compare the equivalency or inequivalency of 2 expressions of the
same field type. The result of a comparison expression is a Boolean value (returns true, false, or NULL for
invalid, such as comparing a text value to a numeric value). Boolean expressions are most often used to
specify data processing conditions or filter criteria.
Example: You can use comparison operators in a CASE expression:

CASE WHEN [age] <= 25 THEN "0-25"

WHEN [age] <= 50 THEN "26-50"

ELSE "over 50" END

This expression compares the value in the age field to a literal number value. If true, it returns the
appropriate boolean value.

Operator Meaning Example

= or == Equal to [order_date] = "12/22/2016"
> Greater than [age] > 18
!> Not greater than (equivalent to <) [age] !> 8
< Less than [age] < 30
!< Not less than (equivalent to >=) [age] !< 12
>= Greater than or equal to [age] >= 20
<= Less than or equal to [age] <= 29
<> or != or ^= Not equal to [age] <> 30
BETWEEN min_value Test whether a date or numeric value [year] BETWEEN 2014 AND 2016
AND max_value is within the min and max values
(inclusive).
IN(list) Test whether a value is within a set. [product_type]
IN("tablet","phone","laptop")
LIKE("pattern") Simple inclusive case-insensitive [last_name] LIKE("?utch*")
character pattern matching. The *
Matches Kutcher, hutch but not
character matches any number of
Krutcher or crutch
characters. The ? character matches
exactly 1 (a single) character. [company_name]
LIKE("workday")
Matches Workday or workday

value IS NULL Check whether a field value or [ship_date] IS NULL

expression is null (empty).
Evaluates to true when the ship_date
field is empty

Logical Operators
Use logical operators in expressions to test for a condition. Logical operators define Boolean expressions.
You might want to use logical operators in Filter transformations or CASE expressions. Filters test if a field
or value meets some condition, such as testing if the value in a Date field falls between 2 other dates:

BETWEEN 2016-06-01 AND 2016-07-31

Operator Meaning Example

AND Test whether 2 conditions are
true.
OR Test if either of 2 conditions are
true.

Operator Meaning Example

NOT Reverses the value of other • year NOT BETWEEN 2013
operators. AND 2016
• first_name NOT
LIKE("Jo?n*")
Excludes John, jonny but not
Jon or Joann
• Weekday NOT
IN("Saturday","Sunday")
• purchase_date IS NOT
NULL
Evaluates to true when the
purchase_date field is not
empty

Arithmetic Operators
Arithmetic operators perform basic math operations on 2 expressions of the same field type resulting in a
numeric value.
Example: You can calculate the gross profit margin percentage using the values of a [total_revenue] and
[total_cost] field:

(([total_revenue] - [total_cost]) / [total_cost]) * 100

Operator Meaning Example

+ Addition [amount] + 10
Add 10 to the value of the
[amount] field.

- Subtraction [amount] - 10
Subtract 10 from the value of the
[amount] field.

* Multiplication [amount] * 100

Multiply the value of the [amount]
field by 100.

/ Division [bytes] / 1024

Divide the value of the [bytes]
field by 1024 and return the
quotient.

Conversion Functions
BUILD_CURRENCY

Description
BUILD_CURRENCY is a row function that constructs a Currency field from a numeric value and a Text or
Instance value that contains a valid currency code. When the currency code isn't valid, this function returns
NULL.

Syntax
BUILD_CURRENCY(number_expression,currency_code_expression)

Return Value
Returns a value of type Currency.

Input Parameters
number_expression
Required. A field or expression of type Double, Numeric, Integer, or Long.
currency_code_expression
Required. A field or expression of type Text or Instance that contains valid currency
code data.

Examples
Convert the values of the Sale Price field (Numeric type) to a Currency field type using the currency codes
from the Currency Code field:
BUILD_CURRENCY([Sale Price], [Currency Code])

CAST

Description
CAST is a row function that converts data values from one field type (data type) to another.
You can use CAST to convert these field types:

From Field Type To Field Types

Boolean Boolean, Numeric, Double, Integer, Long, Text
Date Date, Text
Numeric Boolean, Numeric, Double, Integer, Long, Text
Double Boolean, Numeric, Double, Integer, Long, Text
Integer Boolean, Numeric, Double, Integer, Long, Text
Long Boolean, Numeric, Double, Integer, Long, Text
Instance Instance, Text
Multi-Instance Multi-Instance (using a different business object)
Text Boolean, Numeric, Double, Instance, Integer, Long, Text

Syntax
CAST(field_name AS field_type)

Return Value
Returns one value per row of the specified field type.

Input Parameters
field_name
Required. A field or expression of a supported field type.
field_type
Required. The field type to convert the data values into.
To convert a field to the Text field type, specify String for this parameter.
When specifying Boolean as the field type, CAST converts the value of zero (0) to False,
and all other values to True.
When specifying Instance or Multi-Instance as the field type, you must specify the business
object using its unique identifier (WID). Use this syntax:

Instance(business_object_WID)

Multi_Instance(business_object_WID)

When specifying Numeric as the field type, specify the number of digits to the left of the
decimal point (integers) and the number of digits to the right of decimal point (decimals).
Use this syntax:

Decimal(integers,decimals)

Ensure that the number of integer digits specified is large enough to capture all possible
data values. If the value for a row has more integer digits than the number of integer
digits specified in the function, then CAST returns NULL. Example: CAST(99.9 AS
decimal(1,1)) returns NULL.

Examples
Convert the WID values of the Region field from Text to Instance:
CAST([Region] AS Instance(eecb565181284b6a8ae8b45dc3ed1451))
CAST("3b122818d7934d1c8c663ddbe1937819" AS
Instance(eecb565181284b6a8ae8b45dc3ed1451))
Convert the amount field to Text:
CAST([amount] AS string)
Convert the values of the average_rating field to a Numeric field type:
CAST([average_rating] AS decimal(1,2))
CAST(99.99 AS decimal(10,3)) returns 99.990.
CAST(99.99 AS decimal(20,2)) returns 99.99.
CAST(99.999 AS decimal(10,2)) returns 100.00.
CAST(99.99 AS decimal(1,2)) returns NULL.

EPOCH_MS_TO_DATE

Description
EPOCH_MS_TO_DATE is a row function that converts Long values to Date values, where the input number
represents the number of milliseconds since the epoch.

Syntax
EPOCH_MS_TO_DATE(long_expression)

Return Value
Returns one value per row of type Date in UTC format yyyy-MM-dd HH:mm:ss:SSS Z.

Input Parameters
long_expression
Required. A field or expression of type Long representing the number of milliseconds since
the epoch date (January 1, 1970 00:00:00:000 GMT).

Examples
Convert a number representing the number of milliseconds from the epoch to a human-readable date and
time:
EPOCH_MS_TO_DATE(1360260240000) returns 2013-02-07T18:04:00:000Z or February 7,
2013 18:04:00:000 GMT
Or if your data is in seconds instead of milliseconds:
EPOCH_MS_TO_DATE(1360260240 * 1000) returns 2013-02-07T18:04:00:000Z or February
7, 2013 18:04:00:000 GMT

EXTRACT_AMOUNT

Description
EXTRACT_AMOUNT is a row function that takes a Currency value and extracts the numeric amount as a
Numeric value.

Syntax
EXTRACT_AMOUNT(currency_expression)

Return Value
Returns a value of type Numeric.

Input Parameters
currency_expression
Required. A field or expression of type Currency.

Examples
Get the numeric values from the Salary field (Currency field type):
EXTRACT_AMOUNT([Salary])

EXTRACT_CODE

Description
EXTRACT_CODE is a row function that takes a Currency value and extracts the currency code as an
Instance value.

Syntax
EXTRACT_CODE(currency_expression)

Return Value
Returns a value of type Instance.

Input Parameters
currency_expression
Required. A field or expression of type Currency.

Examples
Get the currency code information from the Salary field (Currency field type) as an Instance field:
EXTRACT_CODE([Salary])

EXTRACT_CODE_TEXT

Description
EXTRACT_CODE_TEXT is a row function that takes a Currency value and extracts the currency code as a
Text value.

Syntax
EXTRACT_CODE_TEXT(currency_expression)

Return Value
Returns a value of type Text.

Input Parameters
currency_expression
Required. A field or expression of type Currency.

Examples
Get the currency code information from the Salary field (Currency field type) as a Text field:
EXTRACT_CODE_TEXT([Salary])

TO_BOOLEAN

Description
TO_BOOLEAN is a row function that converts Text, Boolean, Integer, Long, or Numeric values to
Boolean.

Syntax
TO_BOOLEAN(expression)

Return Value
Returns one value per row of type Boolean.

Input Parameters
expression
Required. A field or expression of type Text, Boolean, Integer, Long, or Numeric.
The function converts these values to true:
1, 1.0, "true", "t", "yes", "y", "1"
The function converts these values to false:
0, 0.0, "false", "f", "no", "n", "0"
The function converts all other values to NULL.

Examples
Convert the values of the is_contingent field to a Boolean:
TO_BOOLEAN([is_contingent])
These expressions return true:
TO_BOOLEAN("TRUE")
TO_BOOLEAN("1")
TO_BOOLEAN(1.0)
These expressions return false:
TO_BOOLEAN("False")
TO_BOOLEAN("0")
TO_BOOLEAN(0.0)
These expressions return NULL:
TO_BOOLEAN("correct")
TO_BOOLEAN("1.0")
TO_BOOLEAN(1.1)

TO_CURRENCY

Description
TO_CURRENCY is a row function that converts Text values that contain valid currency-formatted data to
Currency values.

Syntax
TO_CURRENCY(expression)

Return Value
Returns a value of type Currency.

Input Parameters
expression
Required. A field or expression of type Text that represents a valid currency-formatted
value.
A valid currency-formatted value meets these requirements:
• Includes both the numeric value and currency code.
• Uses a period to separate digits before and after the decimal.
• Doesn't include any character to separate the thousands place.
Example: 10000 EUR and 12345.678 USD.

Examples
Convert this text value to a Currency field type:
TO_CURRENCY("1234.56 USD")
Convert the values of the Grant Price field to a Currency field type using the currency codes in the Grant
Code field:
TO_CURRENCY(CONCAT(TO_STRING([Grant Price]), [Grant Code]))
Convert the Sale Price field Text field to a Currency field, but first transform the occurrence of any N/A
values to NULL values using a CASE expression:
TO_CURRENCY(CASE WHEN [Sale Price]="N/A" then NULL ELSE [Sale Price] END)

TO_DATE

Description
TO_DATE is a row function that converts Text values to Date values, and specifies the format of the date
and time elements in the string.

Syntax
TO_DATE(string_expression,"date_format")

Return Value
Returns one value per row of type Date (which by definition is in UTC).

Input Parameters
string_expression
Required. A field or expression of type Text.
date_format
Required. A pattern that describes how the date is formatted.

Examples
Define a new Date Prism calculated field based on the order_date base field, which contains timestamps
in the format of: 2014.07.10 at 15:08:56 PDT:

TO_DATE([order_date],"yyyy.MM.dd 'at' HH:mm:ss z")

Define a new Date Prism calculated field by first combining individual month, day, year, and depart_time
fields (using CONCAT), and performing a transformation on depart_time to make sure three-digit times are
converted to four-digit times (using REGEX_REPLACE):

TO_DATE(CONCAT([month],"/",[day],"/",[year],":",
REGEX_REPLACE([depart_time],"\b(\d{3})\b","0$1")),"MM/dd/yyyy:HHmm")

Define a new Date Prism calculated field based on the created_at base field, which contains timestamps
in the format of: Sat Jan 25 16:35:23 +0800 2014 (this is the timestamp format returned by Twitter's API):

TO_DATE([created_at],"EEE MMM dd HH:mm:ss Z yyyy")

Related Information
Reference
Reference: Date Format Symbols on page 379

TO_DECIMAL

Description
TO_DECIMAL is a row function that converts Text, Boolean, Integer, Long, Double, or Numeric
values to Numeric values with the default number of digits before and after the decimal point.

Syntax
TO_DECIMAL(expression)

Return Value
Returns one value per row of type Numeric with the default number of digits before and after the decimal
point.

Input Parameters
expression
Required. A field or expression of type Text (must be numeric characters), Boolean,
Integer, Long, Double, or Numeric.

Examples
Convert the values of the average_rating field to a Numeric field type:
TO_DECIMAL([average_rating])
Convert the average_rating field to a Numeric field type, but first transform the occurrence of any NA
values to NULL values using a CASE expression:
TO_DECIMAL(CASE WHEN [average_rating]="N/A" then NULL ELSE [average_rating]
END)

TO_DOUBLE

Description
TO_DOUBLE is a row function that converts Text, Boolean, Integer, Long, or Double values to
Double (a type of numeric) values.

Syntax
TO_DOUBLE(expression)

Return Value
Returns one value per row of type Double.

Input Parameters
expression
Required. A field or expression of type Text (must be numeric characters), Boolean,
Integer, Long, or Double.

Examples
Convert the values of the average_rating field to a Double field type:
TO_DOUBLE([average_rating])
Convert the average_rating field to a Double field type, but first transform the occurrence of any NA values
to NULL values using a CASE expression:
TO_DOUBLE(CASE WHEN [average_rating]="N/A" then NULL ELSE [average_rating]
END)

TO_INT

Description
TO_INT is a row function that converts Text, Boolean, Integer, Long, or Double values to Integer
(whole number) values. When converting Double values, everything after the decimal will be truncated
(not rounded up or down).

Syntax
TO_INT(expression)

Return Value
Returns one value per row of type Integer.

Input Parameters
expression
Required. A field or expression of type Text, Boolean, Integer, Long, or Double. If a
Text field contains non-numeric characters, the function returns NULL.

Examples
Convert the values of the average_rating field to an Integer field type:
TO_INT([average_rating])
Convert the flight_duration field to an Integer field type, but first transform the occurrence of any NA values
to NULL values using a CASE expression:
TO_INT(CASE WHEN [flight_duration]="N/A" then NULL ELSE [flight_duration] END)

TO_LONG

Description
TO_LONG is a row function that converts Text, Boolean, Integer, Long, Decimal, Date, or Double
values to Long (whole number) values. When converting Decimal or Double values, everything after the
decimal will be truncated (not rounded up or down).

Syntax
TO_LONG(expression)

Return Value
Returns one value per row of type Long.

Input Parameters
expression
Required. A field or expression of type Text (must be numeric characters only, no period
or comma), Boolean, Integer, Long, Decimal, Date, or Double. When a Text field
value includes a decimal, the function returns a NULL value.

Examples
Convert the values of the average_rating field to a Long field type:
TO_LONG([average_rating])
Convert the average_rating field to a Long field type, but first transform the occurrence of any NA values to
NULL values using a CASE expression:
TO_LONG(CASE WHEN [average_rating]="N/A" then NULL ELSE [average_rating] END)

TO_STRING

Description
TO_STRING is a row function that converts values of other data types to Text (character) values.

Syntax
TO_STRING(expression)
TO_STRING(date_expression,date_format)

Return Value
Returns one value per row of type Text.

Input Parameters
expression
A field or expression of type Text, Boolean, Integer, Long, Numeric, Double,
Instance, or Multi-Instance. When you convert an Instance or Multi-Instance field to
a string, this function returns the unique identifier (WID), not the display name, of the field
value. When a Multi-Instance field contains more than 1 value, this function concatenates
each value into a single string with no spaces.
date_expression
A field or expression of type Date.
date_format
If converting a Date to Date, a pattern that describes how the date is formatted. See
TO_DATE on page 468 for the date format patterns.

Examples
Convert the values of the sku_number field to a Text field type:

TO_STRING([sku_number])
Convert values in the age column into range-based groupings (binning), and cast output values to a Text:
TO_STRING(CASE WHEN [age] <= 25 THEN "0-25" WHEN [age] <= 50 THEN "26-50" ELSE
"over 50" END)
Convert the values of a timestamp Date field to Text, where the timestamp values are in the format of:
2002.07.10 at 15:08:56 PDT:
TO_STRING([timestamp],"yyyy.MM.dd 'at' HH:mm:ss z")

Date Functions
DAYS_BETWEEN

Description
DAYS_BETWEEN is a row function that calculates the whole number of days (ignoring time) between two
date values (value1 - value2).

Syntax
DAYS_BETWEEN(date_1,date_2)

Return Value
Returns one value per row of type Integer.

Input Parameters
date_1
Required. A field or expression of type Date.
date_2
Required. A field or expression of type Date.

Examples
Calculate the number of days to ship a product by subtracting the value of the order_date field from the
ship_date field:
DAYS_BETWEEN([ship_date],[order_date])
Calculate the number of days since a product's release by subtracting the value of the release_date field
from the current date (the result of the TODAY expression):
DAYS_BETWEEN(TODAY(),[release_date])

DATE_ADD

Description
DATE_ADD is a row function that adds the specified time interval to a date value.

Syntax
DATE_ADD(date,quantity,"interval")

Return Value
Returns a value of type Date.

Input Parameters
date
Required. A field name or expression that returns a date value.
quantity
Required. An integer value. To add time intervals, use a positive integer. To subtract time
intervals, use a negative integer.
interval
Required. One of the following time intervals:
• millisecond - Adds the specified number of milliseconds to a date value.
• second - Adds the specified number of seconds to a date value.
• minute - Adds the specified number of minutes to a date value.
• hour - Adds the specified number of hours to a date value.
• day - Adds the specified number of days to a date value.
• week - Adds the specified number of weeks to a date value.
• month - Adds the specified number of months to a date value.
• quarter - Adds the specified number of quarters to a date value.
• year - Adds the specified number of years to a date value.
• weekyear - Adds the specified number of weekyears to a date value.

Examples
Add 45 days to the value of the invoice_date field to calculate the date a payment is due:
DATE_ADD([invoice_date],45,"day")

EXTRACT

Description
EXTRACT is a row function that returns the specified portion of a date value.

Syntax
EXTRACT("extract_value",date)

Return Value
Returns the specified extracted value as type Integer. EXTRACT removes leading zeros. For example,
the month of April returns a value of 4, not 04.

Input Parameters
extract_value
Required. One of the following extract values:
• millisecond - Returns the millisecond portion of a date value. For example, an
input date value of 2012-08-15 20:38:40.213 would return an integer value of
213.
• second - Returns the second portion of a date value. For example, an input date
value of 2012-08-15 20:38:40.213 would return an integer value of 40.
• minute - Returns the minute portion of a date value. For example, an input date value
of 2012-08-15 20:38:40.213 would return an integer value of 38.
• hour - Returns the hour portion of a date value. For example, an input date value of
2012-08-15 20:38:40.213 would return an integer value of 20.

• day - Returns the day portion of a date value. For example, an input date value of
2012-08-15 would return an integer value of 15 .
• week - Returns the ISO week number for the input date value. For example, an input
date value of 2012-01-02 would return an integer value of 1 (the first ISO week of
2012 starts on Monday January 2). An input date value of 2012-01-01 would return
an integer value of 52 (January 1, 2012 is part of the last ISO week of 2011).
• month - Returns the month portion of a date value. For example, an input date value
of 2012-08-15 would return an integer value of 8.
• quarter - Returns the quarter number for the input date value, where quarters
start on January 1, April 1, July 1, or October 1. For example, an input date value of
2012-08-15 would return a integer value of 3.
• year - Returns the year portion of a date value. For example, an input date value of
2012-01-01 would return an integer value of 2012.
• weekyear - Returns the year value that corresponds to the ISO week number of the
input date value. For example, an input date value of 2012-01-02 would return an
integer value of 2012 (the first ISO week of 2012 starts on Monday January 2). An input
date value of 2012-01-01 would return an integer value of 2011 (January 1, 2012 is
part of the last ISO week of 2011).
date
Required. A field name or expression that returns a date value.

Examples
Extract the hour portion from the order_date Date field:
EXTRACT("hour",[order_date])
Cast the value of the order_date Text field to a date value using TO_DATE, and extract the ISO week year:
EXTRACT("weekyear",TO_DATE([order_date],"MM/dd/yyyy HH:mm:ss"))

HOURS_BETWEEN

Description
HOURS_BETWEEN is a row function that calculates the whole number of hours (ignoring minutes, seconds,
and milliseconds) between two date values (value1 - value2).

Syntax
HOURS_BETWEEN(date_1,date_2)

Return Value
Returns one value per row of type Integer.

Input Parameters
date_1
Required. A field or expression of type Date.
date_2
Required. A field or expression of type Date.

Examples
Calculate the number of hours to ship a product by subtracting the value of the ship_date field from the
order_date field:

HOURS_BETWEEN([ship_date],[order_date])

MILLISECONDS_BETWEEN

Description
MILLISECONDS_BETWEEN is a row function that calculates the whole number of milliseconds between two
date values (value1 - value2).

Syntax
MILLISECONDS_BETWEEN(date_1,date_2)

Return Value
Returns one value per row of type Integer.

Input Parameters
date_1
Required. A field or expression of type Date.
date_2
Required. A field or expression of type Date.

Examples
Calculate the number of milliseconds it took to serve a web page by subtracting the value of the
request_timestamp field from the response_timestamp field:
MILLISECONDS_BETWEEN([request_timestamp],[response_timestamp])

MINUTES_BETWEEN

Description
MINUTES_BETWEEN is a row function that calculates the whole number of minutes (ignoring seconds and
milliseconds) between two date values (value1 - value2).

Syntax
MINUTES_BETWEEN(date_1,date_2)

Return Value
Returns one value per row of type Integer.

Input Parameters
date_1
Required. A field or expression of type Date.
date_2
Required. A field or expression of type Date.

Examples
Calculate the number of minutes it took for a user to click on an advertisement by subtracting the value of
the impression_timestamp field from the conversion_timestamp field:
MINUTES_BETWEEN([impression_timestamp],[conversion_timestamp])

SECONDS_BETWEEN

Description
SECONDS_BETWEEN is a row function that calculates the whole number of seconds (ignoring milliseconds)
between two date values (value1 - value2).

Syntax
SECONDS_BETWEEN(date_1,date_2)

Return Value
Returns one value per row of type Integer.

Input Parameters
date_1
Required. A field or expression of type Date.
date_2
Required. A field or expression of type Date.

Examples
Calculate the number of seconds it took for a user to click on an advertisement by subtracting the value of
the impression_timestamp field from the conversion_timestamp field:
SECONDS_BETWEEN([impression_timestamp],[conversion_timestamp])

TODAY

Description
TODAY is a scalar function that returns the current system date and time as a date value (no time
information). It can be used in other expressions involving Date type fields, such as YEAR_DIFF. Note
that the value of TODAY is only evaluated at the time a dataset is published (it is not re-evaluated with each
query).

Syntax
TODAY()

Return Value
Returns the current system date (no time) as a date value.

Examples
Calculate a user's age using YEAR_DIFF to subtract the value of the birthdate field from the current date:
YEAR_DIFF(TODAY(), [birthdate])
Calculate the number of days since a product's release using DAYS_BETWEEN to subtract the value of the
release_date field from the current date:
DAYS_BETWEEN(TODAY(), [release_date])

TRUNC

Description
TRUNC is a row function that truncates a date value to the specified format.

Syntax
TRUNC(date, "format")

Return Value
Returns a value of type Date truncated to the specified format.

Input Parameters
date
Required. A field or expression that returns a date value.
format
Required. One of the following format values:
• millisecond - Returns a date value truncated to millisecond granularity. Has
no effect since millisecond is already the most granular format for date values. For
example, an input date value of 2012-08-15 20:38:40.213 would return a date
value of 2012-08-15 20:38:40.213.
• second - Returns a date value truncated to second granularity. For example, an input
date value of 2012-08-15 20:38:40.213 would return a date value of 2012-08-15
20:38:40.000.
• minute - Returns a date value truncated to minute granularity. For example, an input
date value of 2012-08-15 20:38:40.213 would return a date value of 2012-08-15
20:38:00.000.
• hour - Returns a date value truncated to hour granularity. For example, an input date
value of 2012-08-15 20:38:40.213 would return a date value of 2012-08-15
20:00:00.000.
• day - Returns a date value truncated to day granularity. For example, an input date
value of 2012-08-15 20:38:40.213 would return a date value of 2012-08-15
00:00:00.000.
• week - Returns a date value truncated to the first day of the week (starting on a
Monday). For example, an input date value of 2012-08-15 (a Wednesday) would
return a date value of 2012-08-13 (the Monday prior).
• month - Returns a date value truncated to the first day of the month. For example, an
input date value of 2012-08-15 would return a date value of 2012-08-01.
• quarter - Returns a date value truncated to the first day of the quarter (January
1, April 1, July 1, or October 1). For example, an input date value of 2012-08-15
20:38:40.213 would return a date value of 2012-07-01.
• year - Returns a date value truncated to the first day of the year (January 1).
For example, an input date value of 2012-08-15 would return a date value of
2012-01-01.
• weekyear - Returns a date value trucated to the first day of the ISO weekyear (the
ISO week starting with the Monday which is nearest in time to January 1). For example,
an input date value of 2008-08-15 would return a date value of 2007-12-31. The
first day of the ISO weekyear for 2008 is December 31, 2007 (the prior Monday closest
to January 1).

Examples
Truncate the order_date date field to day granularity:

TRUNC([order_date],"day")
Cast the value of the order_date Text field to a date value using TO_DATE, and truncate it to day
granularity:
TRUNC(TO_DATE([order_date], "MM/dd/yyyy HH:mm:ss"), "day")

YEAR_DIFF

Description
YEAR_DIFF is a row function that calculates the fractional number of years between two date values
(value1 - value2).

Syntax
YEAR_DIFF(date_1,date_2)

Return Value
Returns one value per row of type Double.

Input Parameters
date_1
Required. A field or expression of type Date.
date_2
Required. A field or expression of type Date.

Examples
Calculate the number of years a user has been a customer by subtracting the value of the registration_date
field from the current date (the result of the TODAY expression):
YEAR_DIFF(TODAY(),[registration_date])
Calculate a user's age by subtracting the value of the birthdate field from the current date (the result of the
TODAY expression):
YEAR_DIFF(TODAY(),[birthdate])

Informational Functions
IS_VALID

Description
IS_VALID is a row function that returns 0 if the returned value is NULL, and 1 if the returned value is NOT
NULL. This is useful for computing other calculations where you want to exclude NULL values (such as
when computing averages).

Syntax
IS_VALID(expression)

Return Value
Returns 0 if the returned value is NULL, and 1 if the returned value is NOT NULL.

Input Parameters
expression
Required. A field name or expression.

Examples
Define a Prism calculated field using IS_VALID. This returns a row count only for the rows where this
field value is NOT NULL. If a value is NULL, it returns 0 for that row. In this example, we create a Prism
calculated field (sale_amount_not_null) using the sale_amount field as the basis.
IS_VALID([sale_amount])
Then you can use the sale_amount_not_null Prism calculated field to calculate an accurate average for
sale_amount that excludes NULL values:
SUM([sale_amount])/SUM([sale_amount_not_null])

Instance Functions
CREATE_MULTI_INSTANCE

Description
CREATE_MULTI_INSTANCE is a row function that constructs a Multi-Instance field from one or more
provided Multi-Instance or Instance fields.

Syntax
CREATE_MULTI_INSTANCE(field_name [, field_name])

Return Value
Returns one value per row of type Multi-Instance.

Input Parameters
field_name
Required. A field of type Multi-Instance or Instance. All instance values must use the same
business object.

Examples
Create a Multi-Instance field out of multiple Instance fields:
CREATE_MULTI_INSTANCE([Journal1], [Journal2], [Journal3])
Create a Multi-Instance field out of instance values:

CREATE_MULTI_INSTANCE(
CAST("070b0d082eee44e1928c808cc739b35f" AS
Instance(eecb565181284b6a8ae8b45dc3ed1451)),
CAST("f4c49debb3dc483baa8707dfe683503c" AS
Instance(eecb565181284b6a8ae8b45dc3ed1451))
)

INSTANCE_CONTAINS_ANY

Description
INSTANCE_CONTAINS_ANY is a row function that compares a Multi-Instance or Instance field to either
a Multi-Instance field, an Instance field, or to a list of instance values, and returns True if at least one
instance value exists in the first argument, and False if none of them exist.

Syntax
INSTANCE_CONTAINS_ANY(input_field, comparison_value , [comparison_value])

Return Value
Returns one value per row of type Boolean. This function returns NULL when it receives a Text value that
isn't formatted as a valid instance value (WID format).

Input Parameters
input_field
Required. A field of type Multi-Instance or Instance.
comparison_value
Required. A field of type Multi-Instance or Instance, or a Text value of a valid instance
value.

Examples
Compare the Worktags Multi-Instance field to the Instance fields Cost Center 1 and Cost Center 2:
INSTANCE_CONTAINS_ANY([Worktags], [Cost Center 1],[Cost Center 2])

INSTANCE_COUNT

Description
INSTANCE_COUNT is a row function that returns the total number of instance values in a Multi-Instance or
Instance field. This function returns 0 when the field is empty.

Syntax
INSTANCE_COUNT(field_name)

Return Value
Returns one value per row of type Integer.

Input Parameters
field_name
Required. A field of type Multi-Instance or Instance.

Examples
Count the number of instance values in the Journal Lines Multi-Instance field:
INSTANCE_COUNT([Journal Lines])

INSTANCE_EQUALS

Description
INSTANCE_EQUALS is a row function that compares a Multi-Instance or Instance field to either a Multi-
Instance field, an Instance field, or to a list of instance values, and checks if the first argument exactly
matches the instance values provided in the other arguments.

Syntax
INSTANCE_EQUALS(input_field, comparison_value [, comparison_value])

Return Value
Returns one value per row of type Boolean. This function returns NULL when it receives a Text value that
isn't formatted as a valid instance value (WID format).

Input Parameters
input_field
Required. A field of type Multi-Instance or Instance.
comparison_value
Required. A field of type Multi-Instance or Instance, or a Text value of a valid instance
value.

Examples
Compare the Worktags Multi-Instance field to the Instance fields Cost Center 1 and Cost Center 2:
INSTANCE_EQUALS([Worktags], [Cost Center 1],[Cost Center 2])

INSTANCE_IS_SUPERSET_OF

Description
INSTANCE_IS_SUPERSET_OF is a row function that compares a Multi-Instance field to either a Multi-
Instance field, an Instance field, or to a list of instance values, and returns True if every instance value
exists in the first argument, and False if at least one doesn't exist.

Syntax
INSTANCE_IS_SUPERSET_OF(input_field, comparison_value [, comparison_value])

Return Value
Returns one value per row of type Boolean. This function returns NULL when it receives a Text value that
isn't formatted as a valid instance value (WID format).

Input Parameters
input_field
Required. A field of type Multi-Instance.
comparison_value
Required. A field of type Multi-Instance or Instance, or a Text value of a valid instance
value.

Examples
Compare the Worktags Multi-Instance field to the Instance fields Cost Center 1 and Cost Center 2:

INSTANCE_IS_SUPERSET_OF([Worktags], [Cost Center 1],[Cost Center 2])

Logical Functions
CASE

Description
CASE is a row function that evaluates each row in the dataset according to one or more input conditions,
and outputs the specified result when the input conditions are met.

Syntax
CASE WHEN input_condition [AND|OR input_condition]THEN output_expression [...]
[ELSE other_output_expression] END

Return Value
Returns one value per row of the same type as the output expression. All output expressions must return
the same field type.
If there are multiple output expressions that return different field types, then you will need to enclose your
entire CASE expression in one of the field type conversion functions, such as TO_INT, to explicitly cast all
output values to a particular field type.

Input Parameters
WHEN input_condition
Required. The WHEN keyword is used to specify one or more Boolean expressions (see
the supported conditional operators). If an input value meets the condition, then the output
expression is applied. Input conditions can include other row functions in their expression,
but cannot contain summarization functions or measure expressions. You can use the AND
or OR keywords to combine multiple input conditions.
THEN output_expression
Required. The THEN keyword is used to specify an output expression when the specified
conditions are met. Output expressions can include other row functions in their expression,
but cannot contain summarization functions or measure expressions.
ELSE other_output_expression
Optional. The ELSE keyword can be used to specify an alternate output expression to use
when the specified conditions are not met. If an ELSE expression is not supplied, ELSE
NULL is the default.
END
Required. Denotes the end of CASE function processing.

Examples
Convert values in the age column into range-based groupings (binning):
CASE WHEN [age] <= 25 THEN "0-25" WHEN [age] <= 50 THEN "26-50" ELSE "over 50"
END
Transform values in the gender column from one string to another:
CASE WHEN [gender] = "M" THEN "Male" WHEN [gender] = "F" THEN "Female" ELSE
"Unknown" END
The vehicle column contains the following values: truck, bus, car, scooter, wagon, bike, tricycle, and
motorcycle. The following example converts multiple values in the vehicle column into a single value:

CASE WHEN [vehicle] in ("bike","scooter","motorcycle") THEN "two-wheelers"

ELSE "other" END
Related Information
Reference
Comparison Operators on page 460
Logical Operators on page 461
Arithmetic Operators on page 462

COALESCE

Description
COALESCE is a row function that returns the first valid value (NOT NULL value) from a comma-separated
list of expressions.

Syntax
COALESCE(expression[,expression][,...])

Return Value
Returns one value per row of the same type as the first valid input expression.

Input Parameters
expression
At least one required. A field name or expression.

Examples
The following example shows an expression to calculate employee yearly income for exempt employees
that have a salary and non-exempt employees that have an hourly_wage. This expression checks the
values of both fields for each row, and returns the value of the first expression that is valid (NOT NULL).
COALESCE([hourly_wage] * 40 * 52, [salary])

Math Functions
DIV

Description
DIV is a row function that divides two Long values and returns a quotient value of type Long (the result is
truncated to 0 decimal places).

Syntax
DIV(dividend,divisor)

Return Value
Returns one value per row of type Long.

Input Parameters
dividend
Required. A field or expression of type Long.
divisor

Required. A field or expression of type Long.

Examples
Cast the value of the file_size field to Long and divide by 1024:
DIV(TO_LONG([file_size]),1024)

EXP

Description
EXP is a row function that raises the mathematical constant e to the power (exponent) of a numeric value
and returns a value of type Double.

Syntax
EXP(power)

Return Value
Returns one value per row of type Double.

Input Parameters
power
Required. A field or expression of a numeric type.

Examples
Raise e to the power in the Value field.
EXP([Value])
When the Value field value is 2.0, the result is equal to 7.3890 when truncated to four decimal places.

FLOOR

Description
FLOOR is a row function that returns the largest integer that is less than or equal to the input argument.

Syntax
FLOOR(double)

Return Value
Returns one value per row of type Double.

Input Parameters
double
Required. A field or expression of type Double.

Examples
Return the floor value of 32.6789:
FLOOR(32.6789) returns 32.0

HASH

Description
HASH is a row function that evenly partitions data values into the specified number of buckets. It creates a
hash of the input value and assigns that value a bucket number. Equal values will always hash to the same
bucket number.

Syntax
HASH(field_name,integer)

Return Value
Returns one value per row of type Integer corresponding to the bucket number that the input value
hashes to.

Input Parameters
field_name
Required. The name of the field whose values you want to partition. When this value is
NULL and the integer parameter is a value other than zero or NULL, the function returns
zero, otherwise it returns NULL.
integer
Required. The desired number of buckets. This parameter can be a numeric value of any
field type, but when it is a non-integer value, the value is truncated to an integer. When the
value is zero or NULL, the function returns NULL. When the value is negative, the function
uses absolute value.

Examples
Partition the values of the username field into 20 buckets:
HASH([username],20)

Description
LN is a row function that returns the natural logarithm of a number. The natural logarithm is the logarithm to
the base e, where e (Euler's number) is a mathematical constant approximately equal to 2.718281828. The
natural logarithm of a number x is the power to which the constant e must be raised in order to equal x.

Syntax
LN(positive_number)

Return Value
Returns the exponent to which base e must be raised to obtain the input value, where e denotes the
constant number 2.718281828. The return value is the same field type as the input value.
For example, LN(7.389) is 2, because e to the power of 2 is approximately 7.389.

Input Parameters
positive_number
Required. A field or expression that returns a number greater than 0. Inputs can be of type
Integer, Long, Double.

Examples
Return the natural logarithm of base number e, which is approximately 2.718281828:
LN(2.718281828) returns 1
LN(3.0000) returns 1.098612
LN(300.0000) returns 5.703782

MOD

Description
MOD is a row function that divides two Long values and returns the remainder value of type Long (the
result is truncated to 0 decimal places).

Syntax
MOD(dividend,divisor)

Return Value
Returns one value per row of type Long.

Input Parameters
dividend
Required. A field or expression of type Long.
divisor
Required. A field or expression of type Long.

Examples
Cast the value of the file_size field to Long and divide by 1024:
MOD(TO_LONG([file_size]),1024)

POW

Description
POW is a row function that raises the a numeric value to the power (exponent) of another numeric value and
returns a value of type Double.

Syntax
POW(index,power)

Return Value
Returns one value per row of type Double.

Input Parameters
index
Required. A field or expression of a numeric type.
power
Required. A field or expression of a numeric type.

Examples
Calculate the compound annual growth rate (CAGR) percentage for a given investment over a five year
span.
100 * POW([end_value]/[start_value], 0.2) - 1
Calculate the square of the Value field.
POW([Value],2)
Calculate the square root of the Value field.
POW([Value],0.5)
The following expression returns 1.
POW(0,0)

ROUND

Description
ROUND is a row function that rounds a numeric value to the specified number of decimal places and returns
a value of type Double.

Syntax
ROUND(numeric_expression,number_decimal_places)

Return Value
Returns one value per row of type Double.

Input Parameters
numeric_expression
Required. A field or expression of any numeric type.
number_decimal_places
Required. An integer that specifies the number of decimal places to round to.

Examples
Round the number 32.4678954 to two decimal places:
ROUND(32.4678954,2) returns 32.47

Text Functions
CIDR_MATCH

Description
CIDR_MATCH is a row function that compares two Text arguments representing a CIDR mask and an IP
address, and returns 1 if the IP address falls within the specified subnet mask or 0 if it does not.

Syntax
CIDR_MATCH(CIDR_string, IP_string)

Return Value
Returns an Integer value of 1 if the IP address falls within the subnet indicated by the CIDR mask and 0
if it does not.

Input Parameters
CIDR_string
Required. A field or expression that returns a Text value containing either an IPv4 or IPv6
CIDR mask (Classless InterDomain Routing subnet notation). An IPv4 CIDR mask can
only successfully match IPv4 addresses, and an IPv6 CIDR mask can only successfully
match IPv6 addresses.
IP_string
Required. A field or expression that returns a Text value containing either an IPv4 or IPv6
internet protocol (IP) address.

Examples
Compare an IPv4 CIDR subnet mask to an IPv4 IP address:
CIDR_MATCH("60.145.56.0/24","60.145.56.246") returns 1
CIDR_MATCH("60.145.56.0/30","60.145.56.246") returns 0
Compare an IPv6 CIDR subnet mask to an IPv6 IP address:
CIDR_MATCH("fe80::/70","FE80::0202:B3FF:FE1E:8329") returns 1
CIDR_MATCH("fe80::/72","FE80::0202:B3FF:FE1E:8329") returns 0

CONCAT

Description
CONCAT is a row function that returns a Text by concatenating (combining together) the results of multiple
Text expressions.

Syntax
CONCAT(value_expression[,value_expression][,...])

Return Value
Returns one value per row of type Text.

Input Parameters
value_expression
At least one required. A field name of any type, a literal string or number, or an expression
that returns any value.

Examples
Combine the values of the month, day, and year fields into a single date field formatted as MM/DD/YYYY.
CONCAT([month],"/",[day],"/",[year])

EXTRACT_COOKIE

Description
EXTRACT_COOKIE is a row function that extracts the value of the given cookie identifier from a semi-colon
delimited list of cookie key/value pairs. This function can be used to extract a particular cookie value from a
combined web access log Cookie column.

Syntax
EXTRACT_COOKIE("cookie_list_string",cookie_key_string)

Return Value
Returns the value of the specified cookie key as type Text.

Input Parameters
cookie_list_string
Required. A field of type Text or literal string that has a semi-colon delimited list of cookie
key=value pairs.
cookie_key_string
Required. The cookie key name for which to extract the cookie value.

Examples
Extract the value of the vID cookie from a literal cookie string:
EXTRACT_COOKIE("SSID=ABC; vID=44", "vID") returns 44
Extract the value of the vID cookie from a field named Cookie:
EXTRACT_COOKIE([Cookie],"vID")

EXTRACT_VALUE

Description
EXTRACT_VALUE is a row function that extracts the value for the given key from a string containing
delimited key/value pairs.

Syntax
EXTRACT_VALUE(string,key_name [,delimiter], [pair_delimiter])

Return Value
Returns the value of the specified key as type Text.

Input Parameters
string
Required. A field of type Text or literal string that contains a delimited list of key/value
pairs.
key_name
Required. The key name for which to extract the value.
delimiter
Optional. The delimiter used between the key and the value. If not specified, the value
u0003 is used. This is the Unicode escape sequence for the start of text character.

pair_delimiter
Optional. The delimiter used between key/value pairs when the input string contains more
than one key/value pair. If not specified, the value u0002 is used. This is the Unicode
escape sequence for the end of text character.

Examples
Extract the value of the lastname key from a literal string of key/value pairs:
EXTRACT_VALUE("firstname;daria|lastname;hutch","lastname",";","|") returns
hutch
Extract the value of the email key from a Text field named contact_info that contains strings in the format
of key:value,key:value:
EXTRACT_VALUE([contact_info],"email",":",",")
Related Information
Reference
PACK_VALUES on page 498

FILE_NAME

Description
FILE_NAME is a row function that returns the original file name from the source file system. This is useful
when the source data that comprises a dataset comes from multiple files, and there is useful information in
the file names themselves (such as dates or server names). You can use FILE_NAME in combination with
other text processing functions to extract useful information from the file name.

Syntax
FILE_NAME()

Return Value
Returns one value per row of type Text.

Examples
Your dataset is based on daily log files that use an 8 character date as part of the file name. For example,
20120704.log is the file name used for the log file created on July 4, 2012. The following expression uses
FILE_NAME in combination with SUBSTRING and TO_DATE to create a date field from the first 8 characters
of the file name.
TO_DATE(SUBSTRING(FILE_NAME(),0,8),"yyyyMMdd")
Your dataset is based on log files that use the server IP address as part of the file name. For example,
172.12.131.118.log is the log file name for server 172.12.131.118. The following expression uses
FILE_NAME in combination with REGEX to extract the IP address from the file name.
REGEX(FILE_NAME(),"(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})\.log")

HEX_TO_IP

Description
HEX_TO_IP is a row function that converts a hexadecimal-encoded Text value to a text representation of
an IP address.

Syntax
HEX_TO_IP(string)

Return Value
Returns a value of type Text representing either an IPv4 or IPv6 address. The type of IP address returned
depends on the input string. An 8 character hexadecimal string returns an IPv4 address. A 32 character
long hexadecimal string returns an IPv6 address.
IPv6 addresses are represented in full length, without removing any leading zeros and without using the
compressed :: notation. For example, 2001:0db8:0000:0000:0000:ff00:0042:8329 rather than
2001:db8::ff00:42:8329.
Input strings that don't contain either 8 or 32 valid hexadecimal characters return NULL.

Input Parameters
string
Required. A field or expression that returns a hexadecimal-encoded Text value. The
hexadecimal string must be either 8 characters long (in which case it's converted to an
IPv4 address) or 32 characters long (in which case it's converted to an IPv6 address).

Examples
Return a plain text IP address for each hexadecimal-encoded string value in the byte_encoded_ips
column:
HEX_TO_IP([byte_encoded_ips])
Convert an 8 character hexadecimal-encoded string to a plain text IPv4 address:
HEX_TO_IP(AB20FE01) returns 171.32.254.1
Convert a 32 character hexadecimal-encoded string to a plain text IPv6 address:
HEX_TO_IP(FE800000000000000202B3FFFE1E8329) returns
fe80:0000:0000:0000:0202:b3ff:fe1e:8329

INSTR

Description
INSTR is a row function that returns an integer indicating the position of a character within a string that is
the first character of the occurrence of a substring. The INSTR function is similar to the FIND function in
Excel, except that the first letter is position 0 and the order of the arguments is reversed.

Syntax
INSTR(search_string,substring,position,occurrence)

Return Value
Returns one value per row of type Integer. The first position is indicated with the value of zero (0).

Input Parameters
search_string
Required. The name of a field or expression of type Text (or a literal string).
substring

Required. A literal string or name of a field that specifies the substring to search for in
search_string. Note that to search for the double quotation mark ( " ) as a literal string, you
must escape it with another double quotation mark: ""
position
Optional. An integer that specifies at which character in search_string to start searching
for substring. A value of 0 (zero) starts the search at the beginning of search_string. Use a
positive integer to start searching from the beginning of search_string, and use a negative
integer to start searching from the end of search_string. When no position is specified,
INSTR searches at the beginning of the string (0).
occurrence
Optional. A positive integer that specifies which occurrence of substring to search for.
When no occurrence is specified, INSTR searches for the first occurrence of the substring
(1).

Examples
Return the position of the first occurrence of the substring "http://" starting at the end of the url field:
INSTR([url],"http://",-1,1)
The following expression searches for the second occurrence of the substring "st" starting at the beginning
of the string "bestteststring". INSTR finds that the substring starts at the seventh character in the string, so
it returns 6:
INSTR("bestteststring","st",0,2)
The following expression searches backward for the second occurrence of the substring "st" starting at 7
characters before the end of the string "bestteststring". INSTR finds that the substring starts at the third
character in the string, so it returns 2:
INSTR("bestteststring","st",-7,2)

JAVA_STRING

Description
JAVA_STRING is a row function that returns the unescaped version of a Java unicode character escape
sequence as a Text value. This is useful when you want to specify unicode characters in an expression.
For example, you can use JAVA_STRING to specify the unicode value representing a control character.

Syntax
JAVA_STRING(unicode_escape_sequence)

Return Value
Returns the unescaped version of the specified unicode character, one value per row of type Text.

Input Parameters
unicode_escape_sequence
Required. A Text value containing a unicode character expressed as a Java unicode
escape sequence. Unicode escape sequences consist ofa backslash '\' (ASCII character
92, hex 0x5c), a 'u' (ASCII 117, hex 0x75), optionally one or more additional 'u' characters,
and four hexadecimal digits (the characters '0' through '9' or 'a' through 'f' or 'A' through
'F'). Such sequences represent the UTF-16 encoding of a Unicode character. For example,
the letter 'a' is equivalent to '\u0061'.

Examples
Evaluates whether the currency field is equal to the yen symbol.
CASE WHEN [currency] == JAVA_STRING("\u00a5") THEN "yes" ELSE "no" END

JOIN_STRINGS

Description
JOIN_STRINGS is a row function that returns a Text by concatenating (combining together) the results of
multiple Text values with the separator in between each non-null value.

Syntax
JOIN_STRINGS(separator,value_expression, [value_expression][,...])

Return Value
Returns one value per row of type Text.

Input Parameters
separator
Required. A field name of type Text, a literal string, or an expression that returns a Text.
value_expression
At least one required. A field name of any type, a literal string or number, or an expression
that returns any value.

Examples
Combine the values of the month, day, and year fields into a single date field formatted as MM/DD/YYYY.
JOIN_STRINGS("/",[month],[day],[year])
The following expression returns NULL:
JOIN_STRINGS("+",NULL,NULL,NULL)
The following expression returns a+b:
JOIN_STRINGS("+","a","b",NULL)

JSON_DECIMAL

Description
JSON_DECIMAL is a row function that extracts a Numeric value from a field in a JSON object.

Syntax
JSON_DECIMAL(json_string, "json_field")

Return Value
Returns one value per row of type Numeric.

Input Parameters
json_string
Required. The name of a field or expression of type Text (or a literal string) that contains a
valid JSON object.

json_field
Required. The key or name of the field value you want to extract.
For top-level fields, specify the name identifier (key) of the field.
To access fields within a nested object, specify a dot-separated path of field names (for
example top_level_field_name.nested_field_name).
To extract a value from an array, specify the dot-separated path of field names and the
array position starting at 0 for the first value in an array, 1 for the second value, and so on
(for example, field_name.0).
If the name identifier contains dot or period characters within the name itself,
escape the name by enclosing it in brackets (for example, [field.name.with.dot].
[another.dot.field.name]
If the field name is null (empty), use brackets with nothing in between as the identifier, for
example [].

Examples
If you had a top_scores field that contained a JSON object formatted like this (with the values contained in
an array):
{"practice_scores":["538.67","674.99","1021.52"], "test_scores":
["753.21","957.88","1032.87"]}
You could extract the third value of the test_scores array using the expression, which returns "1032.87":
JSON_DECIMAL([top_scores],"test_scores.2")

JSON_DOUBLE

Description
JSON_DOUBLE is a row function that extracts a Double value from a field in a JSON object.

Syntax
JSON_DOUBLE(json_string, "json_field")

Return Value
Returns one value per row of type Double.

If the name identifier contains dot or period characters within the name itself,
escape the name by enclosing it in brackets (for example, [field.name.with.dot].
[another.dot.field.name]
If the field name is null (empty), use brackets with nothing in between as the identifier, for
example [].

JSON_INTEGER

Description
JSON_INTEGER is a row function that extracts an Integer value from a field in a JSON object.

Syntax
JSON_INTEGER(json_string, "json_field")

Return Value
Returns one value per row of type Integer.

Input Parameters
json_string
Required. The name of a field or expression of type Text (or a literal string) that contains a
valid JSON object.
json_field
Required. The key or name of the field value you want to extract.
For top-level fields, specify the name identifier (key) of the field.
To access fields within a nested object, specify a dot-separated path of field names (for
example top_level_field_name.nested_field_name).
To extract a value from an array, specify the dot-separated path of field names and the
array position starting at 0 for the first value in an array, 1 for the second value, and so on
(for example, field_name.0).
If the name identifier contains dot or period characters within the name itself,
escape the name by enclosing it in brackets (for example, [field.name.with.dot].
[another.dot.field.name]
If the field name is null (empty), use brackets with nothing in between as the identifier, for
example [].

Examples
If you had an address field that contained a JSON object formatted like this:
{"street_address":"123 B Street", "city":"San Mateo", "state":"CA",
"zip_code":"94403"}

You could extract the zip_code value using the expression, which returns "94403":
JSON_INTEGER([address],"zip_code")
If you had a top_scores field that contained a JSON object formatted like this (with the values contained in
an array):
{"practice_scores":["538","674","1021"], "test_scores":["753","957","1032"]}
You could extract the third value of the test_scores array using the expression, which returns "1032":
JSON_INTEGER([top_scores],"test_scores.2")

JSON_LONG

Description
JSON_LONG is a row function that extracts a Long value from a field in a JSON object.

Syntax
JSON_LONG(json_string, "json_field")

Return Value
Returns one value per row of type Long.

Examples
If you had a top_scores field that contained a JSON object formatted like this (with the values contained in
an array):
{"practice_scores":["538","674","1021"], "test_scores":["753","957","1032"]}
You could extract the third value of the test_scores array using the expression, which returns "1032":
JSON_LONG([top_scores],"test_scores.2")

JSON_STRING

Description
JSON_STRING is a row function that extracts a Text value from a field in a JSON object.

Syntax
JSON_STRING(json_string, "json_field")

Return Value
Returns one value per row of type Text.

Examples
If you had an address field that contained a JSON object formatted like this:
{"street_address":"123 B Street", "city":"San Mateo", "state":"CA",
"zip":"94403"}
You could extract the state value using the expression:
JSON_STRING([address],"state")
If you had a misc field that contained a JSON object formatted like this (with the values contained in an
array):
{"hobbies":["sailing","hiking","cooking"], "interests":
["art","music","travel"]}
You could extract the first value of the hobbies array using the expression, which returns "sailing":
JSON_STRING([misc],"hobbies.0")

LENGTH

Description
LENGTH is a row function that returns the count of characters in a Text value.

Syntax
LENGTH(string_expression)

Return Value
Returns one value per row of type Integer.

Input Parameters
string_expression
Required. The name of a field or expression of type Text (or a literal string).

Examples
Return count of characters from values in the name field. For example, the value Bob would return a length
of 3, Julie would return a length of 5, and so on:
LENGTH([name])

PACK_VALUES

Description
PACK_VALUES is a row function that returns multiple output values packed into a single string of key/
value pairs separated by the default key and pair separators. The string returned is in a format that can be
read by the EXTRACT_VALUE function. PACK_VALUES uses the same key and pair separator values that
EXTRACT_VALUE uses (the Unicode escape sequences u0003 and u0002, respectively).

Syntax
PACK_VALUES(key,value[,key,value][,...])

Return Value
Returns one value per row of type Text. If the value for either key or value of a pair is null or contains
either of the separator values, the full key/value pair is omitted from the return value.
The key separator is u0003, which is the Unicode escape sequence for the start of text character.
The pair separator is u0002, which is the Unicode escape sequence for the end of text character.

Input Parameters
key
At least one required. A field name of any type, a literal string or number, or an expression
that returns any value.
value
At least one required. A field name of any type, a literal string or number, or an expression
that returns any value. The expression must include one value instance for each key
instance.

Examples
Combine the values of the [custid] and [age] fields into a single text field.
PACK_VALUES("ID", [custid], "Age", [age])
This expression returns ID\u00035555\u0002Age\u000329 when the value of the [custid] field is 5555
and the value of the [age] field is 29:
PACK_VALUES("ID", [custid], "Age", [age])

This expression returns Age\u000329 when the value of the [age] field is 29:
PACK_VALUES("ID", NULL, "Age", [age])
This expression returns 29 as a Text value when the [age] field is an Integer and its value is 29:
EXTRACT_VALUE(PACK_VALUES("ID", [custid], "Age", [age]), "Age")
Related Information
Reference
EXTRACT_VALUE on page 489

REGEX

Description
REGEX is a row function that performs a whole string match against a Text value with a regular expression
and returns the portion of the string matching the first capturing group of the regular expression.

Syntax
REGEX(string_expression,"regex_matching_pattern")

Return Value
Returns the matched Text value of the first capturing group of the regular expression. If there is no match,
returns NULL.

Input Parameters
string_expression
Required. The name of a field or expression of type Text (or a literal string).
regex_matching_pattern
Required. A regular expression pattern based on the regular expression pattern matching
syntax of the Java programming language. To return a non-NULL value, the regular
expression pattern must match the entire Text value.

Regular Expression Constructs

See the Regular Expression Reference for information on the constructs used for defining a regular
expression matching pattern.

Capturing and Non-Capturing Groups

Groups are specified by a pair of parenthesis around a subpattern in the regular expression. A pattern can
have more than one group and the groups can be nested. The groups are numbered 1-n from left to right,
starting with the first opening parenthesis. There is always an implicit group 0, which contains the entire
match. For example, the pattern:

(a(b*))+(c)

contains three groups:

group 1: (a(b*))
group 2: (b*)
group 3: (c)

Capturing Groups

By default, a group captures the text that produces a match, and only the most recent match is captured.
The REGEX function returns the string that matches the first capturing group in the regular expression. For
example, if the input string to the expression above was abc, the entire REGEX function would match to
abc, but only return the result of group 1, which is ab.
Non-Capturing Groups
In some cases, you may want to use parenthesis to group subpatterns, but not capture text. A non-
capturing group starts with (?: (a question mark and colon following the opening parenthesis). For
example, h(?:a|i|o)t matches hat or hit or hot, but does not capture the a, i, or o from the
subexpression.

Examples
Match all possible email addresses with a pattern of [email protected], but only return the
provider portion of the email address from the email field:

REGEX([email],"^[a-zA-Z0-9._%+-]+@([a-zA-Z0-9._-]+)\.[a-zA-Z]{2,4}$")

Match the request line of a web log, where the value is in the format of:
GET /some_page.html HTTP/1.1
and return just the requested HTML page names:
REGEX(weblog.request_line,"GET\s/([a-zA-Z0-9._%-]+\.[html])\sHTTP/[0-9.]+")
Extract the inches portion from a height field where example values are 6'2", 5'11" (notice the
escaping of the literal quote with a double double-quote):

REGEX([height], "\d\'(\d)+""")

Extract all of the contents of the device field when the value is either iPod, iPad, or iPhone:

REGEX([device],"(iP[ao]d|iPhone)")

Related Information
Concepts
Concept: Regular Expressions in Prism on page 535
Reference
Regex Literal and Special Characters on page 536
Regex Character Classes on page 537
Regex Line and Word Boundaries on page 538
Regex Quantifiers on page 539
Regex Capturing Groups on page 540

REGEX_REPLACE

Description
REGEX_REPLACE is a row function that evaluates a Text value against a regular expression to determine
if there is a match, and replaces matched strings with the specified replacement value.

Syntax
REGEX_REPLACE(string_expression,"regex_match_pattern","regex_replace_pattern")

Return Value
Returns the regex_replace_pattern as a Text value when regex_match_pattern produces
a match. If there is no match, returns the value of string_expression as a Text.

Input Parameters
string_expression
Required. The name of a field or expression of type Text (or a literal string).
regex_match_pattern
Required. A string literal or regular expression pattern based on the regular expression
pattern matching syntax of the Java programming language. You can use capturing groups
to create backreferences that can be used in the regex_replace_pattern . You
might want to use a string literal to make a case-sensitive match. For example, when
you enter jane as the match value, the function matches jane but not Jane. The function
matches all occurrences of a string literal in the string expression.
regex_replace_pattern
Required. A string literal or regular expression pattern based on the regular expression
pattern matching syntax of the Java programming language. You can refer to
backreferences from the regex_match_pattern using the syntax $n (where n is
the group number).

Regular Expression Constructs

See the Regular Expression Reference for information on the constructs used for defining a regular
expression matching pattern.

Examples
Match the values in a phone_number field where phone number values are formatted as xxx.xxx.xxxx
and replace them with phone number values formatted as (xxx) xxx-xxxx:
REGEX_REPLACE([phone_number],"([0-9]{3})\.([[0-9]]{3})\.([[0-9]]{4})","$$1$
$2-$3")
Match the values in a name field where name values are formatted as firstname lastname and
replace them with name values formatted as lastname, firstname:
REGEX_REPLACE([name],"(.*) (.*)","$2, $1")
Match the string literal mrs in a title field and replace it with the string literal Mrs.
REGEX_REPLACE([title],"mrs","Mrs")
Related Information
Concepts
Concept: Regular Expressions in Prism on page 535
Reference
Regex Literal and Special Characters on page 536
Regex Character Classes on page 537
Regex Line and Word Boundaries on page 538
Regex Quantifiers on page 539
Regex Capturing Groups on page 540

REVERSE

Description
REVERSE is a row function that returns the characters of a string value in the opposite order.

Syntax
REVERSE(string_expression)

Return Value
Returns one value per row of type Text.

Input Parameters
string_expression
Required. The name of a field or expression of type Text (or a literal string).

Examples
Return the string 123 Main Street in reverse order:

REVERSE("123 Main Street")

Returns teertS niaM 321.

SUBSTRING

Description
SUBSTRING is a row function that returns the specified characters of a Text value based on the given start
and optional end position.

Syntax
SUBSTRING(search_string,start,end)

Return Value
Returns one value per row of type Text.

Input Parameters
search_string
Required. The name of a field or expression of type Text (or a literal string).
start
Required. An integer that specifies where the returned characters start (inclusive), with 0
being the first character of the string. If start is greater than the number of characters, then
an empty string is returned. If start is greater than end, then an empty string is returned.
end
Optional. A positive integer that specifies where the returned characters end (exclusive),
with the end character not being part of the return value. If end is greater than the number
of characters, or is not specified, then the whole string value (from start) is returned.

Examples
Return the first letter of the name field:

SUBSTRING([name],0,1)

TO_LOWER

Description
TO_LOWER is a row function that converts all alphabetic characters in a Text value to lower case.

Syntax
TO_LOWER(string_expression)

Return Value
Returns one value per row of type Text.

Input Parameters
string_expression
Required. The name of a field or expression of type Text (or a literal string).

Examples
Return the literal input string 123 Main Street in all lower case letters:
TO_LOWER("123 Main Street") returns 123 main street

TO_PROPER

Description
TO_PROPER is a row function that returns a Text value with the first letter of each word capitalized.

Syntax
TO_PROPER(string_expression)

Return Value
Returns one value per row of type Text.

Input Parameters
string_expression
Required. The name of a field or expression of type Text (or a literal string).

Examples
TO_PROPER("123 Alameda de las Pulgas, San Mateo CA")
Returns 123 Alameda De Las Pulgas, San Mateo Ca

TO_UPPER

Description
TO_UPPER is a row function that converts all alphabetic characters in a Text value to upper case.

Syntax
TO_UPPER(string_expression)

Return Value
Returns one value per row of type Text.

Input Parameters
string_expression
Required. The name of a field or expression of type Text (or a literal string).

Examples
TO_UPPER("123 Main Street")
Returns 123 MAIN STREET

TRIM

Description
TRIM is a row function that removes leading and trailing spaces from a Text value.

Syntax
TRIM(string_expression)

Return Value
Returns one value per row of type Text.

Input Parameters
string_expression
Required. The name of a field or expression of type Text (or a literal string).

Examples
Return the value of the area_code field without any leading or trailing spaces. Example:

TRIM([area_code])

TRIM(" 650 ") returns 650.

TRIM(" 650 123-4567 ") returns 650 123-4567. Note that the extra spaces in the middle of the
string aren't removed, only the spaces at the beginning and end of the string.

XPATH_STRING

Description
XPATH_STRING is a row function that takes XML and returns the first string matching the given XPath
expression.

Syntax
XPATH_STRING(xml_expression,"xpath_expression")

Return Value
Returns one value per row of type Text.
If the XPath expression matches more than one string in the given XML node, this function will return the
first match only. To return all matches, use XPATH_STRINGS instead.

Input Parameters
xml_expression
Required. The name of a field of type Text or a literal string that contains a valid XML
node (a snippet of XML consisting of a parent element and one or more child nodes).
xpath_expression
Required. An XPath expression that refers to a node, element, or attribute within the XML
string passed to this expression. Any XPath expression that complies to the XML Path
Language (XPath) Version 1.0 specification is valid.

Examples
These example XPATH_STRING expressions assume you have a field in your dataset named address that
contains XML-formatted strings such as this:

<list>
<address type="work">
<street1>1300 So. El Camino Real</street1>
<street2>Suite 600</street2>
<city>San Mateo</city>
<state>CA</state>
<zipcode>94403</zipcode>
</address>
<address type="home">
<street1>123 Oakdale Street</street1>
<street2/>
<city>San Francisco</city>
<state>CA</state>
<zipcode>94123</zipcode>
</address>
</list>

Get the zipcode value from any address element where the type attribute equals home:
XPATH_STRING([address],"//address[@type='home']/zipcode")
returns: 94123
Get the city value from the second address element:
XPATH_STRING([address],"/list/address[2]/city")
returns: San Francisco
Get the values from all child elements of the first address element (as one string):
XPATH_STRING([address],"/list/address")
returns: 1300 So. El Camino RealSuite 600 San MateoCA94403

URL Functions
URL_AUTHORITY

Description
URL_AUTHORITY is a row function that returns the authority portion of a URL string. The authority portion
of a URL is the part that has the information on how to locate and connect to the server.

Syntax
URL_AUTHORITY(URL_string)

Return Value
Returns the authority portion of a URL as a Text value, or NULL if the input string is not a valid URL.
For example, in the string http://www.workday.com/company/contact.html, the authority portion
is www.workday.com.
In the string http://user:[email protected]:8012/mypage.html, the authority portion is
user:[email protected]:8012.
In the string mailto:[email protected]?subject=Topic, the authority portion is NULL.

Input Parameters
URL_string
Required. A field or expression that returns a Text value in URI (uniform resource
identifier) format of: protocol:authority[/path][?query][#fragment].
The authority portion of the URL contains the host information, which can be specified
as a domain name (www.workday.com), a host name (localhost), or an IP address
(127.0.0.1). The host information can be preceeded by optional user information
terminated with @ (for example, username:[email protected]), and followed by
an optional port number preceded by a colon (for example, localhost:8001).

Examples
Return the authority portion of URL string values in the referrer field:
URL_AUTHORITY([referrer])
Return the authority portion of a literal URL string:
URL_AUTHORITY("http://user:[email protected]:8012/mypage.html") returns
user:[email protected]:8012.

URL_FRAGMENT

Description
URL_FRAGMENT is a row function that returns the fragment portion of a URL string.

Syntax
URL_FRAGMENT(URL_string)

Return Value
Returns the fragment portion of a URL as a Text value, NULL if the URL or does not contain a fragment,
or NULL if the input string is not a valid URL.
For example, in the string http://www.workday.com/contact.html#phone, the fragment portion is
phone.
In the string http://www.workday.com/contact.html, the fragment portion is NULL.
In the string http://workday.com/news.php?topic=press#Workday%20News, the fragment
portion is Workday%20News.

Input Parameters
URL_string
Required. A field or expression that returns a Text value in URI (uniform resource
identifier) format of: protocol:authority[/path][?query][#fragment].

The optional fragment portion of the URL is separated by a hash mark (#) and provides
direction to a secondary resource, such as a heading or anchor identifier.

Examples
Return the fragment portion of URL string values in the request field:
URL_FRAGMENT([request])
Return the fragment portion of a literal URL string:
URL_FRAGMENT("http://workday.com/news.php?topic=press#Workday%20News") returns
Workday%20News.
Return and decode the fragment portion of a literal URL string:
URLDECODE(URL_FRAGMENT("http://workday.com/news.php?topic=press#Workday
%20News")) returns Workday News.

URL_HOST

Description
URL_HOST is a row function that returns the host, domain, or IP address portion of a URL string.

Syntax
URL_HOST(URL_string)

Return Value
Returns the host portion of a URL as a Text value, or NULL if the input string is not a valid URL.
For example, in the string http://www.workday.com/company/contact.html, the host portion is
www.workday.com.
In the string http://admin:[email protected]:8001/index.html, the host portion is 127.0.0.1.
In the string mailto:[email protected]?subject=Topic, the host portion is NULL.

Examples
Return the host portion of URL string values in the referrer field:
URL_HOST([referrer])
Return the host portion of a literal URL string:
URL_HOST("http://user:[email protected]:8012/mypage.html") returns
mycompany.com.

URL_PATH

Description
URL_PATH is a row function that returns the path portion of a URL string.

Syntax
URL_PATH(URL_string)

Return Value
Returns the path portion of a URL as a Text value, NULL if the URL or does not contain a path, or NULL if
the input string is not a valid URL.
For example, in the string http://www.workday.com/company/contact.html, the path portion is /
company/contact.html.
In the string http://admin:[email protected]:8001/index.html, the path portion is /
index.html.
In the string mailto:[email protected]?subject=Topic, the path portion is
[email protected].

Input Parameters
URL_string
Required. A field or expression that returns a Text value in URI (uniform resource
identifier) format of: protocol:authority[/path][?query][#fragment].
The optional path portion of the URL is a sequence of resource location segments
separated by a forward slash (/), conceptually similar to a directory path.

Examples
Return the path portion of URL string values in the request field:
URL_PATH([request])
Return the path portion of a literal URL string:
URL_PATH("http://workday.com/company/contact.html") returns /company/contact.html.

URL_PORT

Description
URL_PORT is a row function that returns the port portion of a URL string.

Syntax
URL_PORT(URL_string)

Return Value
Returns the port portion of a URL as an Integer value. If the URL does not specify a port, then returns
-1. If the input string is not a valid URL, returns NULL.
For example, in the string http://localhost:8001, the port portion is 8001.

Input Parameters
URL_string

Required. A field or expression that returns a Text value in URI (uniform resource
identifier) format of: protocol:authority[/path][?query][#fragment].
The authority portion of the URL contains the host information, which can be specified
as a domain name (www.workday.com), a host name (localhost), or an IP address
(127.0.0.1). The host information can be followed by an optional port number preceded
by a colon (for example, localhost:8001).

Examples
Return the port portion of URL string values in the referrer field:
URL_PORT([referrer])
Return the port portion of a literal URL string:
URL_PORT("http://user:[email protected]:8012/mypage.html") returns 8012.

URL_PROTOCOL

Description
URL_PROTOCOL is a row function that returns the protocol (or URI scheme name) portion of a URL string.

Syntax
URL_PROTOCOL(URL_string)

Return Value
Returns the protocol portion of a URL as a Text value, or NULL if the input string is not a valid URL.
For example, in the string http://www.workday.com, the protocol portion is http.
In the string ftp://ftp.workday.com/articles/workday.pdf, the protocol portion is ftp.

Input Parameters
URL_string
Required. A field or expression that returns a Text value in URI (uniform resource
identifier) format of: protocol:authority[/path][?query][#fragment]
The protocol portion of a URL consists of a sequence of characters beginning with a letter
and followed by any combination of letter, number, plus (+), period (.), or hyphen (-)
characters, followed by a colon (:). For example: http:, ftp:, mailto:

Examples
Return the protocol portion of URL string values in the referrer field:
URL_PROTOCOL([referrer])
Return the protocol portion of the literal URL string:
URL_PROTOCOL("http://www.workday.com") returns http.

URL_QUERY

Description
URL_QUERY is a row function that returns the query portion of a URL string.

Syntax
URL_QUERY(URL_string)

Return Value
Returns the query portion of a URL as a Text value, NULL if the URL or does not contain a query, or NULL
if the input string is not a valid URL.
For example, in the string http://www.workday.com/contact.html, the query portion is NULL.
In the string http://workday.com/news.php?topic=press&timeframe=today#Workday
%20News, the query portion is topic=press&timeframe=today.
In the string mailto:[email protected]?subject=Topic, the query portion is
subject=Topic.

Input Parameters
URL_string
Required. A field or expression that returns a Text value in URI (uniform resource
identifier) format of: protocol:authority[/path][?query][#fragment].
The optional query portion of the URL is separated by a question mark (?) and typically
contains an unordered list of key=value pairs separated by an ampersand (&) or
semicolon (;).

Examples
Return the query portion of URL string values in the request field:
URL_QUERY([request])
Return the query portion of a literal URL string:
URL_QUERY("http://workday.com/news.php?topic=press&timeframe=today") returns
topic=press&timeframe=today.

URLDECODE

Description
URLDECODE is a row function that decodes a Text value that has been encoded with the application/
x-www-form-urlencoded media type. URL encoding, also known as percent-encoding, is a mechanism
for encoding information in a Uniform Resource Identifier (URI). When sent in an HTTP GET request,
application/x-www-form-urlencoded data is included in the query component of the request URI.
When sent in an HTTP POST request, the data is placed in the body of the message, and the name of the
media type is included in the message Content-Type header.

Syntax
URLDECODE(URL_string)

Return Value
Returns a value of type Text with characters decoded as follows:
• Alphanumeric characters (a-z, A-Z, 0-9) remain unchanged.
• The special characters hyphen (-), comma (,), underscore (_), period (.), and asterisk (*) remain
unchanged.
• The plus sign (+) character is converted to a space character.

• The percent character (%) is interpreted as the start of a special escaped sequence, where in
the sequence %HH , HH represents the hexadecimal value of the byte. Some common escape
sequences:

Percent Encoding Sequence Value

%20 space
%0A or %0D or %0D%0A newline
%22 double quote (")
%25 percent (%)
%2D hyphen (-)
%2E period (.)
%3C less than (<)
%3D greater than (>)
%5C backslash (\)
%7C pipe (|)

Input Parameters
URL_string
Required. A field or expression that returns a Text value. It is assumed that all characters
in the input string are one of the following: lower-case letters (a-z), upper-case letters
(A-Z), numeric digits (0-9), or the hyphen (-), comma (,), underscore (_), period (.) or
asterisk (*) character. The percent character (%) is allowed, but is interpreted as the start
of a special escaped sequence. The plus character (+) is allowed, but is interpreted as a
space character.

Examples
Decode the values of the url_query field:
URLDECODE([url_query])
Convert a literal URL encoded string (N%2FA%20or%20%22not%20applicable%22) to a human-
readable value:
URLDECODE("N%2FA%20or%20%22not%20applicable%22") returns N/A or "not applicable".

Window Functions
AVG

Description
AVG is a window aggregate function that partitions rows into groups, orders rows by a field, and returns the
average of all valid numeric values in the group. It sums all values in the group and divides by the number
of valid (NOT NULL) rows. You can use AVG to calculate moving averages.
The PARTITION BY clause determines which fields to use to partition a set of input rows into groups. The
ORDER BY clause determines how to order the rows in the partition.
Workday separates the input rows into groups according to the partitioning fields, orders the rows
according to the ordering fields, and then computes the aggregate expression (average for this function) in
each group.

Syntax

AVG(input_field) OVER(
PARTITION BY partitioning_field [, partitioning_field]
ORDER BY ordering_field [ASC | DESC] [, ordering_field [ASC | DESC]]
RANGE BETWEEN value PRECEDING AND CURRENT ROW |
ROWS win_boundary | BETWEEN win_boundary AND win_boundary
)

where win_boundary can be:

UNBOUNDED PRECEDING
value PRECEDING
UNBOUNDED FOLLOWING
value FOLLOWING
CURRENT ROW

Return Value
Returns a value of type Numeric or Double depending on the type of input_field.

Input Parameters
input_field
Required. The field on which to perform the aggregate function. You can use any numeric
field or a Currency field.
OVER()
Required. OVER must be used within an AVG expression.
PARTITION BY partitioning_field
Required. Use the PARTITION BY clause to specify 1 or more fields to use to partition
a group of input rows. You can specify any field type except Currency. Example: You
specify the Month field as the partitioning field, so Workday groups into a single partition all
records that have the same value for Month.
ORDER BY ordering_field
Required. Use the ORDER BY clause to specify how to order the input rows in the partition
using the values in the specified field within each partition. You can specify any field type
except Currency. However, you must use a numeric field type, such as Integer or Numeric
when you use the RANGE clause.
You can use the DESC or ASC keywords to sort in descending order (high to low values,
NULLs are last) or ascending order (low to high values, NULLs are first) for each ordering
field. If you don't specify a sort order for an ordering field, Workday automatically sorts
rows in ascending order.
ROWS | RANGE
Required. The ROWS and RANGE clauses define the specific number of rows (relative to
the current row) within the partition by specifying a window frame. You define the window
frame by specifying start and end points within the partition, known as window boundaries.
The window frame is the set of input rows in each partition over which to calculate the
aggregate expression (average for this function). The window frame can include one,
several, or all rows of the partition.
Both ROWS and RANGE specify the range of rows relative to the current row, but RANGE
operates logically on values (logical association) and ROWS operates physically on rows in
the dataset (physical association).

RANGE limits the window frame to contain rows that have their values within the specified
range, relative to the current value. ROWS limits the window frame to contain rows that are
physically next to the current row.
Use RANGE to define absolute window boundaries, such as the past 3 months or year to
date. When you use RANGE, the ORDER BY clause must use a numeric field type, such as
Integer or Numeric.
Example: Suppose you have an Integer field called MonthNum that represents the number
of the month in the year (values 1 to 12). To specify all values from the past 3 months, you
would order by MonthNum and use RANGE BETWEEN 2 PRECEDING AND CURRENT
ROW. This RANGE clause includes the current month and the previous 2 months, resulting
in 3 months total.
Note: When you publish a dataset that contains a window function using RANGE, the
number of rows in the window must be 1000 or less. If a particular window exceeds 1000
rows, the publish job fails.
win_boundary
Required. The window boundaries define the start and end points of the window frame.
Window boundaries are relative to the current row.
A PRECEDING clause defines a window boundary that is lower than the current row (the
number of rows to include before the current row). The FOLLOWING clause defines a
window boundary that is greater than the current row (the number of rows to include after
the current row).
If you specify only 1 window boundary, then Workday uses the current row as the other
boundary in the window frame (either the upper or lower boundary depending on the
expression syntax). The UNBOUNDED keyword includes all rows in the direction specified.
When you need to specify both a start and end of a window frame, use the BETWEEN and
AND keywords.
When specifying a specific number of rows, the value must be 100 or less.
Example: ROWS 2 PRECEDING means that the window is 3 rows in size, starting with 2
rows preceding until and including the current row.
Example: ROWS UNBOUNDED FOLLOWING means that the window starts with the current
row and includes the current row and all rows that come after the current row.

Examples
You can calculate the moving average (rolling average or running average) sales for each employee:

AVG([Sales]) OVER(PARTITION BY [Employee] ORDER BY [SalesDate] DESC

ROWS UNBOUNDED PRECEDING)

You can calculate the overall average sales for every row in the partition, regardless of the fields in the
ORDER BY clause:

AVG([Sales]) OVER(PARTITION BY [Employee] ORDER BY [SalesDate] DESC

ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING)

You can calculate the rolling 12 month average:

AVG([fieldA]) OVER(PARTITION BY [fieldB] ORDER BY [Month] RANGE 11

PRECEDING)

The Month field must be a numeric field type, such as Integer or Numeric.

You can calculate the previous year to date average:

AVG([fieldA]) OVER(PARTITION BY [fieldB] ORDER BY [Year] RANGE 1 PRECEDING)

The Year field must be a numeric field type, such as Integer or Numeric.

COUNT

Description
COUNT is a window aggregate function that partitions rows into groups, orders rows by a field, and returns
the total number of valid rows (NOT NULL) in the group. You can use COUNT together with other functions
to calculate cumulative aggregates.
The PARTITION BY clause determines which fields to use to partition a set of input rows into groups. The
ORDER BY clause determines how to order the rows in the partition.
Workday separates the input rows into groups according to the partitioning fields, orders the rows
according to the ordering fields, and then computes the aggregate expression (count for this function) in
each group.

Syntax

COUNT(input_field) OVER(
PARTITION BY partitioning_field [, partitioning_field]
ORDER BY ordering_field [ASC | DESC] [, ordering_field [ASC | DESC]]
RANGE BETWEEN value PRECEDING AND CURRENT ROW |
ROWS win_boundary | BETWEEN win_boundary AND win_boundary
)

where win_boundary can be:

UNBOUNDED PRECEDING
value PRECEDING
UNBOUNDED FOLLOWING
value FOLLOWING
CURRENT ROW

Return Value
Returns a value of type Long.

except Currency. However, you must use a numeric field type, such as Integer or Numeric
when you use the RANGE clause.
You can use the DESC or ASC keywords to sort in descending order (high to low values,
NULLs are last) or ascending order (low to high values, NULLs are first) for each ordering
field. If you don't specify a sort order for an ordering field, Workday automatically sorts
rows in ascending order.
ROWS | RANGE
Required. The ROWS and RANGE clauses define the specific number of rows (relative to
the current row) within the partition by specifying a window frame. You define the window
frame by specifying start and end points within the partition, known as window boundaries.
The window frame is the set of input rows in each partition over which to calculate the
aggregate expression (count for this function). The window frame can include one, several,
or all rows of the partition.
Both ROWS and RANGE specify the range of rows relative to the current row, but RANGE
operates logically on values (logical association) and ROWS operates physically on rows in
the dataset (physical association).
RANGE limits the window frame to contain rows that have their values within the specified
range, relative to the current value. ROWS limits the window frame to contain rows that are
physically next to the current row.
Use RANGE to define absolute window boundaries, such as the past 3 months or year to
date. When you use RANGE, the ORDER BY clause must use a numeric field type, such as
Integer or Numeric.
Example: Suppose you have an Integer field called MonthNum that represents the number
of the month in the year (values 1 to 12). To specify all values from the past 3 months, you
would order by MonthNum and use RANGE BETWEEN 2 PRECEDING AND CURRENT
ROW. This RANGE clause includes the current month and the previous 2 months, resulting
in 3 months total.
Note: When you publish a dataset that contains a window function using RANGE, the
number of rows in the window must be 1000 or less. If a particular window exceeds 1000
rows, the publish job fails.
win_boundary
Required. The window boundaries define the start and end points of the window frame.
Window boundaries are relative to the current row.
A PRECEDING clause defines a window boundary that is lower than the current row (the
number of rows to include before the current row). The FOLLOWING clause defines a
window boundary that is greater than the current row (the number of rows to include after
the current row).
If you specify only 1 window boundary, then Workday uses the current row as the other
boundary in the window frame (either the upper or lower boundary depending on the
expression syntax). The UNBOUNDED keyword includes all rows in the direction specified.
When you need to specify both a start and end of a window frame, use the BETWEEN and
AND keywords.
When specifying a specific number of rows, the value must be 100 or less.
Example: ROWS 2 PRECEDING means that the window is 3 rows in size, starting with 2
rows preceding until and including the current row.
Example: ROWS UNBOUNDED FOLLOWING means that the window starts with the current
row and includes the current row and all rows that come after the current row.

Examples
You can calculate the moving count (running count or rolling count) of sales for each employee:

COUNT([Sales]) OVER(PARTITION BY [Employee] ORDER BY [SalesDate] DESC

ROWS UNBOUNDED PRECEDING)

You can calculate the overall count of sales for every row in the partition, regardless of the fields in the
ORDER BY clause:

COUNT([Sales]) OVER(PARTITION BY [Employee] ORDER BY [SalesDate] DESC

ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING)

You can calculate the rolling 12 month count:

COUNT([fieldA]) OVER(PARTITION BY [fieldB] ORDER BY [Month] RANGE 11

PRECEDING)

The Month field must be a numeric field type, such as Integer or Numeric.
You can calculate the previous year to date count:

COUNT([fieldA]) OVER(PARTITION BY [fieldB] ORDER BY [Year] RANGE 1

PRECEDING)

The Year field must be a numeric field type, such as Integer or Numeric.

FIRST

Description
FIRST is a window aggregate function that partitions rows into groups, orders rows by a field, and returns
the value from the first row in the group.
The PARTITION BY clause determines which fields to use to partition a set of input rows into groups. The
ORDER BY clause determines how to order the rows in the partition.
Workday separates the input rows into groups according to the partitioning fields, orders the rows
according to the ordering fields, and then computes the aggregate expression (first for this function) in
each group.

Syntax

FIRST(input_field) OVER(
PARTITION BY partitioning_field [, partitioning_field]
ORDER BY ordering_field [ASC | DESC] [, ordering_field [ASC | DESC]]
ROWS start_window_boundary
)

where start_window_boundary can be:

UNBOUNDED PRECEDING

Return Value
Returns a value of the same type as input_field.

Input Parameters
input_field

Required. The field on which to perform the aggregate function. You can use any numeric
field or a Currency field.
OVER()
Required. OVER must be used within a FIRST expression.
PARTITION BY partitioning_field
Required. Use the PARTITION BY clause to specify 1 or more fields to use to partition
a group of input rows. You can specify any field type except Currency. Example: You
specify the Month field as the partitioning field, so Workday groups into a single partition all
records that have the same value for Month.
ORDER BY ordering_field
Required. Use the ORDER BY clause to specify how to order the input rows in the partition
using the values in the specified field within each partition. You can specify any field type
except Currency.
You can use the DESC or ASC keywords to sort in descending order (high to low values,
NULLs are last) or ascending order (low to high values, NULLs are first) for each ordering
field. If you don't specify a sort order for an ordering field, Workday automatically sorts
rows in ascending order.
ROWS
Required. The ROWS clause defines the specific number of rows (relative to the current
row) within the partition by specifying a window frame. You define the window frame by
specifying start and end points within the partition, known as window boundaries. The
window frame is the set of input rows in each partition, relative to the current row, over
which to calculate the aggregate expression (first for this function). The window frame can
include one, several, or all rows of the partition.
window_boundary
Required. The window boundaries define the start and end points of the window frame.
Window boundaries are relative to the current row.
A PRECEDING clause defines a window boundary that is lower than the current row
(the number of rows to include before the current row). If you specify only 1 window
boundary, then Workday uses the current row as the last row in the window frame (the
upper boundary). The UNBOUNDED keyword includes all rows in the direction specified.

LAG

Description
LAG is a window aggregate function that partitions rows into groups, orders rows by a field, and returns the
value of a field in the row at the specified offset before (above) the current row in the group.
The PARTITION BY clause determines which fields to use to partition a set of input rows into groups. The
ORDER BY clause determines how to order the rows in the partition.
Workday separates the input rows into groups according to the partitioning fields, orders the rows
according to the ordering fields, and then computes the aggregate expression (lag for this function) in each
group.

Syntax

LAG(input_field, offset, default_value) OVER(

PARTITION BY partitioning_field [, partitioning_field]
ORDER BY ordering_field [ASC | DESC] [, ordering_field [ASC | DESC]]
)

Return Value
Returns one value per row of the same type as the input_field.

Input Parameters
input_field
Required. The field on which to perform the aggregate function. You can specify any field
type.
offset
Optional. The number of rows before the current row whose value to return. Must be a
literal number greater than or equal to zero (0) and less than or equal to 100. If you don't
specify the offset, Workday uses the value of 1.
default_value
Optional. The value this function returns when the offset row is outside the currently
defined window or when the value in the offset row is NULL. default_value must be the
same type as input_field. If you don't specify a default value, Workday uses the value of
NULL.
OVER()
Required. OVER must be used within a LAG expression.
PARTITION BY partitioning_field
Required. Use the PARTITION BY clause to specify 1 or more fields to use to partition
a group of input rows. You can specify any field type except Currency. Example: You
specify the Month field as the partitioning field, so Workday groups into a single partition all
records that have the same value for Month.
ORDER BY ordering_field
Required. Use the ORDER BY clause to specify how to order the input rows in the partition
using the values in the specified field within each partition. You can specify any field type
except Currency.
You can use the DESC or ASC keywords to sort in descending order (high to low values,
NULLs are last) or ascending order (low to high values, NULLs are first) for each ordering
field. If you don't specify a sort order for an ordering field, Workday automatically sorts
rows in ascending order.

Examples
Example: You have a dataset with these rows and fields.

row_ID Employee_Name Eff_Date Salary

1 Goh 1/1/18 49000
2 Goh 1/1/19 56000
3 Goh 1/1/17 44000
4 Freeman 1/1/18 65000
5 Freeman 1/1/17 57000
6 Freeman 1/1/19 69000
7 Smith 1/1/18 51000
8 Smith 1/1/19 56000
9 Smith 1/1/16 44000

You can order the rows for each employee in ascending (ASC) order by the effective date (Eff_Date) field,
so the most recent salary comes first in each partition.
Use this expression in the Salary_Increase field to calculate the change in salary between each change in
effective date:

[Salary] - (LAG([Salary], 1, [Salary]) OVER(

PARTITION BY [Employee_Name]
ORDER BY [Eff_Date] ASC)
)

You get these results:

row_ID Employee_Name Eff_Date Salary Salary_Increase

2 Goh 1/1/19 56000 7000
1 Goh 1/1/18 49000 5000
3 Goh 1/1/17 44000 0
6 Freeman 1/1/19 69000 4000
4 Freeman 1/1/18 65000 8000
5 Freeman 1/1/17 57000 0
8 Smith 1/1/19 56000 5000
7 Smith 1/1/18 51000 7000
9 Smith 1/1/16 44000 0

Related Information
Reference
Workday 32 What’s New Post: Prism Analytics Data Preparation

LAST

Description
LAST is a window aggregate function that partitions rows into groups, orders rows by a field, and returns
the value from the last row in the group.
The PARTITION BY clause determines which fields to use to partition a set of input rows into groups. The
ORDER BY clause determines how to order the rows in the partition.
Workday separates the input rows into groups according to the partitioning fields, orders the rows
according to the ordering fields, and then computes the aggregate expression (last for this function) in each
group.

Syntax

LAST(input_field) OVER(
PARTITION BY partitioning_field [, partitioning_field]
ORDER BY ordering_field [ASC | DESC] [, ordering_field [ASC | DESC]]
ROWS BETWEEN start_window_boundary AND end_window_boundary
)

where start_window_boundary can be:

CURRENT ROW

and where end_window_boundary can be:

UNBOUNDED FOLLOWING

Return Value
Returns a value of the same type as input_field.

Input Parameters
input_field
Required. The field on which to perform the aggregate function. You can use any numeric
field or a Currency field.
OVER()
Required. OVER must be used within a LAST expression.
PARTITION BY partitioning_field
Required. Use the PARTITION BY clause to specify 1 or more fields to use to partition
a group of input rows. You can specify any field type except Currency. Example: You
specify the Month field as the partitioning field, so Workday groups into a single partition all
records that have the same value for Month.
ORDER BY ordering_field
Required. Use the ORDER BY clause to specify how to order the input rows in the partition
using the values in the specified field within each partition. You can specify any field type
except Currency.
You can use the DESC or ASC keywords to sort in descending order (high to low values,
NULLs are last) or ascending order (low to high values, NULLs are first) for each ordering
field. If you don't specify a sort order for an ordering field, Workday automatically sorts
rows in ascending order.
ROWS
Required. The ROWS clause defines the specific number of rows (relative to the current
row) within the partition by specifying a window frame. You define the window frame by
specifying start and end points within the partition, known as window boundaries. The
window frame is the set of input rows in each partition, relative to the current row, over
which to calculate the aggregate expression (last for this function). The window frame can
include one, several, or all rows of the partition.
window_boundary
Required. The window boundaries define the start and end points of the window frame.
Window boundaries are relative to the current row.
A FOLLOWING clause defines a window boundary that is after the current row (the number
of rows to include after the current row). Workday uses the current row as the first row in
the window frame (the lower boundary). The UNBOUNDED keyword includes all rows in the
direction specified.

LEAD

Description
LEAD is a window aggregate function that partitions rows into groups, orders rows by a field, and returns
the value of a field in the row at the specified offset after (below) the current row in the group.
The PARTITION BY clause determines which fields to use to partition a set of input rows into groups. The
ORDER BY clause determines how to order the rows in the partition.

Workday separates the input rows into groups according to the partitioning fields, orders the rows
according to the ordering fields, and then computes the aggregate expression (lead for this function) in
each group.

Syntax

LEAD(input_field, offset, default_value) OVER(

PARTITION BY partitioning_field [, partitioning_field]
ORDER BY ordering_field [ASC | DESC] [, ordering_field [ASC | DESC]]
)

Return Value
Returns one value per row of the same type as the input_field.

Input Parameters
input_field
Required. The field on which to perform the aggregate function. You can specify any field
type.
offset
Optional. The number of rows after the current row whose value to return. Must be a literal
number greater than or equal to zero (0) and less than or equal to 100. If you don't specify
the offset, Workday uses the value of 1.
default_value
Optional. The value this function returns when the offset row is outside the currently
defined window or when the value in the offset row is NULL. default_value must be the
same type as input_field. If you don't specify a default value, Workday uses the value of
NULL.
OVER()
Required. OVER must be used within a LEAD expression.
PARTITION BY partitioning_field
Required. Use the PARTITION BY clause to specify 1 or more fields to use to partition
a group of input rows. You can specify any field type except Currency. Example: You
specify the Month field as the partitioning field, so Workday groups into a single partition all
records that have the same value for Month.
ORDER BY ordering_field
Required. Use the ORDER BY clause to specify how to order the input rows in the partition
using the values in the specified field within each partition. You can specify any field type
except Currency.
You can use the DESC or ASC keywords to sort in descending order (high to low values,
NULLs are last) or ascending order (low to high values, NULLs are first) for each ordering
field. If you don't specify a sort order for an ordering field, Workday automatically sorts
rows in ascending order.

Examples
Example: You have a dataset with these rows and fields.

row_ID Employee_Name Eff_Date Salary

1 Goh 1/1/18 49000

row_ID Employee_Name Eff_Date Salary

2 Goh 1/1/19 56000
3 Goh 1/1/17 44000
4 Freeman 1/1/18 65000
5 Freeman 1/1/17 57000
6 Freeman 1/1/19 69000
7 Smith 1/1/18 51000
8 Smith 1/1/19 56000
9 Smith 1/1/16 44000

You can order the rows for each employee in descending (DESC) order by the effective date (Eff_Date)
field, so the most recent salary comes first in each partition.
Use this expression in the Salary_Increase field to calculate the change in salary between each change in
effective date:

[Salary] - (LEAD([Salary], 1, [Salary]) OVER(

PARTITION BY [Employee_Name]
ORDER BY [Eff_Date] DESC)
)

You get these results:

row_ID Employee_Name Eff_Date Salary Salary_Increase

Related Information
Reference
Workday 32 What’s New Post: Prism Analytics Data Preparation

MAX

Description
MAX is a window aggregate function that partitions rows into groups, orders rows by a field, and returns the
maximum (highest) value in the group.
The PARTITION BY clause determines which fields to use to partition a set of input rows into groups. The
ORDER BY clause determines how to order the rows in the partition.

Syntax

MAX(input_field) OVER(
PARTITION BY partitioning_field [, partitioning_field]
ORDER BY ordering_field [ASC | DESC] [, ordering_field [ASC | DESC]]
RANGE BETWEEN value PRECEDING AND CURRENT ROW |
ROWS win_boundary | BETWEEN win_boundary AND win_boundary
)

where win_boundary can be:

UNBOUNDED PRECEDING
value PRECEDING
UNBOUNDED FOLLOWING
value FOLLOWING
CURRENT ROW

Return Value
Returns a value of type Numeric or Double depending on the type of input_field.

Input Parameters
input_field
Required. The field on which to perform the aggregate function. You can use any numeric
field or a Currency field.
OVER()
Required. OVER must be used within a MAX expression.
PARTITION BY partitioning_field
Required. Use the PARTITION BY clause to specify 1 or more fields to use to partition
a group of input rows. You can specify any field type except Currency. Example: You
specify the Month field as the partitioning field, so Workday groups into a single partition all
records that have the same value for Month.
ORDER BY ordering_field
Required. Use the ORDER BY clause to specify how to order the input rows in the partition
using the values in the specified field within each partition. You can specify any field type
except Currency. However, you must use a numeric field type, such as Integer or Numeric
when you use the RANGE clause.
You can use the DESC or ASC keywords to sort in descending order (high to low values,
NULLs are last) or ascending order (low to high values, NULLs are first) for each ordering
field. If you don't specify a sort order for an ordering field, Workday automatically sorts
rows in ascending order.
ROWS | RANGE
Required. The ROWS and RANGE clauses define the specific number of rows (relative to
the current row) within the partition by specifying a window frame. You define the window
frame by specifying start and end points within the partition, known as window boundaries.
The window frame is the set of input rows in each partition over which to calculate the
aggregate expression (maximum for this function). The window frame can include one,
several, or all rows of the partition.

Both ROWS and RANGE specify the range of rows relative to the current row, but RANGE
operates logically on values (logical association) and ROWS operates physically on rows in
the dataset (physical association).
RANGE limits the window frame to contain rows that have their values within the specified
range, relative to the current value. ROWS limits the window frame to contain rows that are
physically next to the current row.
Use RANGE to define absolute window boundaries, such as the past 3 months or year to
date. When you use RANGE, the ORDER BY clause must use a numeric field type, such as
Integer or Numeric.
Example: Suppose you have an Integer field called MonthNum that represents the number
of the month in the year (values 1 to 12). To specify all values from the past 3 months, you
would order by MonthNum and use RANGE BETWEEN 2 PRECEDING AND CURRENT
ROW. This RANGE clause includes the current month and the previous 2 months, resulting
in 3 months total.
Note: When you publish a dataset that contains a window function using RANGE, the
number of rows in the window must be 1000 or less. If a particular window exceeds 1000
rows, the publish job fails.
win_boundary
Required. The window boundaries define the start and end points of the window frame.
Window boundaries are relative to the current row.
A PRECEDING clause defines a window boundary that is lower than the current row (the
number of rows to include before the current row). The FOLLOWING clause defines a
window boundary that is greater than the current row (the number of rows to include after
the current row).
If you specify only 1 window boundary, then Workday uses the current row as the other
boundary in the window frame (either the upper or lower boundary depending on the
expression syntax). The UNBOUNDED keyword includes all rows in the direction specified.
When you need to specify both a start and end of a window frame, use the BETWEEN and
AND keywords.
When specifying a specific number of rows, the value must be 100 or less.
Example: ROWS 2 PRECEDING means that the window is 3 rows in size, starting with 2
rows preceding until and including the current row.
Example: ROWS UNBOUNDED FOLLOWING means that the window starts with the current
row and includes the current row and all rows that come after the current row.

Examples
Example: You have a dataset with these rows and fields.

Supervisory Org Quarter Name Comp Change

Marketing 2019-Q1 Goh 2000.00
Marketing 2019-Q1 Freeman 1000.00
Marketing 2019-Q1 Smith 2500.00
Consulting 2019-Q1 Gomez 5000.00
Consulting 2019-Q1 Kimura 3000.00
Consulting 2019-Q1 Fitz 3500.00

Supervisory Org Quarter Name Comp Change

Consulting 2019-Q2 Gomez 0
Consulting 2019-Q2 Kimura 2000.00
Consulting 2019-Q2 Fitz 1500.00

You can calculate the highest change in compensation (Comp Change field) for each supervisory org in
each quarter.
To ensure that Workday returns the same value for every row in a partition, order the rows in descending
(DESC) order by the same field as the input field so the highest compensation change comes first in each
partition.
Use this expression in the Max Comp Change field:

MAX([Comp Change]) OVER(

PARTITION BY [Supervisory Org], [Quarter]
ORDER BY [Comp Change] DESC
ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
)

You get these results:

Supervisory Org Quarter Name Comp Change Max Comp

Change
Consulting 2019-Q1 Gomez 5000.00 5000.00
Consulting 2019-Q1 Fitz 3500.00 5000.00
Consulting 2019-Q1 Kimura 3000.00 5000.00
Consulting 2019-Q2 Kimura 2000.00 2000.00
Consulting 2019-Q2 Fitz 1500.00 2000.00
Consulting 2019-Q2 Gomez 0 2000.00
Marketing 2019-Q1 Smith 2500.00 2500.00
Marketing 2019-Q1 Goh 2000.00 2500.00
Marketing 2019-Q1 Freeman 1000.00 2500.00

Related Information
Reference
Workday 32 What’s New Post: Prism Analytics Dataset Window Functions

MIN

Description
MIN is a window aggregate function that partitions rows into groups, orders rows by a field, and returns the
minimum (lowest) value in the group.
The PARTITION BY clause determines which fields to use to partition a set of input rows into groups. The
ORDER BY clause determines how to order the rows in the partition.
Workday separates the input rows into groups according to the partitioning fields, orders the rows
according to the ordering fields, and then computes the aggregate expression (minimum for this function)
in each group.

Syntax

MIN(input_field) OVER(
PARTITION BY partitioning_field [, partitioning_field]
ORDER BY ordering_field [ASC | DESC] [, ordering_field [ASC | DESC]]
RANGE BETWEEN value PRECEDING AND CURRENT ROW |
ROWS win_boundary | BETWEEN win_boundary AND win_boundary
)

where win_boundary can be:

UNBOUNDED PRECEDING
value PRECEDING
UNBOUNDED FOLLOWING
value FOLLOWING
CURRENT ROW

Return Value
Returns a value of type Numeric or Double depending on the type of input_field.

Input Parameters
input_field
Required. The field on which to perform the aggregate function. You can use any numeric
field or a Currency field.
OVER()
Required. OVER must be used within a MIN expression.
PARTITION BY partitioning_field
Required. Use the PARTITION BY clause to specify 1 or more fields to use to partition
a group of input rows. You can specify any field type except Currency. Example: You
specify the Month field as the partitioning field, so Workday groups into a single partition all
records that have the same value for Month.
ORDER BY ordering_field
Required. Use the ORDER BY clause to specify how to order the input rows in the partition
using the values in the specified field within each partition. You can specify any field type
except Currency. However, you must use a numeric field type, such as Integer or Numeric
when you use the RANGE clause.
You can use the DESC or ASC keywords to sort in descending order (high to low values,
NULLs are last) or ascending order (low to high values, NULLs are first) for each ordering
field. If you don't specify a sort order for an ordering field, Workday automatically sorts
rows in ascending order.
ROWS | RANGE
Required. The ROWS and RANGE clauses define the specific number of rows (relative to
the current row) within the partition by specifying a window frame. You define the window
frame by specifying start and end points within the partition, known as window boundaries.
The window frame is the set of input rows in each partition over which to calculate the
aggregate expression (minimum for this function). The window frame can include one,
several, or all rows of the partition.
Both ROWS and RANGE specify the range of rows relative to the current row, but RANGE
operates logically on values (logical association) and ROWS operates physically on rows in
the dataset (physical association).

Examples
Example: You have a dataset with these rows and fields.

Supervisory Org Quarter Name Comp Change

Marketing 2019-Q1 Goh 2000.00
Marketing 2019-Q1 Freeman 1000.00
Marketing 2019-Q1 Smith 2500.00
Consulting 2019-Q1 Gomez 5000.00
Consulting 2019-Q1 Kimura 3000.00
Consulting 2019-Q1 Fitz 3500.00
Consulting 2019-Q2 Gomez 0
Consulting 2019-Q2 Kimura 2000.00
Consulting 2019-Q2 Fitz 1500.00

You can calculate the lowest change in compensation (Comp Change field) for each supervisory org in
each quarter.
To ensure that Workday returns the same value for every row in a partition, order the rows in ascending
(ASC) order by the same field as the input field so the lowest compensation change comes first in each
partition.
Use this expression in the Min Comp Change field:

MIN([Comp Change]) OVER(

PARTITION BY [Supervisory Org], [Quarter]
ORDER BY [Comp Change] ASC
ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
)

You get these results:

Supervisory Org Quarter Name Comp Change Min Comp

Change
Consulting 2019-Q1 Kimura 3000.00 3000.00
Consulting 2019-Q1 Fitz 3500.00 3000.00
Consulting 2019-Q1 Gomez 5000.00 3000.00
Consulting 2019-Q2 Gomez 0 0
Consulting 2019-Q2 Fitz 1500.00 0
Consulting 2019-Q2 Kimura 2000.00 0
Marketing 2019-Q1 Freeman 1000.00 1000.00
Marketing 2019-Q1 Goh 2000.00 1000.00
Marketing 2019-Q1 Smith 2500.00 1000.00

Related Information
Reference
Workday 32 What’s New Post: Prism Analytics Dataset Window Functions

RANK

Description
RANK is a window aggregate function used to assign a ranking number to each row in a group. If multiple
rows have the same ranking value (there's a tie), then Workday assigns the same rank value to the tied
rows and skips the subsequent rank position.
The PARTITION BY clause determines which fields to use to partition a set of input rows into groups.
The ORDER BY clause determines how to order the rows in the partition before they're ranked.
Workday separates the input rows into groups according to the partitioning fields, orders the rows
according to the ordering fields, and then computes the aggregate expression (rank for this function) in
each group. The ranked rows in each group start at 1.

Syntax

RANK() OVER(
PARTITION BY partitioning_field [, partitioning_field]
ORDER BY ordering_field [ASC | DESC] [, ordering_field [ASC | DESC]]

Return Value
Returns a value of type Integer.

Input Parameters
OVER()
Required. OVER must be used within a RANK expression.
PARTITION BY partitioning_field
Required. Use the PARTITION BY clause to specify 1 or more fields to use to partition a
group of input rows. You can specify any field type except Currency. Example: You specify
the Month field as the partitioning field, so Workday groups together into a single partition
all records that have the same value for Month.
ORDER BY ordering_field
Required. Use the ORDER BY clause to specify how to order the input rows in the partition
using the values in the specified field within each partition. You can specify any field type
except Currency.
You can use the DESC or ASC keywords to sort in descending order (high to low values,
NULLs are last) or ascending order (low to high values, NULLs are first) for each ordering
field. If you don't specify a sort order for an ordering field, Workday automatically sorts
rows in ascending order.

Examples
Example: You have a dataset with these rows and fields.

Employee Sales Date Sales

Goh 12/31/2018 140
Goh 11/30/2018 60
Goh 10/31/2018 140
Freeman 12/31/2018 160
Freeman 11/30/2018 60
Freeman 10/31/2018 110
Smith 12/31/2018 140
Smith 11/30/2018 60
Smith 10/31/2018 120

You can rank the sales for each employee in descending order, so the highest sales is given the ranking of
1. Use this expression in the Rank Sales by Employee field:

RANK() OVER(PARTITION BY [Employee] ORDER BY [Sales] DESC)

You get these results:

Employee Sales Date Sales Rank Sales by

Employee
Goh 12/31/2018 140 1

Employee Sales Date Sales Rank Sales by

Employee
Goh 10/31/2018 140 1
Goh 11/30/2018 60 3
Freeman 12/31/2018 160 1
Freeman 10/31/2018 110 2
Freeman 11/30/2018 60 3
Smith 12/31/2018 140 1
Smith 10/31/2018 120 2
Smith 11/30/2018 60 3

You can also rank the sales for each date in descending order, so the highest sales is given the ranking of
1. Use this expression in the Rank Sales by Date field:

RANK() OVER(PARTITION BY [Sales Date] ORDER BY [Sales] DESC)

You get these results:

Employee Sales Date Sales Rank Sales by Date

Freeman 12/31/2018 160 1
Goh 12/31/2018 140 2
Smith 12/31/2018 140 2
Goh 11/30/2018 60 1
Freeman 11/30/2018 60 1
Smith 11/30/2018 60 1
Goh 10/31/2018 140 1
Smith 10/31/2018 120 2
Freeman 10/31/2018 110 3

Notice that tied values are given the same rank number and the following rank position is skipped.

ROW_NUMBER

Description
ROW_NUMBER is a window aggregate function that partitions rows into groups, orders rows by a field, and
assigns a unique, sequential number to each row in a group, starting at 1 for the first row in each group.
ROW_NUMBER always assigns a unique value to each row in a group. You might want to use ROW_NUMBER
to create a unique ID for each row in your dataset.
The PARTITION BY clause determines which fields to use to partition a set of input rows into groups.
The ORDER BY clause determines how to order the rows in the partition before they're assigned a
sequential number.
Workday separates the input rows into groups according to the partitioning fields, orders the rows
according to the ordering fields, and then computes the aggregate expression (row numbering for this
function) in each group. The numbered rows in each group start at 1.

Syntax

ROW_NUMBER() OVER(
PARTITION BY partitioning_field [, partitioning_field]
ORDER BY ordering_field [ASC | DESC] [, ordering_field [ASC | DESC]]
)

Return Value
Returns a value of type Integer.

Input Parameters
OVER()
Required. OVER must be used within a ROW_NUMBER expression.
PARTITION BY partitioning_field
Required. Use the PARTITION BY clause to specify 1 or more fields to use to partition a
group of input rows. You can specify any field type except Currency. Example: You specify
the Month field as the partitioning field, so Workday groups together into a single partition
all records that have the same value for Month.
ORDER BY ordering_field
Required. Use the ORDER BY clause to specify how to order the input rows in the partition
using the values in the specified field within each partition. You can specify any field type
except Currency.
You can use the DESC or ASC keywords to sort in descending order (high to low values,
NULLs are last) or ascending order (low to high values, NULLs are first) for each ordering
field. If you don't specify a sort order for an ordering field, Workday automatically sorts
rows in ascending order.

Examples
Example: You have a dataset with these rows and fields.

Employee Sales Date Sales

Goh 12/31/2018 140
Goh 11/30/2018 60
Goh 10/31/2018 140
Freeman 12/31/2018 160
Freeman 11/30/2018 60
Freeman 10/31/2018 110
Smith 12/31/2018 140
Smith 11/30/2018 60
Smith 10/31/2018 120

You can assign a unique ID to the sales of each employee in descending order, so the highest sales is
given the ranking of 1. Use this expression in the Sales Num by Employee field:

ROW_NUMBER() OVER(PARTITION BY [Employee] ORDER BY [Sales] DESC)

You get these results:

Employee Sales Date Sales Sales Num by

Employee
Goh 12/31/2018 140 1
Goh 10/31/2018 140 2
Goh 11/30/2018 60 3
Freeman 12/31/2018 160 1
Freeman 10/31/2018 110 2
Freeman 11/30/2018 60 3
Smith 12/31/2018 140 1
Smith 10/31/2018 120 2
Smith 11/30/2018 60 3

You can also assign a unique ID to the sales for each date in descending order, so the highest sales is
given the ranking of 1. Use this expression in the Sales Num by Date field:

ROW_NUMBER() OVER(PARTITION BY [Sales Date] ORDER BY [Sales] DESC)

You get these results:

Employee Sales Date Sales Sales Num by Date

Freeman 12/31/2018 160 1
Goh 12/31/2018 140 2
Smith 12/31/2018 140 3
Goh 11/30/2018 60 1
Freeman 11/30/2018 60 2
Smith 11/30/2018 60 3
Goh 10/31/2018 140 1
Smith 10/31/2018 120 2
Freeman 10/31/2018 110 3

You can also use ROW_NUMBER to determine the latest version of every row in a dataset that contains
multiple rows per ID. In this scenario, the dataset requires a date field that represents when the information
in that row became current. If you're familiar with data warehousing concepts, this is a type 2 slowly
changing dimension table. You have a dataset with these rows and fields.

ID Name Region Effective Date

G1 Gorman West 01/01/2015
H1 Harris West 01/01/2015
G1 Gorman East 09/01/2016
H1 Harris East 01/03/2017
H1 Harris National 01/20/2021

To assign the value of 1 to the latest version of each ID, use this expression in the Latest Version field:

ROW_NUMBER() OVER(PARTITION BY [ID] ORDER BY [Effective Date] DESC)

You get these results:

ID Name Region Effective Date Latest Version

G1 Gorman West 01/01/2015 2
H1 Harris West 01/01/2015 3
G1 Gorman East 09/01/2016 1
H1 Harris East 01/03/2017 2
H1 Harris National 01/20/2021 1

You can filter on Latest Version using a Filter Stage in order to return only the latest row for each ID.

SUM

Description
SUM is a window aggregate function that partitions rows into groups, orders rows by a field, and returns the
total of all values in the group. You can use SUM to calculate running totals.
The PARTITION BY clause determines which fields to use to partition a set of input rows into groups. The
ORDER BY clause determines how to order the rows in the partition.
Workday separates the input rows into groups according to the partitioning fields, orders the rows
according to the ordering fields, and then computes the aggregate expression (sum for this function) in
each group.

Syntax

SUM(input_field) OVER(
PARTITION BY partitioning_field [, partitioning_field]
ORDER BY ordering_field [ASC | DESC] [, ordering_field [ASC | DESC]]
RANGE BETWEEN value PRECEDING AND CURRENT ROW |
ROWS win_boundary | BETWEEN win_boundary AND win_boundary
)

where win_boundary can be:

UNBOUNDED PRECEDING
value PRECEDING
UNBOUNDED FOLLOWING
value FOLLOWING
CURRENT ROW

Return Value
Returns a value of type Numeric, Long, or Double depending on the type of input_field.

Input Parameters
input_field
Required. The field on which to perform the aggregate function. You can use any numeric
field or a Currency field.

OVER()
Required. OVER must be used within an SUM expression.
PARTITION BY partitioning_field
Required. Use the PARTITION BY clause to specify 1 or more fields to use to partition
a group of input rows. You can specify any field type except Currency. Example: You
specify the Month field as the partitioning field, so Workday groups into a single partition all
records that have the same value for Month.
ORDER BY ordering_field
Required. Use the ORDER BY clause to specify how to order the input rows in the partition
using the values in the specified field within each partition. You can specify any field type
except Currency. However, you must use a numeric field type, such as Integer or Numeric
when you use the RANGE clause.
You can use the DESC or ASC keywords to sort in descending order (high to low values,
NULLs are last) or ascending order (low to high values, NULLs are first) for each ordering
field. If you don't specify a sort order for an ordering field, Workday automatically sorts
rows in ascending order.
ROWS | RANGE
Required. The ROWS and RANGE clauses define the specific number of rows (relative to
the current row) within the partition by specifying a window frame. You define the window
frame by specifying start and end points within the partition, known as window boundaries.
The window frame is the set of input rows in each partition over which to calculate the
aggregate expression (sum for this function). The window frame can include one, several,
or all rows of the partition.
Both ROWS and RANGE specify the range of rows relative to the current row, but RANGE
operates logically on values (logical association) and ROWS operates physically on rows in
the dataset (physical association).
RANGE limits the window frame to contain rows that have their values within the specified
range, relative to the current value. ROWS limits the window frame to contain rows that are
physically next to the current row.
Use RANGE to define absolute window boundaries, such as the past 3 months or year to
date. When you use RANGE, the ORDER BY clause must use a numeric field type, such as
Integer or Numeric.
Example: Suppose you have an Integer field called MonthNum that represents the number
of the month in the year (values 1 to 12). To specify all values from the past 3 months, you
would order by MonthNum and use RANGE BETWEEN 2 PRECEDING AND CURRENT
ROW. This RANGE clause includes the current month and the previous 2 months, resulting
in 3 months total.
Note: When you publish a dataset that contains a window function using RANGE, the
number of rows in the window must be 1000 or less. If a particular window exceeds 1000
rows, the publish job fails.
win_boundary
Required. The window boundaries define the start and end points of the window frame.
Window boundaries are relative to the current row.
A PRECEDING clause defines a window boundary that is lower than the current row (the
number of rows to include before the current row). The FOLLOWING clause defines a
window boundary that is greater than the current row (the number of rows to include after
the current row).

If you specify only 1 window boundary, then Workday uses the current row as the other
boundary in the window frame (either the upper or lower boundary depending on the
expression syntax). The UNBOUNDED keyword includes all rows in the direction specified.
When you need to specify both a start and end of a window frame, use the BETWEEN and
AND keywords.
When specifying a specific number of rows, the value must be 100 or less.
Example: ROWS 2 PRECEDING means that the window is 3 rows in size, starting with 2
rows preceding until and including the current row.
Example: ROWS UNBOUNDED FOLLOWING means that the window starts with the current
row and includes the current row and all rows that come after the current row.

Examples
You can calculate the running total (rolling sum or moving sum) of sales for each employee:

SUM([Sales]) OVER(PARTITION BY [Employee] ORDER BY [Sales] DESC

ROWS UNBOUNDED PRECEDING)

You can calculate the overall sum (total sales) for every row in the partition, regardless of the fields in the
ORDER BY clause:

SUM([Sales]) OVER(PARTITION BY [Employee] ORDER BY [Sales] DESC

ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING)

You can calculate the rolling 12 month sum:

SUM([fieldA]) OVER(PARTITION BY [fieldB] ORDER BY [Month] RANGE 11

PRECEDING)

The Month field must be a numeric field type, such as Integer or Numeric.
You can calculate the previous year to date sum:

SUM([fieldA]) OVER(PARTITION BY [fieldB] ORDER BY [Year] RANGE 1 PRECEDING)

The Year field must be a numeric field type, such as Integer or Numeric.

Regular Expression Reference

Concept: Regular Expressions in Prism
Regular expressions vary in complexity using a combination of basic constructs to describe a string
matching pattern. This reference describes the most common regular expression matching patterns, but is
not a comprehensive list.
Regular expressions, also referred to as regex or regexp, are a standardized collection of special
characters and constructs used for matching strings of text. They provide a flexible and precise language
for matching particular characters, words, or patterns of characters.
Prism Analytics regular expressions are based on the pattern matching syntax of the Java programming
language. For more in depth information on writing valid regular expressions, refer to the Java regular
expression pattern documentation.
You can use regular expressions in Prism calculated field expressions that use either the REGEX or
REGEX_REPLACE functions.

Regex Literal and Special Characters

This section describes the regular expression syntax for referring to literal characters, special characters,
nonprintable characters (such as a tab or a newline), and special character escaping.

Literal Characters
The most basic form of pattern matching is the match of literal characters. If the regular expression is foo
and the input string is foo, the match will succeed because the strings are identical.

Special Characters
Certain characters are reserved for special use in regular expressions. These special characters are called
metacharacters. If you want to use special characters as literal characters, you must escape them.

Character Name Character Reserved For

opening bracket [ Start of a character class
closing bracket ] End of a character class
hyphen - Character ranges within a character class
backslash \ General escape character
caret ^ Beginning of string, negating of a character
class
dollar sign $ End of string
period . Matching any single character
pipe | Alternation (OR) operator
question mark ? Optional quantifier, quantifier minimizer
asterisk * Zero or more quantifier
plus sign + Once or more quantifier
opening parenthesis ( Start of a subexpression group
closing parenthesis ) End of a subexpression group
opening brace { Start of min/max quantifier
closing brace } End of min/max quantifier

Escaping Special Characters

You can use these methods to treat a special character as a literal (ordinary) character:
• Precede the special character with a \ (backslash character). Example: to specify an asterisk as a
literal character instead of a quantifier, use \*.
• Enclose the special characters within \Q (starting quote) and \E (ending quote). Everything between \Q
and \E is then treated as literal characters.
• To escape literal double-quotes in a REGEX() expression, double the double-quotes (""). Example: to
extract the inches portion from a height field where example values are 6'2", 5'11":

REGEX([height], "\'(\d)+""$")

NonPrinting Characters
You can use special character sequence constructs to specify nonprintable characters in a regular
expression. Some of the most commonly used constructs are:

Construct Matches
\n newline character
\r carriage return character
\t tab character
\f form feed character

Regex Character Classes

Character Class Constructs

A character class allows you to specify a set of characters, enclosed in square brackets, that can produce
a single character match. A character class matches to a single character only. For example, gr[ae]y
will match to gray or grey, but not to graay or graey. The order of the characters inside the brackets
doesn't matter.
You can use a hyphen inside a character class to specify a range of characters. Example: [a-z] matches
a single lower-case letter between a and z. You can also use more than 1 range, or a combination of
ranges and single characters. Example: [0-9X] matches a numeric digit or the letter X. The order of the
characters and the ranges doesn't matter.
A caret following an opening bracket specifies characters to exclude from a match. For example, [^abc]
matches any character except a, b, or c.

Construct Type Description

[abc] Simple Matches a or b or c
[^abc] Negation Matches any character except a or b or c
[a-zA-Z] Range Matches a through z, or A through Z
(inclusive)
[a-d[m-p]] Union Matches a through d, or m through p
[a-z&&[def]] Intersection Matches d, e, or f
[a-z&&[^xq]] Subtraction Matches a through z, except for x and q

Predefined Character Classes

Predefined character classes are convenient shorthands for commonly used regular expressions.

Construct Description Example

. Matches any single character (except .at matches "cat", "hat", and also "bat"
newline) in the phrase "batch files"
\d Matches any digit character (equivalent \d matches "3" in "C3PO" and "2" in
to [0-9]) "file_2.txt"
\D Matches any non-digit character \D matches "S" in "900S" and "Q" in
(equivalent to [^0-9]) "Q45"

Construct Description Example

\s Matches any single white-space \sbook matches "book" in "blue book"
character (equivalent to [ \t\n\x0B\f but nothing in "notebook"
\r])
\S Matches any single non-white-space \Sbook matches "book" in "notebook"
character but nothing in "blue book"
\w Matches any alphanumeric character, r\w* matches "rm" and "root"
including underscore (equivalent to [A-
Za-z0-9_])
\W Matches any non-alphanumeric \W matches "&" in "stmd &", "%" in
character (equivalent to [^A-Za- "100%", and "$" in "$HOME"
z0-9_])

POSIX Character Classes (US-ASCII)

POSIX has a set of character classes that denote certain common ranges. They're similar to bracket and
predefined character classes, except they take into account the locale (the local language/coding system).

Construct Description
\p{Lower} A lower-case alphabetic character, [a-z]
\p{Upper} An upper-case alphabetic character, [A-Z]
\p{ASCII} An ASCII character, [\x00-\x7F]
\p{Alpha} An alphabetic character, [a-zA-z]
\p{Digit} A numeric digit, [0-9]
\p{Alnum} An alphanumeric character, [a-zA-z0-9]
\p{Punct} A punctuation character, one of !"#$%&'()*+,-./:;<=>?
@[\]^_`{|}~
\p{Graph} A visible character, [\p{Alnum}\p{Punct}]
\p{Print} A printable character, [\p{Graph}\x20]
\p{Blank} A space or tab, [ t]
\p{Cntrl} A control character, [\x00-\x1F\x7F]
\p{XDigit} A hexadecimal digit, [0-9a-fA-F]
\p{Space} A whitespace character, [ \t\n\x0B\f\r]

Regex Line and Word Boundaries

You can use boundary matching constructs to specify where in a string to apply a matching pattern. For
example, you can search for a particular pattern within a word boundary, or search for a pattern at the
beginning or end of a line.

Construct Description Example

^ Matches from the beginning of a line ^172 matches the "172" in IP address
(multi-line matches are currently not "172.18.1.11" but not in "192.172.2.33"
supported)

Construct Description Example

$ Matches from the end of a line (multi-line d$ matches the "d" in "maid" but not in
matches are currently not supported) "made"
\b Matches within a word boundary \bis\b matches the word "is" in "this is
my island", but not the "is" part of "this"
or "island". \bis matches both "is" and
the "is" in "island", but not in "this".
\B Matches within a non-word boundary \Bb matches "b" in "sbin" but not in
"bash"

Regex Quantifiers

Quantifier Constructs
Quantifiers specify how often the preceding regular expression construct should match. The classes of
quantifiers are:
• Greedy
• Reluctant
• Possessive
The difference between greedy, reluctant, and possessive quantifiers involves what part of the string to try
for the initial match, and how to retry if the initial attempt doesn't produce a match.
By default, quantifiers are greedy. A greedy quantifier first tries for a match with the entire input string.
If that produces a match, then it considers the match a success and the engine can move on to the
next construct in the regular expression. If the first try doesn't produce a match, the engine backs-off 1
character at a time until it finds a match. So a greedy quantifier checks for possible matches in order from
the longest possible input string to the shortest possible input string, recursively trying from right to left.
Adding a ? (question mark) to a greedy quantifier makes it reluctant. A reluctant quantifier first tries for
a match from the beginning of the input string, starting with the shortest possible piece of the string that
matches the regex construct. If that produces a match, then it considers the match a success and the
engine can move on to the next construct in the regular expression. If the first try doesn't produce a match,
the engine adds 1 character at a time until it finds a match. So a reluctant quantifier checks for possible
matches in order from the shortest possible input string to the longest possible input string, recursively
trying from left to right.
Adding a + (plus sign) to a greedy quantifier makes it possessive. A possessive quantifier is like a greedy
quantifier on the first attempt (it tries for a match with the entire input string). The difference is that unlike a
greedy quantifier, a possessive quantifier doesn't retry a shorter string if it doesn't find a match. If the initial
match fails, the possessive quantifier reports a failed match. It doesn't make any more attempts.

Greedy Reluctant Possessive Description Example

Construct Construct Construct
? ?? ?+ Matches the previous st?on matches "son" in
character or construct once "johnson" and "ston" in
or not at all. "johnston" but nothing in
"clinton" or "version"
* *? *+ Matches the previous if* matches "if", "iff" in
character or construct zero "diff", or "i" in "print"
or more times.

Greedy Reluctant Possessive Description Example

Construct Construct Construct
+ +? ++ Matches the previous if+ matches "if", "iff" in
character or construct 1 or "diff", but nothing in "print"
more times.
{n} {n}? {n}+ Matches the previous o{2} matches "oo" in
character or construct "lookup" and the first 2 o's
exactly n times. in "fooooo" but nothing in
"mount"
{n,} {n,}? {n,}+ Matches the previous o{2,} matches "oo" in
character or construct at "lookup" all 5 o's in "fooooo"
least n times. but nothing in "mount"
{n,m} {n,m}? {n,m}+ Matches the previous F{2,4} matches "FF" in
character or construct at "#FF0000" and the last 4 F's
least n times, but no more in "#FFFFFF"
than m times.

Regex Capturing Groups

You can use a pair of parentheses around a subpattern in a regular expression to define a group. You can
use regex groups to:
• Apply regex operators and quantifiers to an entire group at once.
• Create a capturing group. You can use capturing groups to specify matching values to save or return
from your regular expression. By default, a group captures the text that produces a match. The portion
of the string that matches the grouped subexpression is captured in memory for later retrieval or use.
• Create a non-capturing group.

Group Numbering
A regular expression can have more than 1 group, and the groups can be nested. The groups are
numbered 1-n from left to right, starting with the first opening parenthesis. There is always an implicit group
zero (0), which contains the entire match. Example:

(a(b*))+(c)

This pattern contains 3 groups:

group 1: (a(b*))
group 2: (b*)
group 3: (c)

Capturing Groups and the REGEX Function

You can use the REGEX function to extract a portion of a string. The REGEX function returns the value of the
first capturing group only.
Suppose you have a field name called email that contains email addresses with this pattern:
[email protected]. You can use the REGEX function to return just the provider portion of the
email address from the email field:
REGEX([email],"^[a-zA-Z0-9._%+-]+@([a-zA-Z0-9._-]+)\.[a-zA-Z]{2,4}$")

Capturing Groups and the REGEX_REPLACE Function

You can use the REGEX_REPLACE function to match a string, and replace matched strings with another
value. The REGEX_REPLACE function takes 3 arguments:
• Input string
• Matching regex
• Replacement regex
You can use capturing groups to capture backreferences, but the entire match is always returned.

Capturing Groups and Backreferences

You can use a backreference to refer back to the matched content of a particular capturing group number.
Typically, you use a backreference in the same regular expression that contains the capturing group. You
specify a backreference by referring to the group number preceded by a backslash. Use \1 to refer to
capturing group 1, \2 to refer to capturing group 2, and so on.
Suppose you want to match a pair of HTML tags and their enclosed text. You could capture the opening
tag into a capturing group, and then use a backreference to match the corresponding closing tag:

(<([A-Z][A-Z0-9]*)\b[^>]*>.*?</\2>)

This regular expression contains 2 capturing groups:

• Group 1 contains the outermost parentheses and captures the entire string.
• Group 2 captures the string matched by [A-Z][A-Z0-9]*.
You can then refer to group 2 using the \2 backreference to match the corresponding closing HTML tag.
When you use the REGEX_REPLACE function, you can use a backreference to refer to a capturing group
in the previous regular expression. The syntax is slightly different when you use a backreference to refer
to a group in the previous regex. Use a dollar sign ($) before the group number, such as $1 to specify a
backreference to group 1 of the previous expression.
Suppose you have a phone_number field where the values are formatted as xxx.xxx.xxxx. The
following example matches the values in phone_number and replaces them with values formatted as
(xxx) xxx-xxxx:

REGEX_REPLACE([phone_number],"([0-9]{3})\.([[0-9]]{3})\.([[0-9]]
{4})","$$1$ $2-$3")

Notice the backreferences in the replacement expression. They refer to the capturing groups of the
previous matching expression.

Non-Capturing Groups
In some cases, you might want to use parenthesis to group subpatterns, but not capture text. A non-
capturing group starts with (?: (a question mark and colon following the opening parenthesis). For
example, h(?:a|i|o)t matches hat or hit or hot, but does not capture the a, i, or o from the
subexpression.

People Analytics

Setup Considerations: People Analytics

You can use this topic to help make decisions when planning your configuration and use of People
Analytics. It explains:
• Why to set it up.
• How it fits into the rest of Workday.
• Downstream impacts and cross-product interactions.
• Security requirements and business process configurations.
• Questions and limitations to consider before implementation.
Refer to detailed task instructions for full configuration details.

What It Is
Workday People Analytics uses augmented analytics technology to surface prioritized insights in the
form of key metrics and business questions, along with their underlying drivers. People Analytics uses
explanatory stories to help you understand these insights and act on the most critical trends and gaps in
your workforce.

Business Benefits
The out-of-the-box, AI-powered insights provided by People Analytics enable you to:
• Identify important opportunities and risks around key workforce metrics.
• Detect patterns that you might not see or have time to discover.
• Eliminate time-consuming, manual analysis, enabling you to focus on strategic work.
• Track workforce developments with clearly written narratives in natural language.

Use Cases
You can track key metrics and trends in these topic areas:
• VIBE Index™
• Diversity and Inclusion
• Organization Composition
• Retention and Attrition
• Hiring
• Talent and Performance
• Skills

Questions to Consider

Question Consideration
What topics are you interested in exploring? You can opt in to each of these topic of interest for
your People Analytics application:
• VIBE Index
• Diversity and Inclusion
• Organization Composition
• Retention and Attrition

Question Consideration
• Hiring
• Talent and Performance
• Skills
• Employee Sentiment
Each topic of interest comprises 1 tab in the
application UI, with the exception of Employee
Sentiment, which is part of the VIBE Index tab.
Topics of interest also have different field selections
requiring your attention as you configure People
Analytics with a Workday consultant.
Raise a Customer Care ticket to request
information if you're interested in:
• Worker topics. These topics are only available if
you've purchased the HCM SKU.
• The Hiring topic. This topic is only available for
Workday Recruiting customers.
• The Skills topic. This topic is only available if you
have purchased the HCM SKU.
• The Employee Sentiment topic. This topic is
only available for Workday Peakon Employee
Voice customers who have opted into the VIBE
Index.

What fields do you want to include in your analysis? A Workday consultant will guide you through the
selection of fields to map to the structure of the
People Analytics data model. These field choices
have a direct impact on how insights are created
and on the quality of these insights.
For each topic of interest you select, some fields
are required and some fields are optional. You can
also customize each field display name.

Which workers do you want to include in your You can filter out populations from the analysis.
analysis? Example: You can filter out contingent workers. The
populations you filter out at installation won't be
included in any analysis.
When you include a population in your analysis,
they’re included in each KPI, visualization, and
business question, in all topic areas, except VIBE.
You define the populations that you want to include
in the VIBE Index when you configure the VIBE
intersection.

Can you filter data in the People Analytics You can use the sheet filters in the application
application after filtering out populations during UI to view insights for different areas of the
installation? organization. The fields that you map during
configuration and the security permissions of the
user determine which views are available. Example:
An HR business partner who represents multiple
supervisory organizations can select different filters
to view stories dynamically for these organizations.

Recommendations
When configuring People Analytics, consider the target audience of the application: HR Business Partners
and executives within an organization. Configuration choices (mapped fields, included or excluded
populations, and so on) impact the content made available for these users.
We recommend that you run People Analytics Data Quality and correct any defects in your configuration
before installing the application. Data Quality also runs automatically when you install the application. You
can run Data Quality from the Configure People Analytics report and view the results by accessing the
People Analytics Data Quality report.
Note: Data Quality module doesn’t check the data obtained from Peakon.

Requirements
Note: You must subscribe to Innovation Services to use this feature. Contact your Customer Success
Manager to request the Innovation Services Addendum (ISA), or see Workday Innovation Services in the
Workday Community for more information.
Note: To access the Employee Sentiment topic of interest, raise a Customer Care ticket to enable the API
data export toggle in your Peakon account and activate the VIBE Index topic of interest in the Configure
People Analytics report.
In order for People Analytics to perform analysis successfully, you must have at least 5 months of
transactional worker data in Workday. You can select 4 to 36 months of historical data to load into People
Analytics from Workday for analysis. Any transactional history converted during deployment is considered
part of the initial data load.
The amount of data history you have in People Analytics determines the analysis type. Year-over-year
analysis requires at least 13 months of data. Rolling 3 month analysis is available with 4 to 12 months of
data.
When you install People Analytics, you automatically enable the automated update activity, which includes
a monthly data refresh. This enables the application to continue to load and analyze the latest data into
Workday on the first Monday of every month. If the initial data load is less than 13 months, the analysis
type automatically changes from rolling 3 month analysis to year-over-year analysis when 13 months of
data are available and loaded into People Analytics. The maximum amount of data history you can have in
People Analytics is 36 months.
Note: For the Belonging metric in the VIBE Index, only the data collected after the Peakon API data export
toggle is turned on can be incorporated into the VIBE Index. Even if you don’t intend to use the metric at
the time, you can still enable the API data export to accumulate a more extensive dataset for potential
future analysis.

Limitations
You can create custom reports and discovery boards using People Analytics data sources for ad hoc
reporting purposes or to validate your data. These resources are only valid until the next automated
update or until you run Data Quality or installation again. However, you must delete these resources
before the next Data Quality, automated update, or installation run to ensure that these activities complete
successfully.

Tenant Setup
No impact.

Security

Domains Considerations

Manage: People Analytics in the People Analytics Can maintain People Analytics.
and Prism Analytics functional areas.

View: People Analytics in the People Analytics and Can access People Analytics.
Prism Analytics functional areas.

For the initial deployment of People Analytics, you can work with a Workday consultant to:
• Configure the securing entity during the configuration and installation of People Analytics.
• Add security groups to a People Analytics domain. You can:
• Add an existing Workday security group, or
• Create a new security group specifically for People Analytics users.
• Add more than 1 security group.
If necessary, you can make post-deployment changes using the Configure People Analytics report.
People Analytics Office Hours are available as a paid service if you would like to request support for
making changes.
People Analytics supports:
• Constrained role-based security groups.
• Unconstrained role-based security groups.
• Unconstrained user-based security groups.

Business Processes
No impact.

Reporting
No impact.

Integrations
No impact.

Connections and Touchpoints

Workday offers a Touchpoints Kit with resources to help you understand configuration relationships in your
tenant. Learn more about the Workday Touchpoints Kit on Workday Community.
The Employee Sentiment topic of interest interacts with Workday Peakon Employee Voice through its API.
Related Information
Concepts
Concept: Security in People Analytics on page 558
Concept: Storyteller Engine on page 609
Concept: Belonging in the VIBE Index on page 601
Reference
Workday Community: Generally Available Innovation Services - Descriptions and Exhibits
2022R2 What's New Post: VIBE Index for Workday Peakon Employee Voice
2022R1 What's New Post: Data Quality for People Analytics
2022R1 What's New Post: Skills in People Analytics

2021R2 What's New Post: VIBE Index in People Analytics

2021R2 What’s New Post: People Analytics Administration
The Next Level: People Analytics Product Demonstration
People Analytics Office Hours

Steps: Prepare for People Analytics Installation

Prerequisites
Note: You must subscribe to Innovation Services to use this feature. Contact your Customer Success
Manager to request the Innovation Services Addendum (ISA), or see Workday Innovation Services in the
Workday Community for more information.
• Review setup considerations for People Analytics.
• Create a Setup Feature request to enable the setup of People Analytics and Prism Analytics on your
tenant.
• For Workday Peakon Employee Voice customers: Enable the API data export toggle in your Peakon
account.

Context
Workday People Analytics uses augmented analytics technology to surface key metrics and business
questions and their underlying drivers so that you can understand and act on workforce trends.

Steps
1. Access the Innovation Services and Data Selection Opt-In report.
On the Innovation Services Opt-In task, select the People Analytics service on the Available
Services tab in the Analytics category.
On the Maintain Innovation Services Data Selection Opt-In task, click Next.
Security: Manage: Innovation Services domain in the Innovation Services functional area.
2. Work with a Workday consultant to set up the security groups needed for People Analytics.
3. (Optional) On the Workday Home page, click the gear icon to add the Configure Analytical Apps and
People Analytics worklets.
4. Work with a Workday consultant to select the configuration inputs (topics, fields, population filters,
prompts, securing entity, and data history) to apply to your configuration of People Analytics.
5. Work with a Workday consultant to create tenant-wide calculated fields that you need for your
configuration based on your field selection.
6. Work with a Workday consultant to set up features in Workday that are needed to complete certain
topic configurations in People Analytics.
Example: Skills Cloud in Workday.
7. Raise a Customer Care ticket to turn on the export API toggle in your Workday Peakon Employee Voice
account.

Result
Your tenant is ready for People Analytics installation.

Next Steps
Using the Configure People Analytics report, work with a Workday consultant to:
• Complete your configuration.

• Run Data Quality and correct any defects in your configuration.

• Install the application.
You can access the People Analytics Activities report after the installation has started to monitor
installation progress.
Related Information
Concepts
Setup Considerations: People Analytics on page 542
Concept: Data Quality Module on page 559
Concept: People Analytics Activities on page 561
Reference
Workday Community: Generally Available Innovation Services – Descriptions and Exhibits
Workday Community: Setup Feature Tenant Request

Maintaining People Analytics

Steps: Change People Analytics Configuration

Prerequisites
• Complete the initial configuration and installation of People Analytics with a Workday consultant.
• Review requirements and considerations for changing People Analytics configuration.
• Plan to run the reinstallation of People Analytics only from Monday to Thursday. Weekly Service
Updates in Workday run on Fridays and can cause the installation to fail.
• Access the People Analytics Activities report to ensure that there are no activities in progress.
• Security: Manage: People Analytics domain in these functional areas:
• People Analytics
• Prism Analytics

Context
You can change your People Analytics configuration and reinstall the application to:
• Ensure that the application is up to date with the business needs of your organization. Example:
Change the mapping for a field in a particular pipeline, or adding a new population filter condition.
• Uptake new content that we deliver as an automated update to production tenants. Example: Enable
and configure the Employee Sentiment topic area.
We recommend that you review Data Quality to evaluate the new configuration and correct any defects
before you reinstall.
Certain changes to your configuration might result in a significant change to application insights and the
data quality of these insights. Example: Applying a new security configuration that doesn't align with your
current organization structure. You might consider requesting assistance with People Analytics Office
Hours (available as a paid service) for these types of changes.
We recommend making changes to your configuration in an implementation tenant or preview sandbox
tenant before you complete them in your production environment.
Note: You can create custom reports and discovery boards using People Analytics data sources for ad
hoc reporting purposes or to validate your data. Custom reports or discovery boards that you created using
these data sources are no longer valid after the next monthly data update or when you run data quality or
reinstall the application. You must delete these reports and discovery boards before the next data quality
check, monthly data update, or installation run to ensure that these activities complete successfully.

Steps
1. Access the Configure People Analytics report.
2. Select Manage Topics to select which topics to include in the configuration.
3. Select Edit or Configure for a pipeline to make changes to that pipeline.
See Steps: Configure a Pipeline in People Analytics on page 548.
4. Select Run Data Quality to check the correctness requirements of the configuration changes.
5. Select View Activities to access the People Analytics Activities report to monitor data quality check
progress.
You can right-click the data quality activity at the top level to access the related actions menu. You can:
• Cancel the activity.
• Retry the activity.
6. Ensure that the data quality activity finishes with the status Successful.
If necessary, we recommend that you update your configuration to address any found defects. Certain
defects might require action before proceeding to installation. For more information, see:
• Concept: Data Quality Module on page 559
• Troubleshooting: Data Quality Module on page 595
7. On the Configure People Analytics report, select Run Installation.
Workday automatically runs the data quality check before committing the configuration changes.
8. Select View Activities to access the People Analytics Activities report to monitor installation
progress.
You can right-click the Installation activity at the top level to access the related actions menu.
9. Ensure that the Installation activity finishes with the status Successful.

Steps: Configure a Pipeline in People Analytics

Prerequisites
Security: Manage: People Analytics domain in these functional areas:
• People Analytics
• Prism Analytics

Context
You can configure a pipeline in People Analytics to:
• Specify which fields Storyteller should analyze for creating stories.
• Filter which populations to analyze.
• Specify how many months of data to analyze.
• Enforce security on the data.
Workday displays the current status of each pipeline on the Configure People Analytics report.

Pipeline Status Description

Committed The current pipeline configuration is committed and installed in the
People Analytics application.
Not Committed The current pipeline configuration has changed since the last
installation. To commit these changes to the People Analytics
application, select Run Installation.
Action Required The pipeline isn't configured correctly to install People Analytics. The
pipeline status might be because:

Pipeline Status Description

• Workday has changed 1 or more pipeline settings since the last
installation. You need to configure the pipeline to confirm or
configure some settings before you can reinstall the application.
• The pipeline is partially configured.
• The pipeline was never configured.

Steps
1. Access the Configure People Analytics report.
2. Select Edit or Configure for a pipeline to make changes to that pipeline.
3. (Skills pipeline only) On the Opt In step, select Match Score.
4. (Employee Sentiment pipeline only) On the Question Selection step, for each question type, select
one or more questions to map.
5. Configure Pipeline Field Mappings on page 554.
For the Skills pipeline, proceed to the Review step.
6. (Optional) On the Population Filters step, add population filters to constrain the data that Workday
analyzes using the Storyteller engine.
The population filters you define affect all business questions, visualizations, stories, and KPIs in the
People Analytics application.
7. (Worker pipeline) On the Prompts step, configure prompts for the source data for this pipeline.
8. On the Security step, select how to enforce security in the application.
You can:
• Provide unconstrained access. Anyone who has permission to view the People Analytics report can
see all data.
• Constrain access to the data by selecting one of the configured hierarchies from the Field Mapping
step:
• Primary hierarchy. When you constrain access using the primary hierarchy, ensure that
the Assigned Organization field accurately reflects the current position of the worker or job
requisition.
• Secondary hierarchy. When you constrain access using the secondary hierarchy, ensure that the
Level 3 field is associated with the worker or job requisition.
For more details, see Steps: Set Up Constrained Security to People Analytics on page 550.
Note: Select the same security option for both the worker and hiring pipelines.
9. On the Data History step, select how much data to include in the application.
10.Review all configuration details, and select Finish to save the changes.

Result
Workday saves the pipeline configuration, but doesn't update the data in the application yet. Workday
changes the pipeline state to Not Committed.

Next Steps
Configure all pipelines necessary and then select Run Installation on the Configure People Analytics
report.
Related Information
Reference
2022R2 What's New Post: People Analytics Configuration

Steps: Set Up Constrained Security to People Analytics

Prerequisites
Security: Manage: People Analytics domain in these functional areas:
• People Analytics
• Prism Analytics

Context
You can provide constrained access to the People Analytics report. To provide constrained access:
• Specify a hierarchy on the Security step when you configure the worker and hiring pipelines.
• Use role-based constrained security group in the View: People Analytics domain security policy.
The hierarchy that you select and the fields included in that hierarchy determine which users have access
to specific content in the application. Example: You map these fields:

Target Field Mapped Business Object and Example Value

Source Field
Level 1 Supervisory Organization - 2nd Sales and Marketing
level of the hierarchy
Level 2 Supervisory Organization - 3rd North America Marketing
level of the hierarchy
Assigned Organization Worker - Supervisory Leads Generation
Organization

A People Analytics user who has constrained access at Level 1 can view stories related to Level 1 and
its subordinates. Therefore, a user who is assigned a role in Sales and Marketing sees stories Sales and
Marketing and North America Marketing.
A People Analytics user who is assigned a role in North American Marketing (mapped to Level 2) can see
stories related to North American Marketing, but not to Sales and Marketing.
Workday secures data in People Analytics at the table level and record level. Users who have access to a
record in People Analytics have access to every field in that record.
If you need to change the security settings after the initial deployment of People Analytics, you might
consider requesting support through People Analytics Office Hours (available as a paid service) to ensure
that the change won't cause security issues.

Steps
1. Access the Configure People Analytics report.
2. Select Edit for the Worker pipeline, and proceed to the Security step.
3. On the Security step, select either Primary Hierarchy or Secondary Hierarchy.
The hierarchy you select must be a valid Prism securing entity field. See Hierarchy Requirements.
4. On the Review step, select Finish to save the changes to the Worker pipeline.
5. Configure the Hiring pipeline, and select the same securing hierarchy on the Security step.
6. Select Run Installation on the Configure People Analytics report.
Note: Wait for the installation activity to complete before proceeding so that Workday can finish
securing the data records. Make sure that Workday secures the data records before you provide access
to constrained users.

7. Create Role-Based Security Groups.

Create security groups for your application viewers, and assign users.
Note: When configuring role-based constrained security groups, ensure that:
• The security group type matches the securing hierarchy that you specified. Example: You use
Primary Hierarchy as the securing hierarchy, and map the Supervisory Organization field to the
Assigned Organization target field. You create a security group of type Roles - Supervisory.
Example: You use Secondary Hierarchy as the securing hierarchy, and map the Location field to the
Level 3 target field. You create a security group of type Roles - Location Hierarchy.
• In the Access Rights to Organizations section, you select Applies To Current Organization And
All Subordinates.
• In the Access Rights to Multiple Job Workers section, you select Roles have access to the
positions they support.
8. Edit Domain Security Policies.
Add the role-based constrained security groups to the View: People Analytics domain security policy.
Provide both View and Modify permissions.
9. Activate Pending Security Policy Changes.
Related Information
Concepts
Concept: Security in People Analytics on page 558
Tasks
Steps: Change People Analytics Configuration on page 547
Reference
2022R2 What's New Post: People Analytics Configuration

Steps: Set Up Skills in People Analytics

Context
The Skills topic area in People Analytics helps you better understand key insights about skills in different
areas of the organization, gaps, and areas for improvement.

Steps
1. Access the Innovation Services and Data Selection Opt-In report.
On the Innovation Services Opt-In task, Available Services tab, select the:
• People Analytics service in the Analytics category.
• HCM Machine Learning GA Features service in the HCM category.
On the Maintain Innovation Services Data Selection Opt-In task, select check boxes in the HCM:
HCM Machine Learning GA Features category to contribute data for Machine Learning. To enable

People Analytics to use Skills data from the HCM Machine Learning GA Features service, you must opt
in to these categories:
• Job Requisition Data
• Talent Profile Data
• Worker Profile Data
• Organizational Data
Important: For all tenant types, after you select the required check boxes in the HCM: HCM Machine
Learning GA Features category, you must wait 24 hours (or until after 1AM Pacific Standard Time on
the next business day) before you install Skills in People Analytics. For implementation tenants, you
need to also run the Run On-Demand Machine Learning Activation for Implementation Tenant task
after selecting the required check boxes, and before you install People Analytics.
Security: Manage: Innovation Services domain in the Innovation Services functional area.
2. (Optional) Access the Edit Tenant Setup - Machine Learning task.
Select the region in which Workday hosts data contributed to the Machine Learning Development
Environment (MLDE). The default region for the MLDE is the U.S.
Security: Set Up: Tenant Setup - Machine Learning in the System functional area.
3. Enable Skills Cloud.
You must include these options:
• Convert Duplicate Skills to Skills Cloud Skills
• Convert Synonymous Skills to Skills Cloud Skills
• Populate Suggested Skills for Workers
• Populate Suggested Skills for External Candidates
The Convert Duplicate Skills to Skills Cloud Skills and Convert Synonymous Skills to Skills
Cloud Skills options remove duplicate and synonymous skills respectively from the Maintain Skills
report, which you must edit in Step 4 of this task. To ensure the Maintain Skills report is up to
date before you make changes, we recommend that you allow sufficient processing time. Workday
processes 100 skills per hour for each of these background jobs.
You can also include the option Populate Suggested Skills for Job Profiles to provide suggested
skills for job profiles in the Suggested Skills for Job Profile report. The skill suggestions update hourly
and provide up to 10 suggested skills for each reporting item. You add skills to job profiles in Step 5.
4. Maintain Skills.
You must select an existing or create a new Category for each skill in the Maintain Skills report.
See Steps: Maintain Skills.
5. Access the Create Job Profiles task or the Edit Job Profiles task to add skills to new or existing job
profiles.
For each skill that you add, ensure that you select Required.
When completing this step, be mindful of the Effective Date for a job profile. Ensure that the date
covers the previous month to align with the current snapshot period for People Analytics.
See Create Job Profiles.
Security: Set Up: Job Domain in the Jobs and Positions functional area.

6. Steps: Change People Analytics Configuration on page 547.

Use these details to complete this step:
• From the Manage Topics page, enable the topic area Skills. You must have at least one other
Worker topic selected to enable Skills and you must complete the configuration for the Worker
pipeline.
• Complete the configuration for the Skills pipeline. We recommend that you use the default field for
each field that you include in the field mapping to ensure the highest quality results.
Related Information
Concepts
Concept: Skills in People Analytics on page 604
Concept: Skills and Competencies Comparison
Setup Considerations: Skills Cloud
Reference
2022R1 What's New Post: Skills in People Analytics

Steps: Set Up VIBE Index in People Analytics

Context
If your People Analytics installation doesn't include the VIBE Index topic area, you can configure it now.
Workday Peakon Employee Voice customers can also opt in to the Employee Sentiment topic area that
offers a Belonging outcome in the VIBE Index.
All requirements and considerations for changing your People Analytics configuration apply when changing
your configuration to include the VIBE Index topic area.

Steps
1. Review the details for choosing and creating intersections.
See Reference: Choosing and Creating Intersections on page 568.
2. Define the intersection for the VIBE Index.
You can:
• Use the default intersection.
• Use an existing field in your tenant.
• Create an intersection.
3. Steps: Change People Analytics Configuration on page 547.
Use these details to complete this step:
• On the Manage Topics page, enable the topic area VIBE Index. You must have at least one other
Worker topic selected to enable VIBE.
• If applicable, on the Manage Topics page, enable the topic area Employee Sentiment.
• On the Field Mapping page, map your VIBE Index intersection field to the target field Intersection 1.
Related Information
Concepts
Concept: VIBE Index in People Analytics on page 599
Concept: Belonging in the VIBE Index on page 601
Tasks
Steps: Change People Analytics Configuration on page 547
Reference
2021R2 What's New Post: VIBE Index in People Analytics
Reference: Requirements and Considerations for Changing People Analytics Configuration on page 563

People Analytics Office Hours

Configure Pipeline Field Mappings

Prerequisites
Security: Manage: People Analytics domain in these functional areas:
• People Analytics
• Prism Analytics

Context
When you configure a pipeline in People Analytics, you specify which fields to include for analysis.
Workday provides a list of target fields grouped into categories, and you provide a source field to map to
each target field. Each target field accepts specific field types. Example: The Ethnicity target field accepts
either a Text or Instance field.
The fields you include and configure affect:
• The data Storyteller uses for generating stories.
• The metrics that People Analytics calculates for KPIs, vizzes, and stories.
• How Workday enforces security for application viewers.
• The filters available to application viewers.
Note: The target fields that you configure in the Primary Hierarchy and Secondary Hierarchy categories
must be identical in the worker and hiring pipelines. Make sure that you:
• Select the same or compatible source fields.
• Include the same target fields in each pipeline.
• Enter the same display name.

Steps
1. Access the Configure People Analytics report.
2. Select Edit for either the Worker or Hiring pipeline.
3. For each Target Field, decide whether or not to Include the field.
Workday automatically includes fields that it requires for the functionality of People Analytics, based on
topics of interest selected by you. Installation can’t proceed if you exclude any of these fields. Workday
marks required fields with an asterisk (*). Workday also distinguished fields crucial for the effectiveness
of data as "Recommended". If you exclude such a field, the People Analytics installation will work, but
the missing data might negatively impacts metrics in the KPIs and vizzes, and in the stories generated.
4. When you include a field, consider:
Option Description
Business Object The business object that includes the source field
that you want to map to this target field.
People Analytics only supports mapping source
fields from the primary business object of a given
pipeline and the related business objects of
that primary business object. See Reference:
Business Objects and Data Sources in People
Analytics on page 591.

Source Field The source field to map to this target field.

Option Description
Workday displays the fields from the selected
business object that use any of the accepted field
types for this target field.
Select a compatible source field in both the
worker and hiring pipelines for the same target
field. Source fields are compatible when:
• They use the same business object.
• Any field values that they contain with the
same display name use the same Workday ID.

Display Name The name you want to display in the People

Analytics application.
Workday uses the display name in KPIs, vizzes,
stories, all charts, and application filters on the
People Analytics report.

For more information, see Reference: Fields in People Analytics on page 573.

Next Steps
Finish configuring the People Analytics pipeline. If you need more time to configure the pipeline, you can
Save For Later to save the changes you've made so far.
Related Information
Reference
2022R2 What's New Post: People Analytics Configuration

Concept: Hierarchies and Organizations in People Analytics

When you configure People Analytics for the worker and hiring pipelines, you select which fields to include
in the application. Workday groups the hierarchy and organization-related fields into these categories:
• Primary Hierarchy
• Secondary Hierarchy
• Organization Details
Workday makes the hierarchy categories and target field names generic to give you flexibility when
deciding which hierarchies that you assign to each category. When deciding which hierarchies to use,
consider how they affect the rest of the application.
The hierarchies and organizations you include in People Analytics determine:
• How Storyteller groups data into different combinations of dimensions for analysis. Workday uses each
field value as a dimension for grouping and analyzing data before aggregating metrics.
• How Workday enforces contextual security in the application. When you select either the Primary
Hierarchy or Secondary Hierarchy for security, Workday uses all source fields mapped in that category
for constraining viewer access to data. The hierarchy that you specify for security must be a valid Prism
securing entity. See Concept: Security in People Analytics on page 558.
• Which filters to display to application viewers. The Level 1, Level 2, and Level 3 target fields that
you include from both hierarchy categories will display as application filters to viewers. See Concept:
Filtering in People Analytics on page 605.
Note: The target fields that you configure in the Primary Hierarchy and Secondary Hierarchy categories
must be identical in the worker and hiring pipelines. Make sure that you:
• Select the same or compatible source fields.

• Include the same target fields in each pipeline.

• Enter the same display name.

Hierarchy Requirements
The hierarchies you use for the Primary Hierarchy and Secondary Hierarchy must meet these
requirements:
• Level consistency. Every child node of a particular parent must be at the same level.
• Single hierarchy. Child nodes can only have 1 parent.
• Population consistency. The worker population can be assigned to 1 hierarchy only. No duplicates are
allowed.
When you configure constrained access to People Analytics using either the Primary Hierarchy or
Secondary Hierarchy, the hierarchy must also meet these requirements:
• Security consistency. Users must be constrained at the specified levels in the hierarchy you use for
security. Example: You specify Primary Hierarchy for security and map source fields to the Level 1,
Level 2, and Level 3 target fields. Users must be constrained at the levels specified for Level 1, Level 2,
and Level 3. Any user constrained at lower levels won't see any stories in the application.
• Supported hierarchy type. The hierarchy must be on of these types:
• Business Unit Hierarchy
• Company Hierarchy
• Cost Center
• Cost Center Hierarchy
• Custom
• Custom/Financial
• Custom/Staffing
• Location Hierarchy
• Region
• Region Hierarchy
• Supervisory

The Assigned Organization Target Field

Workday uses the data in the Assigned Organization target field to determine which organization the
worker is currently assigned to. Typically, this is Supervisory Organization. People Analytics automatically
detects changes due to a reorganization. It ignores stories that result from workers being reassigned to
different organizations, presenting significant stories in the application.

Target Field Descriptions

The Primary Hierarchy category includes these target fields:

Target Field Notes

Assigned Organization The organization that is assigned to the primary position of the worker or the
primary position of the job requisition.
Select a field that accurately reflects the current organization assigned to
or associated with a worker or job requisition. Typically, this is Supervisory
Organization, but in rare cases might be a different organization type, such as
a custom organization or Cost Center.

Level 1 The 1st level of the hierarchy that you want to analyze. Typically, this is the
2nd level from the top of the organization, 1 level below the CEO.

Target Field Notes

The field you select must be in the same organization hierarchy as the
Assigned Organization.

Level 2 The 2nd level of the hierarchy that you want to analyze. Typically, this is the
3rd level from the top of the organization, 2 levels below the CEO.
The field you select must be in the same organization hierarchy as the
Assigned Organization.
When you opt into the level below this level, you must opt into this level, too.

Level 3 The 3rd level of the hierarchy that you want to analyze. Typically, this is the
4th level from the top of the organization, 3 levels below the CEO.
The field you select must be in the same organization hierarchy as the
Assigned Organization.

The Secondary Hierarchy category includes these target fields:

Target Field Notes

Level 1 The 1st level of the hierarchy that you want to analyze. Typically, this is part of
a geographical hierarchy, such as market region.
Level 2 The 2nd level of the hierarchy that you want to analyze. Typically, this is part
of a geographical hierarchy, such as country.
When you opt into the level below this level, you must opt into this level, too.

Level 3 The 3rd level of the hierarchy that you want to analyze. Typically, this is part of
a geographical hierarchy, such as city.
When you constrain access to the application data using the secondary
hierarchy, then this level must be associated with the worker, and you must
opt into this field.

The Organization Details category includes these target fields:

Target Field Notes

Organization Level The number of levels down from the top level of the organization in the primary
hierarchy to the worker’s level.
Applies to the worker pipeline only.

Management Level The management level of the worker or the job profile on the job requisition.
Cost Center Cost center (or equivalent) used for reporting. If you use Cost Center as the
primary or secondary hierarchy, then you can select a field from a different
organization that Workday can use for providing more details on the worker or
job requisition.
Company Company name or ID of the company.
Applies to the worker pipeline only.

Related Information
Reference
2022R2 What's New Post: People Analytics Configuration

Concept: Security in People Analytics

Workday enforces security when you:
• Administer and configure People Analytics.
• View the People Analytics application.
For the initial deployment of People Analytics, you work with a Workday consultant to determine which
security settings best fit your organization and support your desired use of the application. However, you
can use the Configure People Analytics report to make changes after the initial deployment. Any change
you make to the domain security policy groups, organization hierarchies, or securing hierarchy will impact
the data viewers see in the application.
If you want to make post-deployment changes to your security configuration, you might consider requesting
assistance with People Analytics Office Hours (available as a paid service).

People Analytics Application Security

When you view the People Analytics application using the People Analytics report, Workday uses its
configurable security model to control which users have access to specific data. Workday controls access
to the data in:
• Stories
• KPIs
• Vizzes
• Specific data records
Although the People Analytics data comes from the business objects in your tenant, Workday resets all
security domains configured for the business objects and applies new security that you define. The new
security that Workday applies is determined by:
• The specified groups in the View: People Analytics domain security policy
• The selected setting in the Security step when you configure a pipeline in People Analytics. You can
configure unconstrained or constrained access.

Configuring People Analytics Security

When configuring People Analytics, you decide whether or not to constrain access to the data in the
People Analytics application. When you configure the Hiring and Worker pipelines, you specify how to
secure access to the data on the Security step.
On the Security step, you can configure either:
• Unconstrained access. Select Unconstrained Access, and use either a user-based or unconstrained
role-based security group in the View: People Analytics domain security policy.
• Constrained access. Select either the Primary Hierarchy or Secondary Hierarchy. The securing
hierarchy that you select and the fields included in that hierarchy determine which users have access to
specific data in the application. For more information, see Steps: Set Up Constrained Security to People
Analytics on page 550.
Workday constrains access at the record level, not the field level.
This means that a user who is constrained at a specific level within the selected hierarchy can view insights
only for that level and subordinate levels.

How Contextual Security Works

When you provide constrained access to People Analytics, different users will see different data. How
Workday displays the data in People Analytics depends on:
• The content type
• The user’s role and organization level permissions

Content Type Notes

KPIs and Stories Workday displays stories based on your org level security access at
Level 1, Level 2, and Level 3.
Vizzes Workday displays every viz, such as Gender Trend, but only
calculated on the records you have access to at any level.

Security Domains and Groups

People Analytics uses these domains in the People Analytics and Prism Analytics functional areas:

Domain Details Associated Reports and Tasks

Manage: People Analytics Can configure, install, and • Configure People Analytics
maintain People Analytics. • People Analytics Activities
Supports unconstrained security • People Analytics Data Quality
groups. • People Analytics

View: People Analytics Can access the People Analytics • People Analytics
application.
Supports unconstrained
security groups and role-based
constrained security groups.

Related Information
Tasks
Steps: Set Up Constrained Security to People Analytics on page 550
Steps: Change People Analytics Configuration on page 547
Edit Prism Data Source Security on page 424
Create Role-Based Security Groups
Create User-Based Security Groups
Edit Domain Security Policies

Concept: Data Quality Module

The Data Quality module checks your field mapping configuration data to verify that the data satisfies the
usefulness, completeness, and correctness requirements of People Analytics and Storyteller. The Data
Quality module checks these data for issues that will negatively impact your People Analytics installation
and application and returns data quality defects that may need to be addressed before proceeding.
Note: The Data Quality module currently checks the field mapping configuration data for the Worker and
Hiring pipelines, not the Skills pipeline.
Workday automatically runs the Data Quality module when you install or reinstall People Analytics, but you
can also run it manually. Workday recommends that you manually run the Data Quality module before
reinstalling People Analytics to check that any newly made configuration changes meet all requirements.
You can run Data Quality from the Configure People Analytics report and view the results by accessing
the People Analytics Data Quality report.
Some defects have a greater negative impact than other defects. Workday assigns a severity level to each
defect:
• Critical. Critical defects can prevent People Analytics from installing successfully. These defects can
also severely impact the quality of data and the integrity of analysis results, and can potentially impact
constrained security. If encountered, address the critical defects in the Configure People Analytics
report or in your underlying data.

• Major. Major defects won't prevent a successful installation, but they can severely impact the quality of
data and the integrity of analysis results. Workday recommends that you address these issues in the
Configure People Analytics report.
• Moderate. Moderate defects can impact the quality of the KPIs, visualizations, and stories in People
Analytics. You may ignore them as their impact on the quality of data is minimal.
The Data Quality module includes these check types:
• Cardinality
• Cross Pipeline Consistent Values
• Cross Pipeline Data Types
• Duplicates
• Illogical Values
• Invalid Values
• Missing Values
• Multiple Hierarchies
• Population

Cardinality
Checks the number of unique values in a particular field. Compares the number to a threshold defined for
that field, and checks whether the cardinality for the field is consistent in terms of expected levels within the
hierarchy. Workday returns the field that fails the check and shows the cardinality of the field in the Value
column.
High cardinality (a lot of unique values) can negatively affect Storyteller engine performance, and it might
also result in low quality stories due to a large number of smaller populations.

Cross Pipeline
Consistent Values
Checks the consistency of values across pipelines and compares the two pipeline-to-pipeline values to a
defined threshold. Currently, the threshold is when no values overlap in the same field in each pipeline.
Workday returns the fields from each pipeline that fail the check and shows the percentage of inconsistent
values from each pipeline in the Value column.
Data Type
Checks whether a particular field in multiple pipelines is the same by inspecting the field type. Workday
returns the field that fails the check and shows the data types for the field in the Value column.
Cross pipeline defects can severely impact filtering on the KPI tab by preventing a filter you configure from
filtering data in multiple pipelines.

Duplicates
Checks whether there are multiple records of the same worker. Workday returns the Employee ID or
Candidate ID and shows the number of multiple records in the Value column.
Duplicate records cause inaccurate headcounts, potentially with exponential impact.

Illogical Values
Checks if a particular field contains values that fail logic rules defined for that field. Example: if the hire date
is in the future. Workday returns the field that fails the check and shows the percent of illogical values for
that field in the Value column.
Illogical values can lead to inaccurate metrics in topic areas, leading to inaccurate data in visualizations,
KPIs, and stories.

Invalid Values
Checks if a particular field contains values that aren’t in the list of valid values defined for that field.
Workday returns the field that fails the check and shows the percent of invalid values for that field in the
Value column.
Invalid values can lead to inaccurate metrics in topic areas, leading to inaccurate data in visualizations,
KPIs, and stories.

Missing Values
Checks how many values a particular field is missing. Missing values can be blank or NULL. Workday
returns the field with missing values and shows the percent of missing values for that field in the Value
column.
Missing values might skew the data presented in People Analytics, preventing an accurate reflection of
your workforce.

Multiple Hierarchies
Checks whether a child in a hierarchy has parents across multiple hierarchies. Workday returns the field of
the child hierarchy with parents across multiple hierarchies and shows the number of multiple hierarchies in
the Value column.
A multiple hierarchies defect can result in inaccurate data due to duplication, and it can negatively impact
constrained security by potentially displaying to a viewer workers who aren’t in their organization.

Population
Checks the number of unique values in a particular VIBE Index intersection, and compares the number
to the minimum headcount requirement defined for VIBE Index intersections. Workday returns the
intersection field and the number of intersections that fail the check, and shows the number of records for
intersections that don’t have sufficient populations in the Value column.
Population check defects cause Workday to exclude a particular intersection from the VIBE calculation.
Related Information
Reference
Troubleshooting: Data Quality Module on page 595
2022R1 What's New Post: Data Quality for People Analytics

Concept: People Analytics Activities

An activity in People Analytics is a series of job processes that perform a complete task. There are 3 types
of activities in People Analytics.

Data Quality Activity

Workday automatically runs the Data Quality module when you install or reinstall People Analytics, but
you can also run it manually. The Data Quality module checks your field mapping configuration data
to verify that the data satisfies the usefulness, completeness, and correctness requirements of People
Analytics and Storyteller.
The Data Quality module currently checks the field mapping configuration data for the Worker and Hiring
pipelines, not the Skills pipeline.
Only 1 Data Quality activity can run at a given time.

Installation Activity
People Analytics uptakes the latest configuration settings saved in the Configure People Analytics report
and runs them against the series of processes that comprise the installation workflow.
At high level, the installation workflow consists of:
• Acquiring data.
• Securing source data (if configured).
• Publishing the input source data to run through Storyteller.
• Publishing the output source data in the form of stories and explanations.
• Creating a discovery board where you can view KPIs, business questions, and related metrics.
• Exporting input source data to the machine learning development environment to improve the detection
algorithms used in the People Analytics product.
Only 1 installation activity can run at a given time. If you make changes to your current configuration and
reinstall the application, these changes to your application run as an installation activity and not an update
activity.
The Data Quality activity runs automatically when you run the installation activity.

Update Activity
People Analytics runs automated updates every Sunday at 3:00 AM in the tenant time zone. These
updates deliver any newly available content to production tenants to ensure that all users are on the latest
version of the product.
New content delivered to tenants as part of the automated update activity might result in changes to
the Worker and Hiring pipelines and the Storyteller configuration. Most of these changes don't require a
change in your People Analytics configuration and don't alter the configuration settings you ran during the
latest installation.
However, some updates require that you change your People Analytics configuration in order to uptake the
newly delivered content. In the Configure People Analytics report, the pipeline configuration card for the
pipeline that contains the update displays the badge New Content.
Example: People Analytics ran an automated update on Monday, December 13, 2021, that delivered the
configuration inputs to enable the new topic area VIBE Index™. To enable and configure this topic area
in your tenant, you must enable the topic and map the newly delivered field Intersection 1 in the Worker
pipeline.
To change your configuration to uptake new content, you must reinstall People Analytics. A reinstallation
of People Analytics displays in the People Analytics Activities report as an installation activity and not an
update activity.
On the first Sunday of every month, the automated update activity also checks for and loads any new data
that is available since the last data refresh. People Analytics appends the new data to your current data
history. The data refresh process doesn't load data retrospectively.
Example: The People Analytics report displays that you have Data as of September 2021. Your analysis
consists of 13 months of data history. When the monthly data refresh runs on the first Sunday of November
2021, People Analytics loads any new data from October 2021 and appends this data to the current data
history. Any data that was loaded into Workday during the month of October 2021 that reflects previous
months (August 2020 - September 2021) isn't added to the analysis.
Note: If you want to apply retrospective changes, you must reinstall People Analytics.
The update activity doesn't run in implementation tenants. If you want to ensure that your implementation
tenant is on the latest version, reinstall People Analytics using the Configure People Analytics report.

Viewing Activities
The People Analytics Activities report (secured to the Manage: People Analytics domain in the People
Analytics and Prism Analytics functional areas) displays all new and historical activities for your tenant.
By default, the activities table displays the status and details for the activity at the top level. You can
expand an activity to see the status and details of each intermediate step in the activity workflow.
You can customize your view of activities by filtering and sorting them. We recommend applying these
customizations when activities are collapsed and showing only details at the top level.
Workday recommends that you regularly view activities to ensure that scheduled updates are successful.
Note: You can create custom reports and discovery boards using People Analytics data sources for ad
hoc reporting purposes or to validate your data. These resources are only valid until the next automated
update or until you run Data Quality or installation again. However, you must delete these resources
before the next Data Quality, automated update, or installation run to ensure that these activities complete
successfully.

Managing Activities
You can right-click an activity at the top level to access the related actions menu. The related actions menu
enables you to:
• Cancel the remaining steps for an activity that is in progress.
Note: When you cancel an activity, it might take time for remaining steps to terminate and display the
status Canceled.
• Retry a canceled activity.
• Retry any failed steps that exist for a given activity.
Cancel and Retry actions are only available for the latest activity of a given activity type.

Reference: Requirements and Considerations for Changing People Analytics

Configuration
After you initially configure and install People Analytics with a Workday consultant, you can use the
Configure People Analytics report to maintain the application. Use this topic as a reference when
planning for and making changes to your current configuration.

General Considerations
We recommend only making certain types of changes in your tenant after installing the application with a
Workday consultant:
• Maintenance changes. Example: Changing the mapping for a field in a given pipeline or adding a new
population filter condition.
• Uptaking new content that we deliver as an automated update to production tenants. Example: Enabling
and configuring the VIBE Index™ topic area.
Certain changes to your configuration might result in a significant change to application insights and the
data quality of these insights. Examples:
• Applying a new security configuration that doesn't align with your current organization structure.
• Making changes to the field mapping for target fields Level 1, Level 2, and Level 3.
You might consider requesting assistance with People Analytics Office Hours (available as a paid service)
for support with changes that might significantly alter your current configuration.
Consider how a given change will affect which insights the target audience of the application consumes.
The target audience is the HR Business Partner and executives at your organization. Surfaced stories
that bring valuable and actionable insights for these users are stories and insights that you can use in
leadership reporting. Ensure that mapped fields and other configuration inputs support this level of content.

People Analytics uses configuration details based on expected values. We recommend that you adhere to
all specified requirements when making changes to avoid surfacing irrelevant or incorrect insights.
We recommend that you run People Analytics Data Quality and correct any defects in your configuration
before reinstalling the application. Data Quality also runs automatically when you install the application.
You can run Data Quality from the Configure People Analytics report and view the results by accessing
the People Analytics Data Quality report.
Plan to run the reinstallation of People Analytics only from Monday to Thursday. Weekly Service Updates
in Workday run on Fridays and can cause the reinstallation to fail.
We recommend testing all changes in an implementation or preview sandbox tenant before executing
these changes in your production environment.
The Configure People Analytics report doesn’t support concurrent editing. This means that when more
than 1 user is making changes to the configuration, the user with the latest, unsaved changes is unable to
save those changes. This user must refresh the page to get the updated version that reflects the changes
made by the other user. Refreshing the page removes any unsaved changes.
Note: You can create custom reports and discovery boards using People Analytics data sources for ad
hoc reporting purposes or to validate your data. These resources are only valid until the next automated
update or until you run Data Quality or installation again. However, you must delete these resources
before the next Data Quality, automated update, or installation run to ensure that these activities complete
successfully.

Field Mapping
Requirements

Item Details
Source Fields You can’t map a single source field to multiple
target fields.
Field Description and Type Each field that you map must meet the field
description and field type specifications.
If a field doesn't meet the original description, the
metric calculation uses unexpected values. This
results in surfacing stories that aren't computed
correctly. For the VIBE Index topic area, this might
result in no content displaying on the topic area tab.
If you map a field that is available in both the
Worker and Hiring pipelines, ensure that both fields
use the same field type and consist of the same
level of information. Example: The target field
Assigned Organization in the Worker pipeline and
the target field Assigned Organization in the Hiring
pipeline both have mapped source fields of the field
type Single Instance and contain the same level of
information across pipelines.

Calculated Fields People Analytics only supports the use of tenant-

wide calculated fields.
Report-specific calculated fields aren't supported.

Hierarchy Fields The target fields that you configure in the Primary
Hierarchy and Secondary Hierarchy sections must
be identical in the worker and hiring pipelines. For

Item Details
more information, see Concept: Hierarchies and
Organizations in People Analytics on page 555.
Report Effective Date and Created Moment Don't change the default mapping of the field
Report Effective Date in the Worker pipeline and
the field Created Moment in the Hiring pipeline.
These fields contain unique, system-created, time-
related information to a specific record.
Display Name for Fields The display name for a mapped field can only
contain alphanumeric characters and spaces
between those characters. Display names can’t
start or end with a space.

Considerations

Item Details
Blank Elements If you're considering mapping a field that contains a
high number of blank elements, determine whether
the blank elements are expected within the given
context.
Example: The source field mapped into the target
field Job Family Group contains 80% blanks of all
elements. As a result, a story produced on this
dimension focuses only on the elements that aren't
blanks and might provide false positive or negative
information.

Dimensions and Cardinality Be thoughtful when selecting dimensions (subsets

of source fields) for field mapping. Consider the
business added value and the cardinality of the field
(number of distinct values). The expected content
for a field isn't necessarily based on the name of
the field. Check the Field Description and Example
Value for a given field to ensure that the field is the
best choice.
Example: For the target field Location, the expected
dimension (subset of mapped source field) is at
least city level or higher, not street level. If the
expected level is too low (field has too high number
of distinct values), move 1 to 2 hierarchies up.
Usually the rule Would I use this field for reporting?
or Would the field tell me something? applies when
considering cardinality.

Fields that require prompts Avoid mapping source fields that require prompts,
except for the field Total Compensation Calc Field.
Prompts are only available for this field if mapped
using the default source field.
Prompts allow you to configure specific aspects of
a given field. Example: Whether to include one-time
payments in the Total Compensation Calc Field.

Item Details
Populations People Analytics requires the correct populations.
If the wrong population is included in the field
mapping configuration or not filtered out in the
population filters configuration, surfaced stories,
KPIs, and visualizations might provide insights
that aren't relative to the target audience of the
application.
Frequently filtered-out populations:
• Contingent Workers
• Seasonal Workers
• Interns

Fields for Skills Pipeline We recommend not changing the default mapping
for the fields in the Skills pipeline to ensure the
highest quality of results.

Population Filters
Limits

Item Details
Non-supported elements for population filters When configuring population filters, you can't use:
• Multi-instance fields
• Self-referencing fields
• Subfilters
• The aggregation function of a field (average or
sum).

Population filter condition limit per pipeline For each population filter group, you can use
a maximum of 20 population filter conditions.
The limit for nesting is 3 levels, which applies to
both groups of population filter conditions and all
population filter groups.
A population filter group is a population filter
condition that is composed of other population filter
conditions and/or other population filter groups.
Example: A given population filter group contains
these population filter conditions:
• Custom Active Status is equal to True.
• (OR) Termination Date is equal to First Day of
Month of Report Effective Date.
• (AND) Termination Date is less than or equal to
report Effective Date.
• (OR) Achievable Level in the selection list is 1-2
Levels.
These population filter conditions comprise a
population filter group within the population filter
group mentioned above:
• Custom Active Status is equal to True.

Item Details
• (OR) Termination Date is equal to First Day of
Month of Report Effective Date.
• (AND) Termination Date is less than or equal to
report Effective Date.

Report Effective Date and Created Moment Fields Population filter conditions consist of 3 parts from
left to right on the Population Filters step of a given
pipeline:
• Population filter field
• Population filter operator
• Population filter condition
You can’t use these fields as population filter fields.
You can only use these fields as population filter
conditions:
• Report Effective Date field in the Worker
pipeline.
• Created Moment field in the Hiring pipeline.

Prompts
Prompts are only available if you:
• Include the target field Total Compensation Calc Field in the Worker pipeline field mapping
configuration, and
• Use the default source field Total Compensation Calculated Field.
Prompts aren't available for fields available in the Hiring pipeline.

Security
You must select the same security option for both the Worker and Hiring pipelines. For more information,
see Concept: Security in People Analytics on page 558.

Data History
In order for People Analytics to perform analysis successfully, you must have at least 4 months of
transactional worker data in Workday. You can select 4 to 36 months of historical data to load into People
Analytics from Workday for analysis. Any transactional history converted during deployment is considered
part of the initial data load.
The amount of data history determines the analysis type. Year-over-year analysis requires at least 13
months of data. Rolling 3 month analysis is available with 4 to 12 months of data.
When you install People Analytics, you automatically enable the automated update activity, which includes
a monthly data update. This enables the application to continue to load and analyze the latest data into
Workday on the first Monday of every month. If the initial data load is less than 13 months, the analysis
type automatically changes when 13 months of data are available and loaded into People Analytics.

Question Mapping
To measure belongingness in the VIBE Index, you must map the Peakon questions you want to use as
part of the Employee Sentiment topic configuration.
The standard Peakon Belonging question ‘I feel a sense of belonging at [Your Company]’ appears by
default. If you don’t see the standard question by default, check if it is enabled on your Peakon account.

You can remove the default question from the question mapping field, however, we recommend that you
use it as this is the Peakon standard question that directly asks employees about their sense of belonging.
Only standard questions from the Peakon Engagement and Diversity & Inclusion question sets will be
available to select in the question mapping field. For your convenience the questions are organized into
folders grouped into Question Sets, Drivers, and Sub-drivers. You may choose up to 10 questions.
Note: You are required to select at least one question to complete the installation.
Questions disabled on your Peakon dashboard become inactive in People Analytics, and new question
scores for them don’t flow into the report. Inactive questions are marked as such in your question mapping
field in the Configure People Analytics report.
You can revisit the question selection pipeline at any point in time and modify an existing question set to
suit your needs. Any changes to the question list will require reinstallation of the People Analytics report.
Related Information
Reference
The engagement question library and theory references

Reference: Choosing and Creating Intersections

An intersection is a group that ideally consists of workers with various demographics and characteristics.
An intersection is a field or a group of fields that represent the dimensions you want to analyze in the VIBE
Index™.
We strongly recommend that you use a minimum and maximum of 2 fields to define the intersection.
Examples of fields used to define an intersection: Ethnicity, Gender, Disability Status, Veteran Status,
Sexuality.
Example of an intersection: Gender and Ethnicity.
The values of the fields you use to define the intersection determine the intersection values. Each
intersection value is an individual intersection (people group).
Example: The intersection Gender and Ethnicity has the intersection values Female - Asian, Female -
URM, Female - White, Male - Asian, Male - URM, Male - White. The intersection value Female - Asian is
an individual intersection (people group).
Choosing an intersection and creating an intersection (if necessary) are prerequisites to configuring the
VIBE Index topic area in People Analytics.
Getting Started
Review all details for choosing intersections to determine which fields and conditions meet the business
and development needs of your organization. Afterward, review the details for the default intersection field
and the field specifications for intersections. You can then determine if:
• Using the default intersection field or an existing field in your tenant is a suitable choice for an
intersection.
• Creating an intersection is the best choice for your organization.
Note: The intersection you choose or create must meet the requirements listed in the field specifications
for intersections.

Choosing Intersections
We strongly recommend that you use a minimum and maximum of 2 fields to define the intersection.
Example: Gender and Ethnicity.
The best intersections are intersections that align with the general (more broad) business and development
strategy of your organization. This enables you to connect insights that are surfaced in the VIBE Index
topic area in People Analytics with other internal findings that you can act on.

The VIBE Index is a great tool for diagnosing areas for targeted intervention. Therefore, the fields you
choose for the intersection should consist of dimensions in which you can dig deeper into using other data
sources (VIBE Central dashboard or other reporting sources).
Expected Parity
The VIBE Index evaluates parity in several outcomes across intersections. The intersection you choose
should have a reasonable expectation of parity across all outcomes (Attrition, Hires, Leadership,
Promotions).
Examples of choices that meet this criteria:
• Gender / Ethnicity - Organizations often look at gender and ethnicity to determine bias in outcomes
such as hires and promotions. We expect that the gender or ethnicity of an employee shouldn't have
an influence on the rate at which the employee is promoted or on the probability of the employee being
represented in leadership, and so on.
• Sexual Orientation / Disability Status / Veteran Status - Organizations often look at these dimensions
to determine bias across different outcomes. Therefore, we expect that these employee attributes
shouldn't have an influence on certain outcomes, such as employee promotions. Before choosing an
intersection with 1 or more of these fields, determine if you have:
• Accurate and relatively complete data among the chosen dimensions.
• Sufficient headcount in each intersection (minimum 10 workers). Example: The intersection Disability
Status and Veteran Status includes the intersection NotDisabled - IsVeteran, which consists of 10
workers.
Example of choices that don't meet this criteria: Age Group / Generation
Although organizations often look at age and generation as important variables in business and
development work, they aren't dimensions that you would expect parity in for some of the outcomes
included in the VIBE Index. Examples of outcomes where we don’t expect parity for age group and
generation:
• Hires - This outcome usually skews in volume towards early-in-career roles, which results in uneven
representation by age group or generation. Therefore, we expect disparity across intersections for this
outcome.
• Leadership - This outcome is often overrepresented by older age groups. We expect that the
percentage of leaders should vary by age group or generation. Therefore, we expect disparity across
intersections for this outcome.
• Promotions - For the same reason job levels and management levels skew by age group, promotion
rates are often lower as you move higher in an organization (longer time to promotion). We expect that
the percentage of promotions should vary by age group or generation, and therefore expect disparity
across intersections for this outcome.
Example of dimensions that might or might not be a good choice for an intersection, depending on your
organization: Region / Location
If your organization is mostly US-based with only certain types and levels of specific roles that are
subordinate to other locations or regions, you might not expect there to be equal representation in
leadership across regions, equal promotion rates, and so on.
If operations in your organization are currently more homogeneous across regions or are intended to be
more homogeneous across regions, you might expect parity across leadership opportunities, hiring, and
promotions.
Attributes
Unlike some personal attributes (mentioned in the section Expected Parity), job-related attributes almost
always have an impact on other job-related outcomes and don’t make good choices for intersections.
Examples of job-related attributes:

• Job Level or Management Level - We don’t recommend using these attributes for an intersection
because we expect they are:
• Directly related to the outcome Leadership.
• Highly correlated with promotion rates.
• Skewed along Hiring.
• Performance Rating - We expect this attribute to have a negative impact on the outcome metric Hiring
because it's often:
• Highly correlated with promotions.
• Highly correlated with differences in belonging and attrition.
• Skewed by job level.
• Tenure or Time in Role - We expect that tenure has strong correlations with promotions, attrition, and
leadership representation. Therefore, we don’t recommend using these attributes for an intersection
because they might negatively affect the outcome metric Hiring.
Populations
The intersection that you use for VIBE should include the right populations. If a field that is included in the
intersection returns a blank or null value for a worker, Workday doesn't include the associated worker in
the VIBE calculation.
Additionally, if the headcount for a given intersection falls below the minimum requirement of 10 workers
for the respective month, we don't include the intersection in the VIBE calculation.
If the fields that you choose for the intersection consist of both correct and incorrect populations, you can
use condition functions to exclude the incorrect populations.
Intersection Headcount
The minimum headcount requirement for each intersection within a defined intersection is 10 workers.
People Analytics evaluates active headcount at each monthly data refresh.
Example: The intersection Gender and Ethnicity consists of the intersection Female - Asian, which has a
minimum headcount of 10 workers for the latest month that People Analytics analyzes data.
The minimum headcount enables us to derive aggregate-level insights. The VIBE Index relies on the
expectation of parity across groups, not individuals. By having a sufficient population in each intersection,
there's a reasonable expectation that individual-level variances cancel out, and we can make comparisons
on group-level outcomes where we would expect parity.
The minimum headcount enables the VIBE Index to be stable and actionable. Otherwise, there would be
extreme fluctuations in results from time period to time period.
Example: If an organization has a headcount of 5 in an intersection and has a 10% annual attrition rate,
the expected number of attrition events for that intersection in a 12-month period is 0.5. Because you
can’t have 0.5 attrition events, an organization can be perfectly at parity by having 0 attrition events in one
period and 1 attrition event in the next period. However, in the first case (0 attrition events), the intersection
with a headcount of 5 would be 100% below parity for the corresponding time period. In the second case
(1 attrition event), the same intersection would be 100% above parity for the corresponding time period. In
either time period, interpreting the attrition outcome for this group would be misleading and not actionable.
Note: If the headcount for a given intersection falls below the minimum requirement of 10 workers for the
respective month, we don't include the intersection in the VIBE calculation.
Field Specifications for Intersections
The table lists the requirements for intersections and provides guidance on key configuration elements of
intersections.

Specification Details
Number of Fields We strongly recommend that you use a minimum
and maximum of 2 fields to define the intersection.
Field type when the intersection field includes The only allowed field type is Text.
concatenated functions
The field can also be a calculated field.
The field type requirement doesn't apply to fields
used as conditions or other components of the
intersection field.

Field type when the intersection field doesn't The allowed types are Single Instance and Text.
include concatenated functions
Business Objects of Fields People Analytics only supports using the primary
business object for a given pipeline or a related
business object to the primary business object of
that pipeline.
The target field that you map for the VIBE Index is
in the field mapping for the Worker pipeline, which
uses the primary business object Worker.
Ensure that the intersection field is in the business
object Worker (or a related business object).
If the intersection field contains more than 1 field,
ensure that all fields use the same business object.
This includes fields that are used as conditions or
other components of the intersection field.

Minimum Headcount for Intersections The minimum headcount requirement for each
intersection within a defined intersection is 10
workers. People Analytics evaluates active
headcount at each monthly data refresh.
Example: The intersection Gender and Ethnicity
consists of the intersection Female - Asian, which
has a minimum headcount of 10 workers for the
respective month.
If the headcount for a given intersection falls below
the minimum requirement of 10 workers for the
respective month, we don't include the intersection
in the VIBE calculation.

Conditions for Fields If you use conditions in the intersection field, be

mindful of blank or null values. Ensure to exclude
populations where appropriate to avoid blank or null
values returned from fields.
If a field returns a blank or null value, Workday
doesn't include the worker associated with
the blank or null value in the VIBE calculation.
Additionally, if the headcount for a given
intersection falls below the minimum requirement
of 10 workers for the respective month, we don't
include the intersection in the VIBE calculation.

Specification Details
Specifications for People Analytics All requirements and considerations for configuring
People Analytics apply to the intersection you use
for the VIBE Index. Example: People Analytics
only supports tenant-wide calculated fields. When
creating calculated fields to create an intersection
or using an existing calculated field in your tenant,
you can’t use report-specific calculated fields.
Security for Fields Be mindful of your security configuration in People
Analytics when choosing the fields and conditions
you want to include in the intersection. Consider the
target audience of the application: the HR Business
Partner and executives within an organization.

Default Intersection
The default intersection for the VIBE Index is the Workday-owned, text field Intersection 1. To view the
setup and details for the default field, access the Business Object Details report (secured to the Custom
Report Administration and Custom Report Management domains in the System functional area) and
search for the business object Worker.
The table lists the components of the default field Intersection 1.

Component Details
Included in VIBE Calculated field that is used as the condition for the
default intersection.
Gender (text) Calculated field that is used in these fields, which
are also components of the default intersection:
• Included in VIBE
• Concatenate Ethnicity and Gender

Ethnicity (text) Calculated field that is used in these fields, which

are also components of the default intersection:
• Included in VIBE
• Concatenate Ethnicity and Gender

Concatenate Ethnicity and Gender Calculated field that is used as the value if the
condition Included in VIBE is true. This field
consists of the concatenated fields Gender (text)
and Ethnicity (text).

You can’t edit the Workday-owned, default intersection field or the components within the default
intersection field. If you want to use a similar setup for your intersection, review the field specifications for
intersections and the details for creating intersections. You can then determine if you can use an existing
field in your tenant for an intersection or if you need to create an intersection.

Creating Intersections
When creating an intersection field, you can:
• Use an existing field or fields in your tenant that meet the specifications for intersections.
• Create a new field that meets the specifications for intersections.
Note: An intersection field can consist of other fields.

For examples on creating intersections, you can view the setup of the default intersection field and the
example topic on creating an intersection.
Related Information
Concepts
Concept: VIBE Index in People Analytics on page 599
Reference
Reference: Requirements and Considerations for Changing People Analytics Configuration on page 563
Examples
Example: Create an Intersection on page 593

Reference: Fields in People Analytics

People Analytics renders data from mapped fields to calculate metrics and generate content for KPIs,
stories, and visualizations. For each topic area you select, some fields are required and some fields are
optional. Fields are assigned to the corresponding pipeline: Worker, Hiring, or Skills.

Worker Fields
People Analytics organizes Worker fields into these categories:
• Worker Basic Information
• Job Hierarchy
• Job Details
• Compensation
• Primary Hierarchy
• Secondary Hierarchy
• Organization Details
• Talent and Performance
• Tenure Information
• Termination Information
• Other
Worker Basic Information

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Report Date Effective date 2018-01-01 Required Concept:
Effective Date of the monthly Effective Dates
data snapshot.
Employee ID Text Unique H7O90lme0012U Required
identification of
the worker.
Employee Single Instance Full legal name Jane Smith
Name of the worker.
Active Status Boolean Boolean field True/False Required Reference:
that indicates Leave Impacts
the active
status of the
employee.

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Worker Type Single Instance Worker type Regular Required Hire Employees
(employee
or contingent
worker) for a
worker.
Hire Date Date Most recent 2018-01-01 Required Hire Employees
hire date for the
worker. This
field can't be
effective dated.
Termination Date Effective date 2018-01-01 Required Steps: Set Up
Date of the last Termination
termination of
the worker.
Note: To
include
terminations
with a next-day
rehire, use the
Termination
Date - All field.

Gender Single Instance Gender of the Female Steps: Set

worker. Up Personal
Information
Fields
Ethnicity Single Instance/ Ethnicity of the Asian, Black
Text worker. or African
American,
White,
Hispanic, Two
or More Races,
Other, Native
Hawaiian or
Other Pacific
Islander,
American
Indian or Alaska
Native
Generation Single Instance Generation Baby Boomers Steps: Set
cohort of the (year range) Up Personal
worker. Information
Fields
Intersection 1 Single Instance/ Field that Male-Asian Required to Reference:
Text defines the configure the Choosing
intersection VIBE Index and Creating
values found topic area. Intersections on
in the VIBE page 568

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Index. Refer to
setup details for
VIBE Index for
instructions on
how to choose
and create
intersections.

Job Hierarchy

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Job Family Single Instance/ Category of Sales Create Job
Group Text the job family Family Groups
group.
Single Job Single Instance/ Job family for Pre-Sales Create Job
Family Text the primary Family Groups
position of the
worker.
Job Profile Single Instance Job profile of P3 Product Create Job
the employee. Manager Profiles

Job Details

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Job Level Single Instance Job level P3
position of the
employee.
Manager ID Text Unique H7090192Sfdfj102
identification of
the manager of
the worker.
Is Leader Boolean Boolean value True/False
that indicates
whether an
employee is in
a leadership
(usually director
and above)
position.
Manager Boolean Boolean value True/False
for whether a

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
worker is in a
manager role.
Last Date Effective date 2018-01-01 Transfer,
Promotion of the last Promote, or
Date promotion of Change Job
the employee.

Compensation

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Total Currency Total 402800.00 USD Concept:
Compensation compensation Compensation
Calc Field for a worker in Basis
USD.
Note: We don't
recommend
using a different
currency, as it
skews People
Analytics
results.

Compa Ratio Numeric Employee 1.038 Steps: Create a

compensation Compensation
rate. Formula Matrix
field must follow
for calculating
compa-ratio:
Base Pay
or Primary
Compensation /
Compensation
Range 50th
percentile
or Range
Midpoint Value.
(Compensation
Range 50th
percentile
or Range
Midpoint Value
is determined
by system
setup.)

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Compa Ratio Single Instance Category for Above Compa- Steps: Create a
Range compensation Ratio Compensation
rate. Matrix

Primary Hierarchy
For more details, see Concept: Hierarchies and Organizations in People Analytics on page 555.

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Assigned Single Instance The Planning Required
Organization organization Workforce QA
that is assigned
to the primary
position of
the worker.
Typically, this
is Supervisory
Organization,
but in rare
cases might
be a different
organization
type, such
as a custom
organization or
Cost Center.
Level 1 Single Instance The 1st level of 2000 Executive
the hierarchy Management
that you want
to analyze.
Typically, this
is the 2nd
level from
the top of the
organization, 1
level below the
CEO.
The field you
select must be
in the same
organization
hierarchy as
the Assigned
Organization.

Level 2 Single Instance The 2nd level 3000 Finance

of the hierarchy Administration

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
that you want
to analyze.
Typically,
this is the 3rd
level from
the top of the
organization, 2
levels below the
CEO.
The field you
select must be
in the same
organization
hierarchy as
the Assigned
Organization.

Level 3 Single Instance The 3rd level of 4000 Executive

the hierarchy Management
that you want
to analyze.
Typically,
this is the 4th
level from
the top of the
organization, 3
levels below the
CEO.
The field you
select must be
in the same
organization
hierarchy as
the Assigned
Organization.

Secondary Hierarchy
For more details, see Concept: Hierarchies and Organizations in People Analytics on page 555.

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Level 1 Single Instance/ The 1st level of North America
Text the hierarchy
that you want
to analyze.
Typically, this
is part of a

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
geographical
hierarchy,
such as market
region.
Level 2 Single Instance/ The 2nd level United Kingdom
Text of the hierarchy
that you want
to analyze.
Typically, this
is part of a
geographical
hierarchy, such
as country.
Level 3 Single Instance/ The 3rd level of Pleasanton
Text the hierarchy
that you want
to analyze.
Typically, this
is part of a
geographical
hierarchy, such
as city.
When you
constrain
access to the
application
data using
the secondary
hierarchy, then
this level must
be associated
with the worker,
and you must
opt into this
field.

Organization Details
For more details, see Concept: Hierarchies and Organizations in People Analytics on page 555.

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Organization Numeric Number of 4
Level levels down
from the top
level of the
organization to

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
the assigned
organization.
Management Single Instance/ Management 6 Director Set Up
Level Text level of the Job Level
worker. Hierarchies
Cost Center Single Instance Cost center 2069 -
(or equivalent) Augmented
used for Analytics
reporting.
Company Single Company name Workday, Inc.
Instance/ Self- or ID of the
Referencing company.
Instance

Talent and Performance

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
High Potential Boolean Boolean value True/False
for whether an
employee is of
high potential,
based on
the company
definition of
high potential
(values only
for employees,
not contingent
workers).
High Boolean Boolean value True
Performer for whether an
employee is a
high performer,
based on
the company
definition of
high performer.
Current Rating Numeric/ Single Numeric value 4
Instance/ Text representing
the employee
rating, which
is based on
the company
definition of
current rating.

Tenure Information

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Length of Numeric Employee 4.23 Hire Employees
Service in tenure in years,
Partial Years including partial
years.
Tenure Single Instance/ Tenure 10-15 Years
Category Text category for the
worker in their
current position.

Termination Information

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Term Category Text Field Voluntary/ Terminate
representing Involuntary Employees
termination
category.
Values
"Voluntary" /
"Involuntary"
must be present
as text. If
they're not,
import the
appropriate field
as a Text field.
Termination Single Instance/ Primary Personal Terminate
Reason Text termination Employees
reason for the
worker.

Other

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Hiring Source Single Instance Hiring source of LinkedIn Hire Employees
the employee.

Hiring Fields
Hiring fields are only available for Workday Recruiting customers. People Analytics organizes Hiring fields
into these categories:

• Recruiting Process
• Candidate Information
• Candidate Processing
• Job Requisition Information
• Source of Candidates
• Primary Hierarchy
• Secondary Hierarchy
• Organization Details
Recruiting Process

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Created Date Moment at 10/15/2015 Required Steps: Set
Moment which the 10:23:10 AM Up Job
recruiting Requisitions for
status instance Recruiting
was originally
created in
Workday.
Candidate ID Text ID of the CANDIDATE-16-11
Required
candidate
on the job
application.
Stage Single Instance/ Recruiting Review Required
Text stage of the
recruiting
status. This
field is of the
type instance.
Stage Name Text Recruiting Review
stage of the
recruiting
status. This
field is of the
type text.
Status Start Date Date and time 2019-21-09 Required
Date the candidate
entered the
recruiting
status.
Time In Stage Numeric Duration of time 10
the candidate
spent in the
recruiting stage.
Disposition Text Disposition Does not
Reason reason for meet job
a candidate qualifications
being rejected/
declined for

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
the recruiting
process.
Candidate Text External-facing Qualifications
Disposition disposition not met
Reason reason for
an internal
and external
candidate job
application
business
process.

Candidate Information

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Gender Single Instance Gender of the Female
candidate.
Ethnicity Single Instance/ Ethnicity of the Asian, Black
Text candidate. or African
American,
White,
Hispanic, Two
or More Races,
Other, Native
Hawaiian or
Other Pacific
Islander,
American
Indian or Alaska
Native
Candidate Single Instance/ Veteran I am not a Steps: Set Up
Veteran Status Text status of the veteran Veteran Status
candidate. Identification for
Candidates
Candidate Single Instance/ Disability No, I don't have
Disability Text status of the a disability
candidate.
Candidate Single Instance Name of the Quinn
Worker candidate, if a Richardson
worker record
is available in
Workday.
Worker Job Single Instance Job requisition R-00015 Required
Requisition from the worker Web Content

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
record of the Manager
hired candidate, (Open)
if a worker
record is
available in
Workday.
Candidate Date Date and time 2010-24-10
Worker Hire of the initial
Date hire of the
candidate, if a
worker record
is available in
Workday.

Candidate Processing

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Hire Stage Boolean Boolean value True/False
for whether
the recruiting
process is in
the hire stage.
Candidate Single Instance/ Recruiting Ready For Hire
Stage Text stage the
candidate is
in for the job
requisition,
not taking
notification
delays into
consideration.
Last Single Instance/ Last recruiting Review
Recruiting Text stage the
Stage candidate
was in before
being rejected/
declined for
the recruiting
process.
Job Single Instance Most recent Offer
Application offer status
Offer Status of the job
application
that is in the
offer stage or

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
employment
agreement
stage.

Job Requisition Information

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Reference ID Text ID of the job R00367
requisition
to which the
candidate
applied.
Job Single Instance Job requisition R-00015 Required
Requisition to which the Web Content
candidate Manager
applied. (Open)
Recruiting Date First date 2015-15-10
Start Date the recruiting
process can
start for the
position on the
job requisition.
Job Date Date and time 2010-24-10
Requisition on which the
Filled Date job requisition
was filled.
Candidate Job Single Instance/ Status of the Review
Requisition Text job requisition
Status to which the
candidate
applied.
Employee Single Instance Employee Regular Create and
Type type on the job Edit Job
requisition. Requisitions
Time Type Single Instance/ Time type hiring Full time
Text requirement
on the job
requisition.
New Position Boolean Boolean value True/False Create Hiring
for whether the Restrictions
job requisition
created a new
position.

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Job Profile Single Instance/ Job profile Regional Sales Steps: Set
Text for the job Manager Up Job
requisition. Requisitions for
Recruiting
Job Posting Text Name of the Senior Risk
Title position on the Specialist
job requisition.
Job Single Instance Management 11 Individual Create and
Requisition level for the job Contributor Edit Job
Management profile on the Requisitions
Level job requisition.

Source of Candidates

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Candidate Single Instance Category of External
Source the recruiting
Category source of the
candidate
for the job
application.
Candidate Single Instance/ Recruiting LinkedIn
Source Text source (internal,
referral, or
other) for the
candidate
for the job
application.
Job Single Instance Recruiting Referral Steps: Set Up
Application source Job Postings
Source (LinkedIn,
Glassdoor,
etc.) for the
candidate
for the job
application.
Internal Boolean Boolean value True/False
Candidate for whether the
source category
for this job
application is of
internal type.

Primary Hierarchy

For more details, see Concept: Hierarchies and Organizations in People Analytics on page 555.

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Assigned Single Instance The Planning Required Create Hiring
Organization organization Workforce QA Restrictions
that is assigned
Create
to the primary
Positions
position of the
job requisition.
Typically, this
is Supervisory
Organization,
but in rare
cases might
be a different
organization
type, such
as a custom
organization or
Cost Center.
Level 1 Single Instance The 1st level of 2000 Executive
the hierarchy Management
that you want
to analyze.
Typically, this
is the 2nd
level from
the top of the
organization, 1
level below the
CEO.
The field you
select must be
in the same
organization
hierarchy as
the Assigned
Organization.

Level 2 Single Instance The 2nd level 3000 Finance

of the hierarchy Administration
that you want
to analyze.
Typically,
this is the 3rd
level from
the top of the
organization, 2
levels below the
CEO.

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
The field you
select must be
in the same
organization
hierarchy as
the Assigned
Organization.

Level 3 Single Instance The 3rd level of 4000 Executive

Secondary Hierarchy
For more details, see Concept: Hierarchies and Organizations in People Analytics on page 555.

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Level 1 Single Instance/ The 1st level of North America Create and
Text the hierarchy Edit Job
that you want Requisitions
to analyze.
Typically, this
is part of a
geographical
hierarchy,
such as market
region.
Level 2 Single Instance/ The 2nd level Germany Create and
Text of the hierarchy Edit Job
that you want Requisitions
to analyze.
Typically, this

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
is part of a
geographical
hierarchy, such
as country.
Level 3 Single Instance/ The 3rd level of London
Text the hierarchy
that you want
to analyze.
Typically, this
is part of a
geographical
hierarchy, such
as city.
When you
constrain
access to the
application
data using
the secondary
hierarchy, then
this level must
be associated
with the worker,
and you must
opt into this
field.

Organization Details
For more details, see Concept: Hierarchies and Organizations in People Analytics on page 555.

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Cost Center Single Instance/ Cost center 2069 -
Text (or equivalent) Augmented
used for Analytics
reporting. If
you use Cost
Center as
the primary
or secondary
hierarchy,
then you can
select a field
from a different
organization
that Workday
can use for

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
providing more
details on the
job requisition.

Skills Fields
People Analytics organizes Skills fields into these categories:
• Required Opt-ins
• Worker Skills and Gaps
Required Opt-ins

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Match Score Numeric Match score is 0.45 Required HCM ML
a calculation automatically
that compares generates
a worker's values for this
current portfolio field.
of explicit
and inferred
skills to the
skills (explicit
and inferred)
listed on their
job profile.
Workday
calculates the
skill gaps and
subtracts the
total from 1 to
assign each
worker a score
on a scale of 0
- 1.
This is an opt-in
field and isn't a
part of the field
mapping for the
Skills pipeline.

Worker Skills and Gaps

Field Field Type Description Example Value Required? How To

Populate
This Field In
Workday
Skill Multi-Instance Skill categories Pre-Sales, Required
Categories assigned to a Retail Sales
maintained or
Skills Cloud
skill.
Skill Reference Text Skill Reference S0929 Required
ID ID to use for
lookups within
our Workday
Web Services.
Skills Report Date Field that 2022-01-01 Required
Effective Date determines
which skills
records are
included in the
monthly data
snapshot.

Related Information
Reference
The Next Level: People Analytics: Resources to Help Validate Your Organization's Data

Reference: Business Objects and Data Sources in People Analytics

Business Objects
People Analytics only supports mapping source fields from the primary business object of a given pipeline
and the related business objects of that primary business object.

Pipeline in People Analytics Primary Business Object

Worker Worker
Hiring Recruiting Status
Skills Local Skill Item

Data Sources
You can create custom reports and discovery boards using People Analytics data sources for ad hoc
reporting purposes or to validate your data. These resources are only valid until the next automated
update or until you run Data Quality or installation again. However, you must delete these resources
before the next Data Quality, automated update, or installation run to ensure that these activities complete
successfully.
Worker Data Sources

Data Source Description

PPLA Worker Worker data source before Storyteller processing.

Data Source Description

ppla_worker_stories_publish Worker data source after Storyteller processing of
stories.
ppla_worker_explanations_publish Worker data source after Storyteller processing of
explanations.
ppla_vibe_belonging VIBE index data source for Workday Peakon
Employee Voice customers that are using Peakon
belonging data in VIBE. Workday protects individual
confidentiality for belonging responses by providing:
• Aggregated data only for some fields.
• Constrained access to some fields.

Hiring Data Sources

Data Source Description

PPLA Recruiting Status Transactions Hiring data source before Storyteller processing.
ppla_rec_stories_publish Hiring data source after Storyteller processing of
stories.
ppla_rec_explanations_publish Hiring data source after Storyteller processing of
explanations.

Skills Data Sources

Data Source Description

ppla_skill_attributes Skills data source with skill attributes (skill
categories).
ppla_skill_explanations_publish Skills data source after Storyteller processing of
explanations.
ppla_skill_stories_publish Skills data source after Storyteller processing of
stories.
ppla_static_vis_match_score Skills data source with details for visualizations
related to match score.
ppla_static_vis_skill_cats Skills data source with details for visualizations
related to skill categories.
ppla_worker_gaps Skills data source before Storyteller processing.
This data source also provides the detailed data for
workers.

Data Quality Data Sources

Data Source Description

ppla_dq_publish_blank Data source with data quality results for the missing
values check.
ppla_dq_publish_cardinality Data source with data quality results for the
cardinality check.

Data Source Description

ppla_dq_publish_check_aggregation Data source with aggregated data quality results
per data quality check.
ppla_dq_publish_dimension_aggregation Data source with aggregated data quality results
per dimension.
ppla_dq_publish_dupe Data source with data quality results for the
duplicates check.
ppla_dq_publish_incorrect Data source with data quality results for the illogical
values and invalid values checks.
ppla_dq_publish_multi_hier Data source with data quality results for the multiple
hierarchies check.
ppla_dq_publish_population Data source with data quality results for the
population check.
ppla_dq_publish_record_aggregation Data source with aggregated data quality results
per record.
ppla_dq_recruiting_statuses Hiring data source before data quality processing.
ppla_dq_worker Worker data source before data quality processing.

Related Information
Concepts
Concept: Business Objects, Data Sources, and Fields on page 13

Example: Create an Intersection

This example shows 1 way to create an intersection. When configuring the VIBE Index™ topic area in
People Analytics, you map the intersection field to the target field Intersection 1.

Context
You want to create an intersection similar to the Workday-owned, default intersection.
The intersection field you create includes the dimensions Gender and Ethnicity.
You create conditions for the intersection that exclude populations outside of the USA. The USA is the
location of the workers you want to include in the VIBE Index.
You check your tenant for existing fields and determine that you need to create all new fields.

Prerequisites
Security: Custom Field Management domain in the System functional area.

Steps
1. Access the Create Calculated Field task.
2. Enter these values to create a calculated field for the dimension Gender:

Field Enter
Field Name Gender (Text Field)
Business Object Worker
Function Format Text

Field Enter
Source Field Gender
Options Proper Case
3. Enter these values to create a calculated field for the dimension Ethnicity:

Field Enter
Field Name Ethnicity (Text Field)
Business Object Worker
Function Format Text
Source Field Race/Ethnicity
Options Proper Case
4. Enter these values to create a calculated field to use as the condition for the intersection:

Field Enter
Field Name Conditions in VIBE
Business Object Worker
Function True/False Condition
Item 1 • And/Or: And
• Field: Gender (Text Field)
• Operator: is not blank

Item 2 • And/Or: And

• Field: Gender (Text Field)
• Operator: does not contain
• Comparison Type: Value specified in this filter
• Comparison Value: Not Declared

Item 3 • And/Or: And

• Field: Ethnicity (Text Field)
• Operator: is not blank

Item 4 • And/Or: And

• Field: Location
• Operator: in the selection list
• Comparison Type: Value specified in this filter
• Comparison Value: USA

5. Enter these values to create a calculated field to concatenate the fields you created in steps 2 and 3:

Field Enter
Field Name Concatenate Ethnicity and Gender for VIBE
Business Object Worker
Function Concatenate Text
Item 1 Gender (Text Field)

Field Enter
Item 2 Global Fields > Text > -
Item 3 Ethnicity (Text Field)
6. Enter these values to create a calculated field to use as the intersection field:

Field Enter
Field Name Intersection VIBE
Business Object Worker
Function Evaluate Expression
Field Type Text
Default Value Null
Item 1 • Condition: Conditions in VIBE
• Return Value If Condition is True: Concatenate
Ethnicity and Gender for VIBE

Next Steps
When configuring People Analytics, map the intersection source field Intersection VIBE to the target field
Intersection 1.
Related Information
Concepts
Concept: VIBE Index in People Analytics on page 599
Reference
Reference: Choosing and Creating Intersections on page 568
Reference: Requirements and Considerations for Changing People Analytics Configuration on page 563

Troubleshooting: Data Quality Module

This topic provides strategies for diagnosing and resolving issues highlighted by the Data Quality check for
the Configure People Analytics report. If you can’t find the solution to your issue in this topic, consider
requesting assistance with People Analytics Office Hours.

Cardinality
Example defect messages:
• The cardinality for Region in the Location hierarchy is 892, which is inconsistent in terms of expected
levels of cardinality.
• In Region, the cardinality is 983, which is above the threshold of 200.
• The cardinality for Region in the Location hierarchy is 892, which is inconsistent in terms of expected
levels of cardinality. Region also exceeds the threshold of 200.
Cause: The number of unique values in a particular field doesn’t correspond to the expected cardinality
levels within a given hierarchy. High cardinality (a lot of unique values) can negatively affect performance

of the People Analytics report. It might also result in low-quality stories due to your workers being divided
into populations that are too small.
Solution: How you respond to cardinality defects depends on their severity.

Severity Solution Description

Moderate If the cardinality falls within the expected margin
of error, you can ignore these defects. Otherwise,
consider selecting a different source field for the
target field in the Configure People Analytics
report.
Major These defects shouldn’t prevent you from
running the People Analytics report. If the report
installation is too slow or story quality in the People
Analytics report is low due to a high number of
analysis dimensions, select a different source
field for the target field in the Configure People
Analytics report.
Critical This level of cardinality for a field might prevent
the People Analytics report from installing
successfully. To resolve these issues, select a
different source field for the target field in the
Configure People Analytics report.

Cross-Pipeline Defects

Cross-Pipeline Subtype Example Defect Message

Consistent Values 100% of values in the Worker pipeline don’t exist
in the Hiring pipeline. 100% of values in the Hiring
pipeline don’t exist in the Worker pipeline. The
inconsistency of values across pipelines exceeds
the threshold of 100%.
Data Type Data types aren't the same across pipelines. Level
1 uses Text in the Worker pipeline and Single
Instance in the Hiring pipeline.

Cause:

Cross-Pipeline Subtype Cause Description

Consistent Values All of the fields in one pipeline contain values that
aren’t present in the other. This difference suggests
the fields might not be related.
Data Type Data type between 2 fields is different.

Solution:

Cross-Pipeline Subtype Solution Description

Consistent Values Check if the fields are the same between the
pipelines in the Configure People Analytics
report. If they are, you might ignore this issue. If
they aren't, select a different source field for the

Cross-Pipeline Subtype Solution Description

target field in the Configure People Analytics
report to ensure field uniformity across the
pipelines.
Data Type Select the corresponding field for the problem
pipeline in the Configure People Analytics report.

Duplicates
Example defect messages:
• In the Worker pipeline, there are 8 records with the same Employee ID, Hire Date.
• In the Worker pipeline, Employee ID appears 4 times with the same Hire Date 01/01/2022, Report
Effective Date 02/02/2022.
Cause: There are multiple records of the same worker.
Solution: Duplicate records in the primary key field are a critical issue. If encountered, address it
before proceeding to avoid inaccuracy in the results across all tabs in the People Analytics report. In
the Configure People Analytics report, confirm that you've selected the correct source field for the
Employee/Candidate ID target field. If the source and target fields match, use the People Analytics
Data Quality report to find the workers or candidates whose IDs are identical. Search the problem ID and
select the correct records for the worker. You can filter out the incorrect records in the Configure People
Analytics report.

Illogical values
Example defect messages:
• In Recruiting Start Date, 30 of 100 records have illogical values. Recruiting Start Date occurs after
Status Start Date, however the Recruiting Start Date should always be before the Status Start Date.
• In the Supervisory Organization, 30 of 100 records have illogical values. These records don't correlate
with other dimensions in the organization hierarchy. The Supervisory Organization is the org in the
hierarchy where the worker sits.
Cause: A particular field in the pipeline contains values that fail logic rules defined for that field. Example: a
Hire date for a worker is in the future.
Solution:

Severity Solution Description

Moderate You can ignore these issues as this defect might
not have a significant impact on the performance of
the People Analytics report.
Major or Critical Select a different source field for the target field in
the Configure People Analytics report.

Invalid Values
Example defect message:
• In Can_Job_Requisition_Status, 50 of 100 records have invalid values.
Cause: A particular field contains values not considered valid for that field.
Solution:

Severity Solution Description

Missing Values
Example defect message:
• In Region, 50 of 100 records have missing values.
Cause: A particular field is missing a percentage of its values.
Solution:

Severity Solution Description

Multiple Hierarchies
Example defect messages:
• 20 records for Supervisory Organization have multiple parents. Supervisory Organization is mapped to
the Assigned Organization target field in the Worker pipeline.
• The record Supervisory Org A for Supervisory Organization has 5 hierarchies.
Sources of multiple hierarchy defects vary, and each requires its own solution.

Root Cause Solution Description

Multiple hierarchy types have been mapped into the In the Field Mapping step of theConfigure People
target hierarchy fields. Example: Mapping the field Analytics report, ensure that you've mapped your
Cost Center Level 2 into Level 1, Supervisory Level hierarchy correctly across the target hierarchy
3 into Level 2. fields.
Your selected hierarchy has more than 1 top-level Create a calculated field and select your preferred
hierarchy. top-level hierarchy for it. Select the calculated field
for the target hierarchy fields.
There are inactive employees that have filtered Create a Worker report and search for the workers
into the current snapshot with an out-of-date that are in incorrect hierarchies. Look at whether
organizational hierarchy. they have been terminated months in the past and
contain an old hierarchy.

Population
Example defect messages:
• 30 records for Intersection 1 in the Worker pipeline don't have sufficient population.
• The intersection Female-White in the field Intersection 1 has a population of 8, which is less than the
minimum requirement of 10 workers.

Cause: The number of unique values in a particular VIBE Index intersection is less than the minimum
headcount requirement for VIBE Index intersections.
Solution:

Severity Solution Description

You can ignore these issues as this defect might Select a different source field for the target field in
not have a significant impact on the performance of the Configure People Analytics report.
the People Analytics report.

Related Information
Concepts
Concept: Data Quality Module on page 559
Tasks
Create Calculated Fields
Reference
People Analytics Office Hours

VIBE Index in People Analytics

Concept: VIBE Index in People Analytics

VIBE™ stands for Value Inclusion, Belonging, and Equity. The VIBE Index topic area in Workday People
Analytics surfaces key outcome metrics showing where you can improve equity and parity across all
people groups (intersections). These insights help you to set, achieve, and renew goals that cultivate
belonging and diversity in your workplace.

VIBE Maturity Model

To help organizations assess their progress and move forward in cultivating belonging and diversity,
Workday developed the VIBE Maturity Model. The model consists of 3 stages. Each stage represents a
VIBE Score range.

Stage Description VIBE Score Range

Commit Set strategy and define 0-1
commitments.
Drive Identify drivers and develop best 2-3
practices.
Thrive Achieve and renew goals. 4-5

Outcome Scores
To determine the VIBE Score for your organization, we calculate outcome scores and group scores.
Outcome scores identify areas where you can improve parity across all intersections in each metric.

Metric Description Calculation Time Frame

Attrition Number of terminations within Depending on your data history:
rolling period.
• 12 months, or
• 3 months.

Metric Description Calculation Time Frame

Belonging Number of workers with a positive Last Peakon scores for the
belonging sentiment within belonging questions up to 12
period. months back.
Hires Number of new hires within rolling Depending on your data history:
period.
• 12 months, or
• 3 months.

Leadership Number of workers in leadership Current snapshot period

roles at end of period.
Promotions Number of promotions within Depending on your data history:
rolling period.
• 12 months, or
• 3 months.

An outcome score is the total number of successes for an outcome metric, scaled to align with the VIBE
Score range.

Group Scores
Group scores identify opportunities to improve parity across all outcome metrics in each intersection. A
group score is the total number of outcome metric successes for a given intersection, scaled to align with
the VIBE Score range.
The intersection you include in your field-mapping configuration of People Analytics determines the
intersections we include in the VIBE Index.

Successes
When you meet or exceed the parity benchmark for an outcome metric (excluding Attrition), we consider it
a success. Successes determine the group and outcome scores.
High attrition can negatively affect an organization, so we flag attrition as below parity when the
representation is above the comparison point.

Intersections
An intersection is a group that consists of workers with various demographics and characteristics. An
intersection is a field or a group of fields that represent the dimensions you want to analyze in the VIBE
Index.
We recommend that you use a minimum and maximum of 2 fields to define your intersections.
Examples of fields used to define an intersection: Ethnicity, Gender, Disability Status, Veteran Status,
Sexuality.
Example of an intersection: Gender and Ethnicity.
The values of the fields you use to define the intersection determine the intersection values. Each
intersection value is an individual intersection (people group).
Example: You define a Gender and Ethnicity intersection. The intersection includes these values [people
groups]:
• Female - Asian
• Female - URM
• Female - White
• Male - Asian

• Male - URM
• Male - White

Parity
Parity means that different groups get equal, favorable outcomes while incorporating contributing factors.
Demographic parity is a measure of fairness indicating that the difference in favorable outcomes between
groups is zero.
Example: We reach pay parity between men and women when both groups achieve equal pay after
accounting for contributing factors such as job title, industry, education, and experience.

Parity Matrix
The Parity Matrix displays each intersection as the comparison point against the proportional values
of all outcome metrics. When an outcome metric is at or above parity, we consider the outcome metric
a success. An outcome metric is considered below parity when it falls below the representation for an
intersection, except for Attrition.
High attrition can negatively affect an organization, so we flag attrition as below parity when the attrition
value for an intersection is above the comparison point.

Filters
This topic area only includes the Organization Level Hierarchical filter type.
Related Information
Concepts
Concept: Filtering in People Analytics on page 605

Concept: Belonging in the VIBE Index

Note: The Belonging metric is only available for Workday Peakon Employee Voice customers who have
opted into the VIBE Index.
Belonging refers to an employee’s sense that they're an accepted member of a group or team. Employees
express their sense of belonging by completing Workday Peakon Employee Voice surveys. Their answers
determine their individual Belonging score that is measured against a threshold. If an employee’s score
exceeds 8 on a scale of 0 - 10, we consider their sense of belonging to be above the threshold for positive
sentiment. The Belonging outcome score contributes to the VIBE Score for your organization.
You can manage your Peakon data in People Analytics by using the Employee Sentiment topic of interest
in the Configure People Analytics report, where you can select questions for your belonging surveys.
You can only use standard Peakon questions to measure Belonging. If you select only 1 question, the
resulting Belonging score is the latest score per employee from the past 12 months.If you select more than
1 question, the resulting score is the average of the latest scores per employee from the past 12 months,
for each question.
For each monthly People Analytics update, Workday uses the latest employee scores available.
To prevent reporting on a nonrepresentative worker population, Workday measures Belonging outscore
score for organizations where:
• At least 20% of workers have participated in Workday Peakon Employee Voice surveys over the past
12 months
• There are at least 10 such workers.
Example: this means that an organization of 100 employees would require at least 20 participants to
measure the Belonging outcome score. In an organization of 40 active employees, 8 responders meet the
20% requirement, however, at least 10 responders would be necessary to measure the score.
If the conditions aren’t met, the Belonging column doesn’t appear on the VIBE parity matrix.

Related Information
Reference
2022R2 What's New Post: VIBE Index for Workday Peakon Employee Voice
Configuring the diversity and inclusion questions

Concept: Calculating the VIBE Score

The VIBE Score™ is the arithmetic average of the overall outcome score and the overall group score. The
VIBE Score indicates which stage of the VIBE Maturity Model the organization is currently in.
To calculate individual and overall outcome scores and calculate individual and overall group scores, we
first calculate the:
• Representation for each intersection.
• Parity View for each intersection and outcome metric.
• Parity Benchmark for each intersection.
• Parity Definition for each intersection and outcome metric.

Representation
Representation is the percentage of active headcount in each intersection at the end of the period.
Representation is the parity benchmark that drives the scoring in the VIBE Index.
Formula: Representation of [Intersection] = (Active headcount for intersection at end of period / Total active
headcount at end of period) * 100
Example: Representation of Female - White = (2000 / 8600) * 100 = 23.3%

Parity View
The Parity View is the proportional value of a given outcome metric for a given intersection.
Formula: Parity View for [Outcome Metric] in [Intersection] = (Metric Total for Intersection / Metric Total) *
100
Example: Parity View for Promotions in Female - White = (400 / 1593) * 100 = 25.1%

Parity Benchmark
The Parity Benchmark for a given intersection is the level of success in percent for all outcome metrics
after incorporating the default threshold of 3%.
The threshold sets the acceptable range by which we can score an intersection as a success for a given
outcome metric. The default threshold of 3% relaxes all success criteria by 3%.
Formula for most outcome metrics (Hires, Leadership, Promotions, Belonging): Parity Benchmark for
[Intersection] = Representation * (100 - Threshold) / 100
Example: Parity Benchmark for Female - White = 23.3 * (100 - 3) / 100 = 22.6%
Formula for the outcome metric Attrition: Parity Benchmark for [Intersection] = Representation * (100 +
Threshold) / 100
Example: Parity Benchmark for Female - White = 23.3 * (100 + 3) / 100 = 24.0%

Parity Definition
The Parity Definition states whether or not a given outcome metric is a success for a given intersection.
To determine the parity definition for most outcome metrics (Hires, Leadership, Promotions, and
Belonging), we compare the parity view to the parity benchmark for the intersection. 1 is a success, zero is
below parity.

Formula for most outcome metrics (Hires, Leadership, Promotions, Belonging): Parity Definition of
[Outcome Metric] for [Intersection] = IF ((Parity View) >= (Parity Benchmark) , 1, 0)
Example: Parity Definition of Promotions for Female - White = IF (25.1 >= 22.6, 1, 0) = 1
For Attrition, we compare the attrition parity view to the parity benchmark for attrition. 1 us a success, zero
is below parity.
Formula for the outcome metric Attrition: Parity Definition of Attrition for [Intersection] = IF ((Attrition Parity
View) <= (Parity Benchmark for Attrition), 1, 0 )
Example: Parity Definition of Attrition for Female - White = IF (18.8 <= 24.0, 1, 0) = 1

Outcome Scores
An outcome score is the total number of successes for a given outcome metric, scaled to align with the
VIBE Score range.
The raw outcome score is the sum of the successes of all intersections minus 1.
We subtract 1 from the sum because the outcome metric parity view for at least 1 intersection must always
be at or above the intersection representation (for attrition, at least 1 intersection must always be at or
below the intersection representation). Subtracting 1 also resets the scale of the score to have a minimum
of 0 to be consistent with the VIBE Score range.
If the parity view for a given outcome metric is unattainable, we don't calculate the outcome metric score
and we exclude the metric from the VIBE Score calculation. As a result, the Outcome Scores card doesn't
display the excluded outcome metric and the Parity Matrix displays a dash for all intersections in the
corresponding outcome metric column. Example: If there were no terminations in the last 12 months, the
outcome metric Attrition is unattainable. Therefore, we don't include the outcome metric Attrition in the
VIBE calculation.
Formula: Raw Outcome Score for [Outcome Metric] = SUM ((Success Count Intersection 1), (Success
Count Intersection 2), (Success Count Intersection 3), ...) - 1
Example (for 5 intersections): Raw Outcome Score for Hires = SUM (1 + 1 + 0 + 1 + 1) - 1 = 3
Scaling the raw outcome score ensures that each outcome score is on a scale of 0 - 5 to align with the
VIBE Score range.
Formula: Scaled Outcome Score for [Outcome Metric] = (Raw Outcome Score) * (5 / ((Number of Groups)
- 1))
Example (continued): Scaled Outcome Score for Hires = 3 * (5 / (5 - 1)) = 3.75

Group Scores
A group score is the total number of outcome metric successes for a given intersection, scaled to align with
the VIBE Score range.
Formula: Raw Group Score for [Intersection] = SUM ((Attrition Parity Definition), (Hires Parity Definition),
(Leadership Parity Definition), (Promotions Parity Definition), (Belonging Parity Definition))
Example: Raw Group Score for Female - White = SUM (0 + 1 + 1 + 0 + 1) = 3
Scaling the raw group score ensures that each group score is on a scale of 0 - 5 to align with the VIBE
Score range.
Formula: Scaled Group Score for [Intersection] = Raw Group Score * (5 / (Number of Outcome Metrics))
Example: Scaled Group Score for Female - White = 2 * (5 / 5) = 2

VIBE Score
The VIBE Score ranges from 0 to 5 and is the arithmetic average of the overall outcome score and the
overall group score.
The VIBE Score is sensitive to the magnitude of the group and outcome scores and the variance among
these scores. This means that the VIBE Score is higher when intersections have higher group scores,
outcome scores are higher, and there's less overall variance among group scores and among outcome
scores (greater equity).
To get the overall outcome score or the overall group score, we add 1 to each individual score. This
prevents multiplication by a value that is less than 1. We then multiply the individual scores and subtract 1
from the resulting value. This sets the score on a scale of 0 - 5 to align with the VIBE Score range.
Formula: Overall Outcome Score = (PRODUCT ((Each Scaled Outcome Score) + 1)) ^ (1 / (Number of
Outcomes)) - 1
Example: Overall Outcome Score [Hires, Promotions, Leadership, Attrition, Belonging] = ((3 + 1) * (3 + 1) *
(1 + 1) * (2 + 1) * (3 + 1)) ^ (1 / 4) - 1 = 2.29
Formula: Overall Group Score = (PRODUCT ((Each Scaled Group Score) + 1)) ^ (1 / (Number of
Intersections)) - 1
Example: Overall Group Score [Female - Asian, Female - URM, Female - White, Male - Asian, Male -
URM, Male - White] = ((3.75 + 1) * (2.5 + 1) * (2.5 + 1) * (2.5 + 1) * (1.25 + 1) * (5 + 1)) ^ (1 / 6) - 1 = 2.74
The arithmetic average of the overall outcome score and the overall group score is the VIBE Score for your
organization.
Formula: VIBE Score = AVG ((Overall Outcome Score) , (Overall Group Score))
Example: VIBE Score = AVG (2.29, 2.74) = (2.29 + 2.74) / 2 = 2.52

Concept: Skills in People Analytics

Skills Cloud is a machine-learning-powered remote collection of skills for workers and candidates to select
from. You can use Skills Cloud to build qualification requirements and easily track worker capabilities.
Workday brings the power of Skills Cloud to People Analytics through a new Skills topic area. With People
Analytics and Skills Cloud, you can better understand what skills your workforce has with visualizations
of top skill categories for management levels and job families. The Skills topic area in People Analytics
also helps you identify your workforce’s largest skill gaps and helps you prioritize the best opportunities to
upskill workers, with the introduction of a worker Gap Score and Match Score.
The Gap Score is 1 minus the Match Score for a worker. Match Score is a calculation that compares a
worker's current portfolio of explicit and inferred skills to the skills (explicit and inferred) listed on their job
profile. Workday calculates the skill gaps and subtracts the total from 1 to assign each worker a score on
a scale of 0 - 1. Lower match scores indicate opportunities for workers to invest in achieving the expected
skills of their role. High match scores indicate that the workers have the expected skills of their role. Match
Score utilizes Skills Cloud skills and not tenanted skills.
Workday also assigns each worker a Match Score Signal to indicate where on the Match Score Scale a
worker falls.
Match Score Signals

Match Score Signal Definition

0 Score Equal to 0.
Low Greater than equal to 0 and less than or equal to
0.06.

Match Score Signal Definition

Fair Greater than 0.06 and less than or equal to 0.22.
Good Greater than 0.22 and less than or equal to 0.45.
Strong Greater than 0.45 and less than or equal to 1.

The Detailed Data tab shows the Match Score Signal for each worker.
Related Information
Tasks
Steps: Set Up Skills in People Analytics on page 551

Concept: Filtering in People Analytics

When you view the People Analytics report, Workday automatically filters the analysis Storyteller
performs each month and displays prioritized insights on each topic area by default. However, you can use
the filter panel on the left side of the report to view additional stories and key metrics from the analysis, or
to focus on insights related to specific dimensions. Example: You can view attrition for different areas of
your business by filtering by region.
The filter panel displays the filters available on each topic area. When you add or remove a filter value,
Workday immediately refreshes the KPIs, stories, and visualizations displayed.
Your People Analytics configuration determines what displays in the filter panel. Your People Analytics
administrator determines:
• Which filters are available in the filter panel.
• The field mapped to each filter.
• The display name of each filter.
Workday enables up to 6 filters total, from a total of 2 groups. The filters in a group come from different
levels in a hierarchy, either the primary or secondary hierarchy. Typically, the filters in the primary
hierarchy are mapped to levels in Supervisory Organization, and the filters in the secondary hierarchy
are mapped to levels in a geographical hierarchy. Alternatively, your administrator might map fields that
represent levels in Cost Center to either hierarchy.
The People Analytics application doesn't indicate which hierarchy a filter is from, but the top 3 filters come
from the primary hierarchy, and the lower filters come from the secondary hierarchy.
Example: You might have these filters:

Filter Display Name Notes

Org Level 2 By default, this is the second level in the configured organization,
typically a level in Supervisory Organization.
Org Level 3 By default, this is the third level in the configured organization,
typically a level in Supervisory Organization.
Org Level 4 By default, this is the fourth level in the configured organization,
typically a level in Supervisory Organization.
Region Region represents the top-most level of a geographical hierarchy.
This filter isn't available on the VIBE Index topic area.

Country Country represents the middle level of a geographical hierarchy.

This filter isn't available on the VIBE Index topic area.

Filter Display Name Notes

Location Region represents the lowest level of a geographical hierarchy,
usually associated with the worker.
This filter isn't available on the VIBE Index topic area.

The field mapped to each filter might be associated with a worker or a job requisition, depending on which
topic area you're viewing in the application.
The values available in a filter are based on:
• The field mapped to the filter.
• Your security permissions on the values in the field.
Note: If your People Analytics administrator enforces constrained security on the application, then you
might not have permission to view all prioritized insights that display on a topic area by default. Workday
prepopulates filters on the filter panel for constrained users to display prioritized insights based on their
security permissions.

Using Multiple Filters

You can select more than 1 filter when viewing a topic area. You can select multiple filters from the same
hierarchy or from different hierarchies.
However, Workday applies the filters differently to the content depending on:
• From which hierarchy the filters come.
• The type of content, such as viz or story.

Multiple Filters Vizzes KPIs Stories

From different Workday applies all filter Workday applies all filter Workday applies only 1
hierarchies values to the viz data. values to the KPI data. filter to the stories.
To ensure top stories
results when using
filters, use filters from
only one hierarchical
filter type at a time.

From 1 hierarchy only Workday applies all filter Workday applies only 1 Workday applies all filter
values to the viz data. filter to the data in the values to the stories.
KPIs.
Example: You select
both San Francisco
and Pleasanton for the
Location filter. Workday
displays data in the KPIs
for either San Francisco
or Pleasanton, but not
both locations.

Related Information
Concepts
Concept: Storyteller Engine on page 609

Concept: Export and Download Options

From the People Analytics Data Quality report and the People Analytics report, you can export and
download insights to use for presentations, discovery boards, and other resources for further analysis.

People Analytics Data Quality Report

Option Content Prerequisites Action

Download as PNG Visualizations Security: Manage: On a visualization, select
People Analytics domain the related actions menu
in the People Analytics > Download as PNG.
and Prism Analytics
Workday generates
functional areas.
the PNG file and saves
it to the directory
configured in your
browser. The filename is
the visualization name.

Export to Discovery Data Quality Details Steps: Set Up Tenant On the Data Quality
Board table for Discovery Boards on Details visualization,
page 283. select the related actions
menu > Export to
Security: Manage:
Discovery Board.
People Analytics domain
in the People Analytics
and Prism Analytics
functional areas.

Export to Discovery View more content for Steps: Set Up Tenant On the Data Quality
Board a defect in the Data for Discovery Boards on Details visualization,
Quality Details table page 283. select View more for a
defect. Select the related
Security: Manage:
actions menu > Export
People Analytics domain
to Discovery Board.
in the People Analytics
and Prism Analytics
functional areas.

People Analytics Report

Option Content Prerequisites Action

Download as PNG Visualizations Security: View: People On a visualization, select
Analytics domain in the related actions menu
the People Analytics > Download as PNG.
and Prism Analytics
Workday generates
functional areas.
the PNG file and saves
it to the directory
configured in your
browser. The filename is
the visualization name.

Option Content Prerequisites Action

Export to Discovery Detailed Data for a KPI Steps: Set Up Tenant On a KPI card or story
Board or a story for Discovery Boards on card, select View more
page 283. to access the Detailed
Data tab. Select the
Security: View: People
Detailed Data tab >
Analytics domain in
related actions menu >
the People Analytics
Export to Discovery
and Prism Analytics
Board.
functional areas.

Export to Workday KPI content or story Steps: Set Up Security On a KPI card, story
Slides content and associated for Slides on page 796. card, or visualization,
trend chart select the related actions
Security: View: People
menu > Export to
Visualizations Analytics domain in
Workday Slides.
the People Analytics
and Prism Analytics On a KPI card or story
functional areas. card, select View more.
Select the related
actions menu > Export
to Workday Slides.
The Export to Workday
Slides option does not
export content from the
Detailed Data tab. Use
the Export to Discovery
Board option to export
detailed data.

Concept: Providing Feedback on Story Quality

As a data product governed by the Innovations Services Agreement, People Analytics relies on user
input and feedback to increase the quality of stories. People Analytics includes a feedback mechanism
that securely collects individual feedback and reduces the need for offline surveys or extensive feedback
sessions.
If you experience issues with the product or need immediate attention, file a customer support ticket
instead of using the in-app feedback mechanism.

Feedback Process
You can give Workday feedback on the quality of a story by clicking the thumbs up or thumbs down icon
on a story card. The contextual feedback helps People Analytics identify specific aspects of the story that
need improvement. After you submit feedback, the thumbs up or thumbs down icon remains highlighted.
You can see what feedback you submitted, but you can't edit or resubmit feedback. People Analytics
resets feedback icons weekly so you can submit new feedback for each story.

Feedback Data Privacy

Submitting feedback is optional and is opt-out by default. Even after you click the thumbs up or thumbs
down icon, you can decide not to submit feedback by closing the feedback window.
For each story, the same set of feedback reasons displays to all users when you select the thumbs up
or thumbs down icon. People Analytics doesn't capture or solicit any personally identifiable information.
Workday only views feedback reasons in aggregate and uses the data to:

• Improve storyteller engine algorithms.

• Track story quality.

Concept: Storyteller Engine

People Analytics uses an automated analytical engine called Storyteller that:
• Searches millions of combinations of data.
• Makes connections between the combinations of data.
• Surfaces the most significant results in the form of stories.
A story is a finding in the data that addresses a business question. Example: What are key turnover
trends?
Each story describes an instance of significant under- or overperformance in a metric, along with a
combination of dimensions, trends, and drivers that contribute to the finding.
Storyteller uses statistical and heuristic methods to determine the ranking of stories and which stories
should surface after performing one of these comparisons:
• Comparison to historical performance - Storyteller surfaces these stories when the engine detects a
significant variance between the current performance of a metric against historical performance. The
look-back period is usually 12 months if you have at least 13 months of data history in People Analytics,
or 3 months if you have less than 13 months of data history. However, the look-back period might vary
depending on the metric.
• Internal peer group comparison - Storyteller compares current performance in a given organization
or location (region, country, or other location) against the performance of peers within the company
and surfaces significant gaps as stories. Depending which level the story is on, the peer group
changes. Storyteller might make the comparison at the company or region level, or at a different level
in the hierarchy. By comparing performance to the closest peers in the same organization or region,
Storyteller can identify stories that provide insights which are actionable and meaningful in relation to
the dimension where the story takes place. Examples:
• For a story on FP&A suborganization in Finance at Level 3, the Storyteller engine compares
performance of this dimension against the performance of the parent organization Level 2 (instead of
comparing to the performance of Level 1).
• For a story in Canada, Storyteller identifies stories by comparing performance in Canada against
performance at the region level, such as North America or the Americas.

Automatic Filtering
To help ensure the highest quality of insights, Storyteller automatically filters out stories where:
• The population size is 5 or less people.
• There is no active headcount for 1 or more months that are included in the story analysis. This filtering
only applies to stories in these topic areas:
• Diversity and Inclusion
• Organization Composition
• Retention and Attrition
• Talent and Performance
Example: A story on a Female Diversity Trend where there is no active headcount for 1 or more of the
12 months analyzed.
Example: A story on a Female Diversity Gap where there is no active headcount for the month
analyzed.

Related Information
Reference
FAQ: People Analytics on page 645
The Next Level: People Analytics: Storyteller Deep Dive
Workday Community: Generally Available Innovation Services – Descriptions and Exhibits

Concept: Trends, Gaps, Top Drivers, and Detailed Data

You can click View More on a KPI or story card to view a metric as it changed over time, underlying
drivers, and additional details about it.

Trends and Gaps

A trend in People Analytics demonstrates how a metric changed over time. The amount of data history you
have in People Analytics determines the number of months used for comparison in the trend. Example:
Reviewing performance in Canada over the period of 12 months.
Trend stories compare the current performance trend to the performance trend at the beginning of the
historical period.
Gap stories compare the current performance trend with the performance of an internal peer group.
Example: Comparing current performance in Canada to the current performance of the Americas.

Top Drivers
The storyteller engine surfaces top drivers of a metric by slicing the metric by different dimensions.
Examples: Ethnicity, generation, location, or management level.
The Top Drivers tab on a story card displays dimensions:
• Contributing to the performance gap in the story.
• Driving the story in the opposite direction.
Tables underneath the dimensions display personalized insights for each top driver, using conversational
language to convey key information. Example: Female Representation in this Tenure Category is 64.3%
— which is 18.7 percentage points above Cost Center 1. Top drivers display by the severity of their impact
on the story: from High to Low.
The change in metric, population size, and historic trend (for trend business questions) determine the
impact level. High impact labels indicate areas of the organization where there might be an immediate
need for focus.
Decision makers can focus on a few of the biggest drivers to improve performance of the metric as that can
even influence other, not so impactful drivers.
Example: In the last 12 months, female representation in your organization’s level 4 has increased by 18.8
percentage points.
Which drivers are contributing to higher Female Diversity Trend in Org Level 4?

Top drivers (Dimension: Value) Impact level (High, Medium, Low)

Ethnicity: Hispanic High impact
Location: Atlanta Medium
Management level: 9 manager Low
Location: New York City Campus Low

Each top driver tab includes detailed information on the metric composition.

Which areas scored lower for Female Diversity Trend in Org Level 4?

Top drivers (Dimension: Value) Impact level (High, Medium, Low)

Location: New York Medium
Job Level: Team Players 2 Low

Each top driver tab includes detailed information on the metric composition.

Detailed Data
The Detailed Data tab is designed to be a preview and displays the first 100 rows of data with the
possibility of restricting the list to an individual month. You can export the data to a discovery board to view
all rows of data and perform further analysis.
Related Information
Concepts
Concept: Storyteller Engine on page 609
Reference
2022R2 What's New Post: Story Cards and Top Drivers Redesign

Reference: Business Questions by Topic Area

Workday People Analytics surfaces analytics in the form of business questions, organized by topic area.
The business questions for each topic area help you gain insight into your organization and discover
specific trends and patterns.

Diversity and Inclusion

This topic area helps you understand the current demographic of an organization. It can also help you
make improvements in the different segments of diversity within an organization.

Business Question Guidance Related Metric

What are key trends in female Surfaces different trends related Female Representation
representation? to gender diversity within an
organization. Trends can consist
of positive or negative impacts
to overall gender diversity for the
organization.
Where can we improve female Surfaces areas in the Female Representation
representation? organization that need
improvement in gender equality.
This question compares the
female representation of
the segment to the female
representation in the overall
company, organization, or region.
Improvements in this dimension
also drive improvement to the
female representation of the
overall company or organization.

Business Question Guidance Related Metric

Where are gaps in Surfaces areas in the Female Representation
female representation in organization that are lacking
Filtered on Is Manager = Yes
management? female representation in
management level roles.
Where can we improve female Identifies areas where there are Retention Rate
retention in the workforce? low retention rates for female
Filtered on Females
workers in the organization.
Where are gaps in promoting Surfaces areas in the Promotion Rate
females? organization or key indicators
Filtered on Females
that need improvement in
gender diversity for the rate of
promotions. This helps ensure
equal opportunities in upward
mobility within an organization.

Organization Composition
This topic area explores business questions related to the structure of an organization.

Business Question Guidance Related Metric

Where is the organization Surfaces areas in the Headcount Growth Rate
growing? organization that are trending
in a positive direction for active
headcount growth.
What are the outliers in span of Surfaces stories where there Average Span of Control
control? might be high or low span of
Excludes unfilled positions
control in the organization
by comparing the metric in a
particular dimension to the metric
for the overall company, region,
or organization.
Where are gaps in internal Surfaces areas of your Individual Contributor to Manager
mobility to management? organization where, compared Rate
to other areas, fewer individual
contributors, on average, move
into management-level roles.
What are outliers in tenure? Identifies areas in the Average Tenure
organization that are categorized
as an outlier in average tenure.
This could surface areas of high
or low tenure in the organization.
Where are gaps in compa- Identifies areas of the Average Compa-Ratio
ratio? organization that are categorized
as an outlier in average compa-
ratio.
Where are gaps in promotions? Identifies the attributes of workers Promotion Rate
or the areas that aren't being
promoted as much as the overall
population of the organization.

Retention and Attrition

This topic area explores business questions related to why workers are leaving and how to improve
retention of workers in an organization.

Business Question Guidance Related Metric

What are the key turnover Reveals turnover trends in the Attrition Rate
trends? workforce that are impacting the
overall attrition rate in a negative
way. Very low turnover could
lead to stagnant innovation, while
high turnover could lead to high
financial impact. This question
points to problem areas you can
focus on and address proactively.
Who is leaving? Surfaces areas in the company Attrition Rate
where workers are leaving and
the possible reasons workers
state for why they are leaving
an organization. This business
question focuses on the gap
between the overall company,
region, or organization attrition
rate and the area that needs
attention.
Where can we improve Surfaces areas of the Retention Rate
retention? organization that have a high
churn rate, with employees
leaving in the early years of their
tenure.
Where do we have the Sheds insight on when people Average Voluntary Terminations
lowest tenure for voluntary voluntarily leave the organization. Tenure
terminations? This reflects low tenure in the
organization.
Where do we lose the most Surfaces areas where new hires New Hires Attrition Rate
new hires? with an average tenure of less
than 1 year exit the organization.

Hiring
This topic area explores business questions related to candidates and requisitions for hiring.

Business Question Guidance Related Metric

What are the key trends in Surfaces areas within the Average Time to Fill
hiring? organization that show anomalies
in average time to fill from a
historical point of view.
Where does it take longer to Surfaces areas that deviate from Average Time to Hire
hire? the overall company average for
time to hire, as well as drivers of
stages that create bottlenecks in
the hiring process.

Business Question Guidance Related Metric

What areas do we need to Surfaces areas of the Offer Decline Rate
focus on to stay competitive organization that could improve
with offers? offer acceptance by candidates.

Talent and Performance

This topic area explores business questions related to the talent and performance of workers.

Business Question Guidance Related Metric

What are key trends in talent? Surfaces areas in the High Potentials Representation
organization where workers
are flagged as high potentials,
providing insight into
opportunities for performance
growth.
Where are we losing high Surfaces areas of the High Performers Voluntary
performers? organization the business needs Attrition Rate
to focus on and provides insight
on why high performers are
leaving the company.
Where can we focus to improve Surfaces areas within the High Performers Rate
performance? organization that show variances
of high performers deviating
from the norm by comparing to
the high performers rate for the
company, region, or organization.

Skills
This topic area explores the skills data of your workforce.

Business Question Guidance Related Metric

Where are opportunities to Highlights areas of the Average Gap Score
upskill workers? organization to upskill workers
and improve worker skill sets.

Related Information
Reference
The Next Level: People Analytics: Resources to Help Validate Your Organization's Data

Reference: Metrics in People Analytics

People Analytics uses metrics to drive insights to answer key business questions about an organization.
These metrics also support KPIs, visualizations, and stories.
Each KPI and story offers a comparison point. Trend stories and KPIs display the historic performance of a
given metric. The historic performance snapshot varies depending on the metric. Historic snapshot periods
can reflect:
• 12 months ago, if you have at least 13 months of data history.
• 3 months ago, if you have less than 13 months of data history.

• The month prior to the current snapshot period.

Gap stories compare the current performance of the dimension where the story takes place to the current
performance of an internal peer group.
The values of these fields determine which records are included in the analysis for a given month:
• Report Effective Date for the Worker pipeline.
• Status Month for the Hiring pipeline.
People Analytics uses these metrics:
• Attrition Rate on page 615
• Average Compa-Ratio on page 616
• Average Compa-Ratio of Terminations on page 616
• Average Gap Score on page 617
• Average Span of Control on page 617
• Average Tenure on page 618
• Average Time To Fill on page 618
• Average Time To Hire on page 619
• Average Voluntary Terminations Tenure on page 620
• Female Attrition Rate on page 620
• Female Representation on page 621
• Female Representation in Leadership on page 621
• Headcount Growth Rate on page 622
• High Performers Rate on page 622
• High Performers Voluntary Attrition Rate on page 623
• High Potentials Representation on page 624
• High Potentials Voluntary Attrition Rate on page 624
• Individual Contributor to Manager Rate on page 625
• New Hires Attrition Rate on page 625
• New Hires Retention Rate on page 626
• Offer Accepted Rate on page 627
• Offer Decline Rate on page 628
• Promotion Rate on page 628
• Referral Hire Rate on page 630
• Retention Rate on page 630

Attrition Rate

What uses this metric? KPI: Attrition Rate

Trend Business Question: What are key turnover
trends?
Gap Business Question: Who is leaving?

Calculation Time Frame Depending on your data history:

• 12 month rolling period, or
• 3 month rolling period.

Calculation rollingSum(unique([Employee_ID]),
12) for ("Terminated_This_Period",
"True") /
{avg_active_headcount_rolling_12_months},
where

avg_active_headcount_rolling_12_months
= (rollingSum(unique([Employee_ID]),
12) for ("Active_Status", "True") /
12)
OR
rollingSum(unique([Employee_ID]),
3) for ("Terminated_This_Period",
"True") /
{avg_active_headcount_rolling_3_months},
where
avg_active_headcount_rolling_3_months
= (rollingSum(unique([Employee_ID]),
3) for ("Active_Status", "True") / 3)

Translation Based on a 12 month or 3 month rolling period.

Number of terminated workers within period /
Average active headcount for period (Sum of active
headcounts for each month / Number of months in
rolling period) * 100

Comparison Point for KPI and Trend Story Month prior to the current snapshot period
Comparison Point for Gap Story Internal peer group

Average Compa-Ratio

What uses this metric? Gap Business Question: Where are gaps in compa-
ratio?
Calculation Time Frame Current snapshot period
Calculation sum([Compa_Ratio]) for
("Active_Status", "True") /
unique([Employee_ID]) for
("Active_Status", "True")
Translation Sum of compa-ratio of active headcount at end
of previous month / Active headcount at end of
previous month
Comparison Point Internal peer group

Average Compa-Ratio of Terminations

What uses this metric? KPI: Average Compa-Ratio of Terminations

Calculation Time Frame Current snapshot period
Calculation sum([Compa_Ratio]) for
("Terminated_This_Period",
"True") / unique([Employee_ID]) for
("Terminated_This_Period", "True")
Translation Sum of compa-ratio of terminated workers in
previous month / Terminated workers in previous
month

Comparison Point Depending on your data history:

• 12 months ago, or
• 3 months ago.

Average Gap Score

What uses this metric? Gap Business Question: Where are opportunities to
upskill workers?
Calculation Time Frame Current snapshot period
Calculation sum([gap_score_pct]) /
unique([Employee_ID])
Translation Sum of gap scores for workers at end of previous
month / Active headcount at end of previous month
Gap Score = 1 - Match Score

Comparison Point Internal peer group

Average Span of Control

What uses this metric? KPI: Average Span of Control

Gap Business Question: What are outliers in span
of control?

Calculation Time Frame Current snapshot period

Calculation sum([Direct_Reports]) for
("Manager_With_Direct_Reports",
"True") for ("Active_Status",
"True") / unique([Employee_ID])
for ("Manager_With_Direct_Reports",
"True") for ("Active_Status", "True")
Translation Number of active direct reports at end of previous
month / Number of active managers with direct
reports at end of previous month
Excludes unfilled positions

Comparison Point for KPI Depending on your data history:

• 12 months ago, or
• 3 months ago.

Comparison Point for Gap Story Internal peer group

Example:

Supervisory Org Managers Direct Reports

Vice President 1 2
Director A 1 3
Manager A1 1 4

Supervisory Org Managers Direct Reports

Manager A2 1 7
Manager A3 1 3
Director B 1 4
Manager B1 1 2
Manager B2 1 5
Manager B3 1 8
Manager B4 1 3
Total 10 41

Average Tenure

What uses this metric? KPI: Average Tenure

Gap Business Question: What are outliers in
tenure?

Calculation Time Frame Current snapshot period

Calculation sum([Length_Of_Service_In_Partial_Years])
for ("Active_Status", "True") /
unique([Employee_ID]) for
("Active_Status", "True")
Translation Sum of length of service of active headcount at
end of previous month / Active headcount at end of
previous month
Comparison Point for KPI Depending on your data history:
• 12 months ago, or
• 3 months ago.

Comparison Point for Gap Story Internal peer group

Average Time To Fill

What uses this metric? Trend Business Question: What are key trends in
hiring?
Calculation Time Frame Current snapshot period
Calculation (total_reqs_hired_filled_time) /
(reqs_filled_hired)
Variables for Calculation • total_reqs_hired_filled_time =
sum([Requisition_Time_To_Fill]) for
("Can_Job_Requisition_Status_Instance_Evaluate
"filled") for
("Stage_Consolidated", "hire")
• Requisition_Time_To_Fill =
DAYS_BETWEEN([Req_Job_Requisition_Filled_Dat
[Req_Recruiting_Start_Date])

• reqs_filled_hired =
{candidates_hired} for
("Can_Job_Requisition_Status_Instance_Evaluate
• Candidates_hired =
unique([Candidate_JobRequisiton])
for ("Stage_Consolidated","hire")
• Candidate_JobRequisiton =
CONCAT([Candidate_ID], "-",
[Job_Requisition])

Translation Sum of time to fill for hires in filled requisitions in

previous month (Number of days from requisition
start date to requisition filled date) / Number of hires
in filled requisitions in previous month
Comparison Point Depending on your data history:
• 12 months ago, or
• 3 months ago.

Average Time To Hire

What uses this metric? KPI: Average Time to Hire

Gap Business Question: Where does it take longer
to hire?

Calculation Time Frame Current snapshot period

Calculation (total_time_to_hire) /
(candidates_hired)
Variables for Calculation • total_time_to_hire =
sum([Time_To_Hire]) for
("Stage_Consolidated", "hire")
• Time_To_Hire =
DAYS_BETWEEN([Recruiting_Start_Date],
[Worker_Hire_Date])
• candidates_hired =
unique([Candidate_JobRequisiton])
for ("Stage_Consolidated","hire")
• Candidate_JobRequisiton =
CONCAT([Candidate_ID], "-",
[Job_Requisition])

Translation for KPI Sum of time to hire for hires in previous month
(Number of days from requisition start date to hire
date) / Number of hires in previous month * 100
Translation for Gap Business Question Sum of time to hire for hires in previous month
(Number of days from requisition start date to hire
date) / Number of hires in previous month
Comparison Point for KPI Depending on your data history:
• 12 months ago, or
• 3 months ago.

Comparison Point for Gap Story Internal peer group

Average Voluntary Terminations Tenure

What uses this metric? Gap Business Question: Where do we have the
lowest tenure for voluntary terminations?
Calculation Time Frame Current snapshot period
Calculation sum([Length_Of_Service_In_Partial_Years])
for ("Terminated_This_Period",
"True") for ("Termination_Category",
"Voluntary") / unique([Employee_ID])
for ("Terminated_This_Period",
"True") for ("Termination_Category",
"Voluntary")
Translation Sum of length of service of voluntary terminations in
previous month / Voluntary terminations in previous
month
Comparison Point Internal peer group

Female Attrition Rate

What uses this metric? KPI: Female Attrition Rate

Calculation Time Frame Depending on your data history:
• 12 month rolling period, or
• 3 month rolling period.

Calculation rollingSum(unique([Employee_ID]),
12) for ("Terminated_This_Period",
"True") for ("Gender", "Female") /
{avg_female_headcount_rolling_12_months},
where
avg_female_headcount_rolling_12_months
= (rollingSum(unique([Employee_ID]),
12) for ("Gender", "Female") for
("Active_Status", "True") / 12)
OR
rollingSum(unique([Employee_ID]),
3) for ("Terminated_This_Period",
"True") for ("Gender", "Female") /
{avg_female_headcount_rolling_3_months},
where
avg_female_headcount_rolling_3_months
= (rollingSum(unique([Employee_ID]),
3) for ("Gender", "Female") for
("Active_Status", "True") / 3)

Translation Based on a 12 month or 3 month rolling period.

Number of female terminations within period /
Average female headcount for period (Sum of

female headcounts for each month / Number of

months in rolling period) * 100

Comparison Point Month prior to the current snapshot period

Female Representation

What uses this metric? KPI: Female Representation

Trend Business Question: What are key trends in
female representation?
Gap Business Question: Where can we improve
female representation?

Calculation Time Frame Current snapshot period

Calculation unique([Employee_ID]) for
("Active_Status", "True")
for ("Gender", "Female") /
unique([Employee_ID]) for
("Active_Status", "True")
Translation Number of female active workers at end of previous
month / Active headcount at end of previous month
* 100
Comparison Point for KPI and Trend Story Depending on your data history:
• 12 months ago, or
• 3 months ago.

Comparison Point for Gap Story Internal peer group

What uses this metric? Gap Business Question: Where are gaps in female
representation in management?
Calculation Time Frame Current snapshot period
Calculation unique([Employee_ID]) for
("Active_Status", "True") for
("Is_Manager", "True") for ("Gender",
"Female") / unique([Employee_ID])
for ("Active_Status", "True") for
("Is_Manager", "True")
Translation Number of female active workers at end of previous
month / Active headcount at end of previous month
* 100
Filtered on Is Manager = Yes

Comparison Point Internal peer group

Female Representation in Leadership

What uses this metric? KPI: Female Representation in Leadership

Calculation Time Frame Current snapshot period

Calculation unique([Employee_ID]) for

("Is_Leader", "True") for ("Gender",
"Female") for ("Active_Status",
"True") / unique([Employee_ID])
for ("Is_Leader", "True") for
("Active_Status", "True")
Translation Number of female active leaders at end of previous
month / Active leaders at end of previous month *
100
Comparison Point Depending on your data history:
• 12 months ago, or
• 3 months ago.

Headcount Growth Rate

What uses this metric? Trend Business Question: Where is the

organization growing?
Calculation Time Frame Current snapshot period
Calculation (unique([Employee_ID]) -
previous(unique([Employee_ID]), 6)
for ("Active_Status", "True")) /
previous(unique([Employee_ID]), 6) for
("Active_Status", "True")
OR
(unique([Employee_ID]) -
previous(unique([Employee_ID]), 3)
for ("Active_Status", "True")) /
previous(unique([Employee_ID]), 3) for
("Active_Status", "True")

Translation Based on a 6 month or 3 month historic snapshot

period.
(Active headcount at end of previous month -
Active headcount at beginning of period) / Active
headcount at beginning of period

Comparison Point Depending on your data history:

• 6 months ago, or
• 3 months ago.

High Performers Rate

What uses this metric? Gap Business Question: Where can we focus to
improve performance?
Calculation Time Frame Current snapshot period
Calculation unique([Employee_ID]) for
("High_Performer", "True") for
("Active_Status", "True") /

unique([Employee_ID]) for
("Active_Status", "True")
Translation Number of high performer active workers at end
of previous month / Active headcount at end of
previous month * 100
Comparison Point Internal peer group

High Performers Voluntary Attrition Rate

What uses this metric? KPI: High Performers Voluntary Attrition Rate
Gap Business Question: Where are we losing high
performers?

Calculation Time Frame Depending on your data history:

• 12 month rolling period, or
• 3 month rolling period.

Calculation rollingSum(unique([Employee_ID]),
12) for ("Terminated_This_Period",
"True") for ("Termination_Category",
"Voluntary") for
("High_Performer", "True") /
{avg_high_performer_headcount_rolling_12_months},
where
avg_high_performer_headcount_rolling_12_months
= (rollingSum(unique([Employee_ID]),
12) for ("High_Performer", "True") for
("Active_Status", "True") / 12)
OR
rollingSum(unique([Employee_ID]),
3) for ("Terminated_This_Period",
"True") for ("Termination_Category",
"Voluntary") for
("High_Performer", "True") /
{avg_high_performer_headcount_rolling_3_months},
where
avg_high_performer_rolling_3_months
= (rollingSum(unique([Employee_ID]),
3) for ("High_Performer", "True") for
("Active_Status", "True")/ 3)

Translation Based on a 12 month or 3 month rolling period.

Number of voluntary high performers terminations
within period / High performers average active
headcount for period (Sum of active headcounts for
each month / Number of months in rolling period) *
100

Comparison Point for KPI Month prior to the current snapshot period
Comparison Point for Gap Story Internal peer group

High Potentials Representation

What uses this metric? KPI: High Potentials Representation

Trend Business Question: What are key trends in
talent?

Calculation Time Frame Current snapshot period

Calculation unique([Employee_ID]) for
("Is_High_Potential", "True")
for ("Active_Status", "True") /
unique([Employee_ID]) for
("Active_Status", "True")
Translation Number of high potential active workers at end
of previous month / Active headcount at end of
previous month * 100
Comparison Point Depending on your data history:
• 12 months ago, or
• 3 months ago.

High Potentials Voluntary Attrition Rate

What uses this metric? KPI: High Potentials Voluntary Attrition Rate
Calculation Time Frame Depending on your data history:
• 12 month rolling period, or
• 3 month rolling period.

Calculation rollingSum(unique([Employee_ID]),
12) for ("Terminated_This_Period",
"True") for ("Termination_Category",
"Voluntary") for
("Is_High_Potential", "True") /
{avg_high_potentials_headcount_rolling_12_months}
where
avg_high_potentials_headcount_rolling_12_months
= (rollingSum(unique([Employee_ID]),
12) for ("Is_High_Potential", "True")
for ("Active_Status", "True") / 12)
OR
rollingSum(unique([Employee_ID]),
3) for ("Terminated_This_Period",
"True") for ("Termination_Category",
"Voluntary") for
("Is_High_Potential", "True") /
{avg_high_potentials_headcount_rolling_3_months},
where
avg_high_potentials_headcount_rolling_3_months
= (rollingSum(unique([Employee_ID]),
3) for ("Is_High_Potential", "True")
for ("Active_Status", "True") / 3)

Translation Based on a 12 month or 3 month rolling period.

Number of voluntary high potentials terminations
within period / High potentials average active
headcount for period (Sum of high potentials
headcounts for each month / Number of months in
rolling period) * 100

Comparison Point Month prior to the current snapshot period

Individual Contributor to Manager Rate

What uses this metric? Gap Business Question: Where are gaps in internal
mobility to management?
Calculation Time Frame Depending on your data history:
• 12 month rolling period, or
• 3 month rolling period.

Calculation rollingSum(unique([Employee_ID]), 12)

for ("Active_Status", "True") for
("IC_To_MGR_This_Period", "True") /
{avg_active_headcount_rolling_12_months},
where
avg_active_headcount_rolling_12_months
= (rollingSum(unique([Employee_ID]),
12) for ("Active_Status", "True") /
12)
OR
rollingSum(unique([Employee_ID]),
3) for ("Active_Status", "True") for
("IC_To_MGR_This_Period", "True") /
{avg_active_headcount_rolling_3_months},
where
avg_active_headcount_rolling_3_months
= (rollingSum(unique([Employee_ID]),
3) for ("Active_Status", "True") / 3)

Translation Based on a 12 month or 3 month rolling period.

Number of active individual contributors to
management within period / Average active
headcount for period (Sum of active headcounts for
each month / Number of months in rolling period) *
100

Comparison Point Month prior to the current snapshot period

New Hires Attrition Rate

What uses this metric? Gap Business Question: Where do we lose the
most new hires?
Calculation Time Frame Depending on your data history:
• 12 month rolling period, or

• 3 month rolling period.

Calculation rollingSum(unique([Employee_ID]),
12) for ("Terminated_This_Period",
"True") for ("Is_New_Hire", "True") /
{avg_new_hires_headcount_rolling_12_months},
where
avg_new_hires_headcount_rolling_12_months
= (rollingSum(unique([Employee_ID]),
12) for ("Is_New_Hire", "True") for
("Active_Status", "True")/ 12)
OR
rollingSum(unique([Employee_ID]),
3) for ("Terminated_This_Period",
"True") for ("Is_New_Hire", "True") /
{avg_new_hires_headcount_rolling_3_months},
where
avg_new_hires_headcount_rolling_3_months
= (rollingSum(unique([Employee_ID]),
3) for ("Is_New_Hire", "True") for
("Active_Status", "True")/ 3)

Translation Based on a 12 month or 3 month rolling period.

Number of terminated new hires within period / New
hires average active headcount for period (Sum
of new hires active headcounts for each month /
Number of months in rolling period) * 100

Comparison Point Internal peer group

New Hires Retention Rate

What uses this metric? KPI: New Hires Retention Rate

Calculation Time Frame Depending on your data history:
• 12 month rolling period, or
• 3 month rolling period.

Calculation (previous(unique([Employee_ID]),
12) for ("Is_New_Hire", "True")
for ("Active_Status", "True") -
rollingSum(unique([Employee_ID]),
12) for ("Terminated_This_Period",
"True") for ("Is_New_Hire", "True") +
rollingSum(unique([Employee_ID]), 12)
for ("Hired_This_Period", "True")) /
(previous(unique([Employee_ID]),
12) for ("Is_New_Hire", "True")
for ("Active_Status", "True") +
rollingSum(unique([Employee_ID]), 12)
for ("Hired_This_Period", "True"))
OR

(previous(unique([Employee_ID]),
3) for ("Is_New_Hire", "True")
for ("Active_Status", "True") -
rollingSum(unique([Employee_ID]),
3) for ("Terminated_This_Period",
"True") for ("Is_New_Hire", "True") +
rollingSum(unique([Employee_ID]), 3)
for ("Hired_This_Period", "True")) /
(previous(unique([Employee_ID]),
3) for ("Is_New_Hire", "True")
for ("Active_Status", "True") +
rollingSum(unique([Employee_ID]), 3)
for ("Hired_This_Period", "True"))

Translation Based on a 12 month or 3 month rolling period.

(Active new hires at beginning of period + Hired
workers within period - Terminated new hires within
period) / (Active new hires at beginning of period +
Hired workers within period) * 100

Comparison Point Month prior to the current snapshot period

Offer Accepted Rate

What uses this metric? KPI: Offer Accepted Rate

Calculation Time Frame Current snapshot period
Calculation ( (candidates_offered) -
(candidates_offer_pending) -
(candidates_offer_declined) ) /
( (candidates_offered) -
(candidates_offer_pending) )
Variables for Calculation • candidates_offered =
unique([Candidate_JobRequisiton])
for ("Stage_Consolidated","offer")
• candidates_offer_pending =
unique([Candidate_JobRequisiton])
for
("Stage_Consolidated","offer") for
("Candidate_Stage_Instance_Evaluated","offer")
• candidates_offer_declined =
unique([Candidate_JobRequisiton])
for
("Stage_Consolidated","offer") for
("Candidate_Stage_Instance_Evaluated","decline
by candidate")
• Candidate_JobRequisiton =
CONCAT([Candidate_ID],"-",
[Job_Requisition])

Translation (Offers extended - Offers with decision pending

from candidate - Offers declined) / (Offers extended
- Offers with decision pending from candidate) *
100

Comparison Point Depending on your data history:

• 12 months ago, or
• 3 months ago.

Offer Decline Rate

What uses this metric? Gap Business Question: What areas do we need to
focus on to stay competitive with offers?
Calculation Time Frame Current snapshot period
Calculation (candidates_offer_declined) /
( (candidates_offered) -
(candidates_offer_pending) )
Variables for Calculation • candidates_offer_declined =
unique([Candidate_JobRequisiton])
for
("Stage_Consolidated","offer") for
("Candidate_Stage_Instance_Evaluated","decline
by candidate")
• candidates_offered =
unique([Candidate_JobRequisiton])
for ("Stage_Consolidated","offer")
• candidates_offer_pending =
unique([Candidate_JobRequisiton])
for
("Stage_Consolidated","offer") for
("Candidate_Stage_Instance_Evaluated","offer")
• Candidate_JobRequisiton =
CONCAT([Candidate_ID],"-",
[Job_Requisition])

Translation Offers declined / Offers extended (excluding

pending) * 100
Comparison Point Internal peer group

Promotion Rate

What uses this metric? KPI: Promotion Rate

Gap Business Question: Where are gaps in
promotions?

Calculation Time Frame Depending on your data history:

• 12 month rolling period, or
• 3 month rolling period.

Calculation rollingSum(unique([Employee_ID]), 12)

for ("Promoted_This_Period", "True")
for ("Active_Status", "True") /
{avg_active_headcount_rolling_12_months},
where
avg_active_headcount_rolling_12_months

= (rollingSum(unique([Employee_ID]),
12) for ("Active_Status", "True") /
12)
OR
rollingSum(unique([Employee_ID]), 3)
for ("Promoted_This_Period", "True")
for ("Active_Status", "True") /
{avg_active_headcount_rolling_3_months},
where
avg_active_headcount_rolling_3_months
= (rollingSum(unique([Employee_ID]),
3) for ("Active_Status", "True") / 3)

Translation Based on a 12 month or 3 month rolling period.

Number of promoted active workers within period /
Average active headcount for period (Sum of active
headcounts for each month / Number of months in
rolling period) * 100

Comparison Point for KPI Month prior to current snapshot period

Comparison Point for Gap Story Internal peer group
What uses this metric? Gap Business Question: Where are gaps in
promoting females?
Calculation Time Frame Depending on your data history:
• 12 month rolling period, or
• 3 month rolling period.

Calculation rollingSum(unique([Employee_ID]), 12)

for ("Promoted_This_Period", "True")
for ("Active_Status", "True") /
{avg_active_headcount_rolling_12_months},
where
avg_active_headcount_rolling_12_months
= (rollingSum(unique([Employee_ID]),
12) for ("Active_Status", "True") /
12)
OR
rollingSum(unique([Employee_ID]), 3)
for ("Promoted_This_Period", "True")
for ("Active_Status", "True") /
{avg_active_headcount_rolling_3_months},
where
avg_active_headcount_rolling_3_months
= (rollingSum(unique([Employee_ID]),
3) for ("Active_Status", "True") / 3)

Translation Based on a 12 month or 3 month rolling period.

Filtered on females.
Number of promoted active workers within period /
Average active headcount for period (Sum of active

headcounts for each month / Number of months in

rolling period) * 100

Comparison Point Internal peer group

Referral Hire Rate

What uses this metric? KPI: Referral Hire Rate

Calculation Time Frame Current snapshot period
Calculation (candidates_hired_referred) /
(candidates_hired)
Variables for Calculation • candidates_hired_referred
= {candidates_hired} for
("Source_Instance_Evaluated",
"referral")
• candidates_hired =
unique([Candidate_JobRequisiton])
for ("Stage_Consolidated","hire")
• Candidate_JobRequisiton =
CONCAT([Candidate_ID],"-",
[Job_Requisition])

Translation Number of referral hires in previous month /

Number of hires in previous month * 100
Comparison Point Depending on your data history:
• 12 months ago, or
• 3 months ago.

Retention Rate

What uses this metric? Gap Business Question: Where can we improve
female retention in the workforce?
Calculation Time Frame Depending on your data history:
• 12 month rolling period, or
• 3 month rolling period.

Calculation (previous(unique([Employee_ID]),
12) for ("Gender", "Female")
for ("Active_Status", "True") -
rollingSum(unique([Employee_ID]),
12) for ("Terminated_This_Period",
"True") for ("Gender", "Female") +
rollingSum(unique([Employee_ID]),
12) for ("Hired_This_Period",
"True") for ("Gender", "Female")) /
(previous(unique([Employee_ID]),
12) for ("Gender", "Female")
for ("Active_Status", "True") +
rollingSum(unique([Employee_ID]), 12)

for ("Hired_This_Period", "True") for

("Gender", "Female"))
OR
(previous(unique([Employee_ID]),
3) for ("Gender", "Female")
for ("Active_Status", "True") -
rollingSum(unique([Employee_ID]),
3) for ("Terminated_This_Period",
"True") for ("Gender", "Female") +
rollingSum(unique([Employee_ID]),
3) for ("Hired_This_Period",
"True") for ("Gender", "Female")) /
(previous(unique([Employee_ID]),
3) for ("Gender", "Female")
for ("Active_Status", "True") +
rollingSum(unique([Employee_ID]), 3)
for ("Hired_This_Period", "True") for
("Gender", "Female"))

Translation Based on a 12 month or 3 month rolling period.

Filtered on females.
(Active headcount at beginning of period + Hires
within period - Terminations within period) / (Active
headcount at beginning of period + Hires within
period) * 100

Comparison Point Internal peer group

What uses this metric? Gap Business Question: Where can we improve
retention?
Calculation Time Frame Depending on your data history:
• 12 month rolling period, or
• 3 month rolling period.

Calculation (previous(unique([Employee_ID]),
12) for ("Active_Status", "True") -
rollingSum(unique([Employee_ID]), 12)
for ("Terminated_This_Period", "True")
+ rollingSum(unique([Employee_ID]),
12) for ("Hired_This_Period",
"True")) /
(previous(unique([Employee_ID]),
12) for ("Active_Status", "True") +
rollingSum(unique([Employee_ID]), 12)
for ("Hired_This_Period", "True"))
OR
(previous(unique([Employee_ID]),
3) for ("Active_Status", "True") -
rollingSum(unique([Employee_ID]), 3)
for ("Terminated_This_Period", "True")
+ rollingSum(unique([Employee_ID]), 3)
for ("Hired_This_Period", "True")) /
(previous(unique([Employee_ID]),

3) for ("Active_Status", "True") +

rollingSum(unique([Employee_ID]), 3)
for ("Hired_This_Period", "True"))

Translation Based on a 12 month or 3 month rolling period.

(Active headcount at beginning of period + Hires
within period - Terminations within period) / (Active
headcount at beginning of period + Hires within
period) * 100

Comparison Point Internal peer group

Related Information
Reference
The Next Level: People Analytics: Resources to Help Validate Your Organization's Data

Reference: Visualizations by Topic Area

Use the configuration details in the tables to recreate People Analytics visualizations across topic areas.
You can then add additional fields and specifications to customize your analysis according to the needs of
your business.
• Diversity and Inclusion on page 632
• Organization Composition on page 634
• Retention and Attrition on page 638
• Hiring on page 641
• Talent and Performance on page 643
• Skills on page 644

Diversity and Inclusion

Visualization Time Frame Graph Type Fields Filters

Ethnicity Trend Rolling 12 months Type: Line Chart X-Axis: Month 'Active
Status' = 'is
Override Y-Axis
true'
Display Name:
Active Headcount 'Snapshot_Index'
= 'is
Color: Ethnicity
between',
value: [1, 13]

Gender by Tenure Current snapshot Type: Bar Chart X-Axis: Tenure 'Active
Category period Category Status' = 'is
Orientation:
true'
Vertical Override Y-Axis
Display Name: 'Snapshot_Index'
Grouping: Stack to
Active Headcount = 'is
100
between',
Color: Gender
value: [1, 1]

Gender Trend Rolling 12 months Type: Line Chart X-Axis: Month 'Active
Status' = 'is
Override Y-Axis
true'
Display Name:
Active Headcount

Visualization Time Frame Graph Type Fields Filters

Color: Gender 'Snapshot_Index'
= 'is
between',
value: [1, 13]

Generation Trend Rolling 12 months Type: Line Chart X-Axis: Month 'Active
Status' = 'is
Override Y-Axis
true'
Display Name:
Active Headcount 'Snapshot_Index'
= 'is
Color: Generation
between',
value: [1, 13]

Management Level Current snapshot Type: Bar Chart X-Axis: 'Active

by Gender period Management Level Status' = 'is
Orientation:
true'
Vertical X-Axis Sort Order:
Value Total - 'Snapshot_Index'
Grouping: Stack to
Descending = 'is
100
between',
Override Y-Axis
value: [1, 1]
Display Name:
Active Headcount
Color: Gender

Termination Count Rolling 12 months Type: Heatmap X-Axis: Month 'Terminated

by Ethnicity This Period' =
Y-Axis: Ethnicity
'is true'
'Snapshot_Index'
= 'is
between',
value: [1, 13]

Termination Count Rolling 12 months Type: Heatmap X-Axis: Month 'Terminated

by Generation This Period' =
Y-Axis: Generation
'is true'
'Snapshot_Index'
= 'is
between',
value: [1, 13]

Top 5 Termination Rolling 3 months. Type: Bar Chart X-Axis: Termination 'Terminated
Reasons by Reason This Period' =
This graph might Orientation:
Gender - Rolling 3 'is true'
adjust each Vertical X-Axis Sort Order:
Months
snapshot period Value Total - 'Snapshot_Index'
Grouping: Stack
due to the volume Descending = 'is
of terminations per between',
X-Axis Limit: 5
category. value: [1, 3]
groupings
Sum Remaining
Values for X-Axis:
False

Visualization Time Frame Graph Type Fields Filters

Override Y-Axis
Display Name:
Terminated
Headcount
Color: Gender
Color Sort Order:
Value Total -
Descending

Organization Composition

Visualization Time Frame Graph Type Fields Filters Notes

Average Current Type: Bar Chart X-Axis: Job 'Active
Compa-Ratio snapshot period Family Group Status' =
Orientation:
by Job Family 'is true'
Vertical X-Axis
Group
Sort Order: 'Snapshot_Index'
Grouping:
Value Total - = 'is
Cluster
Descending between',
value: [1,
Y-Axis:
1]
AVG(Compa-
Ratio)
Override Y-
Axis Display
Name: Average
Compa-Ratio

Average Current Type: Bar Chart X-Axis: 'Active

Compa-Ratio snapshot period Location Status' =
Orientation:
by Top 10 'is true'
Vertical X-Axis
Locations
Sort Order: 'Snapshot_Index'
Grouping:
Value Total - = 'is
Cluster
Descending between',
value: [1,
X-Axis Limit: 10
1]
groupings
Sum Remaining
Values for X-
Axis: False
Y-Axis:
AVG(Compa-
Ratio)
Override Y-
Axis Display
Name: Average
Compa-Ratio

Average Tenure Rolling 12 Type: Bar Chart X-Axis: 'Active

at Promotion by months Management Status' =
Orientation:
Management Level 'is true'
Vertical

Visualization Time Frame Graph Type Fields Filters Notes

Level - Rolling Grouping: X-Axis 'Promoted
12 Months Cluster Sort Order: this
Value Total - Period' =
Descending 'is true'
Y-Axis: 'Snapshot_Index'
AVG(Length = 'is
of Service In between',
Partial Years) value: [1,
12]
Override Y-Axis
Display Name:
Average Tenure
in Partial Years

Average Tenure Current Type: Bar Chart X-Axis: Job 'Active

by Job Family snapshot period Family Group Status' =
Orientation:
Group 'is true'
Vertical X-Axis
Sort Order: 'Snapshot_Index'
Grouping:
Value Total - = 'is
Cluster
Descending between',
value: [1,
Y-Axis:
1]
AVG(Length
of Service In
Partial Years)
Override Y-Axis
Display Name:
Average Tenure
in Partial Years

Average Tenure Current Type: Bar Chart X-Axis: 'Active

by Top 10 snapshot period Location Status' =
Orientation:
Locations 'is true'
Vertical X-Axis
Sort Order: 'Snapshot_Index'
Grouping:
Value Total - = 'is
Cluster
Descending between',
value: [1,
X-Axis Limit: 10
1]
groupings
Sum Remaining
Values for X-
Axis: False
Y-Axis:
AVG(Length
of Service In
Partial Years)
Override Y-Axis
Display Name:
Average Tenure
in Partial Years

Headcount Rolling 3 Type: Waterfall Measures: 'Headcount The headcount

Movement months Movement' movement

Visualization Time Frame Graph Type Fields Filters Notes

- Rolling 3 Orientation: • SUM(Active = 'is in graph starts
Months Vertical Beginning of list', with a
Quarter) value: beginning
• SUM(Hired [Headcount active
This Movement] headcount
Quarter) and after
• SUM(Terminated aggregates
This hires,
Quarter) terminations,
• SUM(Transfers and transfers
in This for the next 3
Quarter) months. The
last bar displays
• SUM(Transfers
the active
Out This
headcount
Quarter)
with those
Viz Options: changes at the
end of the 3
Show data
month period.
labels: True
Transfers
Hide total: include
False both true
transfers and
Override X-Axis
reorganizations.
Display Name:
""
Override Y-Axis
Displaye Name:
Worker Count
Override
Measure
Display Names:
• Active
Beginning of
Period
• Hired
• Terminated
• Transfers In
• Transfers
Out
• Active End
of Period

Managers Current Type: Bar Chart X-Axis: Job 'Active

vs Individual snapshot period Family Group Status' =
Orientation:
Contributors 'is true'
Vertical X-Axis
by Job Family
Sort Order: 'Snapshot_Index'
Group Grouping: Stack
Value Total - = 'is
to 100
Descending between',
value: [1,
Override Y-
1]
Axis Display

Visualization Time Frame Graph Type Fields Filters Notes

Name: Active
Headcount
Color: Manager
vs Individual
Contributor

Managers Current Type: Bar Chart X-Axis: Tenure 'Active

vs Individual snapshot period Category Status' =
Orientation:
Contributors 'is true'
Vertical Color: Manager
by Tenure
vs Individual 'Snapshot_Index'
Category Grouping: Stack
Contributor = 'is
to 100
between',
Override Y-
value: [1,
Axis Display
1]
Name: Active
Headcount

Monthly Active Rolling 12 Type: Line X-Axis: Month 'Active

Headcount months Chart Status' =
Override Y-
'is true'
Axis Display
Name: Active 'Snapshot_Index'
Headcount = 'is
between',
value: [1,
12]

Monthly Rolling 12 Type: Heatmap X-Axis: Month 'Active

Average months Status' =
Y-Axis:
Number of 'is true'
Organization
Directs by
Level 'Manager
Organization
With Direct
Level Y-Axis
Reports' =
Sort Order:
'is true'
Alphabetical -
Descending 'Snapshot_Index'
= 'is
Color:
between',
AVG(Direct
value: [1,
Reports)
13]
Override
Color Display
Name: Average
Number of
Directs

Organizational Current Type: Bar Chart X-Axis: 'Active Each layer

Depth in Layers snapshot period Organization Status' = represents an
Orientation:
Level 'is true' aggregated
Vertical
group of
Override Y- 'Snapshot_Index'
Grouping: employees
Axis Display = 'is
Cluster based on their
Name: Active between',
level in the
Headcount value: [1,
organization.
1]
This

Visualization Time Frame Graph Type Fields Filters Notes

visualization
helps you
understand the
shape of the
workforce and
gives a visual
representation
of where your
organization
might be top or
bottom heavy.
Organization Current Type: Heatmap X-Axis: 'Active This
Levels by snapshot period Organization Status' = visualization
Management Level 'is true' might reveal
Level whether
Y-Axis: 'Snapshot_Index'
employees
Management = 'is
at higher
Level between',
management
value: [1,
levels are far
1]
from the top
levels of the
organization.

Retention and Attrition

Visualization Time Frame Graph Type Fields Filters Notes

New Hire Rolling 3 Type: Bar Chart X-Axis: Job 'New Hire' New Hires are
Terminations months Family Group = 'is true' defined as
Orientation:
by Job Family workers with
Vertical X-Axis 'Snapshot_Index'
Group - Rolling less than 1 year
Sort Order: = 'is
3 Months Grouping: of tenure.
Value Total - between',
Cluster
Descending value: [1,
3]
Override Y-Axis
Display Name: 'Terminated
Terminated This
Headcount Period' =
'is true'

Termination Rolling 3 Type: Bar Chart X-Axis: Job 'Snapshot_Index'

Count by Job months Family Group = 'is
Orientation:
Family Group between',
Vertical X-Axis
- Rolling 3 value: [1,
Sort Order:
Months Grouping: Stack 3]
Value Total -
Descending 'Terminated
This
Override Y-Axis
Period' =
Display Name:
'is true'
Terminated
Headcount

Visualization Time Frame Graph Type Fields Filters Notes

Color:
Termination
Category
Color Sort
Order:
Value Total -
Descending

Termination Rolling 3 Type: Bar Chart X-Axis: 'Snapshot_Index'

Count by months Management = 'is
Orientation:
Management Level between',
Vertical
Level - Rolling 3 value: [1,
X-Axis
Months Grouping: 3]
Sort Order:
Cluster
Value Total - 'Terminated
Descending This
Period' =
Override Y-Axis
'is true'
Display Name:
Terminated
Headcount

Termination Rolling 3 Type: Bar Chart X-Axis: Tenure The tenure

'Snapshot_Index'
Count by months Category = 'is categories are
Orientation:
Tenure between', defined at the
Vertical Override Y-Axis
Category value: [1, tenant level.
Display Name:
- Rolling 3 Grouping: 3]
Terminated
Months Cluster
Headcount 'Terminated
This
Period' =
'is true'

Terminations by Rolling 3 Type: Bar Chart X-Axis: Compa- The Compa-

'Snapshot_Index'
Compa-Ratio months Ratio Range = 'is ratio ranges are
Orientation:
Range - Rolling between', defined at the
Vertical X-Axis
3 Months value: [1, tenant level.
Sort Order:
Grouping: Stack 3]
Alphabetical -
to 100
Descending 'Terminated
This
Override Y-Axis
Period' =
Display Name:
'is true'
Terminated
Headcount
Color:
Termination
Category
Color Sort
Order:
Alphabetical -
Descending

Top 10 Rolling 3 Type: Bar Chart X-Axis: 'New Hire' New Hires are
Locations months Location = 'is true' defined as
Orientation:
for New Hire workers with
Vertical

Visualization Time Frame Graph Type Fields Filters Notes

Terminations Grouping: X-Axis less than 1 year
'Snapshot_Index'
- Rolling 3 Cluster Sort Order: = 'is of tenure.
Months Value Total - between',
Descending value: [1,
3]
X-Axis Limit: 10
groupings 'Terminated
This
Override Y-Axis
Period' =
Display Name:
'is true'
Terminated
Headcount

Top 10 Rolling 3 Type: Bar Chart Y-Axis: Top 10

'Snapshot_Index'
Voluntary months Termination = 'is termination
Orientation:
Termination Reason between', reasons are
Horizontal
Reasons value: [1, subject to
Y-Axis
by Gender Grouping: Stack 3] change each
Sort Order:
- Rolling 3 month.
Value Total - 'Termination
Months
Descending Category'
= 'is in
Y-Axis Limit: 10
list',
groupings
value:
Sum Remaining [Voluntary]
Values for Y-
'Terminated
Axis: False
This
Color: Gender Period' =
'is true'
Override X-Axis
Display Name:
Terminated
Headcount

Voluntary Rolling 12 Type: Bar Chart X-Axis: Month 'Snapshot_Index'

Termination months. = 'is
Orientation: Override Y-Axis
Count by Month between',
Vertical Display Name:
value: [1,
Terminated
Grouping: 13]
Headcount
Cluster
'Termination
Category'
= 'is in
list',
value:
[Voluntary]
'Terminated
This
Period' =
'is true'

Hiring

Visualization Time Frame Graph Type Fields Filters Notes

Average Rolling 12 Type: Bar Chart X-Axis: 'Req_Management_Level_Job_Requisitio
Time to Fill by months Req_Management_Level_Job_Requisition
= 'is not
Orientation:
Management empty'
Vertical X-Axis
Level - Rolling
Sort Order: 'Last
12 Months Grouping:
Value Total - Requisition
Cluster
Descending Entry'
= 'is in
Override X-Axis
list',
Display Name:
value: [1]
Management
Level 'Last_Year'
Requisition = 'is in
list',
Y-Axis:
value: [1]
AVG(Time To
Fill) 'Requisition_Time_To_Fill'
= 'not
Override Y-Axis
equals',
Display Name:
value: [0]
Average Time
to Fill in Days

Hires per Month Rolling 12 Type: Bar Chart X-Axis: Month 'Last_Year' A hire is
months = 'is in recognized by
Orientation: Override Y-
list', the start date of
Vertical Axis Display
value: [1] the new hire.
Name: Number
Grouping:
of Hires 'Hired this
Cluster
Period'
= 'is in
list',
value:
[yes]

Job Application Rolling 12 Type: Bar Chart X-Axis: Job 'Last_Year'

Sources - months Application = 'is in
Orientation:
Rolling 12 Source list',
Vertical
Months value: [1]
X-Axis
Grouping:
Sort Order: 'Hired this
Cluster
Value Total - Period'
Descending = 'is in
list',
X-Axis Limit: 20
value:
groupings
[yes]
Override X-Axis
Display Name:
Source
Override Y-
Axis Display
Name: Number
of Hires

Visualization Time Frame Graph Type Fields Filters Notes

Number Current Type: Heatmap X-Axis: Job 'Candidate The data
of Open snapshot period Requisition Age Job source only
Requisitions by Category Requisition includes
Aging Status requisitions that
Y-Axis:
Instance have at least
Req_Management_Level_Job_Requisition
Evaluated' 1 candidate
Override Y-Axis = 'is in attached to the
Display Name: list', requisition. This
Management value: visualization
Level [open] helps you:
• Manage
'Req_Management_Level_Job_Requisitio
= 'is not requisitions
empty' that have
not been
'Last
filled for a
Requisition
long time.
Entry'
= 'is in • Understand
list', how many
value: [1] requisitions
are in the
'Job queue and
Requisition for how long.
Age
Category'
= 'is not
blank'

Requisitions Rolling 12 Type: Bar Chart X-Axis: Month 'Last_Year' The data
Opened each months = 'is in source only
Orientation: Override Y-
Month list', includes
Vertical Axis Display
value: [1] requisitions that
Name: Number
Grouping: have at least
of Requisitions 'Req_Opened_This_Month'
Cluster 1 candidate
= 'is in
attached to the
list',
requisition.
value: [1]

Top 10 Decline Rolling 12 Type: Bar Chart X-Axis: 'Candidate Top 10 decline
Reasons - months Disposition Stage reasons are
Orientation:
Rolling 12 Reason Instance subject to
Vertical
Months Evaluated' change each
X-Axis
Grouping: = 'is in snapshot
Sort Order:
Cluster list', period.
Value Total -
value:
Descending
[declined
X-Axis Limit: 10 by
groupings candidate,
rejected]
Override X-Axis
Display Name: 'Stage
Decline Reason Consolidated'
= 'is in
Override Y-
list',
Axis Display
value:
[offer]

Visualization Time Frame Graph Type Fields Filters Notes

Name: Number 'Last_Year'
of Candidates = 'is in
list',
value: [1]

Talent and Performance

Visualization Time Frame Graph Type Fields Filters Notes

Current Rating Current Type: Heatmap X-Axis: Job 'Active Performance
by Job Family snapshot period Family Group Status' = rating is defined
Group 'is true' at the tenant
Y-Axis: Current
level.
Rating 'Snapshot_Index'
= 'is
between',
value: [1,
1]

Current Rating Current Type: Heatmap X-Axis: 'Active

by Management snapshot period Management Status' =
Level Level 'is true'
Y-Axis: Current 'Snapshot_Index'
Rating = 'is
between',
value: [1,
1]

Current Rating Current Type: Bar Chart X-Axis: Current 'Active Performance
Overview snapshot period Rating Status' = rating is defined
Orientation:
'is true' at the tenant
Vertical Override Y-
level.
Axis Display 'Snapshot_Index'
Grouping:
Name: Active = 'is
Cluster
Headcount between',
value: [1,
1]

Termination Current Type: Bar Chart X-Axis: Current 'Terminated

Count by snapshot period Rating This
Orientation:
Current Rating Period' =
Vertical Override Y-Axis
'is true'
Display Name:
Grouping: Stack
Terminated 'Snapshot_Index'
Headcount = 'is
between',
Color:
value: [1,
Termination
1]
Category

Termination Rolling 12 Type: Bar Chart X-Axis: Month 'High High potentials
Type of High months Potential' are defined at
Orientation: Color:
Potentials by = 'is true' the tenant level.
Vertical Termination
Month
Category 'Snapshot_Index'
Grouping: Stack
= 'is
between',

Visualization Time Frame Graph Type Fields Filters Notes

Override Y-Axis value: [1,
Display Name: 12]
Terminated
'Terminated
Headcount
This
Period' =
'is true'

Top 5 Voluntary Rolling 12 Type: Bar Chart X-Axis: 'High The top 5
Termination months Termination Performer' reasons might
Orientation:
Reasons Reason = 'is true' change every
Vertical
for High snapshot
X-Axis 'Snapshot_Index'
Performers Grouping: period.
Sort Order: = 'is
- Rolling 12 Cluster
Value Total - between',
Months
Descending value: [1,
12]
X-Axis Limit: 5
groupings 'Terminated
This
Sum Remaining
Period' =
Values for X-
'is true'
Axis: False
'Termination
Override Y-Axis
Category'
Display Name:
= 'is in
Terminated
list',
Headcount
value:
[Voluntary]

Skills

Visualization Time Frame Graph Type Fields Filters

Match Score Signal Current snapshot Type: Bar Chart X-Axis: Job Family 'Active
by Top 10 Job period Group Status' = 'is
Orientation:
Family Groups true'
Vertical X-Axis Sort Order:
Alphabetical - 'Snapshot_Index'
Grouping: Stack to
Ascending = 'is
100
between',
Override Y-Axis
value: [1, 1]
Display Name:
Match Score Signal
Percentage
Color: Worker
Match Score Signal

Match Score Signal Current snapshot Type: Bar Chart X-Axis: Worker 'Active
Distribution period Match Score Signal Status' = 'is
Orientation:
true'
Vertical Override Y-Axis
Display Name: 'Snapshot_Index'
Grouping: Cluster
Active Headcount = 'is
between',
value: [1, 1]

Visualization Time Frame Graph Type Fields Filters

Top 10 Skill Current snapshot Type: Heatmap X-Axis: Skill 'Active
Categories by Job period Categories Status' = 'is
Family Group true'
X-Axis Sort Order:
Value Total - 'Snapshot_Index'
Descending = 'is
between',
X-Axis Limit: 10
value: [1, 1]
groupings
Color: Job Family
Group

Top 10 Skill Current snapshot Type: Heatmap X-Axis: Skill 'Active

Categories by period Categories Status' = 'is
Management Level true'
X-Axis Sort Order:
Value Total - 'Snapshot_Index'
Descending = 'is
between',
X-Axis Limit: 10
value: [1, 1]
groupings
Y-Axis:
Management Level

Related Information
Tasks
Steps: Create Visualizations on page 286
Reference
The Next Level: People Analytics: Resources to Help Validate Your Organization's Data

FAQ: People Analytics

• What is Storyteller?
• What is augmented analytics?
• What is a story?
• How are stories generated?
• How does Storyteller determine the most relevant information?
• What kinds of analysis do the stories use?
• How can we compare metric performance across dimensions in stories?
• Why do some top drivers contribute more than 100%?
• How do the stories change as time progresses?
• How does the scoring method for stories work?
• Why do some stories have only 2 top drivers and others 10?
• How does cardinality impact People Analytics?
• How can I view more information about a particular business question or metric?
• Why do some metric trends display in a neutral color?

What is Storyteller? Storyteller is an automated analytical engine that:

• Searches millions of combinations of data.
• Makes connections between the combinations of
data.

• Surfaces the most significant results in the form

of stories.

What is augmented analytics? Augmented analytics is an approach that uses

statistical techniques and advanced analytics to
automate findings in the data that aren’t easily
attainable by doing manual analytical work.
Storyteller brings the principles of augmented
analytics into practice.
What is a story? A story is a narrative summary of a finding in the
data that answers a business question. Example:
What are key turnover trends? Each story describes
an instance of significant under or overperformance
in a metric. To enable better decision making, a
story also provides the associated trend and a list of
the most important drivers contributing to the metric.
How are stories generated? Storyteller:
1. Groups the input data into different views by
aggregating metrics for each dimension and
different combinations of dimensions.
2. Filters out any views that have no data or are
statistically insignificant.
3. Makes connections between the views to create
a network that defines the relationships between
views. This network of relationships provides
context when evaluating 1 view compared to
another. Example: The view of Location =
Chicago has these relationships:
• The parent of Location = Chicago;
Cost Center = Sales.
• The child of the whole organization.
• The sibling of Location = New York.
• A proxy to Cost Center = Sales because
the entire Sales department is in Chicago
and 90% of the workforce in Chicago are
salespeople.
4. Analyzes the views in the network of
relationships to determine their significance.
5. Returns the most significant views in the form of
stories.

How does Storyteller determine the most Storyteller analyzes and evaluates the statistical
relevant information? significance of each view of the data. It clusters
views together based on several factors, including:
• Commonality of the underlying data.
• Hierarchical relationship.
• Similarity of problem.
It then ranks each view based on the greatest
impact to the related business question and
displays the most significant views as stories.
What kinds of analysis do the stories use? Each story is the result of either:

• Trend analysis: Storyteller compares the current

month metric performance in a dimension or
combination of dimensions to the historical
performance.
• Gap analysis: Storyteller compares the current
month metric performance for a dimension
or combination of dimensions to the internal
peer group average. Example: If the dimension
is supervisory organization, performance is
compared to Company or Level 1.
Depending on the story, the population might be:
• All active workers.
• All terminated workers.
• All active and terminated workers.
• A subset of those populations filtered by Level
1 in either the Primary Hierarchy or Secondary
Hierarchy.

How can we compare metric performance In order to normalize the metric performance of any
across dimensions in stories? organization or region and make them comparable,
Storyteller weights performance by the underlying
employee population. This helps reduce the outsize
impact of large percentage changes in a small
population.
To do this normalization, Storyteller:
• Calculates the average of the metric for the
combination of dimensions in the story.
• Calculates the average of the metric for the
relevant population. Example: Company or
subset containing peers.
• Calculates the difference or delta between these
2 averages.
• Weighs the delta by multiplying it by the size of
the population of the combination of dimensions.
Storyteller tells you how much the metric for that
combination of dimensions needs to change to be
consistent with the metric for the total population.

Why do some top drivers contribute more than When a top driver contributes more than 100% to
100%? the negative performance of a metric in a story,
other factors might have an opposite effect that
contributed positively to the performance.
Example: If a story displays a red negative number,
the top drivers for that story also display as red
negative numbers. Workday ranks the drivers by
their contribution to the underperformance of the
metric. On the Drivers tab of the View More dialog,
a corresponding green bar displays if there’s a red
bar that’s over 100%.

How do the stories change as time progresses? All stories are recalculated each time Storyteller
runs. After each snapshot update, there's a new
set of stories displayed on the dashboard based

on the current data. In all these cases, what drives

the display of stories is a statistical ranking of the
over or underperformance detected. In some cases,
changes to the configuration or the underlying
algorithms might also affect what stories are
displayed.
It's possible that a story in a given dimension, such
as Org, Mgt Level, or Region, appear again after
the monthly data refresh. The repetition implies
that the performance gap or trend identified in the
previous month remains statistically significant
and ranks among the top stories for the business
question in the current month. Users can still view
performance numbers that include the most recent
monthly update.

How does the scoring method for stories work? The scoring algorithm takes these factors into
account:
• Statistical significance of each story. Is the
detected change of the trend or deviation from
population average important enough?
• Value of a story. What is the calculated impact
on the business question?
• Relationship to the other stories. Is this story
a driver of another story, the effect of another
story, or part of other similar stories?

Why do some stories have only 2 top drivers Workday curates the list of dimensions for analysis
and others 10? depending on the business question to ensure that
Storyteller provides the most relevant analytical
slices. Within those dimensions, Storyteller displays
the top 10 drivers that significantly contribute to the
metric performance in a story.
How does cardinality impact People Analytics? Cardinality defines the size of the population in
the dimension, directly impacting what stories are
surfaced as well as story quality and actionability.
Smaller populations don’t provide interesting
and meaningful insights, which can result in
unnecessary iterations of the mapping process. A
high cardinality can result in long computation time
of the stories.
How can I view more information about a You can click the information icon next to
particular business question or metric? each business question or metric to view more
information, such as:
• Why a business question is important.
• The metric that drives the business question.
• The calculation behind a metric.

Why do some metric trends display in a neutral The expected result for select metrics can vary
color? across organizations, as some metrics don't follow
a universally accepted trend.
Example: To establish parity in gender equality,
an increase in female representation might be

the expected direction for organizations that have

a low percentage of females, while a decrease
might be the focus for organizations where female
representation is already at 70%.
To address differences in metric trends across
organizations, we set a target range for these
metrics:
• Average Span of Control for values between
5-15.
• Female Representation for values between
40-60%.
We display movement within these ranges in a
neutral color. Movement towards these ranges
displays in green, while movement away from these
ranges displays in red.
All changes for the metric Average Target
Compensation display in a neutral color, as
individual cases can determine whether an increase
or decrease is expected.

Related Information
Concepts
Concept: Storyteller Engine on page 609

Worksheets

Worksheets Setup

Set Up Worksheets

Prerequisites
• Steps: Set Up Security for Drive and give all Worksheets users access.
• Steps: Set Up Drive.
• Security: Security Configuration domain in the System functional area.

Context
When setting up Worksheets, give access to all users and groups that might use Worksheets in different
areas of Workday. Example: Workday Slides users use Worksheets to set up defined names and pivot
tables for use in Slides presentations.

Steps
1. Create security groups for Worksheets administrators and users.
Use these security group types:
• Public groups
• Role-based (constrained) groups
• Unconstrained groups
See Reference: Security Domains and Worksheets Actions on page 652.
2. Create or edit a security policy for these domains and add permissions:
• Worksheets
• Manage Bot and User Conversations
a) Access the View Domain report.
b) Select the domain from the Domain prompt.
c) From the related actions menu, select Domain > Create Security Policy, or select Edit Security
Policy Permissions if there's an existing policy.
d) As applicable, in Report/Task Permissions, add, or edit security groups.
e) Select the View and Modify check boxes.
Note: In the domain setup, you must select both View and Modify. You can't use these settings to
manage workbook access. You select view and edit permissions for individual workbooks when you
share them.
f) From the related action menu on the domain security policy, select Domain Security Policy >
Enable.
3. Activate Pending Security Policy Changes.
4. Sign out and sign back in to see your changes.
5. In Edit Tenant Setup - System > System Setup > File Type Setup Instructions, make sure that you
include the WXF file type and all other file types that you want to support in Worksheets, or select to
support all file types.
We recommend supporting these file types in addition to any other file types that you want to support
in your tenant:
• CSV
• HTML
• XLS
• XLSM
• XLSX
See Steps: Set Up Drive.
See Reference: Edit Tenant Setup - System.
6. (Optional) Access the Edit Tenant Setup - System task.
Configure settings for workbook downloading and commenting.
In the Drive Settings section, use the Disable Workbook Download check box to select whether to
prevent users from downloading workbooks out of Workday. Example: If selected, users can't download
workbooks to Excel, PDF, or CSV files. After you change this setting, you might experience a delay of
up to 65 minutes before the change takes effect in Drive.
In the Workday Conversation Settings section, use the Disable Comments for Worksheets check
box to select whether to prevent users from adding or viewing comments. If selected, the Comments
panel doesn't display in the web browser or in the mobile app for any workbook, regardless of the user's
permission settings for the workbook. Worksheets preserves existing comments and restores them

when you enable commenting again. The Can Comment permission level continues to display when
sharing files; if you disable commenting, the Can Comment permission level is the same as Can View.
After you change this setting, you might experience a delay of up to 5 minutes before the change takes
effect in Worksheets.
See Reference: Edit Tenant Setup - System.
7. (Optional) Configure system settings for Worksheets notification delivery.
Access the Edit Tenant Setup - Notifications task. In the Notification Delivery Settings > System
section, customize notification settings for Worksheets:
• Workbook Access Additions (not currently used).
• Workbook Access Removals (not currently used).
• Workbook Comments (not currently used).
• Workbook Conversations: Workday sends a notification, and also sends an email if enabled on the
tenant, to tagged (@mentioned) users in a workbook comment.
• Workbook Import Failures: Workday sends a notification, and also sends an email if enabled on the
tenant, when a file upload to Drive fails.
• Workbook Import Successes: Workday sends a notification, and also sends an email if enabled on
the tenant, when a file upload to Drive succeeds.
• Workbook Live Data Scheduled Updates: Workday sends a notification, and also sends an email if
enabled on the tenant, when you schedule a live data refresh.
• Workbook Notify If Function Notifications:Workday sends a notification, and also sends an email if
enabled on the tenant, when the results of a NOTIFYIF or NOTIFYIFS formula meet the criteria that
you defined.
• Workbook Tasks (not currently used).
See Reference: Edit Tenant Setup - Notifications.
8. If Worksheets hasn't been translated into the language that a user selected as their display language,
your security administrator must access the Edit Workday Account task for the user and select the
Allow Mixed-Language Transactions option. This makes the Worksheets user interface visible to the
user in English.
See Steps: Manage Translations.
Related Information
Concepts
Concept: Translations
Tasks
Steps: Set Up Drive
Reference
Workday 33 What's New Post: Worksheets
The Next Level: Worksheets Overview
The Next Level: Workday Features Leveraging Embedded Worksheets

Copy Live Data Workbooks Between Tenants

Prerequisites
• Security: Worksheets security domain in the System functional area.
• In the definition for the related report, select the Enable for Worksheets option (for all supported report
types) and the Enable as Web Service option (required only for advanced reports).

• If the workbook contains live data from a Workday report and you want to preserve the live data
connection to the report:
• Any report definitions in the source tenant must be identical to the destination tenant.
• All report column selections and prompt selections must be the same in the source and destination
tenants.
If you want to continue using the live data from a Workday report in the workbook, ensure that these items
are the same in the source and destination tenants:
• Report definitions.
• Report column selections.
• Prompt selections.

Context
You can copy (migrate) an existing workbook between tenants by downloading it from a source tenant and
uploading it to a destination tenant.
To avoid having to recreate the live data in the destination tenant, the instance IDs must be the same on
both tenants. Instances in Workday are like rows in a table or spreadsheet; each instance represents a
unique occurrence of a type of business object, such as a specific organization or worker. When you clone
a tenant to create a new one, the instance IDs are the same on both tenants.
Workday doesn't preserve the original workbook versions or comments.

Steps
1. In the source tenant, download the workbook as an Excel file.
2. In the destination tenant, access Drive.
3. Select Add New > Upload. Drive automatically converts the Excel file into a workbook.
4. Select Data > Refresh All Live Data.
5. If the instance IDs aren't identical between the source and destination tenants, you must remove the
Workday report data and manually recreate the live data links:
a) In the source workbook, take note of the report you used to generate the live data, and any selected
prompts. You might want to capture an image of the Live Data Details panel as a record of these
values.
b) In the destination workbook, clear the cells that contain Workday report data, and click Add Live
Data. Select options that match those of the source workbook.
6. Select Data > Protect Range to protect any ranges, sheets, rows, or columns that you protected in the
original workbook.
7. (Optional) Click Share to set sharing permissions to match those of the original workbook.
8. (Optional) Select Data > Schedule Live Data Refresh to periodically refresh the live data.

Reference: Security Domains and Worksheets Actions

This table describes the Worksheets security domains and the actions they manage.

Domain Notes

Worksheets Enables self-service users to:

• Use the Export to Worksheets icon on Workday reports.
• Create, upload, edit, share, and collaborate on workbooks. All users secured to
the Worksheets domain can create workbooks. When you share a workbook,
you can select only users with access to the Worksheets domain. Workday

Domain Notes
determines the user's access to specific data based on report data source and
report field security settings.
• Add data from workbooks into Slides presentations.

Manage Bot Enables administrators to:

and User
• Use the Get Conversation Data report to export a CSV file of comment data
Conversations
for all workbooks in the tenant. Users with access to this domain can view
all comments on all workbooks regardless of the permission setting on the
workbook.
• Edit or delete individual workbook comments from the comment actions prompt if
you have owner, comment, or edit access to the workbook.
• Purge (permanently delete) individual workbook comments from the comment
actions prompt if you have owner, comment, or edit access to the workbook.
• Purge (permanently delete) individual workbook comments using the Purge
Conversation Message Data report.
We recommend that you restrict access to a small subset of your administrators.

Download All Comment Data

Prerequisites
Security: Manage Bot and User Conversations domain in the System functional area.

Context
You can download a comma-separated values (CSV) file of comment data for all workbooks in the tenant.
Example: After a user leaves the company, use this report to confirm whether or not the user created
comments in workbooks that you need to delete.

Steps
1. Access the Get Conversation Data report.
2. Click the URL next to Download Link.
Workday generates the file and sends a notification. The link in the notification expires after 24 hours.
Workday includes this information in the file:

Column Description
conversationID An automatically generated sequential number for the conversation thread; a
comment and its replies have the same conversation ID.
chatMessageID An automatically generated unique sequential number for each comment or
reply.
createdByID The ID of the user who created the comment. Example:
USER:df1d7b0de01c4c81923b8d703a9ca69.
createdTime The date and time when the user created the comment. Example: Fri Jul 12 2019
20:11:46 GMT+0000 (Coordinated Universal Time).
modifiedByID The ID of the user who edited the comment. If no one edited the comment, the
createdByID displays here.

Column Description
modifiedTime The date and time when the user edited the comment. Example: Fri Jul 12 2019
20:11:46 GMT+0000 (Coordinated Universal Time).
deleted Displays a 1 if a user deleted or purged the comment; otherwise, displays zero.
text The text of the comment. Example: "Hello <@USER:dfed7b0dd703a9ca69>.
This cell is ready for review." Cell references in a comment don't display in the
comment text.

Edit, Delete, or Purge Workbook Comments by Other Users

Prerequisites
Security: Manage Bot and User Conversations domain in the System functional area.
You must be the workbook owner, or have edit or comment permission for the workbook.

Context
Administrators with sufficient domain access and permission levels can edit, delete, or purge (permanently
delete) individual workbook comments that any user created.
Example: You might want to edit, delete, or purge a comment if someone included sensitive data, or if
someone asked you to delete their personal information.
Deleting or purging a comment doesn't delete or purge any replies to that comment.
Purging a comment removes it from the Workday database.

Steps
1. In the workbook, open the Comments panel.
2. In the comment options menu for the associated comment (3 dots), click the desired action.
You can't undo your changes to a comment, or restore deleted or purged comments.

Next Steps
If you access the Get Conversation Data report to download workbook comment data, you see a value of
1 in the Deleted column for any deleted or purged comment, indicating that Workday deleted its text from
the user interface.
For deleted comments, Workday includes the comment text in the CSV file.
For purged comments, Workday doesn't include the comment text in the CSV file; purged content was
deleted from the database and no longer exists on the tenant.
When you permanently delete a workbook, Worksheets doesn't purge its associated comments. If you
want to purge the comments later, you can find them using the Get Conversation Data report, and then
purge them using the Purge Conversation Message Data report.

Concept: Managing Workbooks

Use these primary actions to manage workbooks. For more details, select Help > User Guide from any
workbook.

Action Description

Create an empty workbook From Drive, select Add New > Workbook.

Import (upload and convert) a file From Drive, select Add New > Upload.
to create a workbook
You can upload an Excel file or any file that uses:
• Comma-separated values (CSV).
• HTML format.
When you upload one of these file types, Worksheets automatically
converts it into a workbook.
Notes on uploading and converting:
• For Excel files, check the file size in addition to the number of cells
before uploading it. In some cases, an Excel file is apparently
small but the file size is disproportionately large. We call this Excel
file a bloated file. A bloated file might upload very slowly or it might
fail. You need to eliminate the cause of the oversized file. Here
are some common causes and tips:
• Formatting information. Unnecessary formatting is the most
common cause of a bloated file. Sometimes formatting rules
exist for a full sheet, or for all columns or rows in a sheet. The
formatting is invisible but it might dramatically increase the
file size. Spreadsheets that you originally created in Google
Sheets contain formatting information for all cells up to Z:1000
by default. To determine if formatting is an issue, you can
press Ctrl+End to locate the last used cell in a sheet. To
eliminate formatting, you can select each data range in the file
using Ctrl+Shift+{arrow keys}, then paste the content into a
new file.
• Hidden sheets. Unhide all the sheets, and remove any that are
unnecessary.
• Unused defined names or external references (links) to other
workbooks in a copied workbook. Excel can retain data
associated with defined names and external references even
after you break the link to the original workbook. Delete any
unused references.
• Other possible causes of bloat include sharing or revision
information, deleted complex macros, and more.
• For HTML files, Worksheets uses only the table data when
creating the workbook.
• Worksheets doesn't convert charts.
• Worksheets doesn't support Visual Basic macros. If a spreadsheet
contains macros, the conversion to a workbook might fail. Save
the Excel file without macros before uploading it into Worksheets.

Copy a workbook From Drive, select the workbook and click Make a Copy.
If the copied workbook is based on live data, you initially see the
same data as the workbook owner based on their permission level,
but as soon as you refresh live data in the workbook you see only the
data that you have access to. If you don't have access to one or more
data source fields, an error occurs when you refresh live data.

Action Description

Download workbooks From the workbook, select File > Download as and select the file
type to create.
Tenant settings determine whether mobile app users can download
workbooks.
Notes on downloading:
• When downloading to XLSX, there are 2 formatting options:
• Microsoft Excel: Use this format when you want to preserve
Worksheets-specific functionality in your workbook. Example:
You plan to upload the file into Worksheets again later, or
you are copying a workbook from one Workday instance to
another.
Formulas that use Worksheets-unique functions aren't
compatible with Excel. For Worksheets-unique scalar (non-
array) formulas, you see a #NAME error in other spreadsheet
products. For array formulas, Workday prepends the cell
content with identifying text in JSON format such as Workday
Unconstrained Array Ext2: or V2.Workbook.valueNumber:.
This identifying text is for internal use only; its format might
change in future releases, and using custom processes to
parse the text isn't supported.
• Microsoft Excel as Values: Use this format when you want to
work with or review the data but you don't need to preserve
formulas. The downloaded file contains only values, with no
formulas and no charts.
• When downloading to PDF, Worksheets might truncate the data
if the cells aren't wide or tall enough. Merge or expand cells
as needed before downloading to make sure all your data is
displayed in the cells.
• When downloading to a format other than XLSX, only the currently
selected sheet downloads; the automatically assigned filename is
workbookname_sheetname.filetype.
• Worksheets doesn't preserve workbook comments.
• Pivot tables that you create in a workbook don't display when
exported to Excel.
• You might need to enable pop-ups in your browser.
• For troubleshooting purposes, you can download a workbook in
raw WXF format to provide to Support. To do so, press Ctrl + Shift
+ Alt + W (Windows) or Command + Option + Shift + W (Mac).
This isn't a user-readable format. Worksheets doesn't support
using the WXF format to move workbooks between tenants
because results can be unpredictable.
• Because Excel doesn't support instance values or multi-instance
values, Worksheets downloads this type of cell content as a string
(text). If a cell contains a multi-instance value with many instances
in it, the content might be greater than Excel's 32,767 character
limit for cells. If this occurs, you see an #N/A error in the cell.

Remove (move to Trash) a From Drive, select the workbook and then click Remove. The
workbook workbook moves to the Trash view, but it isn't permanently deleted.

Action Description
Worksheets removes access for all users, and the workbook no
longer displays in Drive except for the owner's Trash view.
If an integrating application such as Projects or Payroll automatically
created a workbook, you can remove the workbook only if you disable
the entry area first. Some integrating applications refer to disabling
the entry area as locking.
If you remove a workbook that someone shared with you, you remove
yourself from the list of shared users. The workbook disappears from
Drive and it doesn't display in the Trash view.
After removing a workbook, you can restore it only if you are the
person who created it.

Restore workbooks from Trash From Drive, select Trash. Select the workbooks and then click
Restore.
You can restore a workbook only if you are the person who created it.

Permanently delete workbooks Drive administrators can permanently delete up to 1000 workbooks at
one time by accessing the Drive Permanent File Delete task.

Concept: Live Data in Workbooks

When you add report data to a workbook and you choose to keep the workbook in sync with the original
report data, that data is called live data. You can also add report data to a workbook without keeping the
data in sync; we refer to this data as static data.

Option Description
Live Data The inserted data in the workbook maintains a connection to the Workday report,
providing 1-way updates from the report to the workbook. (This setting doesn't enable
writing data from the workbook to the report.) You can't manually edit the inserted live
data in the workbook.

Static Values Inserted data in the workbook doesn't maintain a connection to the original report. The
data is a snapshot of the report data, as of the time you insert it. You can edit the inserted
data in the workbook. The maximum number of cells that Worksheets can insert as static
values is 5 million (5,000,000).

Live Data Tables and Structured References

Live data areas in Worksheets workbooks are similar to Excel tables. When Worksheets creates a live
data area, it assigns a table name to the area. Optionally you can rename the table. Using a special
syntax, you can create references to the data in a live data area using the table and column name; these
references are called structured references, and the range of cells is automatically updated whenever the
live data is refreshed. For more details about structured references, see Concept: Structured References in
Workbooks on page 659.

Formula Columns and Note Columns in Live Data

To work with formula columns:

• To add a new formula column without using the data wizard, right-click the header of any live data
column to add a new formula column to the right or left. Adding a formula column using this method
causes a live data refresh.
• To add a new formula column without using the data wizard, type the formula into the 2nd row of a
column adjacent to the live data area and press Ente. Worksheets automatically adds the formula into
the live data area and applies the formula to all rows in the live data area, without doing a live data
refresh. (Skip a column if you don't want to add the formula into the live data as a formula column.)
• Type a formula into the cell below the header and press Enter; Worksheets applies the formula to all
rows in the live data area.
• Double-click the column header cell to edit its name.
To work with note columns in the live data area:
• You must have already set up a key column (field) using the data wizard to see this option in the menu.
A key uniquely identifies the data in each row. The key column that you select must contain unique
values, such as Employee IDs. The value must not change over time, and the value must exist in only
one row of the data. Worksheets uses the key to match note rows to live data rows. Make sure your key
is unique; if it isn't, notes will be lost.
• Type notes as desired into the individual cells. To paste text into a cell, double-click in the cell first.
• Double-click the column header cell to edit its name.
• You can right-click the header of any live data column to add a new note column to the right or left.
Adding a note column using this method causes a live data refresh.
• Keep in mind that during a live data refresh, Worksheets doesn't preserve formatting for note columns.
• If rows are added during a live data refresh, Worksheets preserves the alignment of notes with their
corresponding rows. If rows are removed during a live data refresh – for example, you delete a prompt
– any notes related to the deleted prompt are removed but the data is saved in Workday. If you add the
prompt again later, Worksheets shows the notes again in their corresponding rows.
• If you type a note into the 2nd row of a column adjacent to the live data area and press Enter,
Worksheets automatically adds a note column into the live data area without doing a live data refresh.
(Skip a column if you don't want to add the column as a note column.)

Filtering
When you apply a filter, it's applied to that specific live data. The filter doesn't reapply after you refresh the
live data; you need to remove and re-apply the filter.

Sorting
You can sort live data areas and entry areas in a workbook. Optionally, your sort can include contiguous
columns in the workbook that are outside the live data area or entry area. By default, if your workbook
sheet contains live data and you select Advanced Sort on the Data menu, Worksheets selects only the
live data area for the sort. If you want to include additional columns in the sort, highlight the entire range
that you want to sort before selecting Advanced Sort.
When you refresh live data in a workbook, Worksheets preserves the sort order that you set in the Order
By option in the data wizard, but doesn't preserve standard sorting within the workbook (using Data >
Sort).

Formatting
In the Data Wizard Select Columns page, you can use the Column Options menu to set the data format
for your live data columns (if your live data is from an Advanced report). If you set the formatting here,
Worksheets preserves the data format when the live data is refreshed. Data formatting isn't available for
Note columns.
We recommend that you not change any font/style settings (such as bold text) in the workbook live data.
When you refresh the live data, Worksheets resets font/style formatting. If you want to change your live

data's appearance, you can use the ARRAYAREA function on a different sheet to insert the data from the
live data area, and format those rows and columns as desired.

Group Column Headings

If your original report definition contains Group Column Headings, those values become column headings
in your workbook. If you want to change the column headings later, you can do so using the SELECT
formula to copy the data into a different sheet and assign new column names.
Here's an example formula that copies data from Sheet1 into the current sheet and assigns the new
column names ID and Name:
=SELECT("SELECT `~Employee~ ID` `ID`, `Employee Name` `Name` from ? ",ARRAYAREA(Sheet1!A1))
Although this example is related to Group Column Headings, you can use it to change any live data column
headings.

Concept: Structured References in Workbooks

Live data areas in Worksheets workbooks are similar to Excel tables. When you add a live data area to a
workbook based on a Workday advanced report, Worksheets creates a table that contains the live data.
By default, Worksheets assigns a live data table name using the word Report and an incrementing digit.
Example: Report1.
Optionally, you can create your own name for the live data table, either at the time you run the data wizard
or later. Worksheets supports table names only for advanced reports. If you do rename the live data table,
remember that the table name must be unique in the workbook and also can't be the same as any defined
names or pivot table names.
After running the data wizard, you can use a special syntax incorporating the table name and column
name to specify dynamic references in formulas instead of using literal cell ranges. This combination of a
table and column name is a structured reference. Worksheets updates the range of a structured reference
automatically as needed when the live data is refreshed.
Example: Instead of the formula =SUM(B1:B24) you can use =SUM(SalesCategory[Sales Amount])
where SalesCategory is the table name and Sales Amount is the column name. The SalesCategory table
name isn't visible in the live data area but it displays in the live data details panel:

Keep these special considerations in mind:

• For live data areas that were created before Workday 23R1, you need to edit the live data area to add
a table name. You can do this from the Live Data panel by clicking Edit Live Data or by clicking any of
the Edit links in the panel.
• If you change a table name or column name later, Worksheets updates existing structured references
in the workbook; however, if you have an external reference that contains a table or column name,
Worksheets doesn't automatically update the consumer workbook. You need to update the reference
manually.
• Worksheets doesn't support:
• Using structured references (table and column names) to define conditional formatting rules. We
do support applying conditional formatting rules to data that was populated using a structured
reference.
• Uploading files to Worksheets that were originally created in Excel and that contain structured
references.

Structured Reference Syntax Guidelines

• Table names don't need to be inside quotes or square brackets.
• Column names don’t need to be inside quotes, but you do need to surround them with square brackets.
• Use the pound symbol (#) and indicators described below to refer to a special subset of a cell range.
• When including a formula column in a live data area, the formula doesn't need to include the table
name, but it does need to include the at symbol (@) preceding any column names.
• Remember to press the unconstrained array keyboard shortcut when submitting a formula: Ctrl+Alt
+Enter or Ctrl+Alt+Shift+Enter (Windows) or Command+Option+Enter (Mac).

Special Identifiers for Structured References

Specifier Example Refers To

#All [#All] The entire table, including column headers and data.

#Data [#Data] Only the data rows, no header.

#Headers [#Headers] Only the header row, no data.

#This Row Only the cells in the same row as the formula. You can't
combine these specifiers with any other item specifier.
or
This must be used in a live data formula column before
@
every header.
Example: =SUM([@Current Salary],[@Proposed Bonus])

Syntax Examples
Basic example:
=SUM(CompDetails[New Salary],CompDetails[Stock Amount])
Notes:
• The formula adds the values of the two columns together and displays the results in a new column. The
table name is CompDetails.
• The column names are New Salary and Stock Amount (enclosed in brackets).
For the table of examples below, we added live data to a workbook and named the table CompDetails.
Here's an image showing the column names.

Structured Reference Content Included Implied Cell

Range

CompDetails All data in the table, without column A2:G39

headers.
or
CompDetails[#Data]

Structured Reference Content Included Implied Cell

Range

=CompDetails[[#All],[Proposed Bonus %]] All cells in the Proposed Bonus % column F1:F39

=CompDetails[[#Headers],[Salary Increase The header of the Salary Increase % E1

%]] column

=CompDetails[[#All],[Compensation Grade]: All cells between the Compensation Grade B1:E39

[Salary Increase %]] and Salary Increase % columns, inclusive,
with headers

=CompDetails[[Compensation Grade]:[New The data between the Compensation B2:D39

Salary]] Grade and New Salary columns, inclusive,
no headers

=CompDetails[[#Headers],[Employee ID]: The headers of the columns between A1:D1

[New Salary]] Employee ID and New Salary

=CompDetails[[#Headers],[#Data], The header and data of the Compensation B1:B39

[Compensation Grade]] Grade column

=CompDetails[[#This Row], [New Salary]] The cell at the intersection of the current D5 (if the
row and the New Salary column current row is
or
5)
=CompDetails[@New Salary]

Comparing Structured References and Defined Names

Defined names are similar to structured references in some ways, but there are notable differences. This
table summarizes the key differences:

Defined Names Structured References

You can create defined names for any workbook Structured references refer only to data in a live
range. data area, for advanced report data only.
A defined name specifies a fixed range of cells A structured reference combines a table name and
across columns and rows, or you can use the column names to specify a dynamic range of cells
Formula field to define a name for a formula, in one or more live data columns.
constant, or non-contiguous set of cell ranges.
If the defined name is in a live data area, the range The data referred to by the reference is dynamic
of cells remains the same even if the data changes and is updated automatically after a live data
during a refresh. refresh.
A defined names panel ("right pane") shows all Structured references aren't standalone entities -
defined names so you can view and manage them. they're managed as part of the live data area - so
they don't need a separate panel.
You can use defined names in Slides Structured references aren't visible or usable in
presentations. Slides presentations.

If you use a defined name in a Slides presentation You can change a table name or column name. If
linked table and later you change its name or you do so, Worksheets updates existing structured
range, you need to refresh the linked data in the references in the workbook; however, if you have
presentation to see the updated data. an external reference (consumer workbook) that
contains the previous table or column name,

Defined Names Structured References

If you use a defined name value in a Slides Worksheets doesn't automatically update it. For
presentation linked value, and then you edit a more information about external references, see
defined name's range so that the linked value is Concept: Using External References to Refer to
no longer included, you need to remove and re-add Data in Other Workbooks on page 663.
the linked value.

Concept: Using External References to Refer to Data in Other Workbooks

In a workbook, you can refer to cells or ranges of data that exist in other workbooks. We call these
references external references or cross-workbook references. References to other sheets in the same
workbook have a similar syntax so we'll describe them in this topic also. You can make a standalone
reference (by using only an equals sign and the reference) or a reference can be an argument in a formula.
A workbook that refers to (brings in) data from another workbook is a consumer workbook. A workbook
containing data that's being referred to in another workbook is a producer workbook. A workbook can be
both a consumer and a producer.

Consumer workbooks display an external reference icon on the workbook toolbar. The icon turns green if
data in the producer workbook was changed after you opened the consumer workbook; click the icon to
update the data. This action is the same as Recalculate All. After the producer workbook's data changes
occur, there might be a delay of up to 2 minutes before the consumer workbook icon becomes green.
To add references to a producer workbook from a consumer, you must have Can Edit permission for the
consumer and Can View permission or higher for the producer workbook.
When someone creates or changes a formula with an external reference, Worksheets remembers which
user did it. When the formula runs, Worksheets verifies that that user has permission to access to the
externally referenced workbook.

Creating External References

From a producer workbook, you can copy a complete reference, then paste it into a consumer workbook:
1. Select the data that you want to reference, then right-click and select Copy as External Reference.
2. Open the consumer workbook, and in the cell where you want the reference, type an equals (=) sign
and paste the reference by pressing Ctrl + V (Windows) or Command + V (Mac).
Alternatively, you can obtain the producer workbook's Workday ID by navigating to File > Info, then add
the rest of the external reference manually in the consumer workbook.
From a consumer workbook, you can copy the Workday ID of a producer workbook, then add the
defined name, or sheet name and cell/range reference manually:
1. In the cell where you want to place the reference, select Data > Get External Reference. You see all
the workbooks that you have access to.
2. Navigate to the producer workbook and then click Copy Workday ID.
3. In the consumer workbook, type an equals (=) sign and paste the Workday ID by pressing Ctrl + V
(Windows) or Command + V (Mac). Then type the rest of the reference, which might be a defined
name, or it might be a sheet name and cell/range reference.

Syntax Guidelines
For external references:
• Enter the workbook's Workday ID inside square brackets, then the sheet name and cell or cell range, or
the defined name. Don't include folder/path information for the producer workbook.
For cross-sheet references or external references:
• Start with an equals sign (=) in the cell.
• If the sheet name has either of these properties, surround the name with single quotes ('):
• The sheet name doesn't start with a letter or an underscore.
• Any subsequent character in the sheet name isn't a letter, a digit, a period, or an underscore.
• Example cross-sheet references:
• =Sheet1!A1:A4
• ='All Employees'!A1:A4
• ='All Employees'!DataArea1, where DataArea1 is a defined name
This table shows some external reference examples. Workday IDs are shortened for readability.

=[9f9a1]January!A1 Gets data from the workbook with Workday ID

9f9a1, in the sheet January, cell A1.

=SUM([9f9a1]January!A1:B6) Shows the sum of cells in the workbook with

Workday ID 9f9a1, in the sheet January, range
A1:B6.

=[9f9a1]DataArea1 Gets data from the workbook with Workday ID

9f9a1, with the defined name DataArea1.

=SUM([9f9a1]Regions!A1:B6) Shows the sum of cells in the range A1:B6, in the

workbook with Workday ID 9f9a1, sheet Regions.

=SELECT("SELECT * Uses the SELECT function to get an array's data

FROM ?",ARRAYAREA([9f9a1]'Data Sheet'!A1)) from the workbook 9f9a1, sheet Data Sheet.

Considerations for External References

Keep these tips in mind when working with external references:
• If the data changes in a producer workbook:
• Worksheets automatically updates the consumer workbook references when you open it. The
update occurs regardless of the permission level of the user who opens the workbook.
• When you click the green External Reference icon to update the consumer, this action is the same
as Recalculate All.
• If you change the data placement in a producer, such as by deleting a sheet or inserting a column
into a range, Worksheets doesn't update the reference in the consumer workbook.
• Worksheets doesn't automatically update consumer workbooks that are in the trash or in manual
calculation mode (File > Settings > Manual).
• If you lose access to a producer workbook or a producer workbook is deleted, you see a #REF! error in
workbook cells that depend on data from external references.
• Worksheets reassigns broken external references in workbooks when the references become invalid
due to the authoring user's account being deactivated, or when the authoring user no longer has
permissions to the producer and consumer workbooks. Worksheets attempts to fix the external
references whenever a user who has edit or owner to the consumer workbook, and view access or

higher to the producer workbook, clicks the External Reference icon. If Worksheets can't update a
reference, a #REF error displays and you need to update the reference manually.
• If you have an external reference that contains a structured reference (live data table/column name),
and you change the table name or column name, Worksheets doesn't automatically update the
consumer workbook; you need to update the reference manually.
• Formatting in producer workbook references is applied in the consumer workbook, unless the consumer
workbook cells are already formatted. If you change the formatting in the referenced producer workbook
cells later, the new formatting isn't applied in the consumer workbook. (This same behavior occurs for
references in the same workbook.)
• If you hover over the Workday ID in an external reference in the formula bar, Worksheets shows the
name of the producer workbook.
• You can't add a reference to a producer workbook chart into a consumer workbook; an error occurs
when you place the reference in the consumer.
• If you're the workbook owner, you can prevent users with the Can Edit permission from changing
content in the producer workbook by using range protection. However, using range protection in a
consumer workbook doesn't prevent updates from propagating from the producer to the consumer.
• On a particular tenant, up to 10,000 consumer workbooks can refer to a single producer workbook. Up
to 25 producer workbooks can provide data to a single consumer workbook.
• The functions NOTIFYIF and NOTIFYIFS don't update automatically when producer workbook data
changes; you need to update references manually or set up a scheduled live data refresh. (The
workbook doesn't need to contain live data; the scheduled refresh performs a recalculate action, which
updates the consumer workbook data.)

Concept: Creating Reports to Insert into Workbooks

You can add data from one or more Workday reports into a workbook. Adhere to these requirements and
best practices for any reports that you want to add data from.
The Workday report must:
• Be an advanced, matrix, or composite report. Worksheets doesn't support inserting other report types,
such as Simple, Standard, or Xpresso.
• Be enabled for Worksheets. Select Enable for Worksheets in the Advanced tab of the custom report.
Enabling a report causes it to display in the list of available reports, when you start the Data Wizard in a
workbook.
• Be enabled as a web service (required only for advanced reports). Select Enable as Web Service in
the Advanced tab of the custom report.
• Include fields from the primary business object and any necessary related business objects. If you use
related business objects, your report must contain group column headings.
• Use these field types: Boolean, Date, Numeric (integers only), Text, Multi-Instance, or Single Instance.
Worksheets doesn't support other types (Currency, Date Time, DateTimeZone, Time).
• Not contain duplicate column labels (Column Heading Override) or XML aliases.
• Not contain fields that use the Do Not Prompt at Runtime prompt option.
For optimal performance as the report runs and Worksheets inserts the data into the workbook:
• Use indexed calculated fields whenever possible.

• Select report data sources (RDSs) that are efficient with data:
• Use indexed RDSs whenever they're available.
• Use RDSs that provide the smallest set of data that meets your needs. Example: To report on
compensation-related transactions, use employee compensation events instead of all business
process transactions.
• Use RDSs with the prompts you need built in. Example: To report on workers by organization, use
the Workers by Organization RDS instead of using the All Workers RDS and then using filters to
select organizations.
• Limit your use of calculated fields.
• Limit your use of filter conditions.
• When using more than 1 filter, first use the 1 that reduces the most instances.
Keep in mind that your report's efficiency affects how Worksheets performs when adding your report to
a workbook. To ensure that a report is efficient, you can test the report by creating multiple versions of
it using different RDSs and options and then comparing performance data using the View Report Log
report.

Considerations for Workday Reports and the Worksheets Data Wizard

Report Type Notes

Advanced Advanced reports that Workday runs for Worksheets have a timeout
value of 30 minutes. If the report times out before it can finish
calculating, then the Data Wizard can't insert the data into the
workbook, and you see an #ERROR indicator along with a message
that it wasn't possible to do a SELECT. If you see an error and you think
you might have an overly large report, we recommend that you use
the Limit number of rows inserted option in the Data Wizard to test
whether a report timeout issue exists. This limitation doesn't apply to
matrix or composite reports.

Matrix and Composite After you complete the Data Wizard, Worksheets runs the report in the
background before inserting the data into the workbook; this allows
you to continue working on other activities while the report runs. For
advanced reports, you need to wait while the report runs; a spinner icon
lets you know that it's being processed.

Composite By default the associated workbooks display only 1 level of the outline
hierarchy. To include all levels, in the report definition Advanced tab,
select the Enable Export Expansion Hierarchy to Excel option.

The Data Wizard doesn't support:

• Analytic indicators.
• Including Quicklinks in live data. Quicklinks from the report definition will display in the workbook but the
link isn't functional. To enable clicking in a workbook cell to open Quicklink URLs:
1. In the Workday report definition, for the Quicklink Assignment business object, include the fields
URL and Quicklink Item.
2. In the workbook live data, add a formula column and use the URL or HYPERLINK function to display
a clickable link. (To add a formula column, right-click in the header cell of a live data column and
select Insert Formula Column.)
Example: With the URL field in column A and Quicklink Item field in column B of your workbook live
data, adding the formula =URL(A2,B2) in cell C2 provides clickable links in that column.

Related Information
Reference
Reference: Report Types on page 19

Concept: Single- and Multi-Instance Field Values in Workbooks

This topic describes workbooks with multi-instance field values that were inserted after December 2019.
Refreshing live data in older workbooks doesn't add multiple instance values; only the first value would be
returned. To include values for multi-instance fields in your workbook, run the Data Wizard to insert the
report data into a new area of the workbook and select the Enable Multi-Instance Values option.
Multi-instance values display only for live data areas in workbooks - not for workbooks that are created
after you click the Export to Worksheets button from a Workday report.

Enabling Multi-Instance Field Values in the Data Wizard

In the Options dialog of the Data Wizard, the Enable Multi-Instance Values check box causes all
values of all multi-instance fields to be displayed in the resulting workbook. By default, the check box isn't
selected; this preserves backward compatibility with existing workbooks.

Visual Cues for Instance Field Values in Workbooks

To interact with the values, hover over a cell containing single-instance or multi-instance field values.

Instance Value Visual Cues Notes

When you insert instances as live data, you see these

characteristics:
1. Click the instance link to view its details, in the same
browser tab.
2. Click the icon to open the instance details in a new
browser tab.
3. The cell shows the values in a comma-separated list.
If you don't have access to an instance's details, you see
an error when you click the details link.

When you insert instances as values, you see the same

characteristics as above.
When you select a cell containing instance values,
they display in the formula bar as tags with an x icon,
enabling you to delete individual values from the cell if
needed. You can also delete all values from within the
cell using the Delete key.
If you want to type into one of these cells, first you must
remove all instance values; text and instance values
can't coexist in a cell.
Entry area instance values have the same appearance
and behavior as instances that Worksheets inserted as
values.

Workbook Actions and Instance Value Behaviors

Keep these behaviors in mind when your workbook contains instance values:

Action/Object Notes

References in formulas When comparing a single instance value to a string that visually
appears to be the same, the formula evaluates them as equal.

Using the formula editor The formula editor isn't available when working with multi-instance
field values in workbooks.

Filtering Each multi-instance value set displays as a selectable filter.

Sorting Worksheets sequences the sort based on the concatenated set of

values in the cell, as if it were a string.

Pivot tables Worksheets treats each unique set of instance values as a separate
value.

Charts Worksheets treats each unique set of instance values as a separate

value.

Links to documents such as If you click the link of an instance that has a document preview page,
PDFs from an instance but you don't have permission to view the preview, you see the error
message The task submitted is not authorized.
If you click the link of an instance that doesn't have a preview page,
you see the message No task runner for message.

Download to Excel as XLS, XLSX Worksheets converts multi-instance values into a string in the form
of JSON, maintaining the multi-instance values and types if you
reupload the workbook.

Download to CSV Instance values are in a comma-separated list.

Download to Excel as values Worksheets converts instance values to strings with a line break
between each value.

Action/Object Notes

Print or download as PDF Worksheets converts instance values to strings with a line break
between each value.

Example Comparisons of Single Instance, Multi-Instance, and String Values

This table shows when comparisons evaluate as the same or different, based on the type of data you're
comparing.

Comparison Result Example

Multi-instance values in a Not MULTIINST(INSTANCE("ID1","Denver"), INSTANCE("ID2",

different sequence equal "Chicago"))
Compared to:
MULTIINST(INSTANCE("ID2","Chicago"), INSTANCE("ID1",
"Denver"))

Multi-instance with 2 IDs and Not =MULTIINST(INSTANCE("ID1","Denver"), INSTANCE("ID2",

values, compared to string equal "Chicago"))
with values in a different
Compared to:
sequence.
The string "Chicago,Denver"

Multi-instance with 2 IDs and Not =MULTIINST(INSTANCE("ID1","Denver"), INSTANCE("ID2",

values, compared to a single equal "Chicago"))
instance with the value in a
Compared to:
different sequence.
The single instance ("ID1", "Chicago,Denver")

Multi-instance values with Equal =MULTIINST(INSTANCE("ID1","Chicago"))

different IDs but the same
Compared to
descriptors.
=MULTIINST(INSTANCE("ID2","Chicago"))

Multi-instance with a single Equal =MULTIINST(INSTANCE("ID1","Chicago"))

value, compared to an
Compared to:
equivalent string.
The string "Chicago"

Multi-instance with a single Equal =MULTIINST(INSTANCE("ID1","Chicago"))

value, compared to a single
Compared to:
instance value; IDs can
differ. The single instance ("ID4", "Chicago")

Multi-instance with 2 IDs Equal =MULTIINST(INSTANCE("ID1","Denver"), INSTANCE("ID2",

and values, compared to an "Chicago"))
equivalent string.
Compared to:
The string "Denver,Chicago"

Multi-instance with 2 IDs and Equal =MULTIINST(INSTANCE("ID1","Denver"), INSTANCE("ID2",

values, compared to a single "Chicago"))
Compared to:

Comparison Result Example

instance that has the same The single instance ("ID1", "Denver,Chicago")
descriptor.

Worksheets-Unique Formulas That Manipulate Instance Field Values

This table summarizes functions that enable you to work with single-instance and multi-instance values.
For details, see the Function Reference in the User Guide (Help > User Guide).

Function Description
INSTANCE Returns a single-instance value.
INSTANCE.DESCRIPTOR Returns the descriptor (string value) of the instance.
INSTANCE.ID Returns the ID of the instance.
MULTIINST Creates a multi-instance value from a comma-separated list of single-
instance values.
MI.COUNT Returns the number of instances inside a multi-instance value.
MI.INDEX Returns the instance at a specific index in a multi-instance value.

Concept: Array Formulas in Workbooks

An array is a set of data contained in more than 1 spreadsheet cell. An array visually looks like a simple
range of cells, but it's actually a special structure that you work with as a unit. From a Worksheets
perspective, live data areas and entry areas are examples of arrays. We use the term scalar to refer to a
single cell value or a formula that returns a result in a single cell.
An array can be one-dimensional, containing values in a single row or column; or two-dimensional,
containing a rectangular set of values in both columns and rows. You can see horizontal arrays
represented in text with braces around them and commas between the values, such as in the formula
={1,2,3,4}. Vertical arrays have semicolons between the values, such as ={5;6;7;8}. Two-dimensional
arrays have both, such as ={1,2,3;4,5,6}.
An array formula is a single formula that does calculations for the values in an array, and then returns an
array of results. Array formulas use the same syntax as regular formulas. You can:
• Submit a formula to output the results into an array. All the cells in the array are a single unit that you
work with as a single entity. This is a multicell array formula. In Worksheets, multicell array formulas are
either constrained or unconstrained.
• Submit a formula in a single cell to operate on an array, while containing the result in a single cell. This
is a single cell array formula. Single cell array formulas are less commonly used compared to multicell
array formulas.
You can use many common functions, such as SUM and COUNT, in an array formula. A few functions,
such as TRANSPOSE, are meaningful only when they operate on an array. The Function Reference
identifies functions that are intended for use as array functions.
Keep these considerations in mind when using array formulas:
• Array formulas perform better. It's faster to use a 10x100 multicell array formula instead of 1,000
separate formulas.
• Using a multicell array formula helps prevent you or other users from accidentally overwriting a cell
formula.
• You can't edit the data in an individual cell of an array. You might want to prevent users from making
changes here that would affect other parts of the workbook.

Constrained and Unconstrained Array Formulas

In a formula, if you specify the exact range of cells to put results in, you're using a constrained array
formula. Use a constrained array formula only if you know the specific range that should contain the result
set. If you add or remove data in the range, you must modify the array formula to account for it.
Worksheets offers a more flexible method of working with array data. If you're working with live data, such
as Workday report data or entry area data, the data array can change size whenever you refresh the live
data. The array formula needs to adapt to those changes. Worksheets handles variations in array size
using unconstrained array formulas. When you submit a formula without specifying the specific array
size for the output, allowing Worksheets to determine the array result set dynamically, you're using an
unconstrained array formula.
We use the term unconstrained in a few different contexts:
• We call a formula such as GROUPBY an unconstrained array formula because it's intended to have
variable output.
• A live data array such as a Workday report data set is an unconstrained array because the array size
can grow or shrink when the live data refreshes.
• A range reference such as B:B is an unconstrained column reference because you're not specifying
the number of cells containing data in the column.

Submitting Array Formulas

Submit array formulas from either of these locations:
• The formula bar.
• The cell containing the formula. Before submitting, double-click in the cell to make sure it is active.
Submit array formulas using these keyboard shortcuts:
• To submit an unconstrained array formula, press Ctrl+Alt+Enter (on Windows) or Command+Option
+Enter (on Mac). Results display in all required cells in the range. If there aren't enough empty cells
to display the complete results, an error occurs. Make sure that enough empty cells are available to
contain the result.
• To submit a constrained array formula, press Ctrl+Shift+Enter (on Windows) or Command+Shift+Enter
(on Mac). Results display only within the selected range. You see the same behavior in other common
spreadsheet products.

Example: Unconstrained Multicell Array Formula

This example describes how to calculate and display total sales for an item over several months. We'll
simulate a situation where the data in the workbook is live data from a Workday report, so Worksheets
might add or remove rows when we refresh the data. We'll submit our formulas as unconstrained formulas,
and Worksheets will automatically adjust the results as needed when the report data changes and
Worksheets runs the formula again.
Here's the data we'll work with:

A B C D
1 Month Price # Sold Total
2 Jan $5.00 25
3 Feb $2.00 4
4 Mar $1.00 15
5 Apr $3.00 8
6 May $4.00 10

Follow these steps:

1. Create a new workbook.
2. Create a new sheet called Data, and add the data from the table above. Set the format of columns B
and D to Currency by selecting the column header, then selecting Format > Number > Currency.
3. In Sheet1, in the formula bar, type this formula in cell A1, submitting it using the unconstrained
keyboard shortcut Ctrl+Alt+Enter (on Windows) or Command+Option+Enter (on Mac):
=Data!A:C
Submitting the formula using the unconstrained shortcut, and using unconstrained column reference
A:C instead of a cell range, enable the formula to adapt when we add or remove rows in the data later.
4. In Sheet1, in the formula bar, type this formula in cell D2, submitting it using the unconstrained
keyboard shortcut Ctrl+Alt+Enter (on Windows) or Command+Option+Enter (on Mac):
=REMOVEROWS(B:B*C:C)
The REMOVEROWS formula removes the header row from the calculation. B:B*C:C multiplies each
value in column B with each value in column C.
Column D shows the results. If you click any cell in the D2:D6 range, you see the same formula. You
can't edit individual cells in the range.

A B C D
1 Month Price # Sold Total
2 Jan $5.00 25 $125.00
3 Feb $2.00 4 $8.00
4 Mar $1.00 15 $15.00
5 Apr $3.00 8 $24.00
6 May $4.00 10 $40.00
5. In the Data sheet, add some data for June into Row 7, then view Sheet1 again. The new data and
sales totals display.

Concept: Editing Workbooks

These notes describe how to use workbook features in Worksheets that differ from other spreadsheet
applications. For more details, see the Worksheets User Guide, which you can access from the
Worksheets user interface (Help > User Guide).

Workbook Editing

Action Notes

Use full-screen mode In full-screen mode, Workday hides the header to display the maximum
possible number of workbook rows.
Select View > Full Screen.
Workday doesn't support full-screen mode in the Safari browser.

Add Workday report data We use the term live data for Workday data that you add to a workbook.
into a workbook
Select the cell where you want to insert the data and click Add Live Data.
The Data Wizard opens and helps you find the report and add the data. You
can select whether to add the data as:

Action Notes
• Live Data: Worksheets maintains a connection to the Workday report,
providing one-way updates from the report to the workbook.
• Static Values: Worksheets doesn't maintain a connection to the data in
the original report. The data is a snapshot of the report data, as of the time
you insert it. Worksheets can insert a maximum 5,000,000 cells as static
values.
You can add data from more than 1 Workday report into a single workbook.
We recommend using a new sheet for each set of live data.
Worksheets doesn't support using the Do Not Prompt at Runtime prompt
option in a report definition.

Refresh all live data in a You must have permission to edit the workbook and to refresh live data. When
workbook from 1 or more you do a refresh, Worksheets also recalculates formulas affected by changed
reports workbook data.
You can refresh all live data areas in the workbook and recalculate:
• Manually using Data > Refresh All Live Data.
• According to a schedule using Data > Schedule Live Data Refresh. Only
the workbook owner can do this action.
Note: When you recalculate and refresh the live data in a workbook,
Worksheets updates all data, including data in a protected range. You can't
prevent Worksheets from refreshing and recalculating workbook content.
Example: When you update an entry area in Workday Projects, or Workday
runs a scheduled live data refresh, Worksheets updates any necessary data
even if you protected the entry area or live data range.

Refresh live data in a In the workbook, select a cell that includes live data. In the Live Data Details
single range from the panel, click either:
associated Workday
• Refresh Now to immediately refresh the range.
report
• Edit to edit report prompt values if any exist in the live data, then click
Refresh Now to refresh the active live data range.

Edit workbook live data Click the Edit link in the Columns section of the live data details panel.
areas (add, remove, or Alternatively, you can click any of the Edit links in the panel, or the Edit Live
reorder report columns) Data button at the bottom of the panel.)
Live data column editing applies only to live data from advanced reports.
Worksheets doesn't update data references in formulas when you edit live
data columns; you need to manually update formulas that refer to any live data
area that you edit.

Schedule live data (Workbook owner only) In the workbook, select Data > Schedule Live Data
refreshes Refresh.
For workbooks already on a schedule, select Data > Edit Scheduled
Refresh. You can also select this option to edit or delete an existing schedule.
At the scheduled time, Workday automatically:
• Runs any associated Workday reports, acting as the workbook owner, and
refreshes the workbook based on changes in the original data.
• Recalculates formulas affected by changed workbook data.

Action Notes
For any prompts in the Data Wizard where you selected the Use Report
Default option, Worksheets uses the default values from the report definition
when refreshing the data; otherwise, Worksheets uses the current prompt
values displayed in the Live Data Details panel.
You can create 1 schedule per workbook.
When Worksheets runs a scheduled refresh, the updated data is available to
users with shared access to the workbook.
If workbook ownership changes, the schedule stops running; the new owner
must create a new schedule.
If the Workday report associated with the live data refresh times out 3 times
consecutively, Worksheets automatically cancels the refresh and pauses the
schedule. If Worksheets pauses a schedule, the workbook owner receives an
inbox notification that includes a link to the affected workbook. After you fix
the problem that caused the report failure, you need to manually resume the
schedule by clicking Resume in the live data panel in the workbook.
Worksheets doesn't preserve schedules when you refresh a tenant
from a tenant with a different name. You need to create new schedules
for the workbooks in the new tenant. Example: You refresh the
company_name_preview tenant from the company_name tenant.
If a worker sets up a scheduled live data refresh and then leaves the company
(and is in a terminated state), the scheduled refresh returns an error in the
workbook because Workday can't run the associated report.

Undo or redo your To undo a workbook change, select Edit > Undo.
changes
To redo a workbook change, select Edit > Redo.
Worksheets tracks your most recent 15 changes that you can undo.
When you select an action that you can't undo, Worksheets displays a
confirmation message. If you continue with the action, Worksheets resets the
record of your changes. You can't undo earlier changes, unless you previously
created a named version.
Keep in mind that when another person edits the workbook, they might
perform an action that resets change tracking and prevents you from undoing
a change.
We recommend creating a workbook version (File > Versions) before doing
any of these actions, which Worksheets can't undo:
• Delete or insert a sheet
• Change the format
• Recalculate or Recalculate All
• Refresh live data
You can't undo changes to workbook comments, and reverting to a previous
version doesn't restore comment changes.

Define or edit conditional Select the cell or range, then navigate to Format > Conditional Formatting.
formatting rules
To view the existing conditional formatting rules for a range of cells, select
the range and then select View > Panels > Conditional Formatting. To

Action Notes
display all conditional formatting rules for a sheet, select the top left cell in the
workbook data area.

Insert subtotals and a Worksheets can automatically insert subtotals for sets of related data in your
grand total workbook, and calculate a grand total.
Select the cell that you want to subtotal by, and then select Data > Subtotal.
You can't add subtotals in entry areas.

Group (outline) data Select the rows or columns that you want to group, right-click, and then select
Group. After grouping, you can select a group, right-click, and Ungroup a
single group, or select Ungroup All to remove associated groupings.

Define data validation You can define rules that determine what data can go into a set of cells in your
rules workbook. Example: You want to make sure that users select a geographic
region from a list of valid regions, which your workbook stores in another
column.
1. In the workbook, select the cell or range of cells where you want to add
the data validation, and select Data > Validation. The Data Validation
dialog displays and the selected cell or range displays in the Cell Range to
Validate field.
2. In the List of Values from Formula field, enter the formula that
Worksheets can use to determine the values to list in the data validation
cell or range. Alternatively, you can type a list of values surrounded by curly
braces and separated by commas. Example: {1,2,3}.

Rename or copy a To rename the sheet or to do other sheet actions, click the arrow on the
workbook sheet sheet tab. Sheet names can be up to 31 characters long. We recommend
using names of 27 characters or less. When you copy a sheet, Worksheets
uses 4 characters to add a space and a numerical increment in parentheses
to the sheet name. Example: When you copy the sheet named My Sheet,
Worksheets names the copy My Sheet (2).

Open instance details in When a workbook includes instance details, you can open the link to view
a new browser tab them. To open the instance page in a new browser tab, select the icon in the
instance link or use Ctrl+Click (Windows) or Command+Click (Mac).

Collaborate • Share a Workbook

Click Share to:
• Enable link sharing and get a URL so that you can share the workbook
with several users at once.
• Select specific users, or groups, to share the workbook with.
When a workbook owner shares with users or groups, optionally, they can
select whether or not to:
• Let editors share the workbook.
• Let commenters and viewers print, copy, or download the workbook.
The users that you share the workbook with can see any unhidden data in
the workbook.
• Manage Comments
Click the Comments icon to add comments.

Action Notes

Define a name Select the cell or range, right-click, and then select Define Name.
Defined names must be unique per workbook, and can be between 4 and 255
characters long.

Protect ranges (Workbook owners only)

To prevent other users from editing a cell or range, select it and then select
Data > Protect Range.
To protect a sheet, click the sheet menu (the down arrow on the sheet tab)
and then select Protect Sheet.
Note: When you recalculate or refresh the live data in a workbook,
Worksheets updates data even if that data is in a protected range.

Find content in a To find values in a workbook sheet, select Edit > Find or press Ctrl+F (on
workbook sheet Windows) or Cmd+F (on Mac) to open the Find in Sheet panel. You can
search for values, but not formulas.
When you search in a workbook, Worksheets displays results that contain the
characters you type, in the order you specify. The default search is a wild card
search, with an implied asterisk character (*) at the beginning and end of the
string you specify.
For advanced searches, start your query statement with the ^ character.

Break a line in a Double-click the cell in which you want to insert a line break. Click the location
workbook cell inside the selected cell where you want to break the line. Press Alt+Enter
(Windows) or Option+Enter (Mac). If you use the workbook formula editor, it
removes line breaks, so you need to add the breaks again.

Delete workbook sheets Click the sheet menu (the up arrow on the sheet tab) and then select Delete.
Worksheets can't undo deleting a sheet.

Create pivot tables Select the range to include in the pivot table and select Insert > Pivot Table.
Pivot tables containing live data rely on the report column names from the
Workday report. If you change a report column name in the report, and that
data is used as a field in a pivot table, you need to replace the pivot table field
associated with the original name with the field that's based on the new report
column name.

Refer to data in other To add external (cross-workbook) references, you must have edit permission
workbooks for the consumer and view permission or higher for the producer workbook.
A workbook that refers to (brings in) data from another workbook is a
consumer workbook. A workbook containing data that's being referred to
in another workbook is a producer workbook. A workbook can be both a
consumer and a producer.
From a producer workbook, you can copy a reference, then paste it into a
consumer workbook:
1. Select the data that you want to reference, then right-click and select Copy
As External Reference.
2. Open the consumer workbook, and in the cell where you want the
reference, type an equals (=) sign and paste the reference.

Action Notes
From a consumer workbook, you can copy the Workday ID of a producer
workbook, then add the defined name, or sheet name and cell/range reference
manually:
1. In the cell where you want to place the reference, select Data > Get
External Reference.
2. Navigate to the producer workbook and then click Copy Workday ID.
3. In the consumer workbook, type an equals (=) sign and paste the Workday
ID. Then type the rest of the reference, which might be a defined name, or
it might be a sheet name and cell/range reference.
Consumer workbooks display an external reference icon on the workbook
toolbar. The icon turns green if someone changed data in the producer
workbook after you opened the consumer workbook; click the icon to update
the data. The update that occurs as a result of the action is the same as
Recalculate All. After the producer workbook's data changes occur, there
might be a delay of up to 2 minutes before the consumer workbook icon
becomes green.

Merge 2 workbooks You can add the sheets from another workbook into the open workbook if
you're the owner or you have edit permission.
Open the workbook that you want to contain all the content from both
workbooks, then select File > Merge Workbook.
When merging workbooks, Worksheets doesn't:
• Save the original, nonmerged workbook before adding sheets from the
second workbook. To keep your original workbook, copy it before merging.
• Preserve protected ranges or data validations from the workbook that you
merge into the original workbook.
• If updatable data, such as from an entry area, exists in the workbook you're
selecting to merge content from, Worksheets copies the values from that
area but no longer considers the data updatable.

View quick statistics on a When you select a range of cells in a workbook, such as defined names,
selected range columns, or sheets, these formulas display to the right of the formula bar to
provide quick reference statistics about your selection:
• SUM
• AVERAGE
• MIN
• MAX
• COUNT
• COUNTA
Based on the types of data in the selected cells, Worksheets shows the
relevant functions in the drop-down list. For SUM, AVERAGE, MIN, and
MAX, Worksheets converts units in the same dimension (such as length) to
determine the result.
If all selected cells contain non-numeric data, then Worksheets displays only
the COUNTA statistic.

Create a workbook Workbook versions provide a checkpoint for a group of changes.

version
Select File > Versions, then type a version name in the Add Version to
Workbook dialog.

Action Notes
Workbook comments are independent of any versioning status: the user sees
in the Comments panel all comments entered for the workbook, regardless of
the version where the comment was added. Restoring to a previous version of
the workbook doesn't undo or change the Comments panel data.

Sorting, including Select the columns or rows to sort, then select Data > Sort and then select a
advanced sorting of live sort order or select Advanced Sort.
data and contiguous
You can sort live data areas and entry areas in a workbook. Optionally, your
columns
sort can include contiguous columns in the workbook that are outside the live
data area or entry area.
By default, if your workbook sheet contains live data and you select Advanced
Sort on the Data > Sort menu, Worksheets selects only the live data area
for the sort. If you want to include additional columns in the sort, highlight the
entire range that you want to sort before selecting Advanced Sort.
When you refresh live data in a workbook, Worksheets preserves the sort
order that you set in the Order By option in the data wizard, but doesn't
preserve standard sorting within the workbook (using Data > Sort).

Paste content into a You can use Ctrl+C and Ctrl+V to copy and paste content as values from 1
workbook Worksheets workbook to another, or from a desktop spreadsheet application
such as Excel.
You can't use the workbook menu option Edit > Paste Special to paste
desktop application content into a workbook; Paste Special works only
between workbooks that currently reside in Worksheets. Import (upload and
convert) the desktop spreadsheet into Worksheets by selecting Add New >
Upload before pasting data from it that includes formulas into a Worksheets
workbook.
You can copy and paste up to 9 MB of content from 1 workbook to another.

Freeze spreadsheet Locate the freeze handles in the top left corner of the sheet.
cells

Drag a handle to freeze columns or rows.

Alternatively, you can scroll until the desired column or row is in the first
viewable position in the workbook, then freeze at that position by selecting
View > Freeze Panes > Top Row. Worksheets freezes at the location of
the first visible row in the spreadsheet, which might not be row 1. Similarly,
selecting View > Freeze Panes > First Column freezes at the position of the
first visible column in the workbook.
To unfreeze all columns and rows, select View > Freeze Panes > Unfreeze
All.

Navigate within a range If you select a range of cells and then press Tab to move from cell to cell, the
of cells cursor stays inside the selected range.

Action Notes

Insert a chart Select the data to include in the chart, select Insert > Chart, then select a
destination cell for the chart. The chart starts at the selected cell and displays
in an area of merged cells that's approximately 10 rows in height and 4
columns in width.
If you include date information in the chart, make sure that you use standard
date/time formats; otherwise, Worksheets doesn't recognize the information as
dates.
Keep in mind that if you use a pivot table as the source data for a chart, and
later you change the rows, columns, or values to include in the pivot, you need
to make sure your chart still displays correctly.

Auto-fill a formula or These steps provide a keyboard alternative to using drag-fill:

value into all cells in a
1. In the cell you want to copy from, type the formula or value and then press
column
Ctrl+C (Windows) or Command+C (Mac).
2. To select all cells in the column, down to the bottom-most cell, press Ctrl
+Shift+Down Arrow (Windows) or Command+Shift+Down Arrow (Mac).
3. Press Ctrl+V (Windows) or Command+V (Mac).

Change the font Worksheets supports a variety of widely available fonts. The default workbook
font is Roboto. Worksheets doesn't support the Calibri font.

Rebuild a corrupted If a problem, such as a system error or an interrupted process, causes a

workbook workbook to be corrupted, you can return the workbook to a working state
using a keyboard shortcut:
• Ctrl+Alt+Shift+F9 (Windows)
• Command+Option+Shift+F9 (Mac)

Formulas

Task Notes
View reference Click the Function icon (fx) to open the Functions Library panel.
information for all
available formulas

Enter a formula Use one of these methods:

• Type the formula into the cell, starting with = (the equals character).
• Place the cursor in the formula bar and start typing the formula. When you
type a function name that Worksheets recognizes, a function description
displays. When you start typing parameters, syntax information displays.
• From the Functions Library panel, find the function you want, and then click
the + to the left.
• Click the Formula Editor icon to open the interactive formula editor,
and type your formula. The icon doesn't display when there's an active
connection to the Workday report, or when the active cell is in a pivot table.
Worksheets doesn't support using the formula editor for constrained array
formulas.
To treat the data in a cell as text instead of a formula, type a ' (single quote
character) before the = character. Worksheets treats everything after the '

Task Notes
as plain text. The ' character doesn't display in the cell, but it displays in the
formula bar.

Submit a formula from If you expect the formula to return a single value (it's a scalar formula), press
the formula bar or the Enter to run the formula.
cell containing the
If you expect the formula to return multiple values (it's an unconstrained array
formula
formula), use the Ctrl+Alt+Enter (Windows) or Command+Option+Enter (Mac)
keyboard shortcut.

Submit a formula from Click Save & Close.

the formula editor
When you open the formula editor for a formula, the editor detects if the
formula is a standard scalar (single value, nonarray) formula or unconstrained
array formula, and submits it appropriately. Worksheets doesn't support using
the formula editor for constrained array formulas.

Enter numbers into a You can enter numbers in several formats, such as:
formula
• A standard format such as 123, -4.5, 27.0001.
• Scientific format, such as 1E10, 12.4e-4, 8.2E+34.
• Accounting format for negative numbers, such as (12.45), (12E2).
• Formatted with thousands separators, such as 12,234.6789.
• Formatted as a percentage, such as 12.3%, -.23E3%.
• Formatted as a currency, such as $12.45, $50, $34.33, ($1,456.99), ($12).
• Dates and times.
The cell might not display the number exactly as you typed it, depending on
the current cell formatting rules and other factors, but Worksheets preserves
the value.
To make Worksheets handle the format of the cell as text, type a ' (single
quote character) before the = character; Worksheets treats everything after
the ' as plain text. The ' character doesn't display in the cell but it displays in
the formula bar. Example: You can enter dates and preserve the formatting
you typed, instead of displaying it in a format such as DD/MM/YYYY.

Circular References
In almost all cases, a circular reference indicates an error that you must correct.
We strongly recommend not enabling iterative calculations, particularly in workbooks that contain live data;
doing so obscures data errors that can lead to poor performance and unexpected behavior.
A red icon indicates that Worksheets didn't finish calculating; the workbook is in a state where some
formulas didn't fully run and are showing stale values. You can hover the cursor over the icon to see a
tooltip with information about the problem. There are two common causes for a workbook to prematurely
stop calculating: either the calculation limit was reached, or one or more circular references exist in the
workbook. If the problem is caused by a circular reference, you can click the red icon to navigate to the
cell location of the reference. If you have more than one circular reference, Worksheets navigates to the
location of the first one.
In rare situations, you might want to enable circular references. Example: You have a basic cost of
$1,000,000 for a project. A consultant earns a 5 percent fee based on the total project cost, which is
$1,000,000 plus the consultant fee. Because the fee is part of the calculation, it's a circular reference in the
spreadsheet, so you need to enable iterative calculation to occur.

A B C
Basic Cost $1,000,000.00
Consultant Fee =B3*C2 5%
Total Cost =SUM(B1:B2)

To enable the calculation of circular references in a workbook, select File > Settings, select Enable
Iterative Calculation, and add values for:
• Maximum iterations: 100 or fewer.
• Maximum change: Enter a maximum change value. The default is 0.001. Worksheets does the circular
calculation for the number of iterations that you specified, or until the result changes by less than this
value.
If you open a workbook containing circular references, and your recalculation setting is Manual, a
message displays; select Data > Recalculate All to update the data.
Related Information
Reference
2020R2 What's New Post: Worksheets External References

Concept: Automatic and Manual Calculation in Workbook Formulas

It's useful to understand the actions that cause Worksheets to calculate or recalculate the formulas in your
workbook.
Calculations depend on the formula type and the action you're doing. Recalculation time includes the time
spent running reports, executing formulas, and applying conditional formatting.
This table summarizes whether Worksheets recalculates workbook data or not:

Recalculation Formula/Workbook Event/Action Recalculate Formula?

Setting Type
Automatic Volatile Change any cell in workbook. Yes.

• INDIRECT
• NOW
• NOWTZ
• OFFSET
• RAND
• RANDBETWEEN
• TODAY

Automatic Non-Volatile Change any cell that this cell Yes.

depends on.
Automatic ARRAYAREA A formula uses ARRAYAREA Yes.
and the array referenced by
ARRAYAREA changes.
The root cell (top left cell)
of the array referenced by
ARRAYAREA changes.

Automatic RANDCONST No. This non-volatile function

is recalculated only when:

Recalculation Formula/Workbook Event/Action Recalculate Formula?

Setting Type
• A scheduled live data
refresh runs.
• You select Data >
Recalculate.
• You select Data >
Recalculate All.

Automatic SELECT (with live Manually refresh live data Yes.

data) range.
Live data refresh schedule
runs.

Automatic SELECT as a generic Change any cell that the It depends.

formula formula references.
If you use the parameter
section to reference data, the
formula runs when the data
changes. If you change data in
the SELECT statement portion,
the formula doesn't run again.

Automatic ONCE Surround any formula with the No.

ONCE function.
Automatic Copied workbook First time you open copied No. Select Data > Recalculate
workbook. All to update the workbook.
Automatic Converted Microsoft First time you open the No. Select Data > Recalculate
Excel file uploaded/converted workbook. All to update the workbook.
Manual Any Any. No. Worksheets never
recalculates formulas unless
you manually initiate a
recalculation. This is applicable
for all formulas, including
volatile formulas. (New
formulas are calculated when
you first submit them but
they're not recalculated.)

The default recalculation setting in workbooks is Automatic.

You might want to prevent automatic recalculation in some situations. Example: If you're making many
changes to a workbook with complex formulas, you might want to wait until you finish all your changes
before recalculating the formulas.
To specify a calculation option, select File > Settings.
To manually recalculate formulas, use one of these actions:
• Data > Recalculate calculates any formulas in the workbook where the data has changed.
• Data > Recalculate All calculates all formulas in the workbook, whether or not the data has changed
since the last calculation. Recalculate All also updates external references in consumer workbooks
Notes:

• When you do an action that doesn't cause a recalculation, such as uploading a Microsoft Excel file
to Worksheets and opening the converted workbook the first time, select Data > Recalculate All to
update the workbook.
• Live data in a workbook isn't affected when you use the recalculation settings or actions. You can
refresh live data manually by selecting Data > Refresh All Live Data, by selecting Refresh Now in
the Live Data Details panel, or by setting up a scheduled refresh using Data > Schedule Live Data
Refresh.

Concept: Data Analysis with Worksheets Functions

Data analysis is an iterative process of collecting, cleaning, and shaping your data, followed by aggregation
and analysis. Worksheets helps to make your workflow more efficient by enabling you to work with live
Workday data, and to use Worksheets-unique functions that improve the analysis workflow.
As you do each of these steps, remember to keep your original data as a backup by creating new
workbooks for the manipulated data.

Collect
Compile your data, gathering it from resources both outside and within Workday. Make sure that your raw
data is complete. Here's a summary of actions that you might do during data collection:
• Select Add New > Upload from Drive to create workbooks from data that exists outside Workday.
• Select Data > Add Live Data to add live data from Workday reports into a workbook. The Data Wizard
helps you identify the subset of data that you want to insert to the workbook.
• Keep your data current by creating a schedule to refresh the live data.
• Use the ARRAYAREA function to copy data from one unconstrained array to another, creating an
organized set of raw data to manipulate in the Clean step. ARRAYAREA returns the containing range
of the array formula, based on the cell address you specify. The array can originate either in a Workday
report or an array formula.

Clean
Reduce your data to only the information you need by removing duplication, trimming empty workbook
values, and more.
Keep these Worksheets-unique functions in mind:

Function Notes

DISTINCTROWS Combines a set of ranges into a single range while removing any rows that are
duplicates. DISTINCTROWS evaluates text and instance values as not distinct from
each other. When the supplied range contains both an instance value and a text
string that are the same, the function returns 1 row, the instance value.

REMOVECOLUMNS Removes one or more columns from the referenced area. The function removes the
number_of_columns, starting at and including start_column.

REMOVEROWS Removes one or more rows from the referenced area. The function removes the
number_of_rows following start_row, starting at and including start_row. Use
REMOVEROWS without specifying any rows in order to remove the first (heading)
row.

TRIMCOLUMNS Removes trailing blank columns and rows from a range, when the data is a result of
an unconstrained array formula.
TRIMROWS

Function Notes

TRUNCATEMATRIX Removes rows, columns, or both, from a matrix.

UNIQUE Returns a matrix whose rows are unique according to the specified keys. The
function returns only unique rows, based on the values in the specified columns.
This function is similar to DISTINCTROWS(), but UNIQUE() takes a single range
and a set of columns.

Shape
Arrange, convert, and organize your data to create consistency:
• Standardize your columns and create new ones if needed.
• Give each column a unique and descriptive header.
• Format each column consistently.
• Double-check for duplicate or missing rows.
• Make sure the wording and formatting for text data is consistent.
• Make sure that no cells are blank.
• Convert data values to the same unit where needed.
When shaping data, there are 2 main types of data manipulation:
• Value-specific: The action you want to take depends on the value in the cell.
• Data arrangement: The manipulation is value-agnostic and you're moving cells, columns, and rows to
different locations.
For value-specific manipulation, these Worksheets-unique functions can be helpful:

Function Notes

CONVERT Converts a number from 1 unit of measurement to another.

DATESBETWEENReturns an array of dates that starts and ends on a particular date, with a step interval
between each date.

DATESFROM Returns an array of dates that starts on a particular date and continues for the number
of dates you specify, with a step interval between each date.

IN Determines whether a value or list of values that you specify is in another list of values.
If so, returns True; otherwise, returns False.

MATCHCOMPOSITE
A common use case for MATCHCOMPOSITE is to consolidate column data from 2
sheets into 1, where you have data on a sheet, along with notes about that same data
in a column on a different sheet. MATCHCOMPOSITE copies values in one or more
columns from the location to the right of a source array, and returns values to the right
of a destination array. You use a composite key of columns to match copied data to the
correct rows in the destination.

MATCHEXACT Looks up an exact match for the value in the sorted list (one-dimensional array) you
specify, and returns the position of the value. You can use this function to match
logical values, numeric values, or text strings. This function is similar to MATCH, but
MATCHEXACT:
• Always searches for an exact match; it returns an #N/A error if it doesn't find the
value.
• Doesn't allow wildcard characters such as * or ?.

Function Notes
• Uses a binary search for better performance.

MHLOOKUP We recommend this function as a replacement for HLOOKUP. MHLOOKUP performs

a horizontal (row) lookup on a table and returns all matches. MHLOOKUP is similar to
HLOOKUP, but:
• HLOOKUP scans only the top row for matches; in MHLOOKUP you specify the row
to search.
• HLOOKUP stops after finding 1 match, and returns a single cell value; MHLOOKUP
scans the entire lookup row for matches. Each match in that row returns a new row
in the output. If you specify 4 return_row_index values, then each resulting row will
have 4 columns.

MVLOOKUP We recommend this function as a replacement for VLOOKUP, especially when you're
working with live data. MVLOOKUP performs a vertical (column) lookup on a table and
returns all matches. MVLOOKUP is similar to VLOOKUP, but:
• VLOOKUP scans only the left column for matches; in MVLOOKUP you specify the
column to search.
• VLOOKUP stops after finding 1 match, and returns a single cell value; MVLOOKUP
scans the entire lookup column for matches. Each match in that column returns
a new row in the output. If you specify 4 return_column_index values, then each
resulting row will have 4 columns.

REGEXFIND Returns the position of the first character of a substring that matches the regular
expression pattern. The position value is zero-based.

REGEXPARSE Extracts parts of a string by matching to a pattern.

SETUNITS Converts a number from its current unit of measurement to another. This function is
similar to CONVERT(), but in CONVERT() you must specify both the original and the
new unit values.

SELECT Valuable for value-based manipulation as well as data arrangement. The SELECT
function is similar to an SQL SELECT statement. The basic format is: SELECT
column1, [column2], ... FROM table where column is the data to return and table is the
data source to select from. In the FROM clause you can specify, for example:
• Defined name.
• Column, row, or area range.
• Parameter that you specify as an argument.

For data arrangement, these Worksheets-unique functions can be helpful:

Function Notes

WD.ARRANGECOLUMNS
Creates a new range from an existing range, with the columns or rows ordered
according to the specified indexes. Example: With WD.ARRANGECOLUMNS
WD.ARRANGEROWS
you can add an empty column by including a null index value. Example:
=WD.ARRANGECOLUMNS([range],1,2,3,,4) inserts a blank column between the 3rd
index value and the 4th index value.

CORRELATE Creates a new matrix by combining rows from the ranges you specify. This function is
similar to a database join.

Function Notes

FLATTEN Returns an expanded range of data based on the hierarchical data that you specify.
Typically you use this function to expand an organization's manager and employee
information so that it displays all levels of the hierarchy.

JOIN Performs an inner left join on 2 ranges.

MERGECOLUMNS
Merges columns by placing them side by side into a new range.

MERGEROWS Merges rows by placing them 1 below the other into a new range.

MINUS Returns all rows from a first range that don't appear in any of the other supplied ranges.

SORT Sorts an existing matrix and returns a new matrix. SORT accepts 1 sort direction
and sorts all columns you specified based on that direction. SORT2 accepts pairs
SORT2
of parameters for a column reference and the sort direction for that column. SORT3
SORT3 assumes that the first row of the array to be sorted is a header and returns that row at
the top of the results.

VALUEAT Returns the value at the intersection of a column header and row label.

Analyze
Now you're ready to aggregate and analyze the data you've prepared.
The most commonly used analysis tool is the pivot table, which enables you to summarize and analyze
large amounts of data. The Pivot Table Wizard and details panel enable you to create and edit pivot tables
interactively. You can also create charts to visually demonstrate data relationships.
Keep these Worksheets-unique data analysis functions in mind:

Function Notes

CAPPEDVALUES Typically used for 401(k) deductions, ESPP deductions, or tax payments that have
a regular value per period, but drop to zero (0) when the payment reaches the cap.
Returns an array of values over a set of periods from an array of values that you
provide, over the same periods, limited by a provided cap over the whole duration.

FORECAST.WD.SEASONAL
Returns a predicted sequence of values using patterns in the historical linear and
nonlinear data that you specify.

GROUPBY GROUPBY is a powerful function that can often replace COUNTIF(S),

AVERAGEIF(S), and SUMIF(S). GROUPBY aggregates data, and orders the
results based on the order that you specify. The grouping is based on a key that
you can predefine in the table, or you can define it using columns in the workbook.

Function Notes
The result looks similar to a sorted pivot table. This function is often useful as part of
headcount planning.

SELECT The SELECT function is similar to an SQL SELECT statement. The basic format
is: SELECT column1, [column2], ... FROM table where column is the data to return
and table is the data source to select from. In the FROM clause you can specify, for
example:
• Defined name.
• Column, row, or area range.
• Parameter that you specify as an argument.

Other Notable Worksheets-Unique Functions

These functions aren't specific to data analysis but are very useful in all steps:

Function Notes

NOTIFYIF Sends notifications if a condition is met. You can send a notification to a user whether
or not they have access to the workbook.
NOTIFYIFS

ONCE Calculates a formula exactly 1 time. Worksheets never re-evaluates the formula even
if you request re-calculation using Data > Recalculate; however, you can manually
resubmit the formula. Example: Use this function when the volatile function NOW()
places a timestamp in a workbook, and this timestamp must never change.

Reference: Workbook Limits

This table summarizes the primary limits on workbook sizes and data points:

Limit Type Notes

Workbook overall size 20 million cells.

Whenever you modify a workbook that exceeds the limit, a warning
displays. It's very important that you take action to reduce the
workbook size. Overly large workbooks don't perform well and
eventually will fail to open or save.
Here are some actions that you can do if your workbook is
approaching the limit:
• Reduce the number of cells in the workbook that have any data
associated with them, such as formulas, values, or formatting. For
most cells, the best way to fully clear them is to select the range of
cells and select Edit > Clear > All.
• For cells in live data, try reducing the number of columns or rows.
Consider creating more concise reports to limit the number of rows
returned.
• For cells in pivot areas, try adjusting the pivot configuration to
reduce the overall number of rows and columns produced.
• Split large workbooks into two or more smaller workbooks.

Limit Type Notes

Uploads of spreadsheet files 20 million cells.

(XLSX, XLS, CSV, TSV, JWF,
Worksheets also follows the Workday overall file upload limit of 30
HTML)
MB.

Downloads of workbooks 20 million cells.

Report data in a workbook as live 20 million cells.

data
This limit is based on the amount of data being placed into workbook
cells. The report can have more than 20 million cells of data; your live
data prompt selections and other filters should result in a workbook
size that is below the limit.

Report data in a workbook as 5 million cells.

static values

Pivot table results 1,000,000

Data points in a chart 100,000

Sheets in a workbook 256

Columns in a workbook 16,384

Rows in a workbook 1,048,576

Characters in a single cell The limit is generally considered to be 32,767 characters per cell, but
it is usually lower in practice. Internally, characters are measured in
bytes; each character can require from 1 to 3 bytes. For example,
most English characters are 1 byte each, but double-width characters
can require up to 3 bytes.

Content copied from workbook to 5 million cells or 9 MB, whichever is less.

workbook

Report run time Advanced reports time out after 30 minutes. Matrix and composite
reports don't have this limit because they run as a background
process.

Reference: Workbook Actions Available Based on Permissions

This table summarizes the actions available for workbooks based on the user's workbook permission level.
You specify permission levels when you share a workbook.

Action Can Can Can Owner Notes

View Comment Edit
View workbook X X X X
View workbook information X X X X
Copy workbook X X X X Applies for the Can View and
Can Comment permissions

Action Can Can Can Owner Notes

View Comment Edit
only if the workbook owner
selected the Commenters
and viewers can copy,
download, and print option
when sharing the workbook.

Download workbook (if X X X X Applies for the Can View and

enabled in tenant settings) Can Comment permissions
only if the workbook owner
selected the Commenters
and viewers can copy,
download, and print option
when sharing the workbook.

Print workbook (if enabled in X X X X Applies for the Can View and
tenant settings) Can Comment permissions
only if the workbook owner
selected the Commenters
and viewers can copy,
download, and print option
when sharing the workbook.

View pivot table details X X X X You can access the details for
a single pivot table value from
the context (right-click) menu.
Select Show Details. The
Create Sheet button displays
in the details dialog only if you
have edit permission.
View workbook user presence X X X X
View and add comments X X X
View list of users that the X X X
workbook is shared with
Remove (self) from shared X X X
workbook access
Add/edit external references X X Applies for the Can Edit
permission only if the
workbook owner selected the
Editors can share option for
the workbook when sharing it.

Define names for workbook X X

cells or ranges
Share workbook or change X X Applies for the Can Edit
share permissions permission only if the
workbook owner selected the
Editors can share option for
the workbook when sharing it.

Action Can Can Can Owner Notes

View Comment Edit
Edit content including X X
reverting changes
Filter or sort workbook content X X
Merge workbooks X X
Recalculate data X X
Rename workbook X X
Refresh live data X X Applies for the Can Edit
permission only if the
workbook owner didn't
select the Only owner can
refresh live data option in
File > Settings. Note that
during a live data refresh, the
workbook isn't available to
you or anyone you shared
with workbook with.

Define data validation rules X X

Copy pivot data formula X X From the context (right-click)
menu, you can copy the
formula that produces a single
pivot table value. Select Copy
Pivot Data Formula.
Schedule live data refresh X
Protect workbook ranges X
Change workbook owner X
settings
Remove to trash and restore X
from trash

Reference: Automatic Data Updates in Workbooks

A workbook can contain these kinds of data:
• Stand-alone data that might or might not originate in Workday.
• Data from one or more Workday report data sources.
• Data from an integrating application such as Workday Planning or Workday Projects, if applicable.
This table describes the data updates that occur, based on the kind of data you're working with:

Source of Workbook Data Automatic Notes

Data Update

Standalone data, such as: None. When you export from a grid into a workbook using
Export to Worksheets, Workday doesn't preserve
• A new workbook that you
formatting such as bold text.
create in Worksheets.

Source of Workbook Data Automatic Notes

Data Update
• A new workbook that you
create from an uploaded
spreadsheet such as
Microsoft® Excel®.
• A new workbook that you
create when you export
Workday application data
to a workbook. Create the
workbook by selecting the
Export to Worksheets icon
from a grid.

Data from a Workday report data Depends on If you select As Static Values during the insert,
source (Add Live Data) in a the Insert Workday:
workbook. selection (as
• Doesn't update the workbook based on changes
Static Values
in the report.
or as Live Data
Area). • Saves changes you make to data that you
inserted into the workbook.
If you select As Live Data Area during the insert,
Workday:
• Updates the workbook based on data in the
Workday report, either when you manually
refresh live data or when a scheduled refresh
occurs.
• Doesn't save changes that you make later in the
inserted data, but does save changes outside
the live data range.
When Worksheets refreshes live data, it also
recalculates any volatile functions, and formulas
affected by changed workbook data.

Data from entry areas in Updates in

integrating applications such as both directions,
Workday Projects or Workday initiated from
Payroll. the integrating
application.

Reference: Array Formula Keyboard Shortcuts

Use these keyboard shortcuts for array formulas in Worksheets:

Keyboard Shortcut Description

Ctrl+Alt+Enter or Ctrl+Alt+Shift Use for unconstrained array formulas.

+Enter (Windows)
To place results for a formula in all applicable cells, select a single
Command+Option+Enter (Mac) cell and submit the formula using the shortcut.
If the workbook doesn't include enough empty cells to display the
complete results, an error occurs.

Keyboard Shortcut Description

Note: Use the keyboard shortcut to submit changes that you make in
a pivot table formula. A pivot table is an example of an unconstrained
array formula because it can shrink or grow depending on the
underlying data.
Example:
1. Select cell A1.
2. In the formula bar, type ={1,2;3,4}.
3. Press Ctrl+Alt+Enter (Windows) or Command+Shift+Enter (Mac).
Workday shows these 4 values in 2 rows and 2 columns:

1 2
3 4

You can't edit individual cells in the results range.

Ctrl+Shift+Enter (Windows) Use for constrained array formulas. This shortcut is the same in
Worksheets and Excel.
Command+Shift+Enter (Mac)
Select a range of cells, then submit the formula using the shortcut.
Workday displays results only in the selected range.
Don't use this shortcut when you're working with Workday live data,
entry area data, or an array with an undefined or unknown size. Use
the shortcut for unconstrained arrays instead.
When you select more cells than necessary, Workday displays an
#N/A error in the extra cells. When you don't select enough cells to
display the complete results, the remaining results don't display.
Example:
1. Select cells A1-B3.
2. In the formula bar, type ={1,2;3,4}
3. Press Ctrl+Shift+Enter (Windows) or Command+Shift+Enter
(Mac).
Workday shows these values in 3 rows and 2 columns:

1 2
3 4
#N/A #N/A

Workday displays the #N/A error because you selected more cells
than the number of results.
You can't edit individual cells in the range.

Ctrl+Enter (Windows) You can't use the Ctrl+Enter keyboard shortcut in entry areas.
Command+Enter (Mac) This shortcut is the same in Worksheets and Excel.
Technically the shortcut isn't an array formula shortcut; it's similar to a
paste: it places the same formula or data into a range of cells. Unlike
array formulas, using Ctrl+Enter doesn't prevent you from editing
individual cells in the range.
Example:

Keyboard Shortcut Description

1. Select cells A1-B3.
2. In the formula bar, type ={1,2;3,4}.
3. Press Ctrl+Enter (Windows) or Command+Enter (Mac).
Workday shows these 6 values in 3 rows and 2 columns:

1 1
1 1
1 1

Reference: Mobile Features for Worksheets

Workday provides an iOS app and an Android app. Workbooks are available for viewing in the mobile
apps, from the Drive worklet.

FAQ: Collaboration and Security in Worksheets

How do I test my security configuration for To see which data displays in workbooks, we
Worksheets? recommend signing in as multiple users with
different security settings. Then use the Data
Wizard to insert report data into workbooks and
share the workbooks among the users.
Proxy is supported in Worksheets. But keep in mind
that in an application workflow such as HCM, where
the application creates the workbook (not Drive),
proxy usage might not be supported.

Is there a global configuration setting that No. Workbook sharing settings are for individual
enables some users to view workbooks and workbooks. The security group's View and Modify
others to modify them? settings that you assign when initially configuring
Worksheets aren't related to viewing and editing
permissions.

Can I share a Worksheets workbook with Yes, if they have access to the Worksheets
anyone inside Workday even if they can't application (they are in the Worksheets security
access the original data? domain).
Users that you share the workbook with can
initially see any unhidden data included in the
workbook, including Workday data. All users that
you share with can see the same data that you see
in the workbook. This functionality exists because
Worksheets is intended as a collaboration tool
where group of users solve business problems
based on the same set of data. However, if the
shared workbook is based on live data, refreshing
the workbook affects what other users can see:
• As soon as a user refreshes live data in the
workbook, they see only the data they have
access to. Additionally, all other users see the

live data based on the security associated with

the user who refreshed the data.
• Whenever a user does the Refresh All Live
Data action, or whenever a scheduled live data
refresh occurs, all live data in the workbook
refreshes. The live data is visible again to other
users, based on the security associated with the
user who refreshed the data or who set up the
schedule.
• If a user has permission to refresh live data but
they don't have access to one or more of the
data source fields, an error occurs when they try
to do the refresh.
If you share a workbook containing live data with
a user and they make a copy of the workbook, as
soon as they refresh live data in the workbook they
see only the data they have access to.
To ensure that a workbook always displays only the
data that a user has access to, you can create a
workbook template and then distribute the template
to users.

Can I hide content in a workbook to prevent No. Hiding content is useful to reduce distractions
anyone from seeing it in any situation? in your workbook, such as hiding a sheet when
you're using its data for calculations in other sheets.
However, hiding content isn't a security mechanism.
Users with Can View permission for a workbook
can use external references to display and use
the hidden content. Additionally, they can copy
the workbook and unhide any content, if you
enabled the Commenters and viewers can copy,
download, and print option.

What are the colored cell borders in the Colored cell borders are called presence
workbook? indicators. When users view or edit a workbook
simultaneously, Worksheets assigns different colors
to the users. Worksheets highlights cells with that
color as the users interact with the cells. User
avatars also display for any users currently in the
workbook.

When I insert Workday report data into a No, only you have access to the workbook, and
workbook, is the workbook auto-shared with the it contains the data you have access to from the
people I shared with report with? report.

FAQ: Workbook Performance

What's the upper limit on workbook size, and what affects this limit?
The overall limit is 20 million cells per workbook. Keep in mind that performance impacts are much
more dependent on workbook formulas and dependencies than on workbook size. For a complete list of
workbook limits, see Reference: Workbook Limits on page 687.
This table lists workbook characteristics that can have a significant impact on performance, along with
some tips for mitigating that effect:

Performance Impacts Tips

Using many instances of the Instead of using drag-fill to place many occurrences of the same
same formula instead of an array formula in cells, use an unconstrained formula when possible.
formula. Remember to submit the formula using the unconstrained formula
keyboard shortcut. For details, see Concept: Array Formulas in
Workbooks on page 670.

Dependencies within and When using external references, minimize the use of producer
between workbooks. A change workbooks that are referenced by consumer workbooks, particularly if
in 1 cell might cause calculations the producer workbooks are large.
in many other cells. If more
than 1,000 cells are directly or
indirectly affected, performance
might degrade

Calculation-intensive functions, Worksheets provides indexed functions that are optimized for
such as VLOOKUP, SUMIFS, performance. We recommend using these functions instead of their
and so on, when changing a non-indexed counterparts whenever possible:
range value.
• WD.AVERAGEIF/WD.AVERAGEIFS
• WD.COUNTIF/WD.COUNTIFS
• WD.MAXIF/WD.MAXIFS
• WD.MINIF/WD.MINIFS
• WD.MVLOOKUP
• WD.SUMIF/WD.SUMIFS
• WD.VLOOKUP

Volatile functions that run any You can wrap a volatile function in the ONCE function to prevent
time Worksheets recalculates, recalculation.
such as RAND, NOW, TODAY,
Don't create a defined name that uses a volatile function and then
OFFSET, INDIRECT, and INFO.
use that defined name in many places. Instead, place the volatile
Actions that cause the workbook
function in a cell, and create a defined name as a reference to that
to recalculate include:
cell.
• Changing cell values or
Example: To set up and use a defined name for the current date:
formulas.
• Inserting or deleting rows or 1. Place the formula =EDATE(TODAY(),0) in cell A3 of Sheet1.
columns. 2. Create the defined name todays_date. In the formula field type
• Adding or changing defined =Sheet1!$A$3.
names. 3. In formulas where you want to insert the current date, use the
• Filtering. defined name todays_date.
• Hiding or unhiding content.

These workbook characteristics typically have a minimal effect on performance

• Workbook total size
• Number of cells
• Number of sheets (tabs)
• Cross-sheet formulas
• Formula sequence
• Summary tabs
Sometimes I see an alert telling me to come back to my workbook later. Why?

When Worksheets takes more than several seconds to complete an operation, an alert like this displays.
For example, it might display while inserting or refreshing live data, or when recalculating a lot of formulas.
The alert enables you to dismiss the workbook so you can do other work while the action completes. If you
open a workbook that's already running a refresh or a Data Wizard process, you also see the alert.
Sometimes I see a Processing... indicator for a while, in the Drive file list. What determines whether
I see the indicator or not?
When you create a workbook from existing data - such as from a report or an integrating application -
Worksheets displays a Processing... indicator while adding the data into the workbook. The time required
can vary from seconds to hours, depending on several factors, including:
• The number of calculations and formulas.
• The size of the file or Workday report.
• The complexity of the integrating application generation process.
• Whether the workbook contains live data from any Workday reports, or other resource-intensive
processes that the tenant might be running. (Aside from live data, Worksheets processes are
independent of any other tenant processes.)
After Worksheets starts generating the workbook, you can't cancel it or start generating a new integrating
application workbook. However, if a workbook is in a Processing state for more than 24 hours, Worksheets
automatically cancels it, enabling you to move the workbook to the trash or regenerate it.
My workbook calculations are too slow. What improvements can I make?
• If you're making many changes to a workbook with complex formulas, you might want to prevent
recalculations until you finish all your changes. You can temporarily change the recalculation mode to
Manual from the File > Settings dialog.
• Remove any data that you don't need for analysis.
• Minimize external references among workbooks.
• Minimize the number of formulas.
• Use whole-column references (such as A:A) sparingly.
• If you're using lookup formulas, try to organize your data so the calculations are on sorted data. Lookup
functions are much faster with sorted data, and even faster when you can avoid using the exact match
option.
How long should it take to upload an Excel spreadsheet?
Although most uploads finish within a few seconds, extremely large Excel spreadsheets might require
several minutes. The progress bar in Drive lets you know that the process is occurring. You can work in
other workbooks while the upload continues in the background.
Worksheets seems to run faster or slower depending on which computer I run it on. Why?
Rich web applications such as Worksheets can reduce performance if a computer is running other
resource-intensive applications concurrently, or if processing capacity is low for another reason. Although
it's not possible to recommend specific configurations because of the number of variables involved, you
might find that in your environment you need to establish your own hardware configuration requirements.

Example: Use Worksheets with the What's New in Workday Report

This example illustrates how to use Worksheets with the What's New in Workday report. To do so, you
want to create a workbook that includes:
• Live data.
• Note columns for each analyst and their assessments.
• Data validations.
• Formula columns that extract a list of features that affect your training materials.
• Adoption items.

Context
You lead a team of 3 to manage the implementation of a Workday feature release. With each release, you
and your team assess the What's New in Workday report to determine which features you:
• Must implement because they're automatically available.
• Can ignore.
• Want to consider for future adoption and the setup effort needed.
• Need to research to determine what changes to make to your employee training manual.
• Want to create adoption items for.
The steps use GMS tenant names Logan McNeil (you), Betty Liu, Steve Morgan, and Teresa Serrano.
Substitute your team names for these names in your tenant.

Prerequisites
Configure Worksheets and Drive, and give access to the feature planning analysts.
Security for you (not needed for the other users):
• Custom/Standard Report Copy domain in the Tenant Non-Configurable functional area.
• Set Up: Tenant Setup - General domain in the System functional area.

Steps
1. Copy a standard report to create a custom report.
a) Access the Copy Standard Report to Custom Report task.
b) Select What's New in Workday from the Standard Report Name prompt.
c) Click OK.
d) Enter Release Planning with WN Report and Worksheets on the Name field.
e) Click OK. (An alert displays on the page; you can ignore it.)
f) On the Columns tab, click + to add a new column.
g) Select Workday ID from the Field prompt.
h) On the Advanced tab, select these check boxes:
• Enable As Web Service
• Enable for Worksheets
i) Click OK.
2. Create a new workbook in Drive:
a) Select Drive in the Workday main menu.
b) Select New > Workbook.
c) Use Workday [Release #] Release Planning as the name.
d) Click Create.
3. In the workbook, add live data using the report you created:
a) Click Add Live Data.
b) In the Select Report dialog, select the Release Planning with WN Report and Worksheets report.
c) Click Next.
d) In the Select Prompt Values dialog, select:

Option Description
Enabled Functional Areas Select the check box

Option Description
Workday Releases [Next release]
e) Click Next.
f) In the Select Columns dialog:
• Click Select All to add all of the report columns to the workbook.
• Click Add Note Column 2 times to add 2 note columns.
• In the Notes Key field, select Workday ID.
g) Click Next.
h) In the Select Options dialog, select Enable Multi-Instance Values so that all enabled functional
areas display in the workbook.
i) Click Add. The Workday report runs and inserts the data into the workbook.
4. Rename the Sheet1 tab and note column headings:
a) On the Sheet1 tab, click the arrow on the right side of the tab and then click Rename.
b) Rename the sheet as Feature Data.
c) Click OK.
d) Double-click in each of the note column headings to rename them:

From... To...
Note1 Analyst
Note2 Assessment
5. Set up data validation values so you can create drop-down lists for assigning analysts to items, and for
selecting an assessment result:
a) Click + at the bottom left of the workbook to create a new sheet. Worksheets names the sheet
Sheet1.
b) On the Sheet1 tab, click the arrow on the right side of the tab and then click Rename.
c) Rename the sheet as Data Validation Values.
d) Click OK.
e) Enter these values:

A B
1 Betty Implement
2 Steve Investigate
3 Teresa No action
f) In the Feature Data sheet, select the first cell in the Analyst column.
g) Click in the cell below the heading and go to Data > Validation.
h) Enter these values:

Field Value
Cell Range to Validate Enter a range that includes the entire column.
Example: N:N.

Field Value
List of Values from Formula Enter ='Data Validation Values'!A:A.
i) Click OK.
j) In the Assessment column, click in the cell below the heading and go to Data > Validation.
k) In Cell Range to Validate, edit the range to include the entire column. Example: Change the value
from O2:O2 to O:O.
l) In List of Values from Formula, enter ='Data Validation Values'!B:B.
m) Click OK.
6. In the Analyst column, click in each cell and select an analyst from the drop-down list. (We recommend
placing values in at least 20 of the cells, so that later steps in the example will display data.)
7. Share the workbook with your analysts, giving Can Edit access:
a) Click the Share icon at the top right of the workbook.
b) In the Share with Individuals section, enter:
• Betty Liu
• Steve Morgan
• Teresa Serrano
c) Type this comment in the message area: Analysts, please select an assessment value in each of the
workbook rows assigned to you.
d) Click Share. The analysts receive a notification in their Inbox that contains a link to the workbook.
8. The analysts can open the shared workbook, study the What's New Items assigned to them, and select
a value in the Assessment column for each item. We recommend placing values in at least 20 of the
cells, so that later steps in the example will display data.
9. In a new sheet, extract information about What's New items that you're implementing, and that affect
your training materials. Your education team can use this information to update their employee training
materials:
a) Click + at the bottom left of the workbook to create a new sheet.
b) Name the sheet TrainingUpdates.
c) Paste this formula into cell A1 of the sheet, replacing the final argument A1:O200 with the
range of data in the Feature Data sheet: =SELECT("SELECT `Feature`, `What's New
Item`,`Functional Area(s)`, `Feature Description` from ? WHERE `Training
& Testing Impact` = 'This feature may impact your training materials.' AND
`Assessment` = 'Implement'",FeatureData!A1:O200)
d) Press Ctrl+Alt+Enter (Windows) or Command+Option+Enter (Mac) to submit the formula.
10.Add adoption items to your adoption dashboard:
a) Go to the Feature Data sheet.
b) In the What's New Item column, hover the cursor over an item until you see a link.
c) Move the cursor to the far right of the link and click the outward arrow icon; this opens the What's
New Item in a new browser tab.
d) From the related actions menu of the View What's New Item, select What's New Item > Create
Adoption Item. The Create Adoption Item task page displays, with fields from the workbook filled
in automatically.
e) Fill in any additional fields for the adoption item that you want.
f) Click OK.
g) Click Done.
h) Repeat this step for other What's New items.

11.Refresh the live data so that the newly added adoption items display in the workbook:
a) In the Live Data Details panel, click Refresh Now. (If you previously closed the panel to see more
of the workbook data, you can display it again from View > Panels > Live Data.)
b) Click Confirm. The Workday report runs, and the workbook displays any new data; the adoption
items you added display in the Adoption Item(s) column.
12.Create a pivot table to see a summary of the analyst data:
a) In the Feature Data sheet, select Insert > Pivot Table.
b) In the Create Pivot Table dialog, leave the fields as is and click Create.
A basic pivot table displays in a new Sheet1 and the Pivot Table panel displays.
c) In the Pivot Table panel:
• From Available Fields, find Analyst and drag it to the Columns area.
• From Available Fields, find Assessment and drag it to the Rows area.
• Click Update. The table updates to display a summary that looks similar to this image:

Next Steps
Optionally, you can create a formula column in the workbook to create working Community Post links in
the live data area so that the links open the associated What's New posts instead of an instance page.
(Worksheets doesn't support opening external links or attachments from a workbook.) To do this:
1. In the workbook, create a formula column to the right of the Community Post column. Right-click the
Community Post header and select Insert Formula Column > Insert Right.
2. Click Confirm to do the live data refresh and create the formula column.
3. Double-click the Formula1 header and rename the header to Community Post (Corrected).
4. In the first cell of the formula column, type the formula =IFERROR(HYPERLINK(F1),"None"),
replacing the F column identifier with the Community Post column letter in your live data.
5. Press Enter to submit the formula. The IFERROR function causes cells without a Community Post link
to display the text None and the HYPERLINK function takes the content of the non-working cell and
creates a working link.
Refresh the live data at any time to bring in any corrected or newly added What's New items.
Create charts to track progress of analysis.
Share with others outside the team, giving them comment or view access, so they can see the
assessments but can't edit the data.
Related Information
Tasks
Set Up Worksheets on page 649
Steps: Set Up Drive

Create Adoption Items

Workbook Templates

Concept: Workbook Templates

Workbook templates enable you to deliver robust data modeling and analysis that maintains the Workday
security model. You can define a standardized layout and data model in a workbook, convert the workbook
to a template, and distribute that template at scale. Although the most popular reason to use templates
is to preserve live data security, templates can also be extremely valuable for workbooks that contain
complex formulas.
When you distribute a template to a recipient, and they run the template to create a workbook, the resulting
workbook displays Workday data based on the recipient's security permissions.
Workbook templates:
• Retain workbook functionality.
• Display Workday report data based on the template recipient's data access when they run the template.
• Display in Drive like any other item type. A template icon looks like a workbook icon, but it has a T at
the bottom right.
The general template workflow steps are to:
1. (Author/Owner) Convert the workbook to a template.
2. (Author/Owner) Distribute the template to individuals or groups, or turn on link distribution and give
others a link.
3. (Recipient) Run the template to create a workbook.
After converting a workbook to a template, you can edit the template layout, data model, and so on if
needed. Before editing, you must prevent users from running it while it's being edited; to do this, you make
it unavailable to run by switching a toggle. When you're done editing, you make it available again so that
your template recipients can re-run the template to see your updates.

Considerations for Using Workbook Templates

• When you convert a workbook to a template, Worksheets doesn't preserve the original workbook.
• When the template recipient runs a template containing live data to create a workbook, the Workday
report runs with the default prompt values from the report definition wherever applicable.
• Worksheets doesn't preserve live data note column information in converted templates, even if the
template recipient has access to the particular data item; this allows the recipient to enter notes that are
most relevant to their specific data instead of the original workbook owner's data.
• If the template author protected areas in the workbook before converting it to a template, ownership of
those areas transfers to template recipients.
• After you distribute a template, any previous workbook schedules are not preserved in resulting
workbooks; you need to create a new schedule.
• Workday administrators can permanently delete workbooks that are used as the source for templates,
and can also permanently delete templates, regardless of whether they have been distributed.
• Templates aren't supported for active entry areas; the Convert to Template action isn't selectable.

Create and Distribute Workbook Templates

Prerequisites
For group distribution, the administrator must enable the security group for sharing in Drive.

Context
Any Worksheets user can create and distribute templates.

Steps
1. Convert the workbook to a template:
a) In the workbook, select File > Convert to Template.
b) Select the Got it! check box, then click Convert.
2. (Optional) Distribute the template:

To individuals Type user names in the Distribute to Individuals area of the Distribute
dialog.

To groups Type security group names in the Distribute to Groups area of the Distribute
dialog.
Worksheets supports template distribution only for unconstrained security
groups.

To unspecified Click the Link Distribution Off toggle to turn link-based distribution on. Copy
people with a link the link and share it with your recipients.

Distribution is similar to sharing, except that recipients run the template to create their own workbook,
and the permission levels edit, comment, and view aren't applicable.
3. (Optional) Add a description for the template by clicking Template Settings at the top right of the
template.

Next Steps
You can distribute a template immediately after converting it as described above, or:
• From Drive by selecting the template and then clicking Distribute Template.
• From the template by navigating to File > Manage Distribution or by clicking Manage Distribution to
the right of the Available to Run toggle.
After you distribute a template, the recipient runs the template to create a workbook. From Drive, the
recipient selects to open the template, and a dialog guides them to click Run Template to create a
workbook. If the template uses live data, the associated Workday report runs, formulas calculate, and the
workbook is created based on the recipient's level of access to Workday data. If the recipient has limited or
no access to the report, an error occurs for those reports areas and subsequent formulas.
You can edit a template just as you would a workbook, but you need to prevent users from running the
template while you're editing. To do this, click the toggle at the top of the template so it displays Not
Available to Run. In this state, you can edit the template, and users that you distributed the template
to can't run it. Any changes that you make to the template don't automatically propagate to any shared
templates. When you're done editing, click the toggle to display Available to Run. Users that you
previously distributed the template to must run the template again to see your updates.
Just as you can share workbooks, you can share templates, giving edit, comment, or view permission. But
only the author of the template can control the Available to Run setting that allows editing to occur; editors
rely on you to make it unavailable to run, so that they can edit it.

Reference: Template Actions Available Based on Permissions

These tables summarize the primary actions available for templates based on the state of the template and
the user's permission level.

Actions in bold text indicate that the available actions are different based on whether the template is
available to run or not.
The Can Run permission level indicates that the template was distributed to the person, but not shared
with them.

Distributed and Available to Run

Action Can Run Can View Can Can Edit Owner

Comment
Run template X X X X X
View template X X X X
Comment on template X X X
Edit template
Rename template X X
Copy template X Note 1 Note 1 X X
Export template Note 1 Note 1 X X
Share template Note 2 X

Note 1: Allowed only if the workbook owner selected the Commenters and viewers can copy, download,
and print option when sharing.
Note 2: Allowed only if the workbook owner selected the Editors can share option for the workbook when
sharing it.

Not Available to Run (can be edited)

Action Can Run Can View Can Can Edit Owner

Comment
Run template
View template X X X X X
Comment on template X X X
Edit template X X
Rename template X X
Copy template X Note 1 Note 1 X X
Export template Note 1 Note 1 X X
Share template Note 2 X

Worksheets Function Reference

Reference: Worksheets-Unique Functions

Worksheets functions help you organize and manage your data to see trends and obtain insights.
The functions listed in this table distinguish Worksheets from most other spreadsheet products by providing
additional value for data analysis.
Functions in bold text are designed for use as unconstrained array formulas. Submit unconstrained array
formulas with the special keyboard shortcut Ctrl+Alt+Enter (on Windows) or Command+Option+Enter (on
Mac) so Worksheets can use the entire range it needs when returning the results.
As a best practice, use absolute references in Worksheets-unique functions wherever possible to minimize
the use of system resources.
The Workday Administrator Guide describes the Worksheets-unique functions. The Worksheets User
Guide describes all the functions in Worksheets.

Function Type Function

Date • CONVERTTZ
• DATESBETWEEN
• DATESFROM
• DATETIME
• NOWTZ
• WD.DATEDIF

Engineering • DIMENSIONS
• IMCOTH
• IMTANH
• SETUNITS
• UNITS

Information • ISBOOLEAN

Logical • IFEMPTY

Lookup • ARRAYAREA
• IN
• MATCHEXACT
• MHLOOKUP
• MVLOOKUP
• WD.MVLOOKUP
• WD.VLOOKUP

Math • CBRT
• E
• EXPM1
• HYPOT
• LOG1P
• RANDCONST
• RINT
• WD.MAXIFS

Function Type Function

• WD.MINIFS
• WD.SUMIF
• WD.SUMIFS

Matrix • MIDENTITY
• TRUNCATEMATRIX

Miscellaneous • CAPPEDVALUES
• CLUSTER.KMEANS
• CLUSTER.KMEANS.CENTROIDS
• CORRELATE
• DISTINCTROWS
• DISTINCTROWS2
• EMAIL
• GROUPBY
• INSTANCE
• INSTANCE.DESCRIPTOR
• INSTANCE.ID
• JOIN
• MATCHCOMPOSITE
• MERGECOLUMNS
• MERGEROWS
• MI.COUNT
• MI.INDEX
• MINUS
• MULTIINST
• NOTIFYIF
• NOTIFYIFS
• REMOVECOLUMNS
• REMOVEROWS
• SELECT
• SORT
• SORT2
• SORT3
• TRIMCOLUMNS
• TRIMROWS
• UNIQUE
• UNIQUE2
• URL
• URLTEXT
• WD.ARRANGECOLUMNS
• WD.ARRANGEROWS
• WD.LIVEDATA
• WD.SLICE

Operator • COMPARE
• SUBTRACT

Statistical • WD.AVERAGEIF

Function Type Function

• WD.AVERAGEIFS
• WD.COUNTIF
• WD.COUNTIFS
• FORECAST.WD.SEASONAL
• TDISTRT

Table • FLATTEN
• VALUEAT

Text • REGEXFIND
• REGEXPARSE

Reference: Worksheets Functions by Category

This table lists the Worksheets functions, sorted according to category. When you view a function in the
Functions Library panel, you can identify its category by the icon to the left of the name.
The Workday Administrator Guide describes the Worksheets-unique functions. The Worksheets User
Guide describes all the functions in Worksheets.

Function Type Function

Array • CHOOSECOLS
• CHOOSEROWS
• DROP
• EXPAND
• FILTER
• HSTACK
• MS.SORT
• MS.UNIQUE
• MS.UNIQUE2
• RANDARRAY
• SEQUENCE
• SORTBY
• TAKE
• TOROW
• TOCOL
• VSTACK
• WRAPROWS
• WRAPCOLS
• XLOOKUP
• XMATCH

Date • CONVERTTZ
• DATE
• DATESBETWEEN
• DATESFROM
• DATETIME
• DATEVALUE
• DAY
• DAYNAME

Function Type Function

• DAYS
• DAYS360
• DUR2DAYS
• DUR2HOURS
• DUR2MILLISECONDS
• DUR2MINUTES
• DUR2SECONDS
• DUR2WEEKS
• DURATIONVALUE
• EDATE
• EOMONTH
• HOUR
• ISOWEEKNUM
• MINUTE
• MONTH
• MONTHNAME
• NETWORKDAYS
• NETWORKDAYS.INTL
• NOW
• NOWTZ
• SECOND
• TIME
• TIMEVALUE
• TODAY
• WD.DATEDIF
• WEEKDAY
• WEEKNUM
• WORKDAY
• WORKDAY.INTL
• YEAR
• YEARFRAC

Engineering • BESSELI
• BESSELJ
• BESSELK
• BESSELY
• BIN2DEC
• BIN2HEX
• BIN2OCT
• BITAND
• BITLSHIFT
• BITOR
• BITRSHIFT
• BITXOR
• COMPLEX
• CONVERT
• DEC2BIN
• DEC2HEX
• DEC2OCT

Function Type Function

• DELTA
• DIMENSIONS
• ERF
• ERF.PRECISE
• ERFC
• ERFC.PRECISE
• GESTEP
• HEX2BIN
• HEX2DEC
• HEX2OCT
• IMABS
• IMAGINARY
• IMARGUMENT
• IMCONJUGATE
• IMCOS
• IMCOSH
• IMCOT
• IMCOTH
• IMCSC
• IMCSCH
• IMDIV
• IMEXP
• IMLN
• IMLOG10
• IMLOG2
• IMPOWER
• IMPRODUCT
• IMREAL
• IMSEC
• IMSECH
• IMSIN
• IMSINH
• IMSQRT
• IMSUB
• IMSUM
• IMTAN
• IMTANH
• OCT2BIN
• OCT2DEC
• OCT2HEX
• SETUNITS
• UNITS

Financial • ACCRINT
• ACCRINTM
• AMORDEGRC
• AMORLINC
• BONDDURATION
• BONDMDURATION

Function Type Function

• COUPDAYBS
• COUPDAYS
• COUPDAYSNC
• COUPNCD
• COUPNUM
• COUPPCD
• CUMIPMT
• CUMPRINC
• DB
• DDB
• DISC
• DOLLARDE
• DOLLARFR
• DURATION
• EFFECT
• FV
• FVSCHEDULE
• INTRATE
• IPMT
• IRR
• ISPMT
• MDURATION
• MIRR
• NOMINAL
• NPER
• NPV
• ODDFYIELD
• ODDLPRICE
• ODDLYIELD
• PMT
• PPMT
• PRICE
• PRICEDISC
• PRICEMAT
• PV
• RATE
• RECEIVED
• RRI
• SLN
• SYD
• TBILLEQ
• TBILLPRICE
• TBILLYIELD
• VDB
• XIRR
• XNPV
• YIELD
• YIELDDISC

Function Type Function

• YIELDMAT

Information • ERROR.TYPE
• INFO
• ISBLANK
• ISBOOLEAN
• ISERR
• ISERROR
• ISEVEN
• ISFORMULA
• ISLOGICAL
• ISNA
• ISNONTEXT
• ISNUMBER
• ISODD
• ISREF
• ISTEXT
• N
• NA
• TYPE

List • WD.LIST.GET
• WD.LIST.LIST
• WD.LIST.SIZE

Logical • AND
• FALSE
• IF
• IFEMPTY
• IFERROR
• IFNA
• NOT
• OR
• SWITCH
• TRUE
• XOR

Lookup • ADDRESS
• AREAS
• ARRAYAREA
• CHOOSE
• COLUMN
• COLUMNS
• FORMULATEXT
• HLOOKUP
• IN
• INDEX
• INDIRECT
• LOOKUP

Function Type Function

• MATCH
• MATCHEXACT
• MHLOOKUP
• MVLOOKUP
• OFFSET
• ROW
• ROWS
• VLOOKUP
• WD.MVLOOKUP
• WD.VLOOKUP

Math • ABS
• ACOS
• ACOSH
• ACOT
• ARABIC
• ASIN
• ATAN
• ATAN2
• ATANH
• BASE
• BASETONUM
• CBRT
• CEILING
• CEILING.MATH
• CEILING.PRECISE
• COMBIN
• COMBINA
• COS
• COSH
• COT
• COTH
• CSC
• CSCH
• DECIMAL
• DEGREES
• E
• EVEN
• EXP
• EXPM1
• EXPONENT
• FACT
• FACTDOUBLE
• FLOOR
• FLOOR.MATH
• FLOOR.PRECISE
• GCD
• HYPOT
• INT

Function Type Function

• ISO.CEILING
• ISOCEILING
• LCM
• LN
• LOG
• LOG10
• LOG1P
• MAXIFS
• MDETERM
• MINIFS
• MOD
• MROUND
• MULTINOMIAL
• ODD
• PI
• POWER
• PRODUCT
• QUOTIENT
• RADIANS
• RAND
• RANDBETWEEN
• RANDCONST
• RINT
• ROMAN
• ROUND
• ROUNDDOWN
• ROUNDUP
• SEC
• SECH
• SERIESSUM
• SIGN
• SIN
• SINH
• SQRT
• SQRTPI
• SUBTOTAL
• SUM
• SUMIF
• SUMIFS
• SUMPRODUCT
• SUMSQ
• SUMX2MY2
• SUMX2PY2
• SUMXMY2
• TAN
• TANH
• TRUNC
• WD.AVERAGEIFS

Function Type Function

• WD.MAXIF
• WD.MAXIFS
• WD.MINIF
• WD.MINIFS
• WD.SUMIF
• WD.SUMIFS

Matrix • MIDENTITY
• MMULT
• MUNIT
• TRANSPOSE
• TRUNCATEMATRIX

Miscellaneous • CAPPEDVALUES
• CELL
• CLUSTER.KMEANS
• CLUSTER.KMEANS.CENTROIDS
• CORRELATE
• DISTINCTROWS
• DISTINCTROWS2
• EMAIL
• GROUPBY
• HYPERLINK
• INSTANCE
• INSTANCE.DESCRIPTOR
• INSTANCE.ID
• JOIN
• LET
• MATCHCOMPOSITE
• MERGECOLUMNS
• MERGEROWS
• MI.COUNT
• MI.INDEX
• MINUS
• MULTIINST
• NOTIFYIF
• NOTIFYIFS
• REMOVECOLUMNS
• REMOVEROWS
• SELECT
• SORT
• SORT2
• SORT3
• TRIMCOLUMNS
• TRIMROWS
• UNIQUE
• UNIQUE2
• URL
• URLTEXT

Function Type Function

• WD.ARRANGECOLUMNS
• WD.ARRANGEROWS
• WD. EXCHANGE
• WD.LIVEDATA
• WD.SLICE

Operator • ADD
• COMPARE
• DIVIDE
• EQ
• GT
• GTE
• LT
• LTE
• MULTIPLY
• NE
• POW
• SUBTRACT
• UMINUS
• UNARY_PERCENT
• UPLUS

Statistical • AGGREGATE
• AVEDEV
• AVERAGE
• AVERAGEA
• AVERAGEIF
• AVERAGEIFS
• BINOM.DIST
• BINOM.INV
• BINOMDIST
• BINOMINV
• CHIDIST
• CHISQ.DIST
• CHISQ.DIST.RT
• CHISQDIST
• CHISQDISTRT
• CONFIDENCE
• CONFIDENCE.NORM
• CONFIDENCE.T
• CORREL
• COUNT
• COUNTA
• COUNTBLANK
• COUNTIF
• COUNTIFS
• COVARIANCE.P
• COVARIANCE.S
• COVARIANCEP

Function Type Function

• COVARIANCES
• CRITBINOM
• DEVSQ
• EXPON.DIST
• EXPONDIST
• FISHER
• FISHERINV
• FORECAST
• FORECAST.WD.SEASONAL
• FREQUENCY
• GAMMALN
• GAMMALN.PRECISE
• GAUSS
• GEOMEAN
• GROWTH
• HARMEAN
• HYPGEOM.DIST
• HYPGEOMDIST
• INTERCEPT
• KURT
• LARGE
• LINEST
• LOGEST
• LOGINV
• LOGNORM.DIST
• LOGNORM.INV
• LOGNORMDIST
• LOGNORMINV
• MAX
• MAXA
• MEDIAN
• MIN
• MINA
• MODE
• MODE.MULT
• MODE.SNGL
• NEGBINOM.DIST
• NEGBINOMDIST
• NORM.DIST
• NORM.INV
• NORM.S.DIST
• NORM.S.INV
• NORMDIST
• NORMINV
• NORMSDIST
• NORMSINV
• PEARSON
• PERCENTILE

Function Type Function

• PERCENTILE.EXC
• PERCENTILE.INC
• PERCENTRANK
• PERCENTRANK.INC
• PERMUT
• PERMUTATIONA
• PHI
• POISSON
• POISSON.DIST
• QUARTILE
• QUARTILE.EXC
• QUARTILE.INC
• RANK
• RANK.AVG
• RANK.EQ
• RANKAVG
• RANKEQ
• RSQ
• SLOPE
• SMALL
• STANDARDIZE
• STDEV
• STDEV.P
• STDEV.S
• STDEVP
• STDEVS
• T.DIST
• T.DIST.RT
• T.INV
• TDIST
• TDISTRT
• TINV
• TRIMMEAN
• VAR
• VAR.P
• VARA
• VARP
• VARPA
• WD.AVERAGEIF
• WD.COUNTIF
• WD.COUNTIFS
• WEIBULL
• WEIBULL.DIST
• WEIBULLDIST
• Z.TEST
• ZTEST

Text • ASC
• CHAR

Function Type Function

• CLEAN
• CODE
• CONCAT
• CONCATENATE
• ENCODEURL
• EXACT
• FIND
• FIXED
• LEFT
• LEN
• LOWER
• MID
• PROPER
• REGEXEXTRACT
• REGEXFIND
• REGEXMATCH
• REGEXPARSE
• REGEXREPLACE
• REPLACE
• REPT
• RIGHT
• SEARCH
• SPLIT
• SUBSTITUTE
• T
• TEXT
• TEXTAFTER
• TEXTBEFORE
• TEXTJOIN
• TEXTSPLIT
• TRIM
• UNICHAR
• UNICODE
• UPPER
• VALUE
• WD.HALFTOFULL
• WD.FULLTOHALF

Table • FLATTEN
• VALUEAT

Reference: Formula Errors

Error Notes

#DIV/0! The formula is trying to divide by zero. Example: You might have a formula where a
cell value/result is unexpectedly zero or blank, and the formula is trying to divide by
that number.

Error Notes

#ERROR! A rare error. Most error messages are fairly specific, but #ERROR might merely
specify that a syntax error exists, or that you can't submit the formula for an
unknown reason.

#FIELD! A data type error exists.

#GETTING_DATA! Not a true error, but it might display temporarily in workbook cells when large
or complex calculations are in progress. The message disappears when the
calculations complete.

#N/A! A value isn't available to a function or formula. Examples:

• A lookup function can't find a key value.
• An array formula has an argument that's a different size (cell range) from
another argument.
• A function has 1 or more missing arguments.

#NAME! You referenced a defined name or a function that doesn't exist.

#NULL! You might have:

• Used an incorrect range or reference separator such as a space (separating
individual cell references in a formula with a space instead of a comma).
• Used a space (the intersect operator) to do a calculation on intersecting ranges
but there was no intersection.

#NUM! A formula has invalid numeric data for the type of operation.
Example: Pivot tables don't support calculations when the data range contains
multiple currency units. If you have a pivot table that includes salaries, and some
salaries are in USD while others are in CAD, you can't do a SUM, AVERAGE,
or other calculation on the data; if you hover over the error cell you see A unit
conversion issue exists. The only valid function in this situation is COUNTA.
To help troubleshoot a #NUM error that might be a units problem, you can view the
units settings by selecting View > Show Units.

#REF! A reference isn't valid.

#SPILL! The most frequent cause of this error is that array formula results can't be placed
into the workbook because the results would overlap existing data.
When in an entry area, #SPILL occurs when the formula attempts to place data
across the boundary of the entry area.

#VALUE! You used the wrong type of operand or function argument. Example: You see
#VALUE if the formula finds spaces, characters, or text where it's expecting a
number.

####### Not actually an error; your column isn't wide enough to display a value.

Tips for Formula Errors

Remember that you must submit array formulas with the appropriate keyboard shortcut. See Concept:
Array Formulas in Workbooks for information about constrained arrays, unconstrained arrays, and more.

If you see an error related to circular references, you might want to review Concept: Circular References in
the Worksheets User Guide.
Take note of the workbook setting for automatic or manual recalculation in File > Settings.
Try to simplify complex formulas:
• If the formula contains lots of nested functions, separate out one or more of them, placing their results
in a separate range that you refer to in the rest of the original formula.
• If the formula has external references that appear not to resolve, try merging the workbooks so that the
reference is merely to another sheet instead of to a workbook; or, put all the data on 1 sheet.

Displaying User-Friendly Text Instead of Error Codes

Sometimes you use formulas that do calculations based on cell values, and if one of those values is
unexpected you end up with an error such as a #DIV/0 error. If you want to plan for the possibility of an
error and give the workbook user a more friendly message, you can use:
• The IFERROR function or the ISERROR function
• The IFEMPTY formula for unconstrained array formulas where the result is an empty array
Example: We have a workbook that shows salespeople's average bonuses for a quarter. To get a bonus,
a salesperson must sell more than $5,000 in goods in a particular month. Because Matt didn't get any
bonuses, the Avg Bonus cell would contain a #DIV/0 error. To prevent this unfriendly error from displaying,
we can nest our AVERAGEIF function in an IFERROR. This formula is in F2:
=IFERROR(AVERAGEIF(B2:D2,">5000",B2:D2),"No bonuses")

A B C D E F
1 Name Jan Sales Feb Sales Mar Sales # Bonuses Avg Bonus
2 Matt Bond $1500 $3275 $2900 Zero No bonuses

The ISERROR function is similar to IFERROR, but it returns a TRUE or FALSE result based on whether an
error exists.

Reference: Worksheets Rounding Functions

Worksheets supports the same rounding functions as other popular spreadsheet applications. These tables
can help you decide when to use each one.

Rounding a Number to an Integer

Function Rounds... For Positive Numbers For Negative Numbers

EVEN Away from zero to next Result becomes more Result becomes more
even number positive negative
ODD Away from zero to next Result becomes more Result becomes more
odd number positive negative
INT Down to next integer Result becomes more Result becomes more
below negative negative

Rounding a Number Using Decimal Places

Function Rounds... For Positive Numbers For Negative Numbers

ROUND Up or down to the Result becomes more Result becomes more
closest value, based on positive or negative positive or negative

Function Rounds... For Positive Numbers For Negative Numbers

the number of decimal based on the closest based on the closest
places you specify value value
ROUNDUP Away from zero, based Result becomes more Result becomes more
on the number of positive negative
decimal places you
specify
ROUNDDOWN and Away from zero, based Result becomes more Result becomes more
TRUNC on the number of negative positive
decimal places you
specify

Rounding a Number Using a Multiple of Significance (MoS)

Function Rounds... For Positive For Positive For Negative For Negative
Numbers with Numbers with Numbers with Numbers with
a Positive MoS a Negative a Positive MoS a Negative
MoS MoS
CEILING Away from Result becomes Not applicable Result becomes Result becomes
zero, based on more positive (#NUM error) more negative less negative
the MoS you
specify
CEILING.PRECISE
Up, based on Result becomes Result becomes Result becomes Result becomes
AND the MoS you more positive more positive less negative less negative
ISO.CEILING/ specify
ISOCEILING
CEILING.MATH Up, based on Result becomes Result becomes Result becomes Result becomes
the MoS you more positive more positive less negative less negative
specify (or use mode to (or use mode to
reverse it) reverse it)
FLOOR Towards zero, Result becomes Not applicable Result becomes Result becomes
based on less positive (#NUM error) less negative more negative
the MoS you
specify
FLOOR.PRECISEDown, based Result becomes Result becomes Result becomes Result becomes
on the MoS you less positive less positive more negative more negative
specify
FLOOR.MATH Down, based Result becomes Result becomes Result becomes Result becomes
on the MoS you less positive less positive more negative more negative
specify (or use mode to (or use mode to
reverse it) reverse it)
MROUND Up or down, Result becomes Not applicable Result becomes Not applicable
based on more positive or (#NUM error) more positive or (#NUM error)
the MoS you negative, based negative, based
specify on the closest on the closest
multiple multiple

Worksheets Functions
Date Functions
CONVERTTZ

Description
Converts a datetime value from one time zone to another.

Syntax
CONVERTTZ(range, from_time_zone_id, to_time_zone_id)
• range: The cell, or range of cells, to return the converted time zone for.
• from_time_zone_id: The time zone specifier to convert from. Examples: GMT, US/Central.
• to_time_zone_id: The time zone specifier to convert to.

Example

Formula Result
=CONVERTTZ(A8,"America/Montreal","US/ 10/4/2016 2:37 PM
Pacific") where A8 contains 10/4/2016 5:37 PM

Notes
• Time zone IDs are based on the Java TimeZone utility. A complete list of time zones is available at
http://joda-time.sourceforge.net/timezones.html. Examples:
• America/New_York
• Asia/Hong_Kong
• Australia/Melbourne
• Canada/Eastern
• Europe/London
• GMT
• MET
• US/Mountain
• UTC
DATESBETWEEN

Description
Returns an array of dates that starts and ends on a particular date, with a step interval between each date.

Syntax
DATESBETWEEN(start_date, end_date, [ step])
• start_date: The starting date of the range.
• end_date: The ending date of the range.
• step: The number of days to step between each date. The default is 1.

Example

Formula Result
=DATESBETWEEN("01-Jan-2015", "10-Jan-2015", { "1/1/2015"; "1/8/2015" }
7)
=DATESBETWEEN("14-Jul-2016", "01-Jul-2016", { "7/14/2016"; "7/12/2016"; "7/10/2016"; "7/8/2016";
2) "7/6/2016"; "7/4/2016"; "7/2/2016" }

Notes
• This function returns a column of dates starting at the start_date and ending either before or at the
end_date.
• The step parameter must be a positive integer when present.
• Since the step parameter may be such that the end_date is never reached exactly, the final date
Workday returns in the range is the greatest date that is less than the end_date, but where adding step
days to that date would make the new date greater than the end_date.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.
DATESFROM

Description
Returns an array of dates that starts on a particular date and continues for the number of dates you
specify, with a step interval between each date.

Syntax
DATESFROM(start_date, num_dates, [ step])
• start_date: The starting date of the range.
• num_dates: The number of dates to be returned.
• step: The number of days to step between each date. The default is 1.

Example

Formula Result
=DATESFROM("01-Jan-2015", 4, 2) { "1/1/2015"; "1/3/2015"; "1/5/2015"; "1/7/2015" }
=DATESFROM("14-Jul-2016", 3, -1) { "7/14/2016"; "7/13/2016"; "7/12/2016" }

Notes
• This function returns a column of num_dates dates.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.
DATETIME

Description
Returns the date and time based on the year, month, day, hour, minute, and second that you specify.

Syntax
DATETIME(year, month, day, hour, minute, second)
• year: The integer representing the year.
• month: The integer representing the month.
• day: The integer representing the day.
• hour: The integer representing the hour.
• minute: The integer representing the minutes.
• second: The integer representing the seconds.

Example

Formula Result
=DATETIME(2016,7,15,8,12,12) { "7/15/2016 8:12 AM" }

Notes
• If you specify an argument that is outside the 24-hour clock, or you specify a negative number in an
argument, Workday adjusts the resulting time to be valid. Example: =DATETIME(2016,7,15,-44,12,12)
returns the value 7/13/2016 4:12 AM.
• If the result is a numeric value instead of a date, check the formatting for the cell to make sure it's set to
Date .
NOWTZ

Description
Returns the current date and time based on the time zone you specify. NOWTZ() generates a new date
and time whenever any cell on the sheet changes. This function is volatile; it generates a new value any
time any cell in the workbook changes.

Syntax
NOWTZ([ time_zone_id])
• time_zone_id: The time zone specifier, such as GMT, US/Central, and so on.

Example

Formula Result
=NOWTZ("US/Pacific") 10/4/2016 5:37 PM

Notes
• The function doesn't run as a volatile function if the Worksheets calculation mode is set to Manual in
File > Settings .

• Time zone IDs are based on the Java TimeZone utility. A complete list of time zones is available at
http://joda-time.sourceforge.net/timezones.html. Examples:
• America/New_York
• Asia/Hong_Kong
• Australia/Melbourne
• Canada/Eastern
• Europe/London
• GMT
• MET
• US/Mountain
• UTC
WD.DATEDIF

Description
Returns the amount of time between two dates, based on the specified period and its corresponding unit.
We recommend using WD.DATEDIF instead of DATEDIF; we provide DATEDIF for compatibility but it
calculates incorrect results in some situations.

Syntax
WD.DATEDIF(start_date, end_date, period, unit)
• start_date: The starting date for the count. Workday recommends using a cell reference to specify the
date instead of entering the date as text, to ensure reliable results.
• end_date: The ending date for the count. Workday recommends using a cell reference to specify the
date instead of entering the date as text, to ensure reliable results.
• period: The number of whole periods between start_date and end_date. If the period is a grouping
of values, such as YMD, the function calculates all the whole periods as segments; you use the unit
argument to specify which number (segment) to return. Example: If the start_date is January 1, 2010,
and the end_date is February 3, 2020, then the function calculates that Year=10, Month=1 and Day=2.
If the unit=Month, the function returns 1.
• Year (Y)
• Month (M)
• Week (W)
• Day (D)
• Hour (H)
• Minute (M)
• Second (Sec or S)
• Milli (Mil or MS)
• YearMonthWeekDayTime (YMWDT): Years, months, weeks, days, hours, minutes, seconds, and
milliseconds.
• YearMonthDayTime (YMDT): Years, months, days, hours, minutes, seconds, and milliseconds
• YearMonthDay (YMD): Years, months, and days
• YearWeekDayTime (YMDT): Years, weeks, days, hours, minutes, seconds, and milliseconds
• YearWeekDay (YWD): Years, weeks, and days
• YearDayTime (YDT): Years, days, hours, minutes, seconds, and milliseconds
• YearDay (YD): Years and days
• DayTime (DT): Days, hours, minutes, seconds, and milliseconds
• Time (T): Hours, minutes, seconds, and milliseconds

• unit: The number to return. If the period is a single value, such as Day, the unit must match the period.
If the period is a grouped value, such as YMD, the unit must match one of the segments in the period.
• Year (Y)
• Month (M)
• Week (W)
• Day (D)
• Hour (H)
• Minute (Min)
• Second (S or Sec)
• Milli (or MS or Mil)

Example
The examples are based on this data:

A B C D
1 Start Date End Date Period Unit
2 07/02/2018 03/31/2020 Year Year
05:17:33.636 PM 12:00:00.000 AM
3 Month Month
4 Week Week
5 Day Day
6 YMD M

Here are some example formulas and results:

Formula Result
=WD.DATEDIF(A2,B2,C2,D2) 1
=WD.DATEDIF(A2,B2,C3,D3) 20
=WD.DATEDIF(A2,B2,C4,D4) 91
=WD.DATEDIF(A2,B2,C5,D5) 637
=WD.DATEDIF(A2,B2,C6,D6) 8

In a more complex example, you can specify several unit values using a range of cells to calculate the
same number of results.

Place the formula =WD.DATEDIF(A2,B2,C2,D2:F2) in cell D3 and submit it as an unconstrained array

formula using Ctrl+Alt+Enter (Windows) or Command+Alt+Enter (Mac).

Engineering Functions
DIMENSIONS

Description
Returns the dimension of a numeric value. If there are no dimensions, the function returns an empty string.
If the argument is not numeric, the function returns a #VALUE error.
A dimension is a property that can be measured, such as time (T), length (L), or mass (M). A unit is a value
of a dimension; for example, seconds (sec) or meters (m).

Syntax
DIMENSIONS(value)
• value: The value to return the dimension for.

Example

Formula Result

=DIMENSIONS(50) L

where 50 currently has the "m" (meters) unit

Notes
• Valid dimension values are from the base library javax.measure.unit.Dimension.
• This function is similar to UNITS(), but UNITS() returns the unit value instead of the dimension value.
IMCOTH

Description
Returns the hyperbolic cotangent of a complex number.

Syntax
IMCOTH(inumber)
• inumber: The complex number. Specify the number as text in either x+yi or x+yj format, where the x
component or y component is optional.

Example

Formula Result
=IMCOTH( "3 + 4i" ) 0.9992669278059017-0.0049011823943044056i
=IMCOTH(3) 1.004969823313689

IMTANH

Description
Returns the hyperbolic tangent of a complex number.

Syntax
IMTANH(inumber)

• inumber: The complex number. Specify the number as text in either x+yi or x+yj format, where the x
component or y component is optional.

Example

Formula Result
=IMTANH( "3 + 4i" ) 1.000709536067233+0.004908258067495992i
=IMTANH(3) 0.9950547536867306

SETUNITS

Description
Converts a number from its current unit of measurement to another. This function is similar to CONVERT(),
but in CONVERT() you must specify both the original and the new units value.

Syntax
SETUNITS(value, set_unit)
• value: The number to convert.
• set_unit: The units to return the value in. The set_unit argument is case-sensitive.

Example

Formula Result

=SETUNITS(825,"cup") 17.185

where 825 currently has the "tsp" unit

=SETUNITS(98.6,"cel") 37

where 98.6 currently has the "F" unit

Notes
• Valid units values are from the base library javax.measure.unit.Dimension.
UNITS

Description
Returns the units part of a number as a string. If the number does not have a units value, the function
returns an empty string.

Syntax
UNITS(value)
• value: The number to return the unit of measurement for.

Example

Formula Result

=UNITS(A1) cup

Formula Result
where the value in A1 currently has the "cup" unit)

Information Functions
ISBOOLEAN

Description
Returns True if the value you specify is a boolean (logical) value; otherwise, returns False.

Syntax
ISBOOLEAN(value)
• value: The value to evaluate.

Example

Formula Result
=ISBOOLEAN(FALSE) TRUE
=ISBOOLEAN("phrase") FALSE

Notes
• This function does the same action as ISLOGICAL().

Logical Functions
IFEMPTY

Description
If the specified value or expression results in an empty array, the function returns the value_if_empty value;
otherwise, it returns the value. This function is intended for use with unconstrained array formulas.

Syntax
IFEMPTY(value, value_if_empty)
• value: The value or expression to evaluate.
• value_if_empty: The value to return if the initial value or expression results in an empty array; it must be
both empty and an array. Otherwise, the function returns value.

Lookup Functions
ARRAYAREA

Description
Returns the containing range of the array formula, based on the single cell address that you specify. The
array can originate either in a Workday report or an array formula. This function helps you create formulas
that operate on arrays where the cell range is unknown or changes over time.

Syntax
ARRAYAREA(ref_cell)
• ref_cell: The cell reference. Make sure you enter only a single cell address and not a range.

Example
The example is based on this table, where the data in A1:B3 is an array formula result set:

A B
1 4 6
2 8 10
3 14 22

Formula Result
=ARRAYAREA(B2) 4 6 8 10 14 22

Related Functions
COMPARE
GROUPBY
REMOVEROWS
SORT
SORT2
IN

Description
Determines whether a value or list of values that you specify is in another list of values. If so, returns True;
otherwise, returns False.

Syntax
IN(source, target)
• source: The number or list of numbers.
• target: The array of target values.

Example

Formula Result
=IN(5,{1,2,3,4,5}) TRUE
=IN({"a","b"},{"d","c","b","a"}) TRUE

MATCHEXACT

Description
Looks up an exact match for the value in the sorted list (one-dimensional array) you specify, and returns
the position of the value. You can use this function to match logical values, numeric values, or text strings.
This function is similar to MATCH, but MATCHEXACT:
• Always searches for an exact match; it returns an #N/A error if it doesn't find the value.
• Doesn't allow wildcard characters such as * or ?.
• Uses a binary search for better performance.

Syntax
MATCHEXACT(lookup_value, lookup_array, [ match_type])
• lookup_value: The value to find.
• lookup_array: The array to search.
• match_type: The criteria to use when searching. Possible values are:
• 0 or greater = do a binary search for the specified lookup_value. lookup_array data must be sorted
in ascending order. If you omit the argument, the function uses this as the argument value.
• Less than 0 = do a binary search for the specified lookup_value. lookup_array data must be sorted
in descending order.

Example
The examples are based on this workbook:

A B C D E F G H
1 Supervisory
Cost Company Location Jan Feb (HC) Mar PEA KEY
Org Center (HC) 2017 (HC)
2017 2017
2 Finance CC-1 GMS Pleasanton2 2 2 FinanceCC-1
Finance FinanceGMSPleasanton
3 Product CC-2 GMS Boulder 0 1 2 Product
Management
Product ManagementCC-2
ProductGMSBoulder
4 Development
CC-3 GMS-CA Toronto 2 2 2 DevelopmentCC-3
Development DevelopmentGMS-
CAToronto
5 Sales CC-4 GMS-UK London 1 2 2 SalesCC-4
Sales SalesGMS-
UKLondon
6 Sales CC-4 GMS-UK Toronto 0 0 1 SalesCC-4
Sales SalesGMS-
UKToronto
7 5 7 9

For the formula =MATCHEXACT("CC-3 Development",B2:B6) , the result is 3 .

You can also return the matched value instead of its position by combining the MATCHEXACT and INDEX
functions.
For the formula =INDEX(G2:G6,MATCHEXACT("CC-3 Development",B2:B6,1)) :
First, MATCHEXACT searches the array B2:B6 for the string "CC-3 Development" and returns the position
of the value, which is 3 . Then, INDEX uses 3 as its second argument and returns the value in position 3 of
G2:G6, which is 2 .

Notes
• If multiple matches exist, the function returns the position of the first match.

Related Functions
MATCH

MHLOOKUP
MVLOOKUP
MHLOOKUP

Description
We recommend this function as a replacement for HLOOKUP. MHLOOKUP performs a horizontal (row)
lookup on a table and returns all matches. MHLOOKUP is similar to HLOOKUP, but:
• HLOOKUP scans only the top row for matches; in MHLOOKUP you specify the row to search.
• HLOOKUP stops after finding 1 match, and returns a single cell value; MHLOOKUP scans the entire
lookup row for matches. Each match in that row results in a new row in the result. If you specify 4
return_row_index values, then each resulting row will have 4 columns.

Syntax
MHLOOKUP(lookup_value, table_array, lookup_row_index, return_row_index, ...)
• lookup_value: The value to match.
• table_array: The array or table to search.
• lookup_row_index: The row in the table to search (1-based).
• return_row_index: The row number to return results from. You can list any number of row numbers.

Example
The example is based on this workbook:

A B C D E F G H
1 SalespersonDixon Dixon Kelly Kelly Payne Payne Payne
2 Customer O'Reilly, Runolfsson Kuphal Ernser Inc Williamson Ratke- Leuschke
Auer, & and Group Group Sanford and Sons
Lind Steuber
3 Product Qosolex Saoplus Qosolex Voltflarn Singlflix Qosolex Qosolex
4 Revenue $8,232,000.00
$4,853,000.00
$2,358,000.00
$2,064,000.00
$6,974,000.00
$8,433,000.00
$8,181,000.00

The result of MHLOOKUP("Qosolex",A1:H4,3,1,2,4) is:

Dixon Kelly Payne Payne

O'Reilly, Auer, & Lind Kuphal Group Ratke-Sanford Leuschke and Sons
$8,232,000.00 $2,358,000.00 $8,433,000.00 $8,181,000.00

Notes
• MHLOOKUP() scans the columns in the lookup_row_index row for lookup_value, then gathers values
from the rows listed in return_row_index. Then it places each value into a column in the resulting matrix.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
MATCHEXACT
MVLOOKUP
MVLOOKUP

Description
We recommend this function as a replacement for VLOOKUP, especially when you're working with live
data. MVLOOKUP performs a vertical (column) lookup on a table and returns all matches. MVLOOKUP is
similar to VLOOKUP, but:
• VLOOKUP scans only the left column for matches; in MVLOOKUP you specify the column to search.
• VLOOKUP stops after finding 1 match, and returns a single cell value; MVLOOKUP scans the entire
lookup column for matches. Each match in that column results in a new row in the output. If you specify
4 return_column_index values, then each resulting row will have 4 columns.

Syntax
MVLOOKUP(lookup_value, table_array, lookup_column_index, order,
return_column_index, ...)
• lookup_value: The value to match.
• table_array: The array or table to search.
• lookup_column_index: The column in the table to search (1-based).
• order: The order for the search, based on the sort order of table_array.
• 0: The default linear search, for unsorted data.
• 1: Binary search, for data sorted in ascending order.
• -1: Binary search, for data sorted in descending order.
• return_column_index: The column number to return results from. You can list any number of column
numbers.

Example
The example is based on this workbook:

A B C D
1 Salesperson Customer Product Revenue
2 Dixon O'Reilly, Auer, & Qosolex $8,232,000.00
Lind
3 Dixon Runolfsson and Saoplus $4,853,000.00
Steuber
4 Kelly Kuphal Group Qosolex $2,358,000.00
5 Kelly Ernser Inc Voltflarn $2,064,000.00
6 Payne Williamson Group Singlflix $6,974,000.00
7 Payne Ratke-Sanford Qosolex $8,433,000.00
8 Payne Leuschke and Sons Qosolex $8,181,000.00
9 Wu Dach-Halvorson Singlflix $2,361,000.00
10 Wu Wisoky LLC Bextain $5,752,000.00

A B C D
11 Wu Stiedemann Grp Saoplus $3,987,000.00

The result of:

=MVLOOKUP(A6,A2:D11,1,0,2,3,4)
or alternatively, =MVLOOKUP("Payne",A2:D11,1,0,2,3,4)
is:

Williamson Group Singlflix $6,974,000.00

Ratke-Sanford Qosolex $8,433,000.00
Leuschke and Sons Qosolex $8,181,000.00

Notes
• MVLOOKUP() scans the rows in column lookup_column_index for lookup_value. The function then
gathers values in the columns listed in return_column_index. Then it places each value into a column in
the resulting matrix.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
MATCHEXACT
MHLOOKUP
WD.MVLOOKUP

Description
This function is the same as MVLOOKUP but WD.MVLOOKUP creates an index (b-tree) for the specified
range or array, and it ignores the order argument. This function provides better performance for repeated
use on the same range/array. Null and error values are ignored. We recommend this function as a
replacement for VLOOKUP, especially when you're working with live data. WD.MVLOOKUP performs a
vertical (column) lookup on a table and returns all matches. WD.MVLOOKUP is similar to VLOOKUP, but:
• VLOOKUP scans only the left column for matches; in WD.MVLOOKUP you specify the column to
search.
• VLOOKUP stops after finding 1 match, and returns a single cell value; WD.MVLOOKUP scans the
entire lookup column for matches. Each match in that column results in a new row in the output. If you
specify 4 return_column_index values, then each resulting row will have 4 columns.

Syntax
WD.MVLOOKUP(lookup_value, table_array, lookup_column_index, order,
return_column_index, ...)
• lookup_value: The value to match.
• table_array: The array or table to search.
• lookup_column_index: The column in the table to search (1-based).
• order: Not used.

• return_column_index: The column number to return results from. You can list any number of column
numbers.

Example
The example is based on this workbook:

The result of:

=WD.MVLOOKUP(A6,A2:D11,1,0,2,3,4)
or alternatively, =WD.MVLOOKUP("Payne",A2:D11,1,0,2,3,4)
is:

Williamson Group Singlflix $6,974,000.00

Ratke-Sanford Qosolex $8,433,000.00
Leuschke and Sons Qosolex $8,181,000.00

Notes
• WD.MVLOOKUP() scans the rows in column lookup_column_index for lookup_value. The function then
gathers values in the columns listed in return_column_index. Then it places each value into a column in
the resulting matrix.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
MATCHEXACT
MHLOOKUP

WD.VLOOKUP

Description
Finds a value in the leftmost column of the specified array, and returns the value for the corresponding cell
in the same row in a different column. This function is the same as VLOOKUP but WD.VLOOKUP creates
an index (b-tree) for the specified ranges/arrays, and it ignores the range_lookup argument. This function
provides better performance for repeated use on the same range/array. Null and error values are ignored.

Syntax
WD.VLOOKUP(lookup_value, table_array, col_index_num, [ range_lookup])
• lookup_value: The value to find in the first column.
• table_array: The array or table to search.
• col_index_num: The column to return the corresponding value from.
• range_lookup: Not used.

Example
The example is based on this workbook:

The result of =WD.VLOOKUP(A6,A2:D11,4) is $6,974,000.00 .

Related Functions
ARRAYAREA
GROUPBY
MATCHEXACT
WD.MVLOOKUP

Math Functions
CBRT

Description
Returns the cube root of a number.

Syntax
CBRT(value)
• value: The value to compute the cube root for.

Example

Formula Result
=CBRT(8) 2

Description
Returns the value of the base of natural logarithms (approximately 2.71828182845904523536).

Syntax
E()

Example

Formula Result
=E() 2.718281828

EXPM1

Description
Returns e raised to the power you specify, minus 1.

Syntax
EXPM1(value)
• value: The exponent to raise e to.

Example

Formula Result
=EXPM1(2) 6.389056099

HYPOT

Description
Calculates the hypotenuse of a right triangle using the Pythagorean theorem.

Syntax
HYPOT(x, y)
• x: The length of a non-hypotenuse side of the triangle.
• y: The length of the second non-hypotenuse side of the triangle.

Example

Formula Result
=HYPOT(3,4) 5

LOG1P

Description
Returns the natural logarithm of the sum of 1 plus the argument.

Syntax
LOG1P(value)
• value: The value to calculate the natural logarithm + 1 for.

Example

Formula Result
=LOG1P(5) 1.791759469

RANDCONST

Description
Returns a random floating point number. This function is similar to RAND() except that RANDCONST()
generates a random floating point number only when you make the function run (for example, you select
Data > Recalculate ).

Syntax
RANDCONST([ low_bound], [ high_bound])
• low_bound: The low bound on the generated random number. This number is inclusive (the value might
be returned as a result). If you omit the argument, the function uses 0 as the value.
• high_bound: The high bound on the generated random number. This number is inclusive (the value
might be returned as a result). If you omit the argument, the function uses 1 as the value.

Example

Formula Result
=RANDCONST() varies (between 0 and 1)
=50*RANDCONST() varies (between 0 and 50)
=RANDCONST()*(50-10)+10 varies (between 10 and 50)

Notes
• If you need one-time-only calculation, for any formula, enclose it in the ONCE function.
• This non-volatile function is recalculated only when:
• A scheduled live data refresh runs.
• You select Data > Recalculate .
• You select Data > Recalculate All

Related Functions
ONCE
RINT

Description
Returns the integer closest to the number. If two integers are equally close, the result is the integer that is
even.

Syntax
RINT(value)
• value: The number to round.

Example

Formula Result
=RINT(12.34) 12
=RINT(-12.34) -12
=RINT(PI()) 3

WD.MAXIF

Description
Returns the maximum value from a range or array of values, according to a criterion. This function creates
an index (b-tree) for the specified range or array, providing better performance for repeated use on the
same range/array. Null and error values are ignored.

Syntax
WD.MAXIF(max_range, range, criteria)
• max_range: The array of numeric values that you want to return the maximum value from, if the criteria
are met.
• range: The values, or the range/array of cells, to be evaluated according to the condition.
• criteria: The condition to use to evaluate the values.

• The function isn't case-sensitive. Example: When evaluating the values in criteria_range against the
criteria, the text strings "MONTH" and "month" are considered a match.
• Whenever you use a text string or an expression as a condition, surround it with quotes.
• In text-based criteria, you can use the ? wildcard to match any single character or the * wildcard to
match any sequence of characters.
WD.MAXIFS

Description
Returns the maximum value from a range of values, according to one or more criteria. This function is
the same as MAXIFS but WD.MAXIFS creates an index (b-tree) for the specified ranges/arrays. This
function provides better performance for repeated use on the same ranges/arrays. Null and error values
are ignored.

Syntax
WD.MAXIFS(max_range, range, criteria, [ range2], [ criteria2], ...)
• max_range: The array of numeric values that you want to return the maximum value from, if the criteria
are met.
• range: The range or array of values to be evaluated according to the condition.
• criteria: The condition to use to evaluate the values.
• range2: The second set of values, or the range of cells, to be evaluated according to the condition.
• criteria2: A second condition to use to evaluate the values.

Notes
• The condition can be one of these:
• A numeric value (integer, decimal, date, time, or logical value), such as 5, 12/5/2019, or TRUE.
• A text string, such as "Name" or "November".
• An expression, such as ">9" or "<>0".
• The function isn't case-sensitive. Example: When evaluating the values in criteria_range against the
criteria, the text strings "MONTH" and "month" are considered a match.
• Whenever you use a text string or an expression as a condition, surround it with quotes.
• In text-based criteria, you can use the ? wildcard to match any single character or the * wildcard to
match any sequence of characters.
WD.MINIF

Description
Returns the minimum value from a range or array of values, according to a criterion. This function creates
an index (b-tree) for the specified range or array, providing better performance for repeated use on the
same range/array. Null and error values are ignored.

Syntax
WD.MINIF(min_range, range, criteria)
• min_range: The array of numeric values that you want to return the minimum value from, if the criteria
are met.
• range: The range or array of values to be evaluated according to the condition.
• criteria: The condition to use to evaluate the values.

Description
Returns the minimum value from a range or array of values, according to one or more criteria. This function
is the same as MINIFS but WD.MINIFS creates an index (b-tree) for the specified ranges or arrays. This
function provides better performance for repeated use on the same range/array. Null and error values are
ignored.

Syntax
WD.MINIFS(min_range, range, criteria, [ range2], [ criteria2], ...)
• min_range: The array of numeric values that you want to return the minimum value from, if the criteria
are met.
• range: The values, or the range/array of cells, to be evaluated according to the condition.
• criteria: The condition to use to evaluate the values.
• range2: The second set of values, or the range of cells, to be evaluated according to the condition.
• criteria2: A second condition to use to evaluate the values.

Description
Adds the numbers specified as arguments, if a condition is met. This function is the same as SUMIF
but WD.SUMIF creates an index (b-tree) for the specified range or array. This function provides better
performance for repeated use on the same range/array. Null and error values are ignored.

Syntax
WD.SUMIF(range, criteria, [ sum_range])
• range: The range/array of values to test.

• criteria: The condition to test each value against.

• sum_range: The range of values, or cells, to add together. If not specified, the values in the range
argument are summed.
WD.SUMIFS

Description
Adds the numbers specified in the sum_range, if a set of criteria are met. This function is the same as
SUMIFS but WD.SUMIFS creates an index (b-tree) for the specified range or array. This function provides
better performance for repeated use on the same range/array. Null and error values are ignored.

Syntax
WD.SUMIFS(sum_range, range, criteria, [ range2, criteria2], ...)
• sum_range: The range of values, or values in cells, to sum if all criteria are met.
• range: The range or array of values to test.
• criteria: The condition to test each value against.
• range2: The range of values, or cells, to test.
• criteria2: The condition to test each value against.

Matrix Functions
MIDENTITY

Description
Returns a mathematical identity matrix.

Syntax
MIDENTITY(value)
• value: The dimension of the resulting matrix.

Example

Formula Result
=MIDENTITY(3) 1 0 0 0 1 0 0 0 1

Notes
• This function returns a mathematical identity matrix. In an identity matrix, all the values in the matrix are
zero except for values in the diagonal (from upper left to lower right), which are set to one.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.
TRUNCATEMATRIX

Description
Removes rows, columns, or both, from a matrix.

Syntax
TRUNCATEMATRIX(matrix, rows, [ columns])

• matrix: The source matrix to truncate.

• rows: The number of rows in the output matrix. If you specify zero, the output matrix will have the same
number of rows as the input matrix.
• columns: The number of columns in the output matrix. If you specify zero or you don't specify a value,
the output matrix will have the same number of columns as the input matrix.

Example

Formula Result
=TRUNCATEMATRIX({1,2,3;4,5,6;7,8,9}, 2, 2 ) 1 2 4 5

Notes
• This function returns a matrix that is a result of removing rows and/or columns from the input matrix,
essentially cropping the input matrix to a new set of dimensions.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Miscellaneous Functions
CLUSTER.KMEANS

Description
Clustering is a data mining technique for grouping a set of objects into smaller groups, where each group's
members are similar to the other members in some aspect. Clustering is used in machine learning,
for example, where the goal is to find meaningful structures or to explain processes. You can cluster
quantitatively using numbers, or qualitatively using categories. CLUSTER.KMEANS is a quantitative
function that enables you to cluster a range of data in a workbook, by computing the distances between
points, and grouping centers. The function groups each data point with the cluster having the nearest
center.

Syntax
CLUSTER.KMEANS(range1, k, [ maxIterations], [ distanceMeasure], [
emptyStrategy])
• range1: The range of cells to analyze.
• k: The number of clusters to make.
• maxIterations: The maximum number of times to re-run the algorithm. If you don't specify a value, the
limit is 100.
• distanceMeasure: The algorithm used to find the distance between points. Possible values
are CanberraDistance, ChebyshevDistance, EarthMoversDistance, EuclideanDistance, or
ManhattanDistance. If you don't specify a value, the function uses EuclideanDistance.
• emptyStrategy: The strategy to use if the function finds empty clusters while running the algorithm
iterations. Possible values are ERROR, FARTHEST_POINT, LARGEST_POINTS_NUMBER, or
LARGEST_VARIANCE. If you don't specify a value, the function uses LARGEST_VARIANCE.
If you specify ERROR, the function returns #ERROR in the cell with a description. Example:
CLUSTER.KMEANS: Empty cluster in k-means.

CLUSTER.KMEANS.CENTROIDS

Description
Clustering is a data mining technique for grouping a set of objects into smaller groups, where each group's
members are similar to the other members in some aspect. Clustering is used in machine learning,
for example, where the goal is to find meaningful structures or to explain processes. You can cluster
quantitatively using numbers, or qualitatively using categories. CLUSTER.KMEANS.CENTROIDS is a
quantitative function that enables you to cluster a range of data in a workbook, by locating the center point
of each group and computing the distances between points and group centers. The function groups each
data point with the cluster having the nearest center.

Syntax
CLUSTER.KMEANS.CENTROIDS(range1, k, [ maxIterations], [ distanceMeasure], [
emptyStrategy])
• range1: The range of cells to analyze.
• k: The number of clusters to make.
• maxIterations: The maximum number of times to re-run the algorithm. If you don't specify a value, the
limit is 100.
• distanceMeasure: The algorithm used to find the distance between points. Possible values
are CanberraDistance, ChebyshevDistance, EarthMoversDistance, EuclideanDistance, or
ManhattanDistance. If you don't specify a value, the function uses EuclideanDistance.
• emptyStrategy: The strategy to use if the function finds empty clusters while running the algorithm
iterations. Possible values are ERROR, FARTHEST_POINT, LARGEST_POINTS_NUMBER, or
LARGEST_VARIANCE. If you don't specify a value, the function uses LARGEST_VARIANCE.
If you specify ERROR, the function returns #ERROR in the cell with a description. Example:
CLUSTER.KMEANS: Empty cluster in k-means.
CORRELATE

Description
Creates a new matrix by combining rows from the ranges you specify. This function is similar to a database
join.

Syntax
CORRELATE(primary_table, key_column, ignore_case, [ join_range], [
join_key_column], ...)
• primary_table: The matrix whose rows are used as the origin. The function combines rows from this
range with rows from the other ranges if their key values match.
• key_column: The column number in the primary-range whose value is used as the primary key value for
comparison with other ranges.
• ignore_case: If the type of the key column is text, then if ignore_case is TRUE, the function ignores
case when comparing with other key values. If FALSE, the function considers case in the comparisons.
• join_range: The first range to combine with a row from the primary range if the key column values are
equal.
• join_key_column: The column number in the first join range whose value is used as the key value for
comparison with the primary key.

Example
This is the original spreadsheet, with uncombined data in two different sections:

A B C D
25 Salesperson Customer Product Revenue
26 Jeffrey Aberdeen Asset HCM $1,000,000
Management
27 Jeffrey Admiral Group FIN $500,000
28 Lei Babcock HCM $506,000
International
29 Lei Barclays LER $1,500,000
30 Cian Capita LER $1,895,000
31 Cian Centrica PAY $2,004,560

G H I
25 Salesperson Manager Region
26 Jeffrey Peter EMEA
27 Lei Fredrik US
28 Cian John UK

The formula =CORRELATE(A25:D31,1,TRUE,G25:I28,1), placed in cell G37, combines the employee

information with the manager and region information.

G H I J K L
37 Salesperson Customer Product Revenue Manager Region
38 Jeffrey Aberdeen HCM $1,000,000 Peter EMEA
Asset
Management
39 Jeffrey Admiral FIN $500,000 Peter EMEA
Group
40 Lei Babcock HCM $506,000 Fredrik US
International
41 Lei Barclays LER $1,500,000 Fredrik US
42 Cian Capita LER $1,895,000 John UK
43 Cian Centrica PAY $2,004,560 John UK

Notes
• The CORRELATE() function requires at least one pair of join_range and join_key_column values. To
use other ranges, add each one with an argument specifying which column within that range has the
role of the key for that range.
• The function works like this:
1. The function examines each row in primary_table.
2. For each range you specified, the function examines each row in the range. The function compares
the value you specified as the primary key (based on the primary key column index) from the

primary_table with the value you specified as the key within the row in the range currently being
examined.
3. If their values match, then the function merges all the values from the row in that range (except the
key column) onto the end of the row from the primary table.
• A row from the primary table appears in the output only if there was at least one correlated row from
at least one of the other match ranges you specified. If you want all rows from the primary to appear,
regardless, use MERGEROWS. If you want a true database inner join, use JOIN.
• When comparing a single instance value to a string that visually appears to be the same, the function
evaluates them as equal. When comparing a single value in a multi-instance field to a string that
visually appears to be the same, the formula evaluates them as not equal.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
JOIN
DISTINCTROWS

Description
Combines a set of ranges into a single range while removing any rows that are duplicates.
DISTINCTROWS evaluates text and instance values as not distinct from each other. When the supplied
range contains both an instance value and a text string that are the same, the function returns 1 row, the
instance value. DISTINCTROWS is case-sensitive.

Syntax
DISTINCTROWS(range1, [ range2], ...)
• range1: The first range of rows.
• range2: The second range of rows.

Example
This is the original spreadsheet:

A B C D E
1 Heading1 Heading2 Heading3 Heading4
2 A 1 B 2
3 B 2 2 B
4 C 3 C 5
5 D 4 D 4

The result of =DISTINCTROWS(A2:B5,D2:E5) where the formula is in cell A6, is:

A B C D E
7 A 1
8 B 2
9 C 3

A B C D E
10 D 4
11 2 B
13 C 5

Notes
• This function takes any number of ranges. Typically each range has a similar row structure, but this is
not required.
• The function adds a row to the final result if a row containing the exact same values in the exact same
order is not already present in the result. This enables you to combine rows from different ranges
and remove duplicate rows. The function considers all values in a row when determining if a row is a
duplicate or not.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
UNIQUE
DISTINCTROWS2

Description
Combines a set of ranges into a single range while removing any rows that are duplicates.
DISTINCTROWS2 evaluates text and instance values as not distinct from each other. When the supplied
range contains both an instance value and a text string that are the same, the function returns 1 row, the
instance value. DISTINCTROWS2 is case-insensitive.

Syntax
DISTINCTROWS2(range1, [ range2], ...)
• range1: The first range of rows.
• range2: The second range of rows.

Example
This is the original spreadsheet:

A B C D E
1 Heading1 Heading2 Heading3 Heading4
2 A 1 B 2
3 B 2 2 B
4 C 3 C 5
5 D 4 D 4

The result of =DISTINCTROWS2(A2:B5,D2:E5) where the formula is in cell A6, is:

A B C D E
7 A 1
8 B 2
9 C 3
10 D 4
11 2 B
13 C 5

Related Functions
UNIQUE2
EMAIL

Description
Converts an email address into a clickable mailto link. Optionally, you can insert email details such as
email content and recipients.

Syntax
EMAIL(email, [ text], [ cc], [ bcc], [ subject], [ body])
• email: The email address.
• text: The clickable text to be displayed in the cell. If you don't include this argument, the function uses
the email address to generate the clickable text.
• cc: The copy list of recipients for the email. To separate multiple email addresses, use a character that
your email client supports.
• bcc: The blind copy list of recipients for the email. To separate multiple email addresses, use a
character that your email client supports.
• subject: The subject of the email.
• body: The body of the email.

Example

Formula Result
=EMAIL( "[email protected]", "Will Will Davis (as a clickable link)
Davis" )

GROUPBY

Description
GROUPBY is a powerful function that can often replace COUNTIF(S), AVERAGEIF(S), and SUMIF(S).
GROUPBY aggregates data, and orders the results based on the order that you specify. The grouping is
based on a key that you can predefine in the table, or you can define it using columns in the workbook. The
result looks similar to a sorted pivot table. This function is often useful as part of headcount planning.
When you group an array of cells that represent some instance values as strings and others as instances
(variables from a Workday report), GROUPBY bases the grouping on the instance name, not the instance
ID. GROUPBY groups identical names together, even when the instance IDs are different.

Syntax
GROUPBY(join_by_matrix, join_by_matrix_column_indexes, group_by_matrix,
group_by_matrix_column_indexes, group_by_matrix_aggregate_column_indexes,
[group_by_matrix_aggregate_types])
• join_by_matrix: The 1-dimensional array of unique identifiers (keys) that identifies the rows to include
when grouping.
• join_by_matrix_column_indexes: The starting position of the keys in the join_by_matrix, or the set of
columns that comprise the matching key (the column values to concatenate to create the primary key).
• group_by_matrix: The array of cells to group.
• group_by_matrix_column_indexes: The position of the column that contains the keys in the
group_by_matrix.
• group_by_matrix_aggregate_column_indexes: The positions of the columns that contain values to
group.
• group_by_matrix_aggregate_types: The operation to perform.

Argument Value Operation

0 SUM (default)
1 COUNT of non-null values
2 COUNT of non-zero numbers
3 MIN number
4 MAX number
5 AVG number

Example
A workbook has 2 sheets named Working and PEA. This is the Working sheet:

A B C D E F G H I
1 Supervisory
Cost CompanyLocation Name Jan Feb Mar PEA KEY
Org Center (HC) (HC) (HC)
2017 2017 2017
2 Finance CC-1 GMS Pleasanton
Tim 1 1 1 FinanceCC-1
Finance FinanceGMSPleasanton
3 Product CC-2 GMS Boulder Josh 0 0 1 Product
Management
Product ManagementCC-2
ProductGMSBoulder

A B C D E F G H I
4 Development
CC-3 GMS- Toronto Brian 1 1 1 DevelopmentCC-3
Development
CA DevelopmentGMS-
CAToronto
5 Product CC-2 GMS Boulder Scott 0 1 1 Product
Management
Product ManagementCC-2
ProductGMSBoulder
6 Development
CC-3 GMS- Toronto Lenny 1 1 1 DevelopmentCC-3
Development
CA DevelopmentGMS-
CAToronto
7 Sales CC-4 GMS- London Andy 0 1 1 SalesCC-4
Sales UK SalesGMS-
UKLondon
8 Finance CC-1 GMS Pleasanton
Ratna 1 1 1 FinanceCC-1
Finance FinanceGMSPleasanton
9 Sales CC-4 GMS- Toronto Aidan 0 0 1 SalesCC-4
Sales UK SalesGMS-
UKToronto
10 Sales CC-4 GMS- London Katie 1 1 1 SalesCC-4
Sales UK SalesGMS-
UKLondon
11 Total 5 7 9

The GROUPBY array formula is in cells E2:G6 of the sheet PEA:

=GROUPBY('PEA'!H2:H6,1,'Working'!A2:I10,9,{6, 7, 8})
Alternatively, instead of generating a key separately as shown in column I above and H below, you can
specify the columns that you want GROUPBY to use as the key:
=GROUPBY('PEA'!A2:G6,{1,2,3,4},'Working'!A2:H10,{1,2,3,4},{6, 7, 8})
The formula returns these results in sheet PEA:

A B C D E F G H
6 Sales CC-4 GMS-UK Toronto 0 0 1 SalesCC-4
Sales SalesGMS-
UKToronto
7 5 7 9

Note that row 7 in the sheet PEA is a simple calculation of the total headcount number; it's outside the plan
entry area.

Notes
• When doing an operation on date values, GROUPBY converts the date to a serial number before
calculating and does not restore the display format to a date. To show a date format, select Format >
Number > Date .

Related Functions
ARRAYAREA
CHART
INSTANCE

Description
Returns a single-instance value.

Syntax
INSTANCE(id, descriptor)
• id: The Workday ID string value. Example: "371ae106294a76f2702".
• descriptor: The label string. Example: "Boulder".
INSTANCE.DESCRIPTOR

Description
For a single-instance value, the function returns the descriptor (string) of the instance.

Syntax
INSTANCE.DESCRIPTOR(instance)
• instance: A reference to the instance. Example: =INSTANCE.DESCRIPTOR(A1).
INSTANCE.ID

Description
For a single-instance value, the function returns the ID of the instance.

Syntax
INSTANCE.ID(instance)
• instance: A reference to the instance. Example: =INSTANCE.ID(A1).

JOIN

Description
Performs an inner left join on two ranges.

Syntax
JOIN(primary_table, key_column, join_range, join_key_column, [ has_headers], [
ignore_case])
• primary_table: The first table to join. This range can be a matrix, range, or result of a data set transform
operation.
• key_column: The column number in the primary_table expression that acts as the primary key for the
join operation. The function numbers columns starting from 1.
• join_range: The second table to join. This range can be a matrix, range, or result of a data set transform
operation.
• join_key_column: The column number in the join_range expression that acts as the key for the join
operation. The function numbers columns starting from 1.
• has_headers: Not used.
• ignore_case: If TRUE, the function ignores the case of the text when comparing with other key values. If
FALSE, the function considers case. The default is FALSE.

Example
This is the original workbook. The data to join is in two different sections:

G H I
25 Salesperson Manager Region
26 Jeffrey Peter EMEA
27 Lei Fredrik US
28 Cian John UK

The formula =JOIN(A25:D31,1,G25:I28,1,,TRUE), placed in cell L4, combines the employee information
with the manager and region information. The Salesperson, Manager, and Region are on the left because
that data range has fewer rows.

L M N O P Q
4 Jeffrey Peter EMEA Aberdeen HCM $1,000,000
Management
5 Jeffrey Peter EMEA Admiral FIN $500,000
Group
6 Lei Fredrik US Babcock HCM $506,000
International
7 Lei Fredrik US Barclays LER $1,500,000
8 Cian John UK Capita LER $1,895,000
9 Cian John UK Centrica PAY $2,004,560

Notes
• This function does an inner left join. The function considers the range with fewer rows to be the left
table.
• For each row in the left table, the function checks to see if there is a matching row in the right table by
comparing the key values in the key columns you specified. If a match exists, the function creates a
new row by joining the row from each of the tables with the key value only appearing one time. A row
appears in the output only if the join condition is satisfied. It is also possible for a row from the left table
to appear multiple times if multiple rows in the right table have a matching key value.
• If you want all rows from the primary_table to always be present in the output, use the MERGEROWS
function instead.
• When comparing a single instance value to a string that visually appears to be the same, the function
evaluates them as equal. When comparing a single value in a multi-instance field to a string that
visually appears to be the same, the formula evaluates them as not equal.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
CORRELATE
MATCHCOMPOSITE

Description
A common use case for MATCHCOMPOSITE is to consolidate column data from 2 sheets into 1, where
you have data on a sheet, along with notes about that same data in a column on a different sheet.
MATCHCOMPOSITE copies values in one or more columns from the location to the right of a source array,
and returns values to the right of a destination array. You use a composite key of columns to match copied
data to the correct rows in the destination.

Syntax
MATCHCOMPOSITE(destination_matrix, destination_column_indexes, source_matrix,
source_column_indexes, return_column_indexes, [ ifNA])
• destination_matrix: The area of data in the destination.
• destination_column_indexes: The position of the columns that make up the composite key in the
destination.

• source_matrix: The array of the data in the source. You can specify only a cell range, not a column
range.
• source_column_indexes: The position of the columns that make up the composite key in the source.
• return_column_indexes: The position of the columns in the source that you want the formula to return.
• ifNA: The default value to return if the function doesn't find a match. The default is an empty string.

Related Functions
MATCH
GROUPBY
MERGECOLUMNS

Description
Merges columns by placing them side by side into a new range.

Syntax
MERGECOLUMNS(range1, [ range2], ...)
• range1: The first range.
• range2: The second range.

Example

Formula Result
=MERGECOLUMNS({1,2;3,4},{10,20,30;40,50,60}) 1 2 10 20 30 3 4 40 50 60

Notes
• This function creates a new range by combining all the range arguments. It starts with the first range
and then adds the second range on its right side, aligning the top of the new range with the resulting
range. This continues for all subsequent ranges. In the resulting range, the number of rows equals the
number of rows in the largest range. If a range does not have as many rows as the maximum range,
those additional rows are filled with null values. The number of columns in the resulting range equals
the sum of the columns in all of the ranges. Duplicate columns are not removed.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
REMOVECOLUMNS
MERGEROWS

Description
Merges rows by placing them one below the other into a new range.

Syntax
MERGEROWS(range1, [ range2], ...)
• range1: The first range.

• range2: The second range.

Example

Formula Result
=MERGEROWS({1,2;3,4},{10,20,30;40,50,60}) 1 2 3 4 10 20 30 40 50 60

Notes
• This function creates a new range by combining all the range arguments; it starts with the first range
and then adds the second range underneath, left-aligning the new range with the resulting range. This
continues for all subsequent ranges. In the resulting range, the number of columns equals the widest
range in the input. If a range does not have as many columns as the widest range, those additional
columns are filled with null values. The number of rows in the resulting range equals the sum of the
rows in all of the ranges. Duplicate rows are not removed.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
REMOVEROWS
MI.COUNT

Description
Returns the number of single instances inside a multi-instance value.

Syntax
MI.COUNT(instances)
• instances: The instances value.
MI.INDEX

Description
Returns the instance at a specific index in a multi-instance value.

Syntax
MI.INDEX(instances, [ index])
• instances: The instances value. This value can be an array.
• index: The index of the instance.
MINUS

Description
Returns all rows from a first range that do not appear in any of the other supplied ranges.

Syntax
MINUS(range1, [ range2], ...)
• range1: The range to subtract matching rows from.

• range2: The range to subtract from the base range. You can subtract any number of ranges from the
start range.

Example
This is the original spreadsheet:

A B C
1 Cost Center Q1 Q2
2 6010:Benefits Expenses 6200:Marketing 6010:Benefits Expenses
3 6300:Office & 4000:Revenue 6100:Facilities Taxes
Administrative
4 6100:Facilities 5000:Cost of Sales 6300:Office &
Administrative
5 6400:Legal & Service 6870:Talent Acquisition 6500:Information
Fees Technology
6 6800:Travel & 6000:Salaries and 6700:Depreciation
Entertainment Wages
7 6870:Talent Acquisition 6400:Legal & Service 6300:Office &
Fees Administrative

The formula =MINUS(A2:A7,B2:B7,C2:C7), placed in cell A8, returns any values in the first range that are
not present in subsequent ranges (cost centers that were not budgeted for in Q1 or Q2).

A
8 6800:Travel & Entertainment

Notes
• The result of this function is the subset of rows from range1 that do not appear in any of the other
supplied range arguments. A row appears in range1 if all values in the row from a subsequent range
are identical (and in the same order) to values in range1.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
COMPARE
MULTIINST

Description
Create a multi-instance value from a comma-separated list of single instance values.

Syntax
MULTIINST(instance, ...)
• instance: The list of single instance values.

Example
Where cells A4, A5, and A6 contain single instance values, the formula:
=MULTIINST(A4,A5,A6)
creates a multi-instance value in the cell, containing the instances in cells A4-A6.
NOTIFYIF

Description
Sends up to 1,000 notifications if a value in the specified criterion changes to meet a condition. You can
send a notification to a user whether or not they have access to the workbook. If the function exceeds the
limit, notifications stop and the #ERROR indicator displays in the cell containing the function. When you
hover the cursor over the cell, a message describes the error.

Syntax
NOTIFYIF(range, criteria, [ user_names], [ subject], [ message], [
send_on_each])
• range: The range to evaluate the criteria for.
• criteria: The string expression to evaluate against the range. The format is the same as functions such
as SUMIF() and COUNTIF().
• user_names: The array or list of users to send the notification to. If you don't include this argument, the
function uses the user_name of the current user (the user composing the function).
• subject: The text string to use as the subject of the Workday (inbox) notification. If you include a subject,
Workday adds a colon character at the end of the string.
• message: The text to use as the body of the notification. These HTML tags are supported: , ,
, and .
• send_on_each: If TRUE, the function sends a notification on each value in the range that matches the
criterion (TRUE). If FALSE, the function sends a notification only if all the values in the range meet the
criterion. The default is TRUE.

Example

Formula Result
=NOTIFYIF(A1:A3,"=won","dave.smith","Contest Send this notification to dave.smith:
results","you won!" )
"Contest results: You won!"
if a cell in the range A1:A3 equals won .
=NOTIFYIF(E8,"<"&E7,"tserrano","Forecast Send a notification to tserrano if the value in E8 is
Drop",CONCAT(A8, " of $",E8," has fallen below less than E7. This example uses data in the sample
target of $", E7)) workbook on Community. Example notification:
"Forecast Drop: EMEA Forecast of $3214321 has
fallen below target of $3530400"

=NOTIFYIF(A1,">"&0.5,"tserrano","Sales Send a notification to tserrano if the value in A1 is

Goal",TEXT(A1,"0%")&" of your employees met greater than 0.5. The TEXT function causes the
their sales goal.") A1 value to be formatted as an integer percentage.
Example notification:
"Sales Goal: 61% of your employees met their
sales goal.")

Example Notifications Using an Array of Values

Here's an example of how to use NOTIFYIF with an array of values.
The formula in cell A8 puts the different users listed in A3, A4 and A5 into an array:

When including the reference cell in the NOTIFYIF formula, use ARRAYAREA(A8):

Remember to submit the formula using the array keyboard shortcut: Ctrl+Alt+Enter (Windows) or
Command+Option+Enter (Mac).
The inbox notification for the formula looks similar to this, if Oliver Reynolds submitted the formula:

The email notification looks similar to this:

Notes
• The function sends a notification only if a value changes to meet a condition. If, for example, a live data
refresh occurs and a condition that was previously TRUE (notification was sent) remains TRUE when
the schedule runs, no notification is sent. However, a notification is sent if you recalculate the workbook
because this is the equivalent of re-submitting the formula from the cell.
• The user_names format in your tenant might vary from the examples.
• This function evaluates a criterion expression against all the values in the range you specified. If
send_on_each is true, then the function sends a notification for each criterion match in the range. If
send_on_each is false, the function sends a notification only if all values in the match meet the criterion.
The form of the criterion is the same as for SUMIF() and COUNTIF().
• The function generates a Workday notification. If emails are enabled in your environment, an email
is also sent, but the email subject is auto-generated and doesn't match the subject argument of the
notification.
• Workday identifies the sender of the notification as the user who placed the formula into the cell.
• This function returns the value TRUE if it sent a notification or FALSE if it didn't.

Related Functions
NOTIFYIFS
NOTIFYIFS

Description
Sends up to 1,000 notifications if values in the specified criteria change to meet multiple conditions. You
can send a notification to a user whether or not they have access to the workbook. If the function exceeds
the limit, notifications stop and the #ERROR indicator displays in the cell containing the function. When you
hover the cursor over the cell, a message describes the error.

Syntax
NOTIFYIFS(range1, criteria1, [ user_names], [ subject], [ message], [
send_on_each], [ range2, criteria2], ...)
• range1: A range to evaluate the criteria for.
• criteria1: The string expression to evaluate against the range. The format is the same as functions such
as SUMIF() and COUNTIF().
• user_names: The array or list of users to send the notification to. If you don't include this argument, the
function uses the user_name of the current user (the user composing the function).
• subject: The text string to use as the subject of the Workday notification. If you include a subject,
Workday adds a colon character at the end of the string.
• message: The text to use as the body of the notification. These HTML tags are supported: , ,
, and .
• send_on_each: If TRUE, a notification is sent on each value in the range that matches the criterion
(TRUE). If FALSE, the notification is sent only if all the values in the range meet the criterion. The
default is TRUE.
• range2: A range to evaluate the criteria for.
• criteria2: The string expression to evaluate against the range.

Example
A1:B3 contains:
1 2 1 2 1 2

Formula Result
=NOTIFYIFS(A1:A3,1,,,,false,B1:B3,2) TRUE

Notes
• The function sends a notification only if a value changes to meet a condition. If, for example, a live data
refresh occurs and a condition that was previously TRUE (notification was sent) remains TRUE when
the schedule runs, no notification is sent. However, a notification is sent if you recalculate the workbook
because this is the equivalent of re-submitting the formula from the cell.
• This function evaluates a criterion expression against all the values in the range you specified. If
send_on_each is true, then the function sends a notification for each criterion match in the range. If
send_on_each is false, the function sends a notification only if all values in the match meet the criterion.
The form of the criterion is the same as in SUMIFS() and COUNTIFS().
• The difference between NOTIFYIFS() and NOTIFYIF() is that in NOTIFYIFS(), the condition for sending
a notification is met only if every criterion is met against its corresponding range. You can specify any
number of range/criterion pairs; you must specify them as matching pairs. In addition, the shape of
each range must match the shape of the first range (they must all have the same number of rows and
columns). Example: If we have three range/criterion pairs, then a condition is met if the criterion for

each range is met for a specific cell in the range. If send_on_each is false, then the condition must be
met for every cell in every range in order for the function to send a notification.
• The function generates a Workday notification. If emails are enabled in your environment, an email
is also sent, but the email subject is auto-generated and doesn't match the subject argument of the
notification.
• Workday identifies the sender of the notification as the user who placed the formula into the cell.
• The function returns the value TRUE if it sent a notification or FALSE if it didn't.

Related Functions
NOTIFYIF
REMOVECOLUMNS

Description
Removes one or more columns from the sheet. The function removes the number_of_columns, starting at
and including start_column.

Syntax
REMOVECOLUMNS([range], [number_of_columns], [start_column])
• range: The matrix to remove columns from.
• number_of_columns: The number of columns to remove. Use a value greater than 0 to remove
start_column and subsequent columns. Use a value less than 0 to remove start_column and previous
columns.
• start_column: The starting column to remove. You can set start_column to -1 to start removing columns
from the right side of the matrix instead of the left.

Example
The examples are based on this workbook:

A B C D E
1 Item 2014 2015 2016 2017
2 100 6452 6557 6772 6457
3 200 3458 3568 4668 3455
4 300 6791 6552 5382 6235
5 400 3524 6592 3562 3899
6 500 6458 3112 2855 3298

The result of =REMOVECOLUMNS(A1:E6,3,2) is shown in this table:

Item 2017
100 6457
200 3455
300 6235
400 3899
500 3298

The result of =REMOVECOLUMNS(A1:E6,-4,-1) is shown in this table:

Item
100
200
300
400
500

Notes
• In the results, formatting from the original cells is not preserved.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
MERGECOLUMNS
REMOVEROWS

Description
Removes one or more rows from the referenced area. The function removes the number_of_rows following
start_row, starting at and including start_row. Use REMOVEROWS without specifying any rows in order to
remove the first (heading) row.

Syntax
REMOVEROWS([range], [number_of_rows], [start_row])
• range: The matrix to remove the rows from.
• number_of_rows: The number of rows to remove. Use a value greater than 0 to remove start_row and
subsequent rows. Use a value less than 0 to remove start_row and previous rows.
• start_row: The starting row to remove. You can set start_row to -1 to start removing rows from the
bottom of the matrix instead of the top.

Example
The examples are based on this workbook:

A B C D E
1 Item 2014 2015 2016 2017
2 100 6452 6557 6772 6457
3 200 3458 3568 4668 3455
4 300 6791 6552 5382 6235
5 400 3524 6592 3562 3899
6 500 6458 3112 2855 3298

The result of =REMOVEROWS(A1:E6,3,2) is shown in this table:

A B C D E
1 Item 2014 2015 2016 2017
2 400 3524 6592 3562 3899
3 500 6458 3112 2855 3298

The result of =REMOVEROWS(A1:E6,-4,-1) is shown in this table:

A B C D E
1 Item 2014 2015 2016 2017
2 100 6452 6557 6772 6457

The result of =REMOVEROWS(A1:E6) is shown in this table (headings are removed):

A B C D E
1 100 6452 6557 6772 6457
2 200 3458 3568 4668 3455
3 300 6791 6552 5382 6235
4 400 3524 6592 3562 3899
5 500 6458 3112 2855 3298

Related Functions
ARRAYAREA
MERGEROWS
SELECT

Description
Selects data from a workbook range, a defined name, or a Workday report. The SELECT function is
similar to an SQL SELECT statement. The primary rules for writing a SELECT statement are: Data that
you reference in a select statement must have a header name. Surround the select statement with double
quotes. Surround strings with single or double quotes. If you reference a column heading or table name
that contains spaces or special characters, enclose it in backticks. Use question marks for parameters.
If the SELECT formula doesn't finish calculating within 30 minutes, it returns an #ERROR. SELECT can
process up to 5 million rows, but the number of rows processed might not exactly match the number of
returnable rows due to the aggregation that SELECT performs. To see working examples of the SELECT
function, find the "Worksheets Function Example Workbooks" page on Community or paste this link into
your browser: https://community.workday.com/node/408872.
Keep in mind that the SELECT function is not intended as a replacement for the Data Wizard.

Syntax
SELECT(select_statement, [ parameter], ...)
• select_statement: The select statement. The statement is similar to an SQL select statement. Enclose
the select statement in double quotes. The basic format is: "SELECT column1, [column2], ...
FROM table" where column is the data to return and table is the data source to select from.
You can embed functions in the SELECT statement such as COUNT, AVG, SUM, LIMIT, and more.
The complete list of functions that SELECT supports is below.
When doing an operation on date values in your SELECT formulas, keep in mind that Worksheets
works differently from SQL syntax. Worksheets calculations treat dates as serial numbers. Example:
The date March 20, 2023 is represented as the serial number 45005. Also, SQL automatically converts
string dates for calculations, but Worksheets doesn't.
If the string from or where exists in a column name, you must surround it with quotes because from and
where are reserved words in SQL.
In the FROM clause of the statement, you can use values such as a:
• Workday report.
• Defined name.
• Column, row, or area range.
• Parameter that you specify as an argument.
• parameter: A statement parameter.

Examples
We'll use this table to show some simple examples:

header1 header2 header3

1 a red
2 b orange
3 c orange
4 d red
5 e red

The formula:
=SELECT("SELECT header1,header3 FROM ? WHERE header3 = ?",A1:C6,"red")
has this result:

header1 header3
1 red
4 red
5 red

Automatic recalculation and the parameter argument. We recommend using the parameter argument
of the function to reference data; Worksheets considers these references to be data dependencies, so
the SELECT formula runs automatically when you change the data in the referenced cells. If you use the
SELECT statement to refer to data instead, the formula doesn't re-run automatically if the data changes,
and even selecting Data > Recalculate doesn't cause the formula to run again.

In the following formula, we use the parameter argument to reference the data. If the data changes in the
range A1:C6, Worksheets automatically recalculates and updates the result:
=SELECT("SELECT header1,header3 FROM ?",A1:C6)
In the following formula, we use the SELECT statement to reference the data. If the data changes in the
range A1:C6, Worksheets does not recalculate:
=SELECT("SELECT header1,header3 FROM `A1:C6`")
Defined name. In these examples, an area was given the defined name all_employees:
• =SELECT("SELECT employeeName FROM all_employees")
• =SELECT("SELECT employeeName FROM ?", all_employees)
Column, row, or range. You can refer to a column, row, or area in the same sheet, a different sheet, or in
another workbook. If you don't specify a sheet, the range must be on the current sheet.
• =SELECT("SELECT employeeName FROM `$A:$G`")
• =SELECT("SELECT employeeName FROM `AllEmployeesSheet!$A:$G`")
• =SELECT("SELECT employeeName FROM `'All Employees Sheet'!$A:$G`")
• =SELECT("SELECT employeeName FROM ?",$A:$G)
• =SELECT("SELECT employeeName FROM ?",'All Employees Sheet'!$A:$G)
• =SELECT("SELECT employeeName FROM ?",All_Employees_Sheet!$A:$G)
• =SELECT("SELECT employeeName FROM ?", !'Other Workbook Name'!'All Employees Sheet'!A:G)
More Examples and Results

Formula Result
SELECT("SELECT employeeID, employeeName Returns the employeeID and employeeName
FROM `AllEmployeesSheet!$A:$G`") from rows A through G of the sheet named
AllEmployeesSheet.
SELECT("SELECT COUNT(employeeLastName) Returns the number of rows in the
FROM AllEmployeesSheet") employeeLastName column in the sheet named
AllEmployeesSheet.
SELECT("SELECT employeeFirstName, Return the first name, last name, and rating of the 3
employeeLastName, employeeRating FROM highest rated employees.
`AllEmployeesSheet!$A:$G` ORDER BY
employeeRating DESC LIMIT 3")

Workday report. Query data from a Workday report.

• =SELECT("SELECT employeeName FROM WorkdayReports.AllEmployees") where the report name is
AllEmployees.
• =SELECT("SELECT employeeName FROM WorkdayReports.`All Employees`") where the report name
is All Employees.
• =SELECT("SELECT * from WorkdayReports.`All Employees`") selects all rows from the report.

SELECT Functions: Constants

TRUE CURRENT_DATE
FALSE CURRENT_TIME
NULL CURRENT_TIMESTAMP

SELECT Functions: Operators and Logical

UNION JOIN INTERSECT INNER JOIN

UNION ALL LEFT JOIN EXCEPT BETWEEN
NOT BETWEEN IN * <=
STRING CONCAT || NOT IN / <>
% (MOD) parentheses () + !=
BITSHIFT LEFT << IF - >=
BITSHIFT RIGHT >> UNARY - + ~ & "
EXISTS LOGICAL ! | LIKE
NOT EXISTS NOT < NOT LIKE
1
IS NULL AND > CASE
IS NOT NULL OR =
IFNULL ISNULL POW

1
Including WHEN THEN ELSE END keywords

SELECT Functions: Scalar, Substring

DAYOFMONTH YEAR LOWER UPPER

HOUROFDAY COALESCE LTRIM DATE Y M D
MINUTE NULLIF RTRIM DATETIME Y M D H M S
MONTH ROUND SUBSTRING INSTANCE (ID and description)
SECOND LENGTH TRIM DATEDIF
REPLICATE STUFF LOCATE INSTR

SELECT Functions: Math, Financial, Statistical

ABS COUNT LOG10 Q (Quarter)

AVG FLOOR MAX SQRT
CEIL LOG MIN SUM
LIMIT ASC DESC

Notes
• We recommend using the parameter section of the function to reference data; Worksheets considers
these references to be data dependencies, so the SELECT formula runs whenever you select Data >
Recalculate. The data you refer to in the SELECT statement portion of the formula isn't considered
dependent data, so selecting Data > Recalculate doesn't cause the formula to run again even if the
underlying data changed.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

SEQUENCE

Description
Creates an array of sequential values, such as a numbers or a series of dates. This function can be helpful
when creating dynamic models. Example: You are creating an ad hoc forecasting model and you want to
create a dynamic sequence of dates based on time and not based on the live data in the workbook.

Syntax
SEQUENCE(rows, [ columns], [ start], [ step])
• rows: An integer for the number of rows to return.
• columns: An integer for the number of columns to return.
• start: The starting number for the sequence.
• step: The number to increase each value by. Example: When start is for date values, a step value of 7
increments a date series in weekly (7 day) increments.

Example
To download working examples of the SEQUENCE function in a workbook, see https://
collaborate.workday.com/t5/-/-/m-p/910596 .
SORT

Description
Sorts an existing matrix and returns a new matrix. SORT() accepts one sort direction and sorts all columns
you specified based on that direction.

Syntax
SORT(matrix, [ ascending], [ sort_column], ...)
• matrix: The matrix to sort.
• ascending: If TRUE, the values are sorted in ascending order; if FALSE, the values are sorted in
descending order. The default is TRUE.
• sort_column: One or more column names or column positions to use as the columns to sort on. If you
don't specify any columns, then the first (left-most) column is used.

Example
This is the original spreadsheet:

A B C D E
1 Name Grade
2 Joe 85
3 Alice 92
4 Joe 90

The result of =SORT(A1:B4,true,"Name","Grade") is:

Name Grade
Alice 92
Joe 85

Name Grade
Joe 90

Notes
• To specify a different sort direction for each column being sorted, use SORT2().
• This function sorts the rows in the source matrix and returns a new matrix reflecting the sorted rows.
The order of the rows is determined by the values in the sort_column and the direction you specified
(ascending or descending).
• Specify sort columns either by name (as text strings without any surrounding square brackets) or by
position (where the first column is in position 1). You can mix these values (specifying some by name
and others by position).
• When you specify more than one sort column, the function breaks ties by sorting the values in each
subsequently specified column. Example: If the first column has three values of the string "hello" ,
and you specified a second column, the function sorts the values in that column for the three rows that
have "hello" in the first column. This determines the final order of those three columns.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
ARRAYAREA
SORT2
SORT2

Description
Sorts an existing matrix and returns a new matrix. SORT2 accepts pairs of parameters, specifying the
column to sort by and the sort direction for that column. When ties occur during the sort, arguments for
columns after the first column you specified are used.

Syntax
SORT2(matrix, [ sort_column_1, ascending_1], ...)
• matrix: The matrix to sort.
• sort_column_1: The column name or position of the value in the top priority sorting row. If you specify a
sort_column, you must also specify a corresponding ascending boolean.
• ascending_1: If TRUE, the function sorts the values in the associated column in ascending order; if
FALSE, the function sorts the values in the associated column in descending order.

Example
This is the original spreadsheet:

A B
1 Name Grade
2 Joe 85
3 Alice 92
4 Joe 90

A B
5 Luis 92
6 Xibin 85
7 Alice 79
8 Joe 82
9 Luis 95
10 Xibin 88
11 Alice 97

The result of =SORT2(A1:B10,1,,2,FALSE) is:

Name Grade
Xibin 88
Xibin 85
Luis 95
Luis 92
Joe 90
Joe 85
Joe 82
Alice 97
Alice 92
Alice 79

Notes
• You can specify up to 8 column/direction pairs.
• To sort all the columns you specified in only one direction, you can use SORT.
• This function sorts the rows in the source matrix and returns a new matrix reflecting the sorted rows.
The order of the rows is determined by the value in sort_column_n and the direction you specified
(ascending or descending).
• Specify sort columns either by name (as text strings without any surrounding square brackets) or by
position (where the first column is in position 1). You can mix these values (specifying some by name
and others by position). If you use the column header name (string) the function preserves the column
headers, but if you use the column indexes (numbers), the function sorts the headers as data.
• When you specify more than one sort column, the function breaks ties by sorting the values in each
subsequently specified column. Example: If the first column has three values of the string "hello" ,
and you specified a second column, the function sorts the values in that column for the three rows that
have "hello" in the first column. This determines the final order of those three columns.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
ARRAYAREA
SORT
SORT3
SORT3

Description
Sorts an existing matrix and returns a new matrix. SORT3 assumes that the first row is a header, and
returns the header as the first row in the results. SORT3 accepts pairs of parameters, specifying the
column to sort by and the sort direction for that column. When ties occur during the sort, arguments for
columns after the first column you specified are used.

Syntax
SORT3(matrix, [ sort_column_1, ascending_1], ...)
• matrix: The matrix to sort. SORT3 assumes that the first row is a header, and returns the header as the
first row in the results.
• sort_column_1: The column name or position of the value in the top priority sorting row.
• ascending_1: If TRUE, the function sorts the values in the associated column in ascending order; if
FALSE, the function sorts the values in the associated column in descending order.
• sort_column_2: The column name or position of the value in the 2nd priority sorting row.
• ascending_2: If TRUE, the function sorts the values in the associated column in ascending order; if
FALSE, the function sorts the values in the associated column in descending order.
• sort_column_3: The column name or position of the value in the 3rd priority sorting row.
• ascending_3: If TRUE, the function sorts the values in the associated column in ascending order; if
FALSE, the function sorts the values in the associated column in descending order.

Example
This is the original spreadsheet:

A B
1 Name Grade
2 Joe 85
3 Alice 92
4 Joe 90
5 Luis 92
6 Xibin 85
7 Alice 79
8 Joe 82
9 Luis 95
10 Xibin 88
11 Alice 97

The result of =SORT3(A1:B10,1,,2,FALSE) is:

Name Grade
Xibin 88
Xibin 85
Luis 95
Luis 92
Joe 90
Joe 85
Joe 82
Alice 97
Alice 92
Alice 79

Notes
• You can specify up to 8 column/direction pairs. The function ignores empty sort columns.
• Empty parameter pairs are ignored. For strict parameter pairs you can use SORT2.
• To sort all the columns you specified in only one direction, you can use SORT().
• This function sorts the rows in the source matrix and returns a new matrix reflecting the sorted rows.
The order of the rows is determined by the value in sort_column_n and the direction you specified
(ascending or descending).
• Specify sort columns either by name (as text strings without any surrounding square brackets) or by
position (where the first column is in position 1). You can mix these values (specifying some by name
and others by position). With either method, the function preserves the header and returns it as the first
row of results.
• When you specify more than one sort column, the function breaks ties by sorting the values in each
subsequently specified column. Example: If the first column has three values of the string "hello" ,
and you specified a second column, the function sorts the values in that column for the three rows that
have "hello" in the first column. This determines the final order of those three columns.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
ARRAYAREA
SORT
SORT2
TRIMCOLUMNS

Description
Removes trailing blank columns from a range, when the data is a result of an unconstrained array formula.

Syntax
TRIMCOLUMNS(range)
• range: The range to trim.

Example
When you use an array formula such as =SampleWorkerData!3:5, which contains an unconstrained row
reference, the formula returns a blank in each cell across from the cells containing data in rows 3, 4, and 5.
The formula =TRIMCOLUMNS(SampleWorkerData!3:5) removes the trailing columns containing blanks in
the cells.

Notes
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.
TRIMROWS

Description
Removes trailing blank rows from a range, when the data is a result of an unconstrained array formula.

Syntax
TRIMROWS(range)
• range: The range to trim.

Example
When you use an array formula such as =SampleWorkerData!A:C, which contains an unconstrained
column reference, the formula returns blanks in each cell below the cells containing data in columns A, B,
and C.
The formula =TRIMROWS(SampleWorkerData!A:C) removes the trailing blank rows in the cells.

Description
Returns a matrix whose rows are unique according to the specified keys. The function returns only unique
rows, based on the values in the specified columns. This function is similar to DISTINCTROWS(), but
UNIQUE() takes a single range and a set of columns. UNIQUE is case-sensitive.

Syntax
UNIQUE(range, col1, [ col2], ...)
• range: The matrix to extract unique rows from.
• col1: The name of a column to use as a key in determining whether a row is unique.
• col2: The name of a column to use as a key in determining whether a row is unique.

Example
This is the original spreadsheet:

A B C D E
1 Name Grade
2 Joe 85
3 Alice 92
4 Joe 90

The result of =UNIQUE(A1:B4,"Name") is:

Name Grade
Joe 85
Alice 92

Notes
• UNIQUE() is similar to DISTINCTROWS(). DISTINCTROWS() uses all the values in a row to determine
whether the row is different from other rows, but UNIQUE() uses only the values in the specified
columns. UNIQUE() filters the range so that it returns only unique rows based on the values in the
specified columns. The first row it considers unique is the one it returns; it doesn't return subsequent
duplicate rows.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
DISTINCTROWS
UNIQUE2

Description
Returns a matrix whose rows are unique according to the specified keys. The function returns only unique
rows, based on the values in the specified columns. This function is similar to DISTINCTROWS2(), but
UNIQUE2() takes a single range and a set of columns. UNIQUE2 is case-insensitive.

Syntax
UNIQUE2(range, col1, [ col2], ...)
• range: The matrix to extract unique rows from.
• col1: The name of a column to use as a key in determining whether a row is unique.
• col2: The name of a column to use as a key in determining whether a row is unique.

Example
This is the original spreadsheet:

A B C D E
1 Name Grade
2 Joe 85
3 Alice 92

A B C D E
4 Joe 90

The result of =UNIQUE2(A1:B4,"Name") is:

Name Grade
Joe 85
Alice 92

Notes
• UNIQUE2() is similar to DISTINCTROWS2(). DISTINCTROWS2() uses all the values in a row to
determine whether the row is different from other rows, but UNIQUE2() uses only the values in the
specified columns. UNIQUE2() filters the range so that it returns only unique rows based on the
values in the specified columns. The first row it considers unique is the one it returns; it doesn't return
subsequent duplicate rows.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.

Related Functions
DISTINCTROWS2
URL

Description
Converts a URL into a clickable link on a sheet.

Syntax
URL(url, [ label], [tooltip])
• url: The URL. For linking within a workbook, precede the path with a pound sign (#).
• label: The clickable text to display in the cell. If you don't include this argument, the function uses the url
argument as the clickable text. You can use a cell reference to contain the label.
• tooltip: The text to display when the user hovers the cursor over the cell. If you don't include this
argument, the function uses the label argument as the clickable text. You can use a cell reference to
contain the tooltip.

Example

Formula Result
=URL("http://www.workday.com","Workday") Workday (as a clickable link)
=URL("http://www.workday.com","Workday","Open Workday (as a clickable link), with a tooltip of "Open
link in new browser window") link in new browser window"
=URL("#"&REMOVEROWS(INFO("wd.sheet.names")))
Creates a clickable list of links to the sheets of
the workbook; this essentially provides a Table of
Contents of the workbook tabs.

Notes
• This function is similar to the HYPERLINK function; however, to maintain compatibility with Excel,
HYPERLINK doesn't have the optional tooltip argument.
• Keep in mind that if you use the right-click (context) menu in a Microsoft® Excel® workbook to create a
hyperlink, and then you upload the workbook to Worksheets, it isn't converted into a URL function; it
becomes a link-formatted cell containing a URL.

Related Functions
HYPERLINK
URLTEXT

Description
Returns, as a string, the anchor text component of a URL.

Syntax
URLTEXT(url)
• url: The URL, typically the output of the URL function.

Example

Formula Result
=URLTEXT(URL("http:// Workday (as plain text)
www.workday.com","Workday"))

WD.ARRANGECOLUMNS

Description
Creates a new range from an existing range, with the columns ordered according to the
specified indexes. You can add an empty column by including a null index value. Example:
=WD.ARRANGECOLUMNS([range],1,2,3,,4) inserts a blank column between the 3rd index value and
4th index value.

Syntax
WD.ARRANGECOLUMNS(range, column_indexes, ...)
• range: The range to create the new range from.
• column_indexes: The column indexes. The indexes must be in the range of 1 to the number of columns
in the range.

Example
The example is based on this range:

A B
1 4 3
2 8 9
3 14 11

The formula =WD.ARRANGECOLUMNS(A1:B3,1,1,2,2) in cell A5 has these results:

A B C D
5 4 4 3 3
6 8 8 9 9
7 14 14 11 11

Notes
• The index values can repeat, if desired, and can be in any order.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.
WD.ARRANGEROWS

Description
Creates a new range from an existing range, with the rows ordered according to the
specified indexes. You can add an empty row by including a null index value. Example:
=WD.ARRANGEROWS([range],1,2,3,,4) inserts a blank row between the 3rd index value and 4th
index value.

Syntax
WD.ARRANGEROWS(range, column_indexes, ...)
• range: The range to create the new range from.
• column_indexes: The row indexes. The indexes must be in the range of 1 to the number of rows in the
range.

Example
The example is based on this range:

A B
1 4 3
2 8 9
3 14 11

The formula =WD.ARRANGEROWS(A1:B3,1,1,2,2,3,3) submitted in cell A5 has these results:

A B
5 4 3
6 4 3
7 8 9
8 8 9
9 14 11
10 14 11

Description
Returns live data (report) metadata based on the reference and option that you specify. Remember to
submit the formula as an unconstrained formula using Ctrl+Alt+Enter (on Windows) or Command+Option
+Enter (on Mac).

Syntax
WD.LIVEDATA(reference, option)
• reference: The root cell (top left cell) of the live data range.
• option: The metadata to return. Valid options are 0-4 , 100-104, and 10-29. If there are no results for the
option, the function returns an error. Example: If you select option 3 (report prompts used) and there are
no prompts in the report, the function returns the #N/A error. For detailed descriptions of the options,
see the Function Reference in the User Guide (Help > User Guide).

Function Options and Descriptions

Option Description Notes

100 Report metadata (all). With header. All metadata, as described in the
rest of this table.

101 Report column metadata: Name, XML Alias, Type values: STRING, STRINGS,
Type. With header. STRING_RICH, NUMERIC,
NUMERIC_UNITS, CURRENCY,
DATE, DATES, DATE_TIME,
TIME, BOOLEAN, BOOLEANS,
URL, URLS, INSTANCE,
INSTANCES

102 Columns included: Name, XML Alias, Type, Type values: COLUMN,
Editable, Key. With header. EXPRESSION, FORMULA,
NOTE
Editable values: TRUE/FALSE
Key values: TRUE/FALSE

103 Report prompts used: Name, XML Alias, Type. Type values: STRING, STRINGS,
With header. STRING_RICH, NUMERIC,
NUMERIC_UNITS, CURRENCY,
DATE, DATES, DATE_TIME,
TIME, BOOLEAN, BOOLEANS,
URL, URLS, INSTANCE,
INSTANCES

Option Description Notes

104 Report prompts with settings: Name, XML Alias, Type values: STRING, STRINGS,
Type, Value, Prompt Type. With header. STRING_RICH, NUMERIC,
NUMERIC_UNITS, CURRENCY,
DATE, DATES, DATE_TIME,
TIME, BOOLEAN, BOOLEANS,
URL, URLS, INSTANCE,
INSTANCES
Prompt Type values:
AS_SPECIFIED, DO_NOT_USE,
USE_DEFAULT

0 Report metadata (all). No header. All metadata, as described in the

rest of this table.

1 Report column metadata: Name, XML Alias, Type values: STRING, STRINGS,
Type. No header. STRING_RICH, NUMERIC,
NUMERIC_UNITS, CURRENCY,
DATE, DATES, DATE_TIME,
TIME, BOOLEAN, BOOLEANS,
URL, URLS, INSTANCE,
INSTANCES

2 Columns included: Name, XML Alias, Type, Type values: COLUMN,

Editable, Key. No header. EXPRESSION, FORMULA,
NOTE
Editable values: TRUE/FALSE
Key values: TRUE/FALSE

3 Report prompts used: Name, XML Alias, Type. Type values: STRING, STRINGS,
No header. STRING_RICH, NUMERIC,
NUMERIC_UNITS, CURRENCY,
DATE, DATES, DATE_TIME,
TIME, BOOLEAN, BOOLEANS,
URL, URLS, INSTANCE,
INSTANCES

4 Report prompts with settings: Name, XML Alias, Type values: STRING, STRINGS,
Type, Value, Prompt Type. No header. STRING_RICH, NUMERIC,
NUMERIC_UNITS, CURRENCY,
DATE, DATES, DATE_TIME,
TIME, BOOLEAN, BOOLEANS,
URL, URLS, INSTANCE,
INSTANCES
Prompt Type values:
AS_SPECIFIED, DO_NOT_USE,
USE_DEFAULT

10 Workbook name
11 Sheet name
12 Cell Root cell of live data

Option Description Notes

13 Report name
14 Report alias Workday ID

15 Report description
16 Report type ADVANCED_REPORT,
MATRIX_REPORT,
COMPOSITE_REPORT

17 Report async status TRUE, FALSE

18 Report limit
19 Report key column count
20 Report multi-instance enabled TRUE, FALSE

21 Report highlighted status TRUE, FALSE

22 Table range name

23 Formula user
24 Last run user
25 Last run date The date displays as a serial
number; you can use Format >
Number > Date to display the
result using date formatting.
26 Last run time In milliseconds

27 Last run row count

28 Next run user Applicable if a refresh schedule
exists

29 Next run date Applicable if a refresh schedule

exists

Examples
=TRANSPOSE(WD.LIVEDATA(A1,100)) returns all metadata and includes a header. The TRANSPOSE
function puts the headers in a column for improved readability.

WorkbookName Workbook Example

SheetName Sheet1
Cell A1
ReportName Workday Report Example
ReportAlias [Workday ID]
ReportDescription
ReportType ADVANCED_REPORT

ReportAsync FALSE
ReportLimit 0
ReportKeyColumnCount 1
ReportMultiInstanceEnabled TRUE
ReportHighlightEnabled TRUE
ReportTableName
FormulaUser Logan McNeil
LastRunUser Logan McNeil
LastRunDate 05/05/2021 11:09:17.928 PM
LastRunTime 426
LastRunRowCount 34
NextRunUser Logan McNeil
NextRunDate 06/01/2021 7:00:00.000 AM

=WD.LIVEDATA(A1,101) returns column data details and includes a header.

Name Alias Type

Worker Name [XML Alias] INSTANCE
Dependents [XML Alias] INSTANCES

=WD.LIVEDATA(A1,102) returns report column information and includes a header.

Name Alias Type Editable Key

Employee ID [XML Alias] COLUMN FALSE TRUE
Worker Name [XML Alias] COLUMN FALSE FALSE
Dependents [XML Alias] COLUMN FALSE FALSE
Note1 [XML Alias] NOTE TRUE FALSE
Formula1 [XML Alias] FORMULA TRUE FALSE

=WD.LIVEDATA(A1,103) returns report prompt information and includes a header.

Prompt Name Prompt Alias Type

Effective Date [XML Alias] DATE
Cost Centers [XML Alias] INSTANCES

=WD.LIVEDATA(A1,104) returns report prompt details and includes a header.

Prompt Name Prompt Alias Type Value Prompt Type

Effective Date [XML Alias] DATE 4/15/2021 USE_DEFAULT
Cost Centers [XML Alias] INSTANCES Value DO_NOT_USE

Description
This function enables you to extract and return a segment of a specified array; it returns the extracted
(sliced) array. Optionally you can specify indexes. Specify positive indexes to increment from the beginning
of the array, or specify negative indexes to increment from the end of the array (reverse the array). The
indexes are 1-based. The index value 0 isn't allowed.

Syntax
WD.SLICE(array, [ row_start], [ row_end], [ row_step], [ column_start], [
column_end], [ column_step])
• array: The array to slice.
• row_start: The starting row index. If omitted, the default value is 1.
• row_end: The ending row index. If omitted, the default is the current number of rows in the specified
range.
• row_step: The row step index. If omitted, the default value is 1.
• column_start: The starting column index. If omitted, the default value is 1.
• column_end: The ending column index. If omitted, the default is the current number of columns in the
specified range.
• column_step: The column step index. If omitted, the default value is 1.

Operator Functions
COMPARE

Description
Compares two matrices, returning an integer representing the comparative relationship of two values. If the
values match, the function returns null. Optionally, you can set a difference percentage so that if two values
are within a certain percentage of each other, the function considers them to be the same.

Syntax
COMPARE(value1, value2, [ mode], [ percentage])
• value1: The first value to compare.
• value2: The second value to compare.
• mode: Specifies the result to return. If difference, then return the difference. (If value2 is greater
than value1, the return value is positive; otherwise it's negative.) If changed, then the function returns
value2. The default is changed.
• percentage: Specifies a percentage allowance of difference where the function should consider the two
values to be the same. The two values are equal if they are within value1*percentage of each other.

Example

Formula Result
=COMPARE(B2,B3,"changed",0.01) where B2 18
contains 15 and B3 contains 18.

Related Functions
ARRAYAREA
MINUS
SUBTRACT

Description
Subtracts number2 from number1. Although this function is available to you, we recommend that you
simply write number2 - number1 when you want to subtract two numbers.

Syntax
SUBTRACT(number1, number2)
• number1: The number to be subtracted from.
• number2: The number to subtract.

Example

Formula Result
=SUBTRACT(10,3) 7

Notes
• Don't confuse this function with MINUS(). MINUS() performs set-based subtraction.

Statistical Functions
FORECAST.WD.SEASONAL

Description
Returns a predicted sequence of values using patterns in the historical linear and non-linear data you
specify.

Syntax
FORECAST.WD.SEASONAL(values, num_forecast)
• values: An array of historical values to predict from.
• num_forecast: The number of values to predict.

Example
An analyst wants to predict revenue values for the 12 months of 2017 based on historical revenue values
from 2012 through 2016. The values for 2012-2016 are in cells C2 through C61. This table excerpt shows
the values from 2012:

A B C
1 Year Month Actual Total Rev per Month (millions)
2 2012 Jan 0.984
3 2012 Feb 1.012
4 2012 Mar 1.045
5 2012 Apr 1.109

6 2012 May 1.112

7 2012 Jun 1.458
8 2012 Jul 1.892
9 2012 Aug 2.018
10 2012 Sep 2.203
11 2012 Oct 2.43
12 2012 Nov 1.897
13 2012 Dec 0.894

This graph shows the values as a dark blue line:

This formula adds 12 predicted values to the workbook:

=FORECAST.WD.SEASONAL(C2:C61, 12)
The light blue line in this graph shows the forecast values:

TDISTRT

Description
Returns the right-tailed t-distribution.

Syntax
TDISTRT(x, deg_freedom)
• x: The input value.
• deg_freedom: The number of degrees of freedom.

Example

Formula Result
=TDISTRT(18.307,10) 0.000000003

Notes
• This function does the same action as T.DIST.RT().
WD.AVERAGEIF

Description
Returns the average of the values that meet the specified condition (criterion). This function is the same as
AVERAGEIF but WD.AVERAGEIF creates an index (b-tree) for the specified range or array. This function
provides better performance for repeated use on the same range/array. Null and error values are ignored.

Syntax
WD.AVERAGEIF(range, criteria, [ average_range])
• range: The values, or the range/array of cells, to be evaluated according to the condition.
• criteria: The condition to use to evaluate the values.
• average_range: The values, or the range of cells, to be averaged if the range meets the specified
condition. If not specified, the range is averaged.
WD.AVERAGEIFS

Description
Returns the average of the values that meet multiple conditions (criteria). This function is the same as
AVERAGEIFS but WD.AVERAGEIFS creates an index (b-tree) for the specified ranges/arrays. This
function provides better performance for repeated use on the same range/array. Null and error values are
ignored.

Syntax
WD.AVERAGEIFS(average_range, range, criteria, [ range2, criteria2], ...)
• average_range: The values, or the range of cells, to be averaged if the specified ranges meet the
specified conditions.
• range: The values, or the range/array of cells, to be evaluated according to the condition.
• criteria: The condition to use to evaluate the values.
• range2: The values, or the range of cells, to be evaluated according to the condition.
• criteria2: The condition to use to evaluate the values.
WD.COUNTIF

Description
Returns the number of specified values that meet the condition (criterion). You can use the * wildcard to
match string values. This function is the same as COUNTIF but WD.COUNTIF creates an index (b-tree) for

the specified range or array, providing better performance for repeated use on the same range/array. Null
and error values are ignored.

Syntax
WD.COUNTIF(range, criteria)
• range: The range or array of values to be counted if the condition is met.
• criteria: The condition to use to evaluate the values.
WD.COUNTIFS

Description
Returns the number of times that the cells in the specified ranges or arrays meet multiple conditions
(criteria). You can use the * wildcard to match string values. This function is the same as COUNTIFS but
WD.COUNTIFS creates an index (b-tree) for the specified ranges or arrays, providing better performance
for repeated use on the same range/array. Null and error values are ignored.

Syntax
WD.COUNTIFS(range, criteria, [ range2, criteria2], ...)
• range: The range/array of values to be evaluated according to the condition.
• criteria: The condition to use to evaluate the values.
• range2: The value, or list of values, to be evaluated according to the condition.
• criteria2: The condition to use to evaluate the values.

Table Functions
FLATTEN

Description
Returns an expanded range of data based on the hierarchical data that you specify. Typically you use this
function to expand an organization's manager and employee information so that it displays all levels of the
hierarchy.
JOIN
Performs an inner left join on 2 ranges.

Syntax
FLATTEN(source, primary_column, detail_column, data_columns, [ root_values])
• source: The range of data to flatten.
• primary_column: The index value in the source for the higher-level item that you want to flatten by.
• detail_column: The index value in the source for the lower-level item that you want to flatten by.
• data_columns: The column indexes to select into the output.
• root_values: Values that identify the topmost items in the hierarchy. The default is null (indicating the
highest point in the hierarchy).
VALUEAT

Description
Returns the value at the intersection of a column header and row label.

Syntax
VALUEAT(table, column_name, row_name)
• table: The table.
• column_name: The column name.
• row_name: The row name.

Example
Results are based on this spreadsheet:

A B
1 Name Grade
2 Joe 85
3 Alice 92
4 Luis 90

Formula Result
=VALUEAT(A1:B4,"Grade","Alice") 92

Related Functions
INDEX
MATCHEXACT

Text Functions
REGEXFIND

Description
Returns the position of the first character of a substring that matches the regular expression pattern. The
position value is zero-based. If the function doesn't find a match, it returns the #N/A error.

Syntax
REGEXFIND(text, regex, [ ignore_case])
• text: The text to search.
• regex: The regular expression.
• ignore_case: If TRUE, the function ignores the case of the text. If FALSE, the function considers case.
The default is FALSE.

Example

Formula Result

=REGEXFIND(A1,"el+") 1

Where cell A1 contains hello world .

Notes
• Workday uses Java's regular expression parser; the expression must conform to Java's regex rules
(http://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html) .
REGEXPARSE

Description
Extracts parts of a string by matching to a pattern.

Syntax
REGEXPARSE(text, regex, [ ignore_case])
• text: The text to parse.
• regex: The regular expression.
• ignore_case: If TRUE, the function ignores case when searching. If FALSE, the function considers
case. The default is FALSE.

Example

Formula Result
=REGEXPARSE("[Los Angeles]","\[(.*)\]") Los Angeles
=REGEXPARSE("12-OCT-2015","(\d\d)-([A-Z]{3})- 12-OCT-2015 12 OCT 2015
(\d{2,4})")
=INDEX(REGEXPARSE("aa;bbbbbb24;cccc;","(.*?); bbbbbb24
(.*?);.*"),3)
Extracts the nth part of a delimited string

Notes
• This function returns an array of values where each value is part of the string where it found a pattern
match. This function is useful if you have a pattern and you want to pull out the parts of the text that
matched the pattern.
• This function is intended for use in array formulas. You submit array formulas with special keyboard
shortcuts. We recommend that you use the unconstrained keyboard shortcut Ctrl+Alt+Enter (on
Windows) or Command+Option+Enter (on Mac) so Worksheets can use all the cells it needs for the
results. For more information, see Reference: Array Formula Keyboard Shortcuts.
• Workday uses Java's regular expression parser; the expression must conform to Java's regex rules
(http://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html) .

Reference: Measurement Units in Worksheets Functions

These tables list the primary units of measurement that Worksheets functions support. Use the
abbreviations in formulas.
For more information, see the Java library javax.measure.unit.Dimension.
Abbreviations are case-sensitive.
Make sure that all unit types in a formula are compatible. Example: Don't try to convert a distance unit to a
time unit.

Weight and Mass

Abbreviation Name
g Gram
u U (Atomic Mass Unit)
grain Grain
uk_cwt Imperial hundredweight
lcwt Imperial hundredweight
hweight Imperial hundredweight
stone Stone
ton Ton
uk_ton Imperial ton
LTON Imperial ton
brton Imperial ton

Distance

Abbreviation Name
m Meter
mi Statute mile
Nmi Nautical mile
in Inch
ft Foot
yd Yard
ang Angstrom
ly Light year
Picapt Picapt (point: 1/72 inch)
Pica Pica (1/72 inch)
pica pica (1/6 inch)
survey_mi US survey mile (statute mile)

Time

Abbreviation Name
yr Year
day Day
d Day
hr Hour

Abbreviation Name
mn Minute
min Minute
sec Second
s Second

Energy

Abbreviation Name
J Joule
c Thermodynamic calorie
cal IT calorie
eV Electron volt
HPh Horsepower-hour
hh Horsepower-hour

Temperature

Abbreviation Name
C Degree Celsius
cel Degree Celsius
F Degree Fahrenheit
fah Degree Fahrenheit
K Kelvin
kel Kelvin

Volume (Liquid Measure)

Abbreviation Name
tsp Teaspoon
tbs Tablespoon
oz Ounce
cup Cup
pt Pint
us_pt US pint
uk_pt UK pint
qt Quart
uk_qt Imperial quart
gal Gallon

Abbreviation Name
uk_gal Imperial gallon
l Liter
L Liter
lt Liter
barrel US oil barrel
bushel US bushel
ft^3 Cubic feet
in^3 Cubic inch
m^3 Cubic meter
mi^3 Cubic mile
yd^3 Cubic yard
Pica^3 Cubic Pica
MTON Measurement ton (freight ton)

Area

Abbreviation Name
uk_acre International acre
us_acre US survey/statute acre
ang^2 Square angstrom
ft^2 Square feet
in^2 Square inches
m^2 Square meters
mi^2 Square miles
Picapt^2 Square Pica
Pica^2 Square Pica
yd^2 Square yards

Information

Abbreviation Name
bit Bit
byte Byte

Speed

Abbreviation Name
m/h Meters per hour

Abbreviation Name
m/hr Meters per hour
m/s Meters per second
m/sec Meters per second
mph Miles per hour

Persons

Abbreviation Name
person Person
pers Person
emp Employee
hc Headcount
head Head

Currency

Abbreviation Name
AFA Afghani
AFN Afghani
ALK Albanian Old Lek
DZD Algerian Dinar
ADF Andorran Franc
ADP Andorran Peseta
AOR Angolan Kwanza Readjustado
ARS Argentine Peso
AMD Armenian Dram
AWG Aruban Florin
AUD Australian Dollar
ATS Austrian Schilling
AZM Azerbaijani Manat
AZN Azerbaijanian Manat
BSD Bahamian Dollar
BHD Bahraini Dinar
THB Baht
PAB Balboa
BBD Barbados Dollar
BYR Belarussian Ruble

Abbreviation Name
BEF Belgian Franc
BZD Belize Dollar
BMD Bermudian Dollar
VEF Bolivar
BOB Boliviano
BRL Brazilian Real
BND Brunei Dollar
BGN Bulgarian Lev
BIF Burundi Franc
CVE Cabo Verde Escudo
CAD Canadian Dollar
KYD Cayman Islands Dollar
XOF CFA Franc BCEAO
XAF CFA Franc BEAC
XPF CFP Franc
CLP Chilean Peso
COP Colombian Peso
KMF Comoro Franc
CDF Congolese Franc
BAM Convertible Mark
NIO Cordoba Oro
CRC Costa Rican Colon
HRK Croatian Kuna
CUP Cuban Peso
CYP Cyprus Pound
CZK Czech Koruna
GMD Dalasi
DKK Danish Krone
MKD Denar
DJF Djibouti Franc
STD Dobra
DOP Dominican Peso
VND Dong
NLG Dutch Guilder

Abbreviation Name
XCD East Caribbean Dollar
ECS Ecuador Sucre
ECV Ecuador Unidad de Valor Constante
TJR Tajikistani ruble
EGP Egyptian Pound
SVC El Salvador Colon
ETB Ethiopian Birr
EUR Euro
XEU European Currency Unit
FKP Falkland Islands Pound
FJD Fiji Dollar
FIM Finnish Markka
HUF Forint
FRF French Franc
DEM German Mark
GHC Ghana Cedi
GHS Ghana Cedi
GIP Gibraltar Pound
XFO Gold Franc
HTG Gourde
GRD Greek Drachma
PYG Guarani
GNF Guinea Franc
GWP Guinea-Bissau Peso
GYD Guyana Dollar
HKD Hong Kong Dollar
UAH Hryvnia
ISK Iceland Krona
INR Indian Rupee
IRR Iranian Rial
IQD Iraqi Dinar
IEP Irish Pound
ITL Italian Lira
JMD Jamaican Dollar

Abbreviation Name
JOD Jordanian Dinar
KES Kenyan Shilling
PGK Kina
LAK Kip
EEK Kroon
KWD Kuwaiti Dinar
MWK Kwacha
AOA Kwanza
MMK Kyat
GEL Lari
LVL Latvian Lats
LBP Lebanese Pound
ALL Lek
HNL Lempira
SLL Leone
LRD Liberian Dollar
LYD Libyan Dinar
SZL Lilangeni
LTL Lithuanian Litas
LSL Loti
LUF Luxembourgian Franc
MGA Malagasy Ariary
MGF Malagasy Franc
MYR Malaysian Ringgit
MTL Maltese Lira
TMM Manat
MUR Mauritius Rupee
MXN Mexican Peso
MXV Mexican Unidad de Inversion (UDI)
MDL Moldovan Leu
MCF Monegasque Franc
MAD Moroccan Dirham
MZM Mozambique Metical
MZN Mozambique Metical

Abbreviation Name
BOV Mvdol
NGN Naira
ERN Nakfa
NAD Namibia Dollar
NPR Nepalese Rupee
ANG Netherlands Antillean Guilder
ILS New Israeli Sheqel
RON New Romanian Leu
TWD New Taiwan Dollar
NZD New Zealand Dollar
BTN Ngultrum
KPW North Korean Won
NOK Norwegian Krone
PEN Nuevo Sol
OMR Omani Rial
MRO Ouguiya
TOP Pa'anga
PKR Pakistan Rupee
MOP Pataca
UYU Peso Uruguayo
PHP Philippine Peso
PTE Portugese Escudo
GBP Pound Sterling
BWP Pula
QAR Qatari Rial
GTQ Quetzal
ZAR Rand
KHR Riel
ROL Romanian Leu
MVR Rufiyaa
IDR Rupiah
RUB Russian Ruble
RWF Rwanda Franc
SHP Saint Helena Pound

Abbreviation Name
SML San Marinese Lira
SAR Saudi Riyal
CSD Serbian Dinar
RSD Serbian Dinar
SCR Seychelles Rupee
SGD Singapore Dollar
SKK Slovak Koruna
SIT Slovenian Tolar
SBD Solomon Islands Dollar
KGS Som
SOS Somali Shilling
TJS Somoni
SSP South Sudanese Pound
ESP Spanish Peseta
LKR Sri Lanka Rupee
SDD Sudanese Dinar
SDG Sudanese Pound
SRD Surinam Dollar
SRG Suriname Guilder
SEK Swedish Krona
CHF Swiss Franc
SYP Syrian Pound
BDT Taka
WST Tala
TZS Tanzanian Shilling
KZT Tenge
TTD Trinidad and Tobago Dollar
MNT Tugrik
TND Tunisian Dinar
TRL Turkish Lira
TRY Turkish Lira
TMT Turkmenistan New Manat
AED UAE Dirham
UGX Uganda Shilling

Abbreviation Name
COU Unidad de Valor Real
CLF Unidades de fomento
UYI Uruguay Peso en Unidades Indexadas
USD US Dollar
UZS Uzbekistan Sum
VAL Vatican Coins
VUV Vatu
VEB Venezuelan Bolívar
CHE WIR Euro
CHW WIR Franc
KRW Won
YER Yemeni Rial
JPY Yen
CNY Yuan Renminbi
YUM Yugoslav Dinar
ZMK Zambian Kwacha
ZMW Zambian Kwacha
ZWD Zimbabwe Dollar
ZWL Zimbabwe Dollar

Slides

Steps: Set Up Security for Slides

Prerequisites
• Set up Drive for users who need to create, edit, or view Slides presentations. See Steps: Set Up
Security for Drive.
• Security: Security Configuration domain in the System functional area.

Context
Slides is a presentation application that enables you to share data insights, create narrative, and
provide relevant context around Workday data. With Slides you can create, collaborate on, and share
presentations that integrate live transactional data from Worksheets workbooks or exported data from
People Analytics stories.

Steps
1. (Optional) Set up Worksheets.
Enable the Worksheets domain to provide access for linking to workbook data from a Slides
presentation.
See Set Up Worksheets on page 649.
2. (Optional) Set up People Analytics.
Enable the People Analytics domain to provide access for exporting People Analytics data to a Slides
presentation.
See Steps: Prepare for People Analytics Installation on page 546.
3. Create Role-Based Security Groups.
Create these types of security groups for Slides administrators and users:
• Public groups
• Role-based (constrained) groups
• Unconstrained groups
4. Create or edit a security policy for the Slides domain in the System functional area.
Ensure that every user who has access to the Slides domain also has access to the Drive and
Worksheets domains.
a) Access the View Domain report.
b) Select the domain from the Domain prompt.
c) From the related actions menu, select Domain > Create Security Policy, or select Edit Security
Policy Permissions if there's an existing policy.
d) In Report/Task Permissions, add or edit security groups.
e) Select the View and Modify check boxes.
Note: In the domain setup, you must select both View and Modify. You can't use these settings to
manage access to presentations. You select view and edit permissions for individual presentations
when you share them.
f) As a related action on the domain security policy, select Domain Security Policy > Enable.
5. Activate Pending Security Policy Changes.
Related Information
Reference
2021R1 What's New Post: Slides

Concept: Slides
Slides enables you to share data insights, create narrative, and provide relevant context around Workday
data. With Slides you can create, collaborate on, and share presentations that integrate live transactional
data from Worksheets workbooks or exported data from People Analytics.
With Slides, you can create new presentations from Drive and then:
• Add text, tables, charts, and images and apply formatting and branding.
• Insert linked data from Worksheets workbooks by using defined names or references to pivot tables.
• Export data into presentations from People Analytics.
• Provide narrative and insights alongside linked Workday data.
• Refresh linked Workday data as it changes to keep presentations up to date.
• Share presentations with others and assign viewing or editing permissions.
• Collaboratively edit presentations with others who have edit access.
• Present or download presentations.

Linked Data Indicators

Slides presentations identify data that is linked to a Worksheets workbook. When you refresh the linked
data in the presentation, visual indicators display if the data in the workbook changed. These visual
indicators don't display when the presentation is in the Present mode.

Indicator Description
Blue background color around text. The text contains a linked data item.
Orange background color around text, tile, or slide The text, tile, or slide contains the linked data item
thumbnail. selected in the Linked Data panel.
Orange icon with arrows next to a data item. The last data refresh updated the linked data item.

Collaboration
Presentation owners can share presentations with other users who have access to Slides to collaborate
on the content. When more than 1 user simultaneously views or edits a presentation, Slides assigns
a different colored avatar for each user and displays the avatars above the presentation. Colored dots
display next to slides in the thumbnail panel and colored squares display next to tiles on slides.
Related Information
Reference
The Next Level: Leveraging Workday Slides in Project Economics Tracking

Concept: Managing Slides Presentations

This table summarizes some of the actions that you can take with presentations. Users must have access
to the Slides and Drive domains to create, copy, share, and delete presentations.

Action Notes

Create a presentation From Drive, select Add New > Presentation.

Slides uses the branding color from the Configure Tenant Branding task
for slide layouts by default. You can override the color setting by clicking
File > Color Settings.

Copy a presentation From Drive, select the presentation and click Make a Copy, or from a
presentation, select File > Copy only Presentation.
If the presentation has linked workbook data, the copy of the presentation
maintains the links to the original workbooks.

Copy a presentation and To copy a presentation along with the associated workbooks and data
copy the linked workbooks links, from the presentation select File > Copy with Workbook(s). Copies
of the presentation and copies of the linked workbooks are saved together
in a folder in Drive.
The copy of the presentation creates links to the copies of the workbooks.
You must have view or edit access to all of the workbooks linked to the
presentation to copy the presentation and the workbooks.

Share a presentation From Drive, or from an open presentation, select Share.

When you share a presentation, you can:
• Enable link sharing and provide the URL to multiple users at once.

Action Notes
• Select specific users, or groups, to share with.
• Select a permission level for the actions that users can do.
Note: The ability to use group sharing is a system setting that requires
additional Drive configuration.
When you share a presentation with a specific user, Workday sends a
notification and an email (if the Workday administrator enabled email
notifications). When you enable link sharing and provide a URL, or when
you share with a group, Workday doesn't send notifications.
If you share a Slides presentation containing linked data from a
Worksheets workbook, but you don't share the underlying workbook, the
user won't be able to open the workbook.

Download a presentation From the presentation, select File > Download as and select the file type
to create. The download might take a few minutes depending on the size
of the presentation.
When downloading the presentation as a PowerPoint file, each slide
downloads as an image.

Remove (move to Trash) a From Drive, select the presentation and click Remove.
presentation
The presentation remains in Trash forever, unless a Drive administrator
permanently deletes it.

Restore a presentation from From Trash in Drive, select the presentation and then click Restore.
Trash Workday places the restored presentation in My Files.
You can restore a presentation only if you're the person who created it.
If you remove a presentation that someone shared with you, and
you're not the owner, you remove your access to the presentation. The
presentation disappears from the Drive and it doesn't display in Trash.

Related Information
Tasks
Set Up Group Sharing for Drive

Concept: Editing Slides Presentations

Slide Editing and Navigating

This table summarizes some of the actions that you can take within Slides presentations. Users must have
access to the Slides and Drive domains to create and edit presentations.
A session in Slides will time out after 15 minutes of inactivity.

Action Notes

Add a slide To add a slide with the same layout as another slide, click the + icon below
the slide in the thumbnail panel. To add a slide with a different layout,
select a layout from the drop-down list.
A presentation can include up to 100 slides.

Action Notes

Select branding and chart Click File > Color Settings. You can select a color or type a color hex
colors code for the slide accent color and to represent each of the colors in a
chart.
You can also save custom hex colors and reuse them throughout the
presentation when applying color to text, table cells, backgrounds, and
borders.
Slides uses the branding color from the Configure Tenant Branding task
for slide layouts by default. If there's no branding color configured in the
Configure Tenant Branding task, Slides uses the blue Workday brand
color as the default.

Add background color or Hover over the slide in the thumbnail panel and click Slide Background.
image to a slide You can select an image or color, or type a color hex code.
Duplicate a slide Hover over the slide in the thumbnail panel and click Duplicate Slide.
Delete a slide Hover over the slide in the thumbnail panel and click Delete Slide.

Tile Editing
You can add text, tables, charts, and images to a presentation by inserting content tiles. Each slide can
include up to 50 tiles.
You can also link to data from Worksheets by selecting defined names or references to pivot tables from a
Worksheets workbook. A presentation can have links to as many as 500 unique data items, including up to
20 different Worksheets workbooks.
Note: Currently Slides can use only explicitly specified defined names from Worksheets such as =Sheet1!
$A$1:$A$13. It can't use "dynamic" defined names from a workbook such as =ARRAYAREA('Sheet1'!A1).
You can also export data into presentations from People Analytics.

Action Notes

Add text Click Insert > Text and type the text to add. Use the toolbar to select
fonts, styles, formats, and colors. Each text tile can include up to 1 MB
(1048576 characters) of text, excluding linked values.
To add linked data, click Insert > Linked Value, navigate to the workbook,
and select the defined name containing the data.
To open the workbook containing the linked data, click the text and then
click the workbook name. You must have view or edit access to the
workbook.

Add a table Click Insert > Table and select the type of table to add:
• Linked table: Inserts a table with data that is linked to a workbook.
Navigate to the workbook, select the defined name containing the data,
and click Insert. Linked tables can have a maximum of 1,000 cells.
• Editable table: Inserts an empty table with cells that are editable.
Click to change the table size and click Insert. You can type data in the
cells or click Insert > Linked Value to add linked data.

Action Notes
To open the workbook containing the linked data, click the table and
then click View Data Source. You must have view or edit access to the
workbook.

Add a chart Click Insert > Linked Chart. Navigate to a workbook, select a data item,
click Choose Chart Type, and click Insert Chart. Click the chart to open
the chart editor panel and add titles, labels, and legends.
To open the workbook containing the linked data, click the chart and
then click View Data Source. You must have view or edit access to the
workbook.
To select custom chart colors, click File > Color Settings. You can select
a color or type a color hex code to represent each of the colors in the
chart.
Linked charts can have a maximum of 5,000 cells. Slides doesn't support
linked charts with data that includes numbers and percentages.

Add an image Click Insert > Image and navigate to the image. Presentations can include
up to 100 unique images and each image can be up to 5 MB in size.
To crop the image and fill the entire area within the tile, click Format >
Image Fit > Crop to fit.
To change the shape of the image to a circle, click Format > Image to
Circle. To change it back to a square, click Tile > Border Radius > None.

Add a video Click Insert > Video and navigate to a media file in Drive. You can only
add media file types available in Drive.
Add a text hyperlink Highlight the text, click Insert > Hyperlink and type or paste the URL.
Show or hide linked data Click View > Show Linked Value Indicator to show or hide the blue
values background color that indicates text contains a linked value.

View linked data Click View > Linked Data to open the Linked Data panel and view all
linked data sources and data items in the presentation.
When you select a data item in the Linked Data panel, an orange border
displays around each tile and slide that contains that linked data.
If the name of a workbook is missing in the Linked Data panel then you
don’t have access to that workbook or the linked data, either because the
workbook is not shared with you or because the workbook is in Trash in
Drive.

Refresh linked data Click File > Refresh Linked Data to check for changes in linked workbook
data and update it throughout the presentation. An orange icon displays in
the Linked Data panel next to the data items that change.
To refresh data for a specific workbook data source or item, click the
Refresh arrows. You must have view or edit access to the workbook to
refresh the data. If the name of the workbook is missing in the Linked
Data panel then you don’t have access to that workbook, either because
the workbook is not shared with you or because the workbook is in Trash
in Drive.
You can’t refresh data items exported from People Analytics.

Action Notes
When you insert a linked table from Worksheets, table formatting is copied
to the table in Slides. When linked data is refreshed in Slides, format
changes made to the Worksheets table are not updated in Slides, unless
the size of the table in Worksheets has changed.

Revert last data refresh Click Revert Last Refresh to revert changes that occurred during the
preceding data refresh.
Move a tile Select and hold a tile and then move it to the new location.

Resize a tile Select a tile and click and drag the border sizing handles.
Press and hold the Shift key while dragging the corner of the tile to
maintain the tile’s width and height ratio.

Adjust tile alignment Select View > Show Grid to display visual gridlines and View > Grid Size
to adjust the size of the gridlines.
Select View > Snap to Grid to have a tile automatically align to the
gridlines when you move it.

Arrange tiles on a slide Select a tile and click Tile > Order to move a tile in front of or behind
another tile.
Add background color to a Select a tile and click Tile > Background. You can then select a color or
tile type a color hex code.
Increase or decrease tile Select a tile and click Tile > Padding.
padding
Change the type of content Select a tile, click Tile > Change Tile Type, and select the type of content
in a tile for the tile.
Delete a tile Select a tile and click Tile > Delete.

Reference: Access to Linked Worksheets Data in Slides

The actions you can do with linked Worksheets data in Slides is based on the type of access you have
to the presentation. If you create the presentation, you have edit access. If you share a presentation with
someone else, you can specify either Can View or Can Edit permissions.

Actions Can View Permissions Can Edit Permissions

View linked data X X
Insert linked data X
Refresh linked data X
Copy a presentation with linked workbooks X X

You can view all linked data in a presentation by clicking View > Linked Data to open the Linked Data
panel. If you have view or edit access to a linked workbook, you can click the link in the workbook name to
open it and view the source of the data. If the name of a workbook is missing, or the link to the workbook is
disabled, you don’t have access to that workbook.

Reference: Slides Presentation Limits

These limits apply when creating a presentation:

Limit Maximum Value

Number of slides per presentation 100
Number of tiles per slide 50
Size of text 1 MB (1048576 characters excluding linked values
embedded in text)
Size of an image 5MB
Number of unique images 200
Number of unique linked data items 500
Number of unique linked Worksheets 20
workbooks
Number of cells in linked table 1,000
Number of cells in linked chart 5,000

Reference: Presentation Actions Available Based on Permissions

This table summarizes the actions available for Slides presentations based on the user's permission level.
You specify permission levels when you share a presentation.

Action Can View Can Edit Owner

Permission Permission
View a presentation. X X X

Copy a presentation. X X X

(Allowed for Can View permissions only if the presentation

owner selected the Commenters and viewers can copy,
download, and print option when sharing the presentation.)

Download a presentation. X X X

(Allowed for Can View permissions only if the presentation

owner selected the Commenters and viewers can copy,
download, and print option when sharing the presentation.)

View a list of users the presentation is shared with. X X X

Remove (self) from shared presentation access. X X

Share a presentation or change share permissions. X X

(Allowed for Can Edit permissions only if the presentation

owner selected the Editors can share option when sharing
the presentation.)

Edit content in a presentation (including format and delete). X X

Rename a presentation. X

Action Can View Can Edit Owner

Permission Permission
Remove a presentation and restore it from Trash. X

Reporting on Modeled Data Sources

Steps: Set Up Your Tenant for OfficeConnect for Financial Management

Prerequisites
Note: The solutions described in this section are not part of the Workday Service. See Legal Notice for
details.
Before you set up your tenant for OfficeConnect, you must:
• Set up the Workday Financial Management area.
• Meet eligibility requirements as described in Enable OfficeConnect for Workday Financial Management.

Context
You can set up your tenant for OfficeConnect to use with Financial Management data.

Steps
1. Enable OfficeConnect for Workday Financial Management on page 805.
2. Create or edit a security policy for these security domains:
• Set Up: Financial Reporting and Analytics Data Model. The users in the groups you add to this policy
are able to set up the financial reporting data model. Add a security group with View permissions,
such as Finance Administrator.
• Access Workday Financials OfficeConnect. The users in the groups you add to this policy have
permission to log in to Workday from OfficeConnect using the financial modeled data source. Add a
security group with View and Modify permissions.
See Edit Domain Security Policies.
3. Activate Pending Security Policy Changes.
4. Set Up the Financial Reporting Data Model on page 805.
5. Install OfficeConnect on the computer of each financial analyst.
You can install OfficeConnect either as:
• An Administrator. See Install OfficeConnect as an Administrator.
• An end user. See Install OfficeConnect as an End User.
6. Connect OfficeConnect to Your Financial Management Tenant on page 808.
Use the API client settings Workday generated when you enabled OfficeConnect for Workday Financial
Management.
Related Information
Concepts
Concept: Reporting on the Financial Modeled Data Source on page 810
Concept: Currencies and Currency Translation on page 814
Concept: Differences in OfficeConnect Between Financials and Planning Data Sources on page 816

Reference
The Next Level: Setting the Foundation for Financial Management
2022R1 What's New Post: OfficeConnect Availability for Financial Management

Enable OfficeConnect for Workday Financial Management

Prerequisites
Security: Set Up: Tenant Setup - Financials domain in the System functional area.

Context
You can enable OfficeConnect in your tenant to use it with Workday Financial Management data.

Steps
1. Access the Tenant Setup report.
2. Navigate to Financials > OfficeConnect.
3. Select Enable OfficeConnect.
4. Click the API Client link.
Copy these values and save somewhere for a later step:
• Client ID
• Workday REST API Endpoint
• Authorization Endpoint
Related Information
Tasks
Connect OfficeConnect to Your Financial Management Tenant
Reference
The Next Level: Video Shorts - OfficeConnect - Financial Management

Set Up the Financial Reporting Data Model

Prerequisites
Security: Set Up: Financial Reporting and Analytics Data Model domain in the System functional area.

Context
Set up the financial reporting data model before you sign in to Workday in OfficeConnect. By defining the
reporting data model, you're curating the Workday Financials data model (FDM), so that you only expose
the components of the FDM needed for reporting. When you set up the financial data model, Workday
creates the financial modeled data source.

Steps
1. Access the Set Up Financial Reporting and Analytics Data Model task.
2. As you complete this task, consider:
Option Description
Company Select the primary top-level hierarchy for the company to report on.

Option Description
The company you select determines the Account Set value and
the Fiscal Schedule value.
In the Alternate Company Hierarchies field, optionally select one
or more additional company hierarchies to use.

Ledger Accounts Select the top-level hierarchy that includes the accounts to report
on and analyze.
The company you select determines the Account Set value.
In the Alternate Account Top-Level Hierarchies field, optionally
select one or more additional ledger account hierarchies to use.
The Default Amount Field is summarized by ledger debit minus
credit. When creating a report in OfficeConnect, you can select a
different amount field, such as Natural Amount, by applying a filter
to the worksheet or workbook.

Time Select a Fiscal Summary Schedule that represents a time period in

the selected Fiscal Schedule that's between year and the posting
interval period, such as quarter.
Workday creates a three-tier time hierarchy in the reporting data
model that goes from year (based on Fiscal Schedule) to the
selected Fiscal Summary Schedule to the posting interval period.
Example: FY2021 > Quarter > Month
The company hierarchy that you select determines the Fiscal
Schedule value.

Currency Select the default currency to use when reporting on the Corporate
currency or any company hierarchy level.
When reporting on a single company, Workday uses the ledger
currency for that company by default.
Select the Default Translation Rule Set that defines the
translation method to apply based on ledger account type when
Workday performs currency translation. In OfficeConnect, you
can select a different translation rule set by applying a filter to the
worksheet or workbook.

Versions For journal line, Actuals is selected by default.

For plan lines, select the financial plan structures and plans to
report on. There's a limit to the number of plans you can select
(listed on the setup page).

Effective Date Select the default effective date that determines the dimension
hierarchies and values in your model elements. The date can be:
• Dynamic. Select a date relative to the current date (or the
current date itself).
Example: Prior Period End Date. If the period is monthly and
the current date is April 5, 2022, then the effective date is March
31, 2022. If the period is monthly and the current date is May 5,
2022, then the effective date is April 30, 2022.

Option Description
• Static. Commonly used static dates that the system populates.
These dates are auto-generated based on the model's selected
fiscal schedule and summary schedule. The list updates
automatically over time.
Example: The date of the end of each interval posting period for
the past 12 months.
• Custom: Define custom dates that represent something specific
to the company. These dates are available for selection
indefinitely.
Example: An org change that occurred on mm/dd/yyyy.
A change in the date applies to all users of the model.
Note: OfficeConnect displays the effective date as a label under
Labels > Model > Model Effective Date so that users know which
effective date is used.

Dimensions Select the optional dimensions, such as worktags and

organizations, to drill down into the data. If you add a hierarchical
dimension, select a hierarchy to use. If you don't specify a
hierarchy, Workday includes the values as a flat list.
The dimensions you select determine how report creators can filter
and group the data.
In Alternate Top-Level Hierarchies, optionally select one or
more additional hierarchies to use. You have to select a primary
hierarchy before you can add alternate hierarchies.

Show Details Manage the journal line details users can view for a report cell
when they click Show Details for deeper analysis. You can:
• Delete any optional fields.
• Search for and add fields.
• Reorder the fields to change the display and sort order.
If you don't change anything, Show Details displays the default set
of fields from OfficeConnect reports.
Note: The number of fields you configure to display in the
OfficeConnect worksheet impacts performance. A large number of
rows and columns creates larger and slower reports.

Result
Workday creates the financial modeled data source using the components you defined in the financial
reporting data model. You can use this modeled data source when you sign in to Workday from
OfficeConnect.
Related Information
Concepts
Concept: The Financial Reporting Data Model
Tasks
Display Journal Line Details for Report Cells
Reference
2023R1 What's New Post: Multiple Hierarchy Support in OfficeConnect for Financial Management

2023R1 What's New Post: Effective Date Support in OfficeConnect for Financial Management
2022R2 What's New Post: Workday Financial Plan Lines in OfficeConnect for Financial Management
2022R2 What's New Post: Journal Line Details in OfficeConnect for Financial Management
2022R1 What's New Post: OfficeConnect Availability for Financial Management

Connect OfficeConnect to Your Financial Management Tenant

Prerequisites
Ensure that:
• OfficeConnect is available to your Financial Management instance, based on specific eligibility
requirements.
• You have the Access OfficeConnect permission.
• You've enabled OfficeConnect on the Financials tab on the Tenant Setup report and saved the
OfficeConnect API Client information.
• You have set up the Financial Reporting and Analytics Data Model.
• Based on the security policy of your company, you’ve downloaded and installed the latest version of
OfficeConnect.
Security:
• Access Workday Financials OfficeConnect domain in the Financial Accounting functional area.
• At least 1 of these security domains in the Financial Accounting functional area:
• Reports: Financial Accounting (Company based).
• Reports: Organization Financial Reporting (Organization based).
• Reports: Organization Journal Lines (Organization based).
• Reports: Projects (Project based).
• Process: Budget (Company based)
• Reports: Company Financial Budgets (Company based)
• Reports: Manager Budgets (Organization based)
• Reports: Manager Financial Budgets (Organization based)

Context
You can set up an OfficeConnect installation with Workday sign-in settings. Users can then sign in to
OfficeConnect for Financial Management with their Workday credentials. If you don't include the Workday
sign-in settings, users can manually enter these settings when they first sign in to OfficeConnect.

Steps
1. Get these sign-in settings from the Financials tab on the Tenant Setup report for each Workday tenant
you want to connect to:
• Client ID
• Workday REST API Endpoint
• Authorization Endpoint URL
2. Click Log In from the OfficeConnect tab in Excel.
Workday automatically displays the Planning sign in page.
3. Select Log in with Workday.
Workday automatically displays the Manage Tenants page.

4. On the Manage Tenants page specify these connection details:

Option Description
Name The name of the Workday tenant you're
connecting to. Example: Production tenant or
Sandbox tenant.
Data Source The data source for the tenant: Financials.
Client ID Created when you enabled OfficeConnect
for Financial Management. See Enable
API endpoint URL
OfficeConnect for Workday Financial
Authorization Endpoint URL Management on page 805.

5. Click Save and then Close.

6. Sign in to your Financial Management tenant.
7. At the prompt, select Allow.
8. (Optional) Create additional tenant connections. When saved, the tenant names display in the drop-
down.
9. (Optional) If you configured multiple tenants for Workday Single Sign-On and your identity provider
automatically signs you in, change the Connections user setting to allow users to select a tenant when
signing-in. See Reference: User Settings Fields.

Result
The settings persist after the first successful sign-in. The next time you sign in to OfficeConnect, you see
the Workday sign-in page. The Workday tenant that you last signed into automatically populates.
Use the Manage Tenants option to add, edit, or delete tenants. To switch to a different Workday tenant,
select the tenant name from the Select Tenant drop-down menu.

Next Steps
Your organization can use this process to setup multiple connections, such as to Preview, Sandbox or
Production instances of Financial Management. Continue to sign in to a single selected instance from the
list of connections you setup.
Related Information
Tasks
Steps: Set Up Your Tenant for OfficeConnect for Financial Management

Concept: Modeled Data Sources

A modeled data source is a curated tenant-specific data source that makes it easier to interact with
Workday data when creating reports by exposing relevant dimensions in a data model. You create a
modeled data source in Workday by setting up a reporting data model. When you set up a reporting data
model, you can use it in OfficeConnect to query Workday data directly. Modeled data sources enable easy,
performant reporting.
Workday provides the financial reporting data model that you can set up to create the financial modeled
data source.
Related Information
Concepts
Concept: The Financial Reporting Data Model

Concept: Reporting on the Financial Modeled Data Source

Workday provides the financial reporting data model that you can set up to create the financial modeled
data source. You can use the financial modeled data source in OfficeConnect to query Workday Financial
Management data directly, enabling easy, performant reporting.
OfficeConnect is a Microsoft Excel add-in that enables you to create reports in Excel securely using up-to-
date financial data in Workday directly from the financial modeled data source. With OfficeConnect, you
can create financial reports using the Excel interface you’re familiar with, using data backed by Workday,
such as journal lines.
OfficeConnect updates the data when you run or refresh your report in real time. These reports are based
on model elements like ledger accounts, time period, and worktags.
You might want to use OfficeConnect to perform ad hoc analysis on journal line data.
When creating and editing a report, you can:
• Use Excel formatting capabilities.
• Use Excel cell formulas and calculations.
• Expand and collapse hierarchies in the data model.
• Filter Workday data.
Example: You can use OfficeConnect for Financial Reporting to:
• Create an income statement.
• Create a balance sheet.
• Perform ad hoc dimension analysis.
• Perform salary and benefit analysis.
• Calculate product and customer margin.
OfficeConnect is only supported on Windows operating systems.
Related Information
Reference
The Next Level: Getting Started with OfficeConnect - Financial Management
Reference: OfficeConnect Technical Requirements
2022R1 What's New Post: OfficeConnect Availability for Financial Management
The Next Level: Support the Physician Bonus Process with OfficeConnect

Concept: The Financial Reporting Data Model

The financial reporting data model is a curated subset of components selected from the Workday financial
data model (FDM). The reporting data model determines which information from the FDM, such as which
company hierarchies, ledger account hierarchies, and dimensions, is available for analyzing and reporting
on in OfficeConnect.
When you set up the financial reporting data model, Workday creates the financial modeled data source
that you can access from OfficeConnect.
When you sign in to Workday from OfficeConnect using the financial data source, OfficeConnect displays
most of the information in the reporting data model in the Elements tab. You can drag and drop individual
elements, such as a company or ledger account, from the Elements tab into the worksheet.
OfficeConnect summarizes the data in your Workday ledger accounts as determined by the intersection of
the elements you place in the worksheet.
The financial reporting data model includes these elements:

Model Elements Description

Company The primary top-level company hierarchy you can report on.
One or more alternate company hierarchies you can report on.

Ledger Accounts The primary account top-level hierarchy you can report on.
One or more alternate ledger account hierarchies you can report on.

Time The three-tier time hierarchy defined in the reporting data model.
Typically, the hierarchy goes from year to quarter to month/period:
• Year is based on the Fiscal Schedule.
• Quarter is based on the configured Fiscal Summary Schedule.
• Month/Period is based on the posting interval period.
Example: FY2021 > Quarter > Month

Currency Defines:
• The default currency to use when reporting on the Corporate
currency or any company hierarchy level.
• The translation method to apply based on ledger account type
when Workday performs currency translation.

Versions The scenarios used for comparison: Journal Line or Plan Lines.
Effective Date The default effective date that determines the dimension hierarchies
and values in your model elements (prepopulated dynamic and static
dates, or custom dates defined by an administrator).
Dimensions The list of optional dimensions, such as worktags and organizations,
that you can use to group and filter the data.
For hierarchical dimensions, a primary top-level hierarchy and
optionally one or more alternate hierarchies.
Required dimensions don't count toward your maximum number of
dimensions that can have alternate hierarchies.

Show Details The contributing journal line and transaction details that users can
view for a data point.

The financial reporting data model:

• Includes aggregated data at the ledger account level. You can display the contributing journal line and
transaction details from a cell intersection with actuals data.
• Summarizes the amount field by Ledger Debit Minus Credit. When creating a report in OfficeConnect,
you can select a different amount field, such as Natural Amount, by applying a filter to the worksheet or
workbook. You can't change the amount field at the row, column, or cell level.
• Specifies a default translation rule set to use for currency translation. You can select a different
translation rule set by applying a filter to the worksheet or workbook. You can't change the translation
rule set at the row, column, or cell level.
• Includes these amount types:
• Ending Balance (default)
• Beginning Balance
• Beginning Balance Translation Adjustment
• Adjusted Beginning Balance
• Activity

• Displays intercompany eliminations in OfficeConnect at the lowest common parent level.

Considerations for Plan Lines

When working with plan lines, keep these considerations in mind:
• Only Workday Financial Plan Lines are supported.
• You can’t disable the currency translation adjustment (CTA) account, which might affect your partial
balance sheet plans.
• Revisit the dimensions selected for the model to ensure that the selected plan structure dimensions are
also in the model, or add them.
Example: If a plan uses Cost Center as its dimension, the model doesn't require that specific dimension
to be present. For reporting purposes, you need to add the same dimensions to the model so that
they’re available in reports.
• When applying a plan version in a report, specify the company (or companies) and time periods for the
report.
Example: Even if a plan name says 2012 Company A Plan, the time period for 2012 and Company A
aren't automatically applied and should be applied to the row, column, cell, or worksheet filter.
• When using dimensions for plan lines that are intended only for journal lines:
• Journal Status: Plan lines have a default status of Posted because there’s no journal status for plan
lines.
• Journal Source: Plan lines have a blank status and appear under Journal Source (Uncategorized/
Blanks) because there are no journal sources for plan lines.
• Match Status: Plan lines have a match status of Not Matched and can't be changed.
Note: These fields can’t be ignored for plan lines because the same summarized Plan Value would
be applied for every instance of Journal Status.
• You can now include a new dimension called Plan Entry Document Status in the financial reporting data
model to filter on the financial plan line status explicitly (Available, Draft, In Progress). Otherwise, all
available Plan Entry Document Statuses are included.
• If your plan is at a higher summary level than period, OfficeConnect uses the last period for any activity
on that plan and the last period's end date to match up with its translation exchange rate.
Example: If your plan is at the quarterly level for Q3 (Jul-Sep), the plan amount registers activity in
September and uses the September 30 end date for the currency translation exchange rate. A similar
impact would apply to a plan amount meant to cover an entire year.
• All plan amounts entered in Workday Budgets are considered as period activity (plan amount for a
specific time period). If you enter plan ending balances as plan amounts, use the Amount Type of
"Activity" when reporting on ending balances for these plans.
Related Information
Concepts
Concept: Currencies and Currency Translation on page 814
Concept: Modeled Data Sources on page 809
Tasks
Set Up the Financial Reporting Data Model
Display Journal Line Details for Report Cells
Reference
2023R1 What's New Post: Multiple Hierarchy Support in OfficeConnect for Financial Management
2023R1 What's New Post: Effective Date Support in OfficeConnect for Financial Management
2022R2 What's New Post: Workday Financial Plan Lines in OfficeConnect for Financial Management
2022R2 What's New Post: Journal Line Details in OfficeConnect for Financial Management
2022R1 What's New Post: OfficeConnect Availability for Financial Management

The Next Level: Support the Physician Bonus Process with OfficeConnect

Concept: Caching and Refreshing the Financial Modeled Data Source

Workday saves some information from the financial modeled data source, such as exchange rates and
the data model elements, in a cache for a limited time to optimize performance in OfficeConnect. Workday
automatically refreshes this information at different intervals depending on the type of data. Workday saves
the cached data in Workday.
You can run the Clear Financial Reporting Caches report (secured to the Set Up: Financial Reporting
and Analytics Data Model domain) to clear these caches immediately:
• Security Data Access. This cache stores user permissions to access financial data for each user.
By default, Workday updates this cache each hour. You can clear this cache if you changed the
permissions of a particular user in Workday and need to enforce the new permissions immediately.
• Currency Exchange Rates. This cache stores the exchange rates between different source and target
currencies. By default, Workday updates this cache each day. You can clear this cache if you did a bulk
upload of new exchange rates and you want to use the new rates immediately.

Refreshing Data in OfficeConnect

By default, OfficeConnect queries the data in financial modeled data source each time you click:
• Refresh
• Expand
• Collapse
You can change the default Refresh behavior by adjusting the Explore settings in the workbook properties.
Workday also saves the financial reporting data model elements in OfficeConnect. OfficeConnect updates
the reporting data model elements only when you log in to Workday using the financials data source. If
you're logged in to OfficeConnect and the financial reporting data model updates, you need to log out and
log in to Workday from OfficeConnect to get the latest model elements.
Related Information
Reference
Reference: User, Workbook, and Selection Properties

Concept: Enforcing Security in OfficeConnect

Workday enforces security in OfficeConnect based on the user’s permissions. Your security access in
Workday determines:
• Your ability to log in to Workday from OfficeConnect.
• The lowest-level hierarchy subordinate from the reporting data model that OfficeConnect displays in the
Elements tab.
• The data in the spreadsheet.
To sign in to Workday from OfficeConnect, you must have permission on the Access Workday Financials
OfficeConnect security domain, and also have permission on at least 1 of these security domains:
• Reports: Financial Accounting (Company based)
• Reports: Organization Financial Reporting (Organization based)
• Reports: Organization Journal Lines (Organization based)
• Reports: Projects (Project based)
• Process: Budget (Company based)
• Reports: Company Financial Budgets (Company based)

• Reports: Manager Budgets (Organization based)

• Reports: Manager Financial Budgets (Organization based)
OfficeConnect displays model elements and data that Workday secures using at least 1 of these security
domains:
• Reports: Financial Accounting (Company based)
• Reports: Organization Financial Reporting (Organization based)
• Reports: Organization Journal Lines (Organization based)
• Reports: Projects (Project based)
• Process: Budget (Company based)
• Reports: Company Financial Budgets (Company based)
• Reports: Manager Budgets (Organization based)
• Reports: Manager Financial Budgets (Organization based)
The data in the modeled data source contains data controlled by multiple security domains. As a result,
when you create a report in OfficeConnect, you can see model elements and data that you have access to
from multiple domains.
When a user logs in to Workday from OfficeConnect, OfficeConnect stores their security permissions for up
to 1 hour.
Related Information
Concepts
Concept: Caching and Refreshing the Financial Modeled Data Source on page 813

Concept: Currencies and Currency Translation

The Workday Financial Management data that you report on might use different currencies for different
companies.
By default, Workday uses these currencies in the report you create in OfficeConnect:
• The ledger currency when you report on a single company.
• The configured default report currency when you report on any company hierarchy level.
• The configured default report currency when you select Corporate Currency from the Workbook
Properties.
You can perform currency translation by dragging a different currency onto a row or column in the report.
OfficeConnect uses the default translation rule set configured in the financial reporting data model when
performing currency translation. You can select a different translation rule set by applying a filter to the
worksheet or workbook. You apply filters to an individual worksheet or workbook, not to specific rows,
columns, or cells.
OfficeConnect stores the currency rates for up to 24 hours before retrieving the latest rates from Workday.
Related Information
Concepts
Concept: Caching and Refreshing the Financial Modeled Data Source on page 813
Add Elements to Report Filters

Concept: Differences Between OfficeConnect and Report Writer

This section describes the differences between reporting on journal line data using OfficeConnect with the
financial modeled data source and using Workday Report Writer with a Workday-delivered data source.

Eliminations
OfficeConnect supports intercompany elimination rules only. OfficeConnect doesn't support other
elimination rules, such as interworktag or noncontrolling interest (NCI).
OfficeConnect displays intercompany eliminations at the lowest common parent level.

Currency Translation Adjustment

OfficeConnect only uses Translation Loss account and its posting conditions for currency translation
adjustment.

Current Year Retained Earnings

OfficeConnect doesn't automatically calculate the current year retained earnings. To include current year
retained earnings in your worksheet, add a row that aggregates net revenue and expenses.

Filtering Data
OfficeConnect filters data differently than Report Writer. In Report Writer, data source filters, built-in
prompts, and report filters all filter the data displayed in the report in an additive way, further constraining
the data that ultimately is displayed.
OfficeConnect uses default values for filtering data in the report, and you can define filters at different
levels. The filters you define at the different levels might conflict with each other, so OfficeConnect follows
predefined precedence rules to determine what data to display.
Example: Cells override rows.

Breadth of Data
When you create a report in Report Writer, you specify a data source and data source filter to determine
the data that the report displays.
When you create a report in OfficeConnect, the modeled data source contains data that comes from
multiple security domains. The data you see in a report in OfficeConnect is all data you have access to
in all applicable domains. As a result, the data in your OfficeConnect report is a union of data you have
access to in multiple domains.

Rounding and Significant Digits with Currency Translation

Significant digits and rounding are important when performing arithmetic operations. When you report on a
currency that's different than the ledger currency, the report performs currency translation.
When performing currency translation, OfficeConnect and Report Writer round numbers at different times.
This difference in rounding might lead to a small, but noticeable difference in numbers when you compare
reports using the same data from each tool.
• OfficeConnect retains all significant digits without rounding when performing internal calculations.
OfficeConnect leaves all formatting decisions, such as rounding, to the user. Retaining the precision
until the last possible moment improves performance when performing currency translation.
• Report Writer performs currency translation for each journal line and then rounds the value before
performing other calculations.
If you compare the numbers in an OfficeConnect worksheet to a Workday Report Writer report with the
same data, there might be a difference in numbers due to the different method of handling significant digits.

Time Period Planning

If your plan is at a higher summary level than period, OfficeConnect uses the last period for any activity on
that plan and the last period's end date to match up with its translation exchange rate.

Example: If your plan is at the quarterly level for Q3 (Jul-Sep), the plan amount registers activity in
September and uses the September 30 end date for the currency translation exchange rate. A similar
impact would apply to a plan amount meant to cover an entire year.
In contrast, Report Writer uses the first period in the summary period but the end for the translation rate.
In the prior example, the plan amount registers activity in July, but uses the September 30 end date for the
currency translation exchange rate.
Related Information
Concepts
Concept: Default Types and Precedence Rules

Concept: Differences in OfficeConnect Between Financials and Planning

Data Sources
This table describes the differences in OfficeConnect between using the Financials data source and the
Adaptive Planning data source.

Functionality Financials Data Source Adaptive Planning Data Source

Elements hierarchy • Ledger Accounts • Accounts
• Company • Level
• Dimensions • Custom Dimensions

Workbook Properties: By default, we: By default, we:

• Round to • Select No Rounding. • Select Thousands.
• Report date • Don't select Make new time • Select Make new time
• Clear Data elements relative to the elements relative to the
report date. report date
• Don't select Always clear • Select Always clear data
data upon save. upon save.

Groups Not available Available

View cell details Use Show Details. Use Explore Cell.
Update Elements Doesn't update the element Updates the element structure in
structure in the Reporting pane. the Reporting pane to reflect the
OfficeConnect updates the data latest changes to the data model.
model elements only when you
sign in to Workday.
Versions The default version is Actuals. The default version depends on
You can select a plan element your model. You can override
from any plan structure that the default version by applying a
your administrator configures in version element to a report cell,
Workday. row, or column.
Exclude elimination elements Available in user settings and Not Available
when expanding Expand dialog
Time contexts and components Not available Available
Labels • Model label type is available. • Model label type isn't
• Account Contra Indicator label available.
type value isn't available. • Account Contra Indicator label
type value is available.

Functionality Financials Data Source Adaptive Planning Data Source

• Levels and dimensions include • Levels and dimensions include
these display type values: these display type values:
• Dimension short name • Dimension code
• Dimension display name • Dimension display name
• Label Suppression option • Dimension name
isn't available. • Dimension short name
• Label Suppression option is
available.

Effective Date for reporting on Available Not Available

dimension hierarchies
Multiple hierarchies per Available Only available for Time dimension
dimension

Benchmarking

Setup Considerations: Workday Benchmarking

Note: You must subscribe to Innovation Services to use this feature. Contact your Customer Success
Manager to request the Innovation Services Addendum (ISA), or see Workday Innovation Services in the
Workday Community for more information.
You can use this topic to help make decisions when planning your configuration and use of Workday
Benchmarking. It explains:
• Why to set it up.
• How it fits into the rest of Workday.
• Downstream impacts and cross-product interactions.
• Security requirements and business process configurations.
• Questions and limitations to consider before implementation.
Refer to detailed task instructions for full configuration details.

What It Is
When you opt in to Workday Benchmarking, you contribute your tenant data for the benchmark categories
and subcategories you select. Workday uses this data to calculate benchmark percentiles for your industry.
Workday Benchmarking is available through the Workday Benchmarking Innovation Service. Workday
Benchmarking includes these benchmarking groups:
• Human Capital Management.
• Recruiting.
• Time, Absence, and Payroll.
• Workday Usage.

Business Benefits
Workday Benchmarking enables you to compare data for your company with peers in your industry.
Workday Benchmarking provides on-demand benchmarks that your stakeholders can use to make
informed decisions about your business.

Use Cases
You can use Workday Benchmarking to:
• Compare your actuals data to benchmark data.
• Build custom reports based on benchmark report data sources (RDS).
• Create scorecards that include benchmark data.

Questions to Consider

Questions Considerations
Which benchmarks do you want access to? Certain benchmarks require you to configure your
tenant in a specific way. The amount of effort
required to set up Workday Benchmarking will
depend on which benchmarks you opt in to.
What are your internal company policies and local Workday de-identifies your data and uses
government regulations around sharing data? contribution thresholds so you can access
benchmarks while still meeting internal and
government privacy regulations.
Who needs to view benchmark values and actuals? Segment-based security is available for specific
benchmark categories and subcategories.
Who administers the Workday Benchmarking You can enable notifications on the Edit Tenant
feature for your company? Setup - Notifications task to notify your
administrators when changes to your tenant might
impact benchmark results.

Recommendations
Workday recommends you update your worker trending data after any changes to ensure that your data
contributions are accurate. Consider the impact on performance when updating trended worker data.
Workday recommends running this task during nonpeak hours.

Requirements
Workday requires you to contribute data in order to access benchmark values.
For your actuals to display correctly, your trending period on the Maintain Trended Workers task must
align with a standard monthly schedule. That is, your periods must begin on the first day of a month and
end on the last day of a month.
For Absence Policy benchmarks, you must map time off plans in your tenant to Workday time off plans.
For these benchmarks, you must correctly map your tenant values to standard values to receive accurate
benchmark data:
• Military Status.
• U.S. Diversity and Inclusion.
• Workforce Diversity and Leadership.

Limitations
Workday displays benchmark percentiles based on the number of participants who contribute data for that
benchmark. If the number of participants falls beneath certain thresholds, you can view only limited or no
data for that benchmark.

Tenant Setup
Enable trended worker data on the Edit Tenant Setup - Reporting and Analytics task to access HCM
and Absence benchmarks. You can also use this task to enable scorecarding, which enables you to view
benchmark data on your scorecards.
You can access the Edit Tenant Setup - Notifications task to enable notifications for the Benchmark
notification type.

Security
These security domains enable you to opt in to benchmarks and access benchmark values:

Domain Considerations
Benchmark Management Can opt in to benchmarks on the Benchmarking
Opt-In task.
Benchmark Values Can access benchmark percentiles for all
benchmarking groups.
Actual Values for Benchmarking Can access the Actual Values report field on the
Benchmark Value business object to create custom
benchmark reports.

These domains enable you to set up your tenant for Workday Benchmarking:

Domain Considerations
Manage: Innovation Services Can opt in to the Workday Benchmarking
Innovation Service on the Innovation Services
Opt-In task.
Benchmark Management Can map absence policy types on the
Maintain Dimension Mappings for Workday
Benchmarking task for Absence benchmarks.
Security Configuration Can access the Maintain Functional Areas task to
enable functional areas for benchmarking.
Set Up: Contact Info, IDs, and Personal Data Can map tenant values to standard values on these
tasks:
• Maintain Ethnicities
• Maintain Genders
• Maintain Military Status

Set Up: Tenant Setup - Reporting and Analytics Can enable worker trending and scorecarding on
the Edit Tenant Setup - Reporting and Analytics
task.
Custom Report Administration Can run the Create Worker Trending Data task.
Set Up: Tenant Setup - BP and Notifications Can enable benchmark notifications on the Edit
Tenant Setup - Notifications task.

Business Processes
No impact.

Reporting

Reports Considerations
Benchmark Definitions Enables you to view details about each benchmark,
including:
• The equation used to calculate the benchmark
value.
• Available dimensions.
• Your opt-in status.

Benchmark vs. Actual Enables you to view your company actuals

alongside benchmark percentiles.
Benchmark vs. Actual by Period Range Enables you to view benchmark values over a
period of up to 12 months.
Benchmark Values as a Source for Scorecard Enables you to create a scorecard that displays
benchmark values.

Integrations
No impact.

Connections and Touchpoints

Feature Considerations
Scorecards You can create a scorecard report that displays
benchmark data.

Workday offers a Touchpoints Kit with resources to help you understand configuration relationships in your
tenant. Learn more about the Workday Touchpoints Kit on Workday Community.
Related Information
Concepts
Concept: Workday Benchmarking on page 824
Concept: Workday Benchmarking Reports on page 826
Tasks
Set Up the Trended Workers Report Data Source on page 172
Reference
Workday Community: Innovation Services Descriptions and Exhibits

Steps: Set Up Workday Benchmarking

Context
You can set up Workday Benchmarking to contribute your de-identified Production tenant data to a
structured, secure data warehouse. Workday then makes these data available as useful benchmarks that
are representative of your industry.
Workday Benchmarking groups include:
• Human Capital Management.
• Recruiting.
• Time, Absence, and Payroll.
• Workday Usage.

Steps
1. Access the Innovation Services and Data Selection Opt-In report.
On the Innovation Services Opt-In task, select the Workday Benchmarking service on the Available
Services tab in the Analytics category.
On the Maintain Innovation Services Data Selection Opt-In task, click Next.
Security: Manage: Innovation Services domain in the Innovation Services functional area.
2. Access the Maintain Functional Areas task.
Select the Enabled check box for these functional areas:
• Benchmarking.
• Recruiting (to opt in to Recruiting benchmarking).
• Time Off and Leave (to opt in to Absence benchmarking).
• Time Tracking (to retrieve actual values in the Time Tracking benchmarking category).
Security: Security Configuration domain in the System functional area.
3. If you opt in to the U.S. Diversity and Inclusion benchmarking subcategory, access the Maintain
Ethnicities task and map the United States tenanted races to the standard races.
For the benchmarks and actual values to calculate correctly, map each of the standard U.S. Equal
Employment Opportunity (EEO) aliases, including Declined to Answer.
Security: Set Up: Contact Info, IDs, and Personal Data domain in the Contact Information functional
area.
4. If you opt in to the Workforce Diversity or Leadership benchmarking subcategories, access the
Maintain Genders task and map both tenanted genders.
Also, select either the Is Male or Is Female check box for both tenanted genders.
Security: Set Up: Contact Info, IDs, and Personal Data domain in the Contact Information functional
area.
5. If you opt in to the Military Status benchmarking subcategory, access the Maintain Military Status task
and map the United States tenanted military statuses.
For the benchmarks and actual values to calculate correctly, map each of the standard military statuses
including Not a Veteran.
Security: Set Up: Contact Info, IDs, and Personal Data domain in the Contact Information functional
area.
6. If you opt in to the Absence Policy subcategory, access the Maintain Dimension Mappings for
Workday Benchmarking and map time off plans in your tenant to Workday time off plans.
Security: Benchmark Management domain in the Benchmarking functional area.

7. Access the Edit Tenant Setup - Reporting and Analytics task and select:
• Enable Worker Trending to enable opt in to the Human Capital Management benchmarks.
• (Optional) Enable Scorecarding to create custom metrics and scorecards based on benchmarking
data. This step enables you to view your benchmark data on your scorecard.
Security: Set Up: Tenant Setup - Reporting and Analytics domain in the System functional area.
See Reference: Edit Tenant Setup - Reporting and Analytics.
8. Access the Create Worker Trending Data task.
Access this task after any updates to worker trending data, such as ethnicity or gender, so your data
contributions and benchmarking actuals reflect these updates.
Consider the impacts on performance when using the Create Worker Trending Data task. Workday
recommends running this task during nonpeak hours.
Security: Custom Report Administration in the System functional area.
9. Edit Domain Security Policies.
Set up domain security access to the Benchmark Management domain to enable your benchmarking
administrator to opt in to benchmarking. To enable the benchmarking administrator to see benchmarks
and actuals, set up access to these domains:
• Benchmark Values
• Actual Values for Benchmarking
Workday doesn't deliver a Benchmark Administrator security group. However, you can create a user-
based security group for people in your organization who should have access to set up benchmarks.
10.(Optional) Set up segment-based security to control access to benchmarks in specific benchmark
subcategories.
See Steps: Set Up Workday Benchmarking Subcategory Security on page 822.
11.Opt in to Benchmarking on page 823.
12.(Optional) Set up notifications for the Benchmark notification type.
See Steps: Set Up Workday Notifications.
Related Information
Concepts
Concept: Notifications
Tasks
Set Up the Trended Workers Report Data Source on page 172
Reference
Workday Community: Innovation Services Descriptions and Exhibits

Steps: Set Up Workday Benchmarking Subcategory Security

Context
You can set up segment-based security to control access to benchmarks and actuals in specific
subcategories. Example: You can set up segment-based security to give an HR executive visibility of
benchmarks and actuals for selected HR benchmark subcategories.

Steps
1. Create User-Based Security Groups.
Create a new unconstrained security group or use an existing one, and add users to the group.

2. Access the Create Benchmark Subcategory Security Segment task.

Select the subcategories to include in the security segment.
Security: Benchmark Management domain in the Benchmarking functional area.
3. Create Segment-Based Security Groups.
Create a new segment-based security group, and add:
• The unconstrained security group.
• The security segment for the benchmark subcategory.
4. Add the segment-based security group to the Benchmark Values domain.
5. (Optional) To grant access to the tenant actual values, add the unconstrained security group to the
Actual Values for Benchmarking domain.

Result
The segment-based security group members can only see benchmarks and actuals for those
subcategories you add to the security segment for the benchmark subcategory. You can use the Delete
Benchmark Subcategory Security Segment task to delete a segment if it isn't used in any security
groups.

Opt in to Benchmarking

Prerequisites
• Set up Workday Benchmarking for your tenant.
• Security: Benchmark Management domain in the Benchmarking functional area.

Context
You can contribute your Production tenant data for the categories and subcategories you select by opting
in to benchmarking. You can opt in to benchmarking for all or individual categories and subcategories for a
benchmarking group.
Benchmarks are available only for the Workday services to which you subscribe:
• To opt in to Recruiting benchmarking, you must be a Workday Recruiting customer. Workday also
requires a minimum of 20 job applications in your tenant to opt in.
• To opt in to Time, Absence, and Payroll benchmarking, you must be a Workday Payroll customer.
You can exclude data contribution by country for categories that support the country dimension. Excluding
countries can impact benchmark data visibility if data contribution falls below the minimum participation
threshold.
When you set up Workday Usage Metrics security, Workday automatically opts you in to benchmarks in
the Workday Usage category and subcategories.
When you opt out of a subcategory:
• You no longer contribute nor can you view benchmark data for benchmarks in that subcategory.
• Workday removes your tenant data from benchmark calculations after the next complete refresh of the
benchmark dataset.

Steps
1. Access the Benchmarking Opt-In task.

2. As you complete the task, consider:

Option Description
My Industry Group Workday returns benchmark data at the industry
group level until enough data is available to return
My Industry
results at the industry level.
Subscribe to all Current and Future Categories Select to opt in automatically to any new
benchmarks, categories, and subcategories
added in the future.
Subscribe to all Current and Future Select to opt in automatically to benchmarks for
Subcategories any new subcategories added to the category in
the future.
Countries Excluded from Data Contribution When you exclude data contribution for a country,
you can still report on benchmarking data for that
country.

Result
Workday makes this data available immediately:
• Workday Usage category benchmark data, when you've enabled security to Workday Usage Metrics.
• Benchmark data for opted-in subcategories. This benchmark data doesn't include your data
contributions until the next benchmarking processing job runs in your tenant.
• Actual values for your tenant.
Workday schedules calculation of the non-Workday Usage benchmarks you opt in to for the next
scheduled benchmarking processing job. Workday:
• Collects 12 months of data for opted-in subcategories.
• Makes data for the previous month available by the sixth of the month.
Related Information
Concepts
Concept: Workday Usage Metrics
Tasks
Steps: Set Up Workday Benchmarking on page 820

Concept: Workday Benchmarking

Note: You must subscribe to Innovation Services to use this feature. Contact your Customer Success
Manager to request the Innovation Services Addendum (ISA), or see Workday Innovation Services in the
Workday Community for more information.
The Workday Benchmarking service enables you to compare your key performance indicators to metrics
from peers in your industry. Workday de-identifies the benchmarking data to ensure that no one can
identify data for a specific customer. You can explore benchmarking data for various opted-in categories
and subcategories. Workday Benchmarking groups include:
• Human Capital Management.
• Recruiting.
• Time, Absence, and Payroll.
• Workday Usage.
With Workday Benchmarking, you can:
• Build custom reports based on benchmark report data sources.

• Compare your actuals data to benchmark data.

• Filter benchmarks by dimensions.
• Use benchmark data with scorecards.
When you set up Workday Usage Metrics security, Workday automatically opts you in to benchmarks in
the Workday Usage benchmarking category and subcategories.

Benchmarking Data Collection

Workday collects and displays Production tenant data only for the subcategories that you opt in to.
Workday protects the identities of benchmark participants through multiple methods, including:
• De-identification.
• Encryption.
• Meeting minimum customer participation threshold.
Workday enables you to exclude data contribution for specific countries when you opt in to applicable
categories. Excluding countries impacts benchmarking results and can restrict access to data if
contributions are fewer than the minimum participation threshold.
You can set up benchmarking in your non-Production tenants the same way you do in your Production
tenant. Workday doesn't collect data from your non-Production tenant, and benchmarking results returned
in your non-Production tenant represent mock data.

Benchmarking Data Availability

Workday calculates your non-Workday Usage benchmarks when the next scheduled benchmarking
processing job runs. Benchmark results don't include your contribution until the job runs for your tenant.
Workday makes data for the previous month available by the sixth of the month.

Benchmarking Industry Groups and Industries

When you opt in to Workday Benchmarking, you can select only a single primary industry and industry
group. This functionality prevents double-counting of your data contributions when calculating benchmark
values. However, you can view benchmarks for any industry or industry group for the categories and
subcategories you opt in to.

Benchmarking Groups, Categories, and Subcategories

Workday organizes benchmarks by:

Level Description
Group A grouping of benchmarking categories by data
type.
Category Functional grouping of subcategories.
Subcategory Functional grouping of similar types of benchmarks.

You can click the related actions menu of benchmarking subcategories on the Benchmarking Opt-In task
to display:
• Benchmarks and their descriptions.
• Components, which are measurements that make up a benchmark expression used to calculate each
benchmark.
• Data granularity of tenant contribution for benchmark components in the subcategory.
• Dimensions supported for filtering.

Benchmarking Notifications
You can enable notifications on the Edit Tenant Setup - Notifications task to notify your benchmarking
administrators when changes to your tenant might affect your benchmarks. Workday sends a notification
when your tenant no longer meets eligibility criteria for a benchmark subcategory. Certain tenant
changes can prevent you from contributing data for a benchmark subcategory and viewing benchmark
data. Workday checks your tenant every month and sends a notification to all users in the Benchmark
Management domain when you need to take action.
Related Information
Concepts
Concept: Workday Usage Metrics
Concept: Notifications
Tasks
Steps: Set Up Workday Benchmarking on page 820

Concept: Workday Benchmarking Reports

You can use Workday-delivered reports or create custom reports to view benchmarking data.
Workday enables you to filter benchmarking data by dimension, including:
• Absence Policy.
• Benchmark.
• Country.
• Gender.
• Industry.
• Industry Groups.
• Size, which is number of employees.
• Workday Tenure, which represents the length of time in years between the current date and the move-
to-production date for your tenant. If you don't have an active Production tenant, you won't see any
values for this dimension.
• Worker Type.
For benchmarking reports, Workday precalculates and displays benchmarking percentile data based on
the number of participants. Workday displays:

Participants Data Returned

Fewer than 6. No percentile data for row.
6 to 11 inclusive. 25th, 50th, and 75th percentiles.
More than 11. 10th, 25th, 50th, 75th, and 90th percentiles.

Benchmarks are only available for full calendar months. If you select a benchmarking period start or end
date for any day of a month, Workday delivers benchmarking data that represents that entire calendar
month.

Workday-Delivered Benchmarking Reports

Benchmark Definitions Report With this report, you can view:

• The calculation that Workday uses to determine
the benchmark value.
• Which dimensions are available for each
benchmark.

• Your opt-in status for the benchmark

subcategory.
• The countries that you've excluded from data
contribution.

Benchmark vs. Actual Reports You can use these reports to compare your actuals
to benchmarks in the categories and subcategories
you opt in to:
• Benchmark vs. Actual.
• Benchmark vs. Actual by Period Range, for a
maximum 12-month range.
Workday returns benchmarks based on the
dimension values you select.
For your actuals to display correctly, the fiscal
period specified in the Maintain Trended Workers
task must align with a standard monthly schedule.
That is, your fiscal periods must begin on the first
day of a month and end on the last day of a month.

Benchmark Values as a Source for Scorecard Workday enables you to use benchmarking data in
Report your custom metrics that use the WD Matrix Report
calculation type. The Benchmark Values as a
Source for Scorecard report is a matrix report,
based on the Trended Benchmark Values report
data source (RDS). With this report you can:
• Copy and edit report data. Example: You can
remove benchmarking percentile fields from your
custom report definition.
• Use as the source matrix report. Set up
your metric calculation on the Calculation
Configuration tab on the Edit Custom Metric
task.
When you set up metrics based on benchmarking
data, consider:
• The metric calculation must reference a custom
report based on the Benchmark Values As a
Source for Scorecard report.
• Workday returns the benchmark value at the
tenant, not organization, level.
• Workday calculates benchmarks based on
standard benchmark definitions and dimension
values that you select.
• Workday only returns data for the latest
benchmarking period.
• When creating a scorecard composite report,
you must set the Target to Benchmark Value on
the KPI Card Layout setting.

Custom Benchmarking Reports

Workday enables you to create simple or advanced custom reports from these benchmarking RDSs and
enable them on custom or Workday-delivered dashboards:

• Benchmark Definitions
• Benchmark Values
• Trended Benchmark Values
For reports based on these RDSs:
• Benchmark Values
• Trended Benchmark Values
Workday doesn't support:
• Drill down on actuals.
• Effective-dated reporting.

Reference: Benchmarking Security Domains and Report Data Sources

Workday Benchmarking Security Domains

Workday Benchmarking includes these security domains:

Security Domain Description Restricted to Security Suggested Security

Group Types Groups
Benchmark Grants access to Unconstrained. Administrators who
Management administrator tasks, should have access to
reports, and objects set up benchmarks.
related to benchmarking
services. Includes the list
of benchmarks available
for opt in.
Benchmark Values Grants access to Unconstrained and Analysts and any other
benchmarking data only. Segment - Benchmark user group that should
Values. have access to view
benchmarks.
Actual Values for Grants access to the Unconstrained. Executives, senior
Benchmarking Actual Values report management, and
field on the Benchmark any other user group
Value business object. authorized to view
company actuals in
addition to benchmarks.

Workday Benchmarking Report Data Sources and Domain Security

Workday Benchmarking includes these report data sources (RDSs):

Benchmark RDS RDS Description Primary Business Security Domain Workday

Object Standard Reports
Based on RDS
Benchmark Provides a list Benchmark Benchmark Benchmark
Definitions of benchmarks Definition Management Definitions
available for opt
in. Includes data
fields related
to benchmark
calculation

Benchmark RDS RDS Description Primary Business Security Domain Workday

Object Standard Reports
Based on RDS
expressions and
descriptions.
Benchmark For reports based Benchmark Value Benchmark Values Benchmark vs.
Values on this RDS, Actual
Workday doesn't
support:
• Drill down on
actuals.
• Effective-dated
reporting.

Trended You can use this Benchmark Value Benchmark Values Benchmark vs.
Benchmark RDS to create an Actual by Period
Values advanced custom Range
report that includes
Benchmark
benchmarking data
Values As a
filtered by time
Source for
period.
Scorecard
Each customer
contributes 12
months of data
for opted-in
subcategories.
For reports based
on this RDS,
Workday doesn't
support:
• Drill down on
actuals.
• Effective-dated
reporting.

Benchmarking-Related Business Objects and Fields

You can access the Business Object Details report to see related business objects and fields for
Workday Benchmarking business objects. You can also access the Data Sources report, and select the
related actions menu on a data source to see available fields.

FAQ: Workday Benchmarking

I signed the Benchmarking Services order form There can be several reasons why you don't see
and opted in to nonusage benchmarks. When benchmarks to which you opted in:
I run a report, why don't I see results for the
• You haven't completed the necessary setup for
nonusage benchmarks?
the opted-in subcategories.
• The minimum threshold for customer
participation in the opted-in subcategory
isn't sufficient, so Workday doesn't display
benchmarks.

• The most recent status of your signed

Benchmarking Services order form doesn't
reflect in your tenant. You must log a new
Workday Support case to update your tenant
status.

I didn't sign the Innovation Services Agreement Workday Usage benchmarks access comes from
nor Benchmarking Services order form, so why your Workday usage metrics authorization.
am I seeing Workday Usage benchmarks?
I didn't opt in to any benchmarks. Why do I see Since all customers are eligible for usage metrics,
a DAAS Job in the Process Monitor report? they contribute data to usage-related benchmarks.
Also, why am I seeing a daas-integration user? Workday runs a regular job named DAAS Job that
extracts usage benchmarks. Workday creates a
daas-integration username the first time the job
runs in your tenant. You can't use daas-integration
to sign in to a user-interface session in Workday.
I'm already a Workday Benchmarking customer No, opting in to Innovation Services doesn't
through the Benchmarking Services order affect your access to Workday Benchmarking
form, and I just signed the Innovation functionality. However, Workday recommends that
Services Agreement. Do I need to take any you select the Workday Benchmarking check box
additional steps to continue benefiting from on the Innovation Services Opt-In task.
benchmarking?
Note: If you clear the Workday Benchmarking
check box on the Innovation Services Opt-In task,
you'll opt out of benchmarking even if you've signed
the Benchmarking Services order form.

Related Information
Concepts
Concept: Workday Usage Metrics

Glossary

Glossary
In this book, you can explore Workday glossary terms.

Cross Application Services Glossary

Aggregation Security Group

A security group whose members are other security groups. Grants access to workers associated with any
included security group.

Approve
An action in a business process that designated participants select to progress the event to the next step.

Assignable Roles
Positions you can assign to organization roles.

Business Object
Objects used to store data in Workday (such as organizations or workers). A business object has fields and
instances, which are analogous to rows and columns in a spreadsheet. Workday links related business
objects: a worker is associated with a position, the position to a job profile, and so on.

Business Process Definition

The tasks that compose a business process, the order in which they must be done, and who can do them.

Business Process Instance

A business process that the initiator has started. The Hire Employee for Organization X business process
definition becomes an instance when the initiator uses it to hire an employee.

Business Process Security Policy

A business process security policy secures the steps and process-wide actions including view, rescind,
cancel and correct. It specifies which security groups have access to each action.

Cancel (business process)

Canceling a business process stops the workflow in progress and reverses changes made to data. You
can't cancel a completed business process; you must rescind it. A securable action in a business process
security policy.

Conditions
Conditions are one or more logical matches that are resolved to True or False and used to decide if some
action should be taken. You can add conditions to steps in a business process to determine if the step
should run.

Contextual Custom Report

A custom report created from the related actions menu of a Workday object by selecting Reporting >
Create Custom Report from Here. Simplifies choices of data and fields to those related to the context of
the object.

Correct (business process)

Correcting a business process changes a specification or data in the workflow while in progress. A
securable action in a business process security policy.

Custom Report
Reports not delivered by Workday and built using the Workday Report Writer. Can be created new or by
copying another standard or custom report.

Dashboard (landing pages)

A specialized landing page containing a set of pre-configured worklets for a functional area that you can
copy or modify. You can add additional custom worklets to dashboards using the report writer.

Data Source
A data source defines a set of business object instances for reporting purposes. Allows reporting access to
all business objects related to those in the data source.

Deny (business process)

When you deny a business process, the business process is terminated and all Workday data is restored
to its state before the business process started. To restart the business process, you need to submit the
process again, and redo all previously completed steps.

Domain
A collection of related securable items such as actions, reports, report data, report data sources, or custom
report fields. Each domain is secured by a domain security policy.

Domain Security Policy

A collection of related securable elements of different types and user-specified security groups that have
access to elements of each type.

Event
A business process transaction that occurs within your organization, such as hiring or terminating an
employee.

Functional Area
A collection of domain or business process security policies that are related to the same set of product
features, for example, Benefits or Compensation.

Intersection Security Group

A security group whose members are other security groups. Members associated with all included security
groups are granted access through an intersection security group.

Initiation Step
The first step of a business process.

Job-Based Security Group

A security group that includes one or more job-related attributes or objects including job profile, job family,
job category, management level, or exempt/non-exempt status.

Landing Page
Landing pages display a collection of worklets. Landing pages may have different display formats (grid or
bubble) and support different functions. The Home landing page is intended for common worklets, such as
self-service worklets.

Location Membership Security Group

A security group whose members are any workers assigned to that location.

Organization Security Group

A security group whose members are any workers assigned to that organization.

Position Management Staffing Model

A structure that defines different staffing rules and restrictions for each position in an organization.

Position Restrictions
The attributes and conditions that apply to an unfilled position in a supervisory organization that uses the
position management staffing model. Example: Job profile, location, qualifications, and worker type.

Primary Business Object

When defining a report, the primary business object is the business object returned by the data source.

Predefined Security Group

Security groups whose members are assigned through a business process. These groups cannot be
changed except by reversing the business process or executing a new business process, such as applying
for a position, or being hired. Examples include: Employee, Contingent Worker, and Pre-Hire.

Related Business Object

When defining a report, fields that return objects related to the primary business object are said to contain
related business objects. These related objects may have their own set of fields that can be included in the
report.

Report Data Sources

Predefined groups of logically related fields, used when creating reports with Report Writer, which define
the data in the report row. For example, the Employees report data source contains contact information,
personal data, and identification information. Report data sources also include which roles have access to
see the report data.

Rescind (business process)

On completed business processes, reverses all changes made to Workday data. A securable action in a
business process security policy.

Role Assignee
A person, position, or position restriction assigned to a role.

Role Assigner
A business object that you assign a role for. It is also called a role-enabled object.

Role Assignment
The combination of a role assigner and a role.

Role Assignment Snapshot

A view of the status of a role assignment at a specified moment in time.

Role-Based Security Group

A security group that specifies one organization role and includes workers in positions defined for that
organization role.

Roles
Groupings of specific responsibilities within an organization that are assigned to positions. A role is
assigned to a security group to gain access to data associated with the role's responsibilities.

Securable Item
An action, report, or data that is part of a security policy. You secure access by defining the security
policy to restrict access to an item to specified security groups. Related securable items are grouped into
domains.

Security Group
A collection of users or objects that are related to users. Security group access to a securable item in a
security policy grants access to the users associated with the security group.

Segment
A grouping of related securable items, such as pay components, that can be secured together using a
segment-based security group for that segment.

Standard Report
Reports that Workday creates and delivers to all Workday customers. Workday creates standard reports
using Report Writer or XpressO, an internal development tool. You can only copy and modify standard
reports created with Report Writer.

Target
The object that a business process operates on. For example, for business processes that deal with an
employee record, the target is the employee. Because the target determines the organization, it controls
which business process custom definition Workday uses.

Task
A step, either standalone or in business process, that you must complete. For example, task alert
notifications are triggered by steps in a business process.

Temporary Report
A custom report that you designate as Temporary when creating the report. Workday automatically
deletes temporary simple reports after 7 days. For advanced and matrix reports you can change the
Temporary option on the Advanced tab of the report definition.

To Dos
Reminders to do something outside of Workday. They can be part of business processes, and must be
marked complete before the workflow will advance to the next step.

User-Based Security Group

A security group whose members are workers. In a security policy, it grants access to the securable items
to all members of the group.

View (business process)

A securable item used to allow members to view status of a business process and report on it. A securable
item in a business process security policy.

View (permission)
The ability to see objects or data through the Workday user interface, when permitted in a domain security
policy.

Worklet
A compact report displayed as an icon (a tile or a bubble) on any landing page, providing easy access
to tasks and information that are used regularly. Examples: My Leadership Roles, Open Positions, and
Anniversaries.

Worktag
A named attribute that you can assign to events and objects to indicate their business purpose. For
example, you can create a Customer worktag, whose values are the names of your customers. You can
use the worktag to assign a customer to an expense in an expense report or a product sales event.

Financial Management Glossary

Accounting Cash
A group of cash ledger accounts that you can use to check cash balances against during settlement.

Accounting Cash Pool

One or more primary balancing worktag hierarchies that you can use to pool cash ledger balances for cash
balance checks during settlement.

Award
A contract agreement with your sponsor in the form of funding to perform an activity for a public purpose.
It defines how to capture direct and facilities and administration costs, recognize revenue, and bill your
sponsor.

Award Costs Processing (ACP)

Processing facilities and administration costs and revenue recognition related to spend transactions on
awards.

Award Credits
Percentage of award or award lines you allocate to specific worktags for reporting purposes.

Basis Limit
The maximum amount of direct costs you can use to calculate facilities and administration costs.

Cost Reimbursable Spend

A billing item that Workday creates to help you bill your sponsor for award-related spending. The cost
reimbursable spend amount includes both the original spend amount and any overhead costs Workday
calculates based on your award costs configurations.

Estimate at Completion (EAC)

Includes all the hours logged and approved for the project, as well as the future hours the worker expects
to complete.

Estimate to Completion (ETC)

Includes the future hours the worker expects to complete.

Grant
A worktag that you can use to capture expenses.

Object Class
The spend categories that award sponsors agree to reimburse award recipients for maintaining their
projects.

Payment Group
The payments that result from a settlement run.

Project Advanced Labor Costing

Prorating project labor costs using standard or fully burdened costing.

Project Asset
A container that captures separate, ongoing costs of a capital project in progress. You can associate
multiple projects assets with a project to track costs over the life of a project.

Revenue Category
An attribute in customer contracts and billing used to search for and report on goods and services you sell.
Also a dimension in account posting rule types for customer contracts, billing, and accounts receivable that
drives accounting behavior.

Spend Category
A logical grouping to search and report on acquired items and services. Also a dimension in account
posting rules for procurement and spend that drives accounting behavior.

Unnamed Resources
Placeholders for project resources that you can use to assign tasks and perform resource forecasting
without specific resource assignments.

HCM Glossary

Academic Unit
A Workday organization type that represents a school, college, university, or other unit of your institution.
These units can recruit prospective students, admit students, offer programs of study or courses, or
administer financial aid. Academic units are also used with academic appointments in Workday.

Academic Unit Hierarchy

A hierarchical grouping of academic units primarily used for roll-up reporting.

Active Candidate
A person with an application for a specific job requisition. Candidates must be linked to a job requisition for
Workday to initiate a job application event.

Auto-fill
A time entry option that copies time blocks from a worker's schedule or from a previous week when
entering time.

Base Pay Element

The compensation components that are included in the calculation of base pay for the purposes of
determining the compa-ratio and target penetration.
Example: Include both base pay and bonuses in the base pay calculation for compa-ratio.

Benefit Defaulting Rule

A rule that identifies the benefit plans, coverage targets, and coverage amounts that employees receive by
default when they do not complete an enrollment event.

Benefit Event Rules

These rules specify coverage increase limits, EOI requirements, waiting periods, and other rules and
conditions of enrollment for benefits enrollment events.

Benefit Event Type

Identifies the events that trigger benefit enrollment, such as open enrollment, new hires, or the birth of a
child. It also identifies the coverage types to make available to employees for when an event of this type
occurs.

Calculated Time
Result of applying time calculations to a worker's reported time. Automates application of company or
regulatory rules.

Calendar-Based Time Entry

A time entry method that uses the time entry calendar as the focal point for entering, editing, and
submitting time.

Candidate
Candidates include both prospects and active candidates.

Candidate Pipeline
All active candidates.

Candidate Pool
Candidates grouped together based on specific criteria.

Cascading Leave
A sequence of related leave types that are linked together. When an employee meets the conditions
defined for ending a leave, Workday generates a return from leave request and a separate request for the
next leave.

Compensation Basis
A grouping of compensation components, such as salary, commission, and allowance plans, that define
estimated earnings for an employee population.

Compensation Component
The umbrella term for compensation packages, grades, grade profiles, and plans that can be associated
with compensation eligibility rules.

Compensation Defaulting Rule

A rule that establishes the criteria for how compensation components default to worker compensation
during staffing transactions (such as hire or job change).

Compensation Element
Compensation elements link Compensation to Payroll. When a compensation element is attached to a plan
that is assigned to an employee, Workday can determine which earnings to use to pay the employee.

Compensation Package
A grouping of compensation guidelines (grades, grade profiles, and their associated steps) and plans that
you can assign to workers as a set. Packages provide a quick view of the eligible plans for a particular job
or group of employees.

Compensation Rule
Guidelines for determining which workers are eligible for which components of compensation.

Compensation Step
A specific monetary amount within a grade or grade profile.

Compensation Target Rule

A rule used to segment your employee population for assignment of compensation plans.

Conditional Calculation
Time calculation that tags time blocks that meet certain conditions.

Coverage Target
Defines whether a specific health care plan or insurance plan applies only to the employee or also to the
dependents, spouse, family, and so on.

Cross Plan Dependency

Limits the coverage options available to workers during an enrollment event based on their choice of other
benefit plans and coverage amounts.
Example: You can limit coverage in a specific plan to a percentage of the total coverage in 1 or more other
benefit plans.

Day Breaker
The time of day on which a worker's work day and work week begins. Defines the 24-hour period over
which daily time calculations execute and the 168-hour period over which weekly time calculations
execute. Unless otherwise specified, the default day breaker is 12am.

Disposition
Status of candidates that have been rejected for hire or declined a job during the job application event.

Enrollment Event Rule

A rule that defines coverage start and end dates, waiting periods, coverage increase limits, Evidence of
Insurability requirements, and other coverage rules and conditions. Rules ensure that the benefits process
presents only the options that each employee is eligible for based on the event type.

Grade Profile
A breakdown of a compensation grade by functional task, geographical region, or other categorization your
business requires. A profile enables you to assign more granular compensation ranges to workers.

Headcount Plan
Provides visibility into the number of workers necessary to achieve your business goals within a specified
period of time.

Individual Target
An individual bonus or merit target for a worker during a compensation review process that overrides the
target defined on the compensation plan.

Job Management Staffing Model

A structure that defines 1 set of hiring restrictions for all jobs in a supervisory organization, with no specific
limits on the number of jobs that can be filled.

Job Profile
The generic features and characteristics of a job or position, such as management level, pay rate type,
compensation, skills, and other qualifications.

Leave Family
A set of similar leave of absence types. Example: A company-specific family includes disability leave and
bereavement leave, while a separate regulatory family includes jury duty and family medical leave.

Leave of Absence Rule

A rule that defines worker eligibility for leaves of absence.

Linked Leave
A leave type that shares an entitlement with other leave types or time offs. Eligibility rules, validation rules,
and supporting data reference the combined balance of the associated leave types and time offs. Also
known as coordinated leaves and time off.

Micro-edit
The ability to edit existing time blocks or add time blocks directly to a day by clicking the time entry
calendar.

Multiplier-Based Coverage
Insurance coverage based on multiples of salary, such as 1x, 2x, or 3x salary.

Passive Event
Events that result from the passage of time rather than from a specific change to employee data.

Position Management Staffing Model

A structure that defines different staffing rules and restrictions for each position in an organization.

Pre-Hire
In Staffing, an individual you're tracking before employment. In Recruiting, a candidate who is in the Offer,
Employment Agreement, Background Check, or Ready for Hire stage.

Prospect
Someone you are interested in tracking who isn't associated with a specific job. You can use tags,
prospect types, and prospect statuses to help track these individuals.

Quick Add
A time entry option that enables you to create a time block and copy it to multiple days in a week.

Reference Pay Range

A range of pay established for a compensation grade or grade profile.

Reported Time
A worker's time that has been entered, but has not had any time calculations applied.

Staffing Model
A structure that defines how jobs and positions are created and filled in a supervisory organization.
Workday supports 2 kinds of staffing models:
• Job management.
• Position management.

Staffing Organization
An organization category that includes supervisory organizations, matrix organizations, or retiree
organizations.

Termination Adjustment
A time off adjustment that automatically sets the remaining balance of a worker's time off plan to zero upon
the worker's termination.

Time Block
A time block carries information about a portion of time, such as the number of hours worked or in/out
times. Time blocks can be reported or calculated, but only calculated time blocks are pulled into Workday
Payroll.

Time Calculation
A set of rules to apply time calculation tags to calculated time blocks for Payroll or other purposes.
Example: You could create a time calculation to convert regular hours into overtime hours automatically if a
worker works more than 40 hours in a week.

Time Calculation Tag

Workday applies calculation tags to time blocks during time calculations. The tags map to payroll earnings
to drive how time blocks are paid and can be included in time off and accrual calculations. You can also
use them to display time and time off totals on the time entry calendar.

Time Clock Event

A time clock event describes a worker's actions, such as a check in or check out, on the web time clock
or an external time clock. Workday matches time clock events to form time blocks, which workers can edit
and submit.

Time Code Group

The primary use of a time code group is to determine which time entry codes a worker is eligible for. Time
code groups are assigned to a worker or to a position through eligibility rules.

Time Entry Calendar

A set of self-service pages that workers use to enter, edit, and submit time, when using calendar-based
time entry. When using high volume time entry, workers can view and submit time from the time entry
calendar.

Time Entry Code

A time entry code describes the type of time a worker enters, such as worked time or meal allowance. To
use time entry codes, you must attach them to time code groups, except for the default time entry code
assigned to a time entry template.

Time Entry Template

A template defines how a worker's time entry calendar is configured. Workers are matched to time entry
templates through eligibility rules.

Time Entry Validation

Errors or warnings that prevent users from entering invalid time. Critical validations prevent a user from
submitting time. Warnings display when entering time but don't prevent the worker from submitting time.

Time Off
The rules that apply to a specific type of time off, including eligibility rules, whether adjustments are
allowed, and limits that differ from the time off plan.

Time Off Plan

The rules for entering and tracking 1 or more related time offs. Identifies the unit of time, eligibility
requirements, whether to track balances, and if time offs are position-based or worker-based.

Time Period Schedule

A time period schedule defines which dates are available for entry at a given time and defines which dates
are paid in which pay periods. They can line up with pay periods, or, in more complex scenarios, they can
be paid on a lag.

Time Proration Rule

A rule that prorates employees' target compensation in a bonus or merit increase compensation event
according to time-based criteria, such as leave of absence or time since hire.

Time Shift
A grouping of consecutive time blocks that you can use in standard overtime calculations, time block
conditional calculations, and validations.

Worker
An employee or a contingent worker.

Work Schedule Calendar

A calendar that defines the days and hours that a worker is scheduled to work. In Time Tracking, work
schedule calendars affect time entry options, calendar displays, and time calculations.

Integration Glossary

Connector
A set of 1 or more integration templates that provide a framework for building integrations in a particular
functional area. The integration can support a specific type of data, or can support a specific endpoint
(example: Salesforce.com or Okta).

Enterprise Interface Builder (EIB)

An integration tool that enables you to create simple, secure, and customizable integrations with Workday.
Alternately, an EIB is a simple integration created by the integration tool. An EIB consists of an integration
system, an integration data source, an integration transformation, and an integration transport protocol.

Field Overrides
A tool that lets you customize integration systems that are based on a connector template. Field overrides
are managed through an integration service. They use calculated fields or report fields to supply values to
an integration system. Example: member IDs in benefit provider integrations.

Integration Attribute
An integration component that specifies the tenanted value of a data element in Workday. Example: Plan
Sponsor Name is a type of attribute in benefit provider integrations.

Integration Data Source

Indicates the type of data that Workday receives from or exports to an external system and its location.

Integration Map
An integration component that specifies how values in Workday map to values in an external system.
Example: Pay Rate Frequency is a type of map in third-party payroll integrations.

Integration Service
A group of related integration attributes, maps, and XSLT that provides a framework to transform Workday
data into the format required by an external system.

Integration System
A tenanted definition of an integration between Workday and an external system based on a template that
provides the methodology for communicating data.

Integration Template
A collection of integration services that enables communication between Workday and an external system.
Workday provides integration templates in categories such as Benefits, Financials, HCM, Payroll, Payroll
Interface, Procurement, Recruiting, Security, and Settlement. Many of the delivered templates contain
default values for attributes, as well as prompt values for attributes and maps, to define the integration
further.

Integration Transformation
Converts data into a format that Workday or a receiving external system can understand. Workday
provides some delivered transformations, and you can also create custom transformations.

Integration Transport Protocol

Controls how Workday exports data to an external endpoint or service or imports the data from an external
endpoint or service. Workday supports several types of transport protocols, including email, FTP and
SFTP, HTTP/SSL, Workday attachments, and Workday Web Services.

Reference ID
A unique identifier used to look up data for integration purposes.

System User
An account associated with and required to launch a Connector or Studio integration. Workday delivered
integrations and custom integrations require a system user account for authentication and web service
calls. A system user account is not associated with a person in Workday.

Workday Studio
An Eclipse-based development environment that enables you to build more complex integrations with
Workday.

Workday Web Services

Workday’s public API. Based on open standards, Workday Web Services (WWS) provide the core method
for integration with Workday.

Payroll Glossary

Manual Payment
A record of a payment made outside of Workday Payroll used to maintain accurate payroll information.
Example: Payments for the exercise of stock options.

Off-Cycle Payment
A payment made outside the regularly scheduled payroll run. Manual, on-demand, reversals and history
payments are classified as off cycle.

On-Cycle Payment
A payment made in a scheduled payroll run.

On-Demand Payment
An off-cycle payment that replaces, or is issued in addition to, a worker's on-cycle pay.

Pay Component Group

A collection or combination of related earnings, deductions, or pay component related calculations
combined to simplify payroll calculations.

Pay Component Related Calculation (PCRC)

A related calculation that resolves automatically with earnings and deductions. Often used in the earning or
deduction definition, can be used to display on pay results.

Pay Run Group

A set of pay groups that share a period schedule. Used to process multiple pay groups at the same time.

Payroll Effect
An option available in Workday Absence Management to stop paying workers while on leave. You can
configure a run category to pay workers on certain leave types when the Payroll Effect option is enabled for
the leave type.

Related Calculation
A calculation that returns a value, such as hours, rate, or percent.

Run Category
Specifies which employees to process, and which pay components to calculate for each type of payroll run.

Student Glossary

Academic Date Range

The period of time associated with a student recruiting cycle.

Academic Unit Hierarchy

A hierarchical grouping of academic units primarily used for roll-up reporting.

Application Grouping
A grouping of applications for the same admitting level of an academic unit and the same anticipated start
date. Groupings can have 1 or more application pools, with an admissions counselor assigned to each
pool.

Applicant Pool
A subset of applications in an application grouping. Applicant pools enable you to control and adjust
workload for application reviewers.

Conversation Tag
A descriptor, such as Dietary Restrictions or Special Needs that you can assign to an engagement
conversation to identify its topic. You can search for conversations by conversation tag.

Conversation Topic
A conversation tag or recruiting event name that you can associate with an engagement conversation to
make conversations easier to find.

Designation
An attribute, such as Community Learning Partner, Honors, or STEM, that you can associate with
educational institutions and external associations to make them easy to find and report on.

Dynamic Period
A date that identifies the anticipated start date for a student of online education or other asynchronous
learning.

Educational Taxonomy
A taxonomy scheme and set of codes you can assign to programs of study and their concentrations to
meet state, local, or other classification requirements.

Engagement Action Item

Defines a requirement that must be met for an application for admission to be considered complete.
Example: Submit transcripts.

Engagement Item
An engagement email or printed engagement item. You can include engagement items in engagement
plans and use them to support student recruiting events.

External Association
A nonprofit, community-based, or other noneducational organization that you can associate with student
prospects or identify as a location for recruiting events.

External Engagement Item

Used to send and track third-party engagement items for recruiting events, communication plans, or ad hoc
communications.

Fast Path
A streamlined approach to moving applications for admission from submission to matriculation as quickly
as possible.

Match and Merge

A process that helps eliminate duplicate student prospect information in Workday.

Recipient Threshold
The maximum number of prospects to whom you can send an engagement item at the same time without
requiring approval.

Recruiting Cycle
A recruiting period for 1 or more academic levels of an academic unit. You associate recruiting cycles with
campaigns to measure the effectiveness of each campaign per recruiting cycle.

Student Recruiting Region

Workday term for recruiting territory. A recruiting region can represent a geographical area, 1 or more
schools, or schools in selected school districts.

Stage
A value, such as Lead, Inquirer, or Applicant, that identifies where a student prospect is in the recruitment
or admissions process.

Student Prospect Profile

A worklet that displays information for a prospective student, including contact information and recruitment
details.

Student Prospect Type

A value, such as First Year or Adult Returning, that you can assign to prospective students and use to
match student prospects to admissions counselors automatically.

Student Tags
An attribute, such as Veteran, Athlete, or Scholarship Recipient, that you can assign to student prospects.
You can use tags to match student prospects to recruiters automatically, find prospects, and use as criteria
for associating engagement plans with prospects.

Report Writer: Course Manual and Activity Guide
100% (6)
Report Writer: Course Manual and Activity Guide
137 pages
Intrusion Detection Honeypots
From Everand
Intrusion Detection Honeypots
Chris Sanders
3/5 (2)
Complete WD Report Writer Course PDF
100% (3)
Complete WD Report Writer Course PDF
235 pages
1.0.0 Workday Reports: Report Writer
100% (1)
1.0.0 Workday Reports: Report Writer
19 pages
Report Writer: Course Manual and Activity Guide
No ratings yet
Report Writer: Course Manual and Activity Guide
89 pages
Audio, Video, and Media in the Ministry
From Everand
Audio, Video, and Media in the Ministry
Clarence Floyd Richmond
No ratings yet
1.0.0 Workday Reports: Report Writer
100% (3)
1.0.0 Workday Reports: Report Writer
19 pages
How to Sell on Amazon and Product Research: Product Research Tips and Practical Guide on How to Find a Winning Product to Sell on Amazon Fba
From Everand
How to Sell on Amazon and Product Research: Product Research Tips and Practical Guide on How to Find a Winning Product to Sell on Amazon Fba
David L. Ross
No ratings yet
Sheqxel Kpi Dashboard Template
100% (1)
Sheqxel Kpi Dashboard Template
15 pages
SCGX Fino Userguide
No ratings yet
SCGX Fino Userguide
189 pages
ChatGPT for Business: Strategies for Success
From Everand
ChatGPT for Business: Strategies for Success
Matthew C. Smith
1/5 (1)
Gray Hat Hacking the Ethical Hacker's
From Everand
Gray Hat Hacking the Ethical Hacker's
Çağatay Şanlı
5/5 (1)
Cybersecurity for Executives: A Guide to Protecting Your Business
From Everand
Cybersecurity for Executives: A Guide to Protecting Your Business
Matthew C. Smith
No ratings yet
10K Blueprint
From Everand
10K Blueprint
Cian O Farrell
5/5 (2)
Software Patterns Made Easy
From Everand
Software Patterns Made Easy
Justice Nanhou
No ratings yet
Blog Smarter, Not Harder: SEO, Blogging, and AI Strategies to Skyrocket Your Traffic
From Everand
Blog Smarter, Not Harder: SEO, Blogging, and AI Strategies to Skyrocket Your Traffic
Jay Nans
No ratings yet
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
From Everand
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
Matthew C. Smith
No ratings yet
Content Creation Revolution with chatGPT
From Everand
Content Creation Revolution with chatGPT
Maria Cowen
No ratings yet
Human Nature Potential in Nurture
From Everand
Human Nature Potential in Nurture
David L. Hawk
No ratings yet
Unlocking Statistics for the Social Sciences
From Everand
Unlocking Statistics for the Social Sciences
Norma Sinclair
No ratings yet
WD UV ReportingFunctionalityinWorkday Final
No ratings yet
WD UV ReportingFunctionalityinWorkday Final
8 pages
1-W23 RW Student Guide
No ratings yet
1-W23 RW Student Guide
162 pages
Agile: 2 Manuscripts- Agile Project Management and Scrum- Mastering Agile Scrum Project Management
From Everand
Agile: 2 Manuscripts- Agile Project Management and Scrum- Mastering Agile Scrum Project Management
Jeff Branson
No ratings yet
Business English Writing: Effective Business Writing Tips and Will Help You Write Better and More Effectively at Work
From Everand
Business English Writing: Effective Business Writing Tips and Will Help You Write Better and More Effectively at Work
Mary G. Lewis
No ratings yet
Breaking Barriers: S.T.E.M Mentorship in Business
From Everand
Breaking Barriers: S.T.E.M Mentorship in Business
Matthew C. Smith
No ratings yet
AI-Driven Digital Transformation: A Proven Blueprint for Responsible AI Scaling
From Everand
AI-Driven Digital Transformation: A Proven Blueprint for Responsible AI Scaling
Srikanth Victory
No ratings yet
Interview Q&A
No ratings yet
Interview Q&A
72 pages
Interview Manual
No ratings yet
Interview Manual
71 pages
Workday Advance Report Tool
100% (2)
Workday Advance Report Tool
10 pages
Conquering the Competition: Strategies for Standing Out in the Gaming Content Landscape
From Everand
Conquering the Competition: Strategies for Standing Out in the Gaming Content Landscape
Rian McCullen
No ratings yet
Aquaponics for Profit
From Everand
Aquaponics for Profit
David H Dudley
No ratings yet
Workbook Analytics
No ratings yet
Workbook Analytics
48 pages
SFDC Training Series - Associate IV
No ratings yet
SFDC Training Series - Associate IV
51 pages
BlockChain for Beginners
From Everand
BlockChain for Beginners
Matthew Smith
No ratings yet
Workday Reports A Brief Guide To Optimization
No ratings yet
Workday Reports A Brief Guide To Optimization
5 pages
Aquaponics Design Plans, Construction, Operation, and Income: Organic Food
From Everand
Aquaponics Design Plans, Construction, Operation, and Income: Organic Food
David H Dudley
No ratings yet
Guide to Workday Reporting
No ratings yet
Guide to Workday Reporting
10 pages
Workbook Analytics
No ratings yet
Workbook Analytics
41 pages
Workday Reporting eBook 1729766316
No ratings yet
Workday Reporting eBook 1729766316
15 pages
Workday Glossary of Terms
100% (1)
Workday Glossary of Terms
31 pages
Sap Concur Webinar November Reporting
No ratings yet
Sap Concur Webinar November Reporting
44 pages
ReportWriter 1
100% (3)
ReportWriter 1
65 pages
Datasheet Workday Prism Analytics Uk
No ratings yet
Datasheet Workday Prism Analytics Uk
2 pages
Workday Job Aid Cross Application Glossary
No ratings yet
Workday Job Aid Cross Application Glossary
7 pages
CM AdvancedReportingandAnalytics 30v1
No ratings yet
CM AdvancedReportingandAnalytics 30v1
215 pages
Reporting and Dashboards
0% (1)
Reporting and Dashboards
40 pages
Analytics
No ratings yet
Analytics
204 pages
Datasheet Financial Management Se
No ratings yet
Datasheet Financial Management Se
6 pages
Workday For Asset Accounting: Finance ILT
No ratings yet
Workday For Asset Accounting: Finance ILT
45 pages
Connector Layouts CSV Format
No ratings yet
Connector Layouts CSV Format
39 pages
Global Anti-Bribery Policy - 2020 Final Revision History
No ratings yet
Global Anti-Bribery Policy - 2020 Final Revision History
7 pages
Asset Management
0% (1)
Asset Management
374 pages
(Rajiv Gandhi University of Knowledge Technologies) : (Act 18 0f 2008) Telefax: 040-6515 2339
No ratings yet
(Rajiv Gandhi University of Knowledge Technologies) : (Act 18 0f 2008) Telefax: 040-6515 2339
2 pages
Marshall MarketingMgmn 3e Chap005 IM
No ratings yet
Marshall MarketingMgmn 3e Chap005 IM
23 pages
James Serra Data & AI Architect Microsoft, NYC MTC
No ratings yet
James Serra Data & AI Architect Microsoft, NYC MTC
93 pages
M7078 Vision Spec Sheet-Rev 02
No ratings yet
M7078 Vision Spec Sheet-Rev 02
2 pages
AIHR HR Competency Framework
100% (1)
AIHR HR Competency Framework
25 pages
Day 1 Tableau 30 June 2024
No ratings yet
Day 1 Tableau 30 June 2024
3 pages
JIRA - Acp-100-Exam-Topics-And-Resources
No ratings yet
JIRA - Acp-100-Exam-Topics-And-Resources
8 pages
Technology PPT REMAX
No ratings yet
Technology PPT REMAX
29 pages
Sarath STATA CV
No ratings yet
Sarath STATA CV
2 pages
BRM 2022 Chapter 1
No ratings yet
BRM 2022 Chapter 1
36 pages
Advance Data Analytics Unit 4
No ratings yet
Advance Data Analytics Unit 4
60 pages
Sandvine - TB - ActiveLogic PTS Transition AW 20201110
No ratings yet
Sandvine - TB - ActiveLogic PTS Transition AW 20201110
6 pages
Cargo Connect (1) (1)
No ratings yet
Cargo Connect (1) (1)
13 pages
Dadosfera Commercial Eng
No ratings yet
Dadosfera Commercial Eng
16 pages
Anatomy of A Business Intelligence Strategy Document
No ratings yet
Anatomy of A Business Intelligence Strategy Document
10 pages
1 Analysis and Design of Visualization
No ratings yet
1 Analysis and Design of Visualization
8 pages
Visualization, Data and Tableau: Alexander Mou
No ratings yet
Visualization, Data and Tableau: Alexander Mou
22 pages
Exp-1 Excel Dashboard To Covid 19
No ratings yet
Exp-1 Excel Dashboard To Covid 19
11 pages
Powerbiinterviewquestionspdfbyscholarhat 240716104017 E79d91b9
No ratings yet
Powerbiinterviewquestionspdfbyscholarhat 240716104017 E79d91b9
18 pages
Kumaraman07226 6725dd069a1d2
No ratings yet
Kumaraman07226 6725dd069a1d2
1 page
Chapter-I Introduction to Data Analytics
No ratings yet
Chapter-I Introduction to Data Analytics
9 pages
MaheshResume
No ratings yet
MaheshResume
3 pages
CNN 3-Insight-Dashboard
No ratings yet
CNN 3-Insight-Dashboard
8 pages
OpenEMIS Jordan Evaluation 2017
No ratings yet
OpenEMIS Jordan Evaluation 2017
45 pages
Timothee Schlumberger Resume
No ratings yet
Timothee Schlumberger Resume
2 pages
TNSCST DI Oct 2019 V1
No ratings yet
TNSCST DI Oct 2019 V1
12 pages
Rohit Agrawal - Analyst
No ratings yet
Rohit Agrawal - Analyst
2 pages
User Guide Plan View 2005
100% (1)
User Guide Plan View 2005
618 pages
JMMB Virtual Queue Management System Software Requirements Specification V2.0
No ratings yet
JMMB Virtual Queue Management System Software Requirements Specification V2.0
43 pages