Integrations and Data Loads
Integration options, simplest first
Enterprise Interface Builder (EIB) is the low-code workhorse: one inbound load or outbound extract against a single business object, driven by a template, delivered as spreadsheet or XML, with launch parameters and optional transformation. Core Connector handles multi-object, sequenced payloads such as worker plus dependents, and ships with a defined specification. Workday Studio is for complex orchestration, custom logic, and serious error handling. Document Transformation produces formatted output such as PDFs.
Every integration authenticates as an Integration System User belonging to an Integration System Security Group with a deliberately narrow domain scope. The ISU is not a person, has no UI access, and should never be a human account.
Data loads
Identify the business object, the correct operation (add, update, or maintain), and the required key fields. Validate in sandbox first, then load to production through the ISU with minimum permissions. For unique identifiers across records, use a sequence generator rather than hand-keyed numbers.
Traps:
- One EIB cannot natively keep two business objects in sync from a single file; that is a Core Connector or Studio conversation.
- Direction matters: outbound Get and inbound Put or load are different verbs. Check the wording.
- Scheduled launches and integration events are different triggers; real-time behavior needs an event, not a schedule.
- A failed load is usually data or security, not a defect: verify required fields, reference IDs, and ISSG scope.
Rule of thumb: if you must transform, sequence, or reconcile multiple objects, escalate EIB to Core Connector to Studio.