The XML fragment shown follows the ReportasaService (RaaS) structure typical for Workday custom report output:
< wd:Report_Entry >
< wd:Dependents_Group >
< wd:Name > Megan McNeil < /wd:Name >
< wd:Age > 25 < /wd:Age >
< wd:Relationship wd:Descriptor= " Child " >
< wd:ID wd:type= " WID " > 7507df6a99664ce7bc0cb902cf370543 < /wd:ID >
< wd:ID wd:type= " Relationship_ID " > Child < /wd:ID >
< /wd:Relationship >
< /wd:Dependents_Group >
< /wd:Report_Entry >
Inside each < wd:Report_Entry > , the target value Relationship_ID resides under:
wd:Dependents_Group
# wd:Relationship
# wd:ID (wd:type= " Relationship_ID " )
When writing the template:
< xsl:template match= " wd:Report_Entry " >
XSLT uses a relative XPath (starting with ./) to navigate from the matched node.
Therefore, the correct XPath should be:
/wd:Dependents_Group/wd:Relationship/wd:ID
That expression selects the wd:ID element so you can then test/extract where wd:type= " Relationship_ID " .
Why the other options are incorrect:
Option
Why Incorrect
A & B
These use an equality test incorrectly inside the XPath expression - they would not return the node value and are syntactically invalid for value extraction.
C
Missing ./ - would still work in many cases, but Workday XSLT best practice is to use relative paths when inside a match.
Workday Pro Integration guidance for RaaS/XSLT stresses:
Always scope node selection relative to the current context tree using prefixqualified XPath expressions.
Reference:Workday Pro: Integrations - XSLT for Workday XML (Namespaces, Context Node, Relationship ID Extraction)W3C XSLT Specification - Relative XPath from context node

In Workday Report Writer, the available data sources depend heavily on the selected report type and the reporting context. If the required data source, such as All Active and Terminated Workers, does not appear in the prompt, the most likely cause is that the wrong report type has been selected during report creation.
Workday filters the available data sources based on compatibility with the selected report type. Enabling a report as a web service does not remove data sources from the prompt, and temporary report settings do not determine whether this worker data source appears. Optimized for Performance affects report execution and performance behavior, not whether the core data source is selectable. Correcting the report type allows the proper worker data source to appear.

In Workday, for an Integration System User (ISU) to be selectable as a Custom Report Owner, the security group the ISU belongs to must have Modify access to custom reports.
From Workday's security configuration principle:
An ISU does not appear as a valid report owner unless its security group has Modify permission in the Report
/Task Permissions section of the Custom Report Creation domain security policy.
This is because report ownership requires writelevel access over custom report objects.
Therefore, you must update the Report/Task Permissions table to include the ISSG with Modify access.
Options B, C, and D are incorrect because View or Get/Put do not provide report ownership capabilities.
References:Workday Pro: Integrations - Integration Security and Report Ownership RulesAdminGuideAuthenticationandSecurity.pdf - Security Policies & Required Permissions Model

When an integration is moved to an Integration System User, ownership must support unattended execution.
The integration system itself can be owned by the ISU, but if an integration schedule exists, that schedule also needs to be owned by the ISU or transferred appropriately. Otherwise, the automated run can fail or continue to depend on the original human owner's security context. Integration Maps, Integration Attributes, and Integration Field Attributes are configuration components inside the integration; they do not independently control scheduled execution ownership. The schedule is the object responsible for recurring automated launches, so it must align with the service account that owns and runs the integration. This is a security and operational control for stable Workday integration execution.

Let's break this down:
* Effective Date of salary change: May 10, 2024
* Entry Moment (data entry timestamp): May 13, 2024, 2:00 PM
* Integration Run As of Entry Moment: May 11, 2024, 2:00 PM
* Salary data was entered AFTER this moment (May 13 vs May 11)
So based on Workday's Change Detection logic:
A worker is included in the integration output only if the transaction was entered into Workday after the last successful entry moment, and the effective date is on or after the "Last Successful Effective Date".
In this case:
* Entry was made after the last As-of Entry Moment (May 13 > May 11)
* Effective date (May 10) is after the last successful effective date (May 9) Both conditions are met, so Brian Hill will be included, and the new salary of $90,000.00 will be reflected in the output.
Why other options are incorrect:
* A. The effective date is valid.
* B. $60,000 would be outdated.
* C. Entry moment is after the As-of date, so not excluded.
Reference:Workday Pro: Core Connector Change Detection - How Entry Moment and Effective Date Determine Output