Ir para o conteúdo principal
Documentação
Documentação
Workday User Guide
Última atualização: 2023-09-08
Troubleshooting: Data Quality Module

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 experience issues with an installation that aren't highlighted by
Data Quality
, consider raising a customer care ticket. For more context, see Concept: People Analytics Activities.

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.
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 focus insights due to your workers being divided into populations that are too small.
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 the quality of focus insights 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.
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.
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 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.
There are multiple records of the same worker.
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.
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.
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.
A particular field contains values not considered valid for that field.
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.

Missing Values

Example defect message:
  • In Region, 50 of 100 records have missing values.
A particular field is missing a percentage of its values.
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.

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
If the number of records affected by the defect is less than 10, the most likely cause is terminations that don’t reflect reorganizations within the company.
You can choose to ignore this issue as this may not have a significant impact on the performance of the
People Analytics
 report.
If the number of records affected is more than 10, multiple hierarchy types must have been mapped into your target hierarchy fields. Example: Mapping the field Cost Center Level 2 into Org Level 2, Supervisory Level 3 into Org Level 3.
To diagnose the problem:
  • In the
    View More
     window, find how many Org level or Geo level instances have multiple hierarchies.
  • Create a new discovery board using the associated data source.
  • In your discovery board, select the fields that represent the problem hierarchy to create an Advanced Report (type: table). Org Level structure fields:
    • Org_Level_2
    • Org_Level_3
    • Org_Level_4
    • Supervisory_Organization
    Geo level structure fields:
    • Region
    • Country
    • Location
  • Create a Sheet filter for your report and filter your report by the Workday ID (WID) of the instances taken from your
    Data Quality
     report. To find a WID for your instances, use Workday’s search feature.
Remap your hierarchy fields in the Field Mapping based on what you’ve found in your discovery board.
Your chosen hierarchy has more than 1 top level hierarchy.
Create a calculated field and select your preferred top level hierarchy for it. Select the calculated field for the target hierarchy fields.
You are using a custom hierarchy, but haven’t created a Primary/Supervisory org type field for it and are using the People Analytics default field. Note: This problem also returns an Illogical Value check defect for the Supervisory Organization field.
Create a calculated field using the following parameters: CF_Primary_ORG = "IF org level 5 IS NOT NULL THEN org level 5 ELSE IF level 5 IS NULL AND org level 4 IS NOT NULL THEN org level 4 ELSE IF level 4 IS NULL AND org level 3 IS NOT NULL THEN org level 3 ELSE IF level 3 IS NULL AND org level 2 IS NOT NULL THEN org level 2 ELSE IF level 2 IS NULL AND org level 1 IS NOT NULL THEN org level 1"
There are inactive employees that have filtered into the current snapshot with an out-of-date organizational hierarchy.
Create a Worker report and search for the workers that are in incorrect hierarchies. Look at whether 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.
The number of unique values in a particular VIBE Index intersection is less than the minimum headcount requirement for VIBE Index intersections.
Severity
Solution Description
You can ignore these issues as this defect might not have a significant impact on the performance of the
People Analytics
 report.
Select a different source field for the target field in the
Configure People Analytics
 report.

Este conteúdo não faz parte do Guia do Administrador Workday