New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Workday-Pro-Integrations Exam - Topic 4 Question 5 Discussion

Actual exam question for Workday's Workday-Pro-Integrations exam
Question #: 5
Topic #: 4
[All Workday-Pro-Integrations Questions]

Refer to the scenario. You are configuring a Core Connector: Worker integration with the Data Initialization Service (DIS) enabled to extract worker demographic and contact information. The integration must include worker fields such as name, address, and a calculated field identifying workers eligible for a phone allowance.

The Phone Allowance Type calculated field exists and is functional in the tenant, but it is not displaying in the output.

What configuration step should you complete to include this field in the output?

Show Suggested Answer Hide Answer
Suggested Answer: D

In this scenario, a calculated field (Phone Allowance Type) is available and validated in the tenant, but it does not appear in the Core Connector: Worker output. The integration is configured with DIS enabled, and the expected behavior is for all specified worker data --- including name, address, and calculated fields --- to be included in the output file.

The correct action is to enable the field from the Configure Integration Field Attributes step.

From Workday Pro: Integrations materials:

''In order for a calculated field to be included in a Core Connector output, it must be explicitly located and selected from within the Configure Integration Field Attributes task. This step determines what fields are extracted in the integration output --- including any standard or calculated fields available in the object model.''

Even though the field exists and is functional, it must be manually located within the relevant section (e.g., Worker Data > Compensation or Worker Details), and marked to include in the output.

Incorrect Options Explained:

A . Configure Integration Field Overrides: This is used to change or override output formatting but does not control field visibility.

B . Configure Integration Maps: Used for mapping values or converting code sets, not for selecting fields for output.

C . Create a Custom Field Override service: This is not necessary for simply adding a calculated field; the existing field can be enabled via attributes configuration.


Workday Pro: Core Connector -- Field Selection Using Configure Integration Field Attributes

Workday Community: How to Include Calculated Fields in Connector Outputs

Contribute your Thoughts:

0/2000 characters
Ernest
12 hours ago
Are you sure it’s not in the Field Attributes step?
upvoted 0 times
...
Matthew
6 days ago
I agree, that's the right move!
upvoted 0 times
...
Lacey
11 days ago
You need to add the field in the Field Overrides step.
upvoted 0 times
...
Maricela
16 days ago
Haha, this question is a real head-scratcher. I'm just hoping I don't get any trick questions about coffee allowances on the exam!
upvoted 0 times
...
Elly
21 days ago
Option A is the answer, no doubt. Overriding those integration fields is the solution.
upvoted 0 times
...
Margurite
26 days ago
I'm going with C. A custom field override service is the way to handle this kind of tricky calculated field situation.
upvoted 0 times
...
Mabelle
1 month ago
I’m leaning towards option A, but I’m a bit uncertain if the calculated field needs a custom service instead.
upvoted 0 times
...
Aliza
1 month ago
I feel like the field attributes step could be relevant, but I can't recall if it directly affects the output.
upvoted 0 times
...
Valentine
1 month ago
I think we might need to check the integration maps. There was a similar question about mapping fields in our practice tests.
upvoted 0 times
...
Freeman
2 months ago
I remember we discussed the importance of field overrides in class, but I'm not sure if that's the right step here.
upvoted 0 times
...
Leonor
2 months ago
Ah, I see. This is all about getting that calculated field to show up in the output. I'm pretty confident that option C is the way to go, but I'll verify the details just to be sure.
upvoted 0 times
...
Franchesca
2 months ago
Alright, time to put on my problem-solving hat. I'm a bit unsure about the different configuration steps, so I'll make sure to read through the question thoroughly and consider each option carefully.
upvoted 0 times
...
Felicitas
2 months ago
D is the obvious choice here. You gotta configure those field attributes to make sure the calculated field shows up.
upvoted 0 times
...
Glenna
2 months ago
Option B seems like the way to go. Mapping is key for getting that calculated field into the output.
upvoted 0 times
...
Lynette
3 months ago
Hmm, this is a good one. I think I know the answer, but I want to make sure I'm not missing anything. I'll review the question again and then make my decision.
upvoted 0 times
...
Desiree
3 months ago
I thought it would show up automatically, kinda weird.
upvoted 0 times
...
Jarvis
3 months ago
Okay, let's see here. I think the key is figuring out where that calculated field is supposed to be configured. I'm leaning towards option B, but I'll double-check the details.
upvoted 0 times
...
Lettie
3 months ago
Hmm, this looks like a tricky one. I'll need to carefully review the steps to make sure I don't miss anything.
upvoted 0 times
Billi
2 months ago
I think adding the calculated field in the Field Overrides step makes sense.
upvoted 0 times
...
...

Save Cancel