Refer to the scenario. You are configuring a Core Connector: Worker integration to extract worker demographic and contact information. The integration uses the Data Initialization Service (DIS) and must include worker fields such as name, address, and a calculated field identifying workers eligible for a phone allowance.
During a Full File test run, the output file is missing all address-related information, even though the Address Line Data, Municipality, Region, and Postal Code fields were configured in the Configure Integration Field Attributes step. You also confirmed that the Worker Personal Data Section is marked as Include in Output.
What should you do to resolve this issue?
This question concerns a Full File test of a Core Connector: Worker integration where address fields (Address Line, Municipality, Region, Postal Code) are missing from the output, despite being configured in Configure Integration Field Attributes. Additionally, the Worker Personal Data Section is marked as Include in Output.
This issue commonly stems from a missed Enablement of the Address Data subfolder, which acts as a container for the address-related fields. Even if individual fields are selected, they will not appear in the output if their parent subfolder is not enabled.
From the Workday Pro Integrations documentation:
''Each subfolder in the integration field hierarchy, such as Address Data under Worker Personal Data, must be explicitly enabled. If the subfolder itself is not enabled, the fields within it, even if marked as Required or Included, will not be rendered in the output.''
To resolve this:
Navigate to Configure Integration Field Attributes
Expand the Worker Personal Data > Address Data subfolder
Enable the subfolder
Then reselect the required address fields
Incorrect Options Explained:
A . Mark each address field as RequiredMarking fields as Required is only effective if the parent subfolder is enabled. Without enabling the subfolder, fields remain excluded.
C . Enable the Worker Personal Data Section Fields integration serviceThis pertains to service execution, not field visibility. The issue lies in field hierarchy and inclusion, not the service configuration.
D . Enable All Services in Configure Integration ServicesThis enables all integration services but does not impact field inclusion or subfolder visibility within field attribute configuration.
Workday Pro: Integrations -- Field Attributes Configuration and Subfolder Enablement
Workday Community: Integration Field Attributes -- Common Issues with Address Data
Core Connector Deployment Guide -- Field Selection and Troubleshooting
Quentin
26 days agoMoon
1 month agoEloisa
1 month agoLili
1 month agoLinette
2 months agoDanica
2 months agoLinette
2 months agoNorah
2 months agoAmalia
2 months agoGiuseppe
2 months agoLawrence
3 months agoCarrol
3 months agoRodolfo
3 months agoPeggie
4 months agoErnie
4 months agoStephaine
4 months agoTennie
4 months agoRoslyn
4 months agoMalcolm
4 months agoEzekiel
5 months agoDonette
5 months agoJanine
5 months agoDahlia
5 months agoCatina
5 months agoDesire
6 months agoMinna
6 months agoKarol
15 days agoDelisa
20 days agoJulie
5 months agoLino
6 months agoNovella
6 months ago