Cross-source questions
Ellucian and Workday in one question
Ask questions that join Ellucian enrollment and credit hours with Workday staffing, salary expense and budget, with the query and lineage for each system.
Short answer
One question can span Ellucian and Workday, such as how census credit hours by college in Ellucian compare with instructional salary expense in Workday. Nexatron queries each within the requesting user’s existing access, combines the results in an isolated step inside your workspace, and shows each source’s query. Ellucian and Workday are both available.
Example joined questions
Questions to ask. Each needs data from both systems; the answer depends on your own data and definitions.
- How do census credit hours by college in Ellucian compare with instructional salary expense posted in Workday this fiscal year?
- What is the ratio of students to full-time faculty by department, using Ellucian enrollment and Workday faculty headcount?
- Which departments offered more sections this year while their faculty headcount in Workday fell?
- How does actual spending against budget in Workday compare with enrollment change in Ellucian for each college?
How the two systems relate
Agree how Ellucian colleges, departments and instructors map to Workday cost centers, supervisory organizations and workers before joining. Most institutions keep a mapping table and a shared employee ID.
Check before you trust a joined answer
- Both sides use user-level access: Nexatron inherits each user’s Ellucian security classes and their Workday security groups, so a dean sees their own college.
- Enrollment is counted on a census date and expense builds up over a fiscal period. Agree which terms fall in which fiscal year.
- Faculty can teach for one department and be paid from another. Ask finance whether a section follows the instructor’s cost center or the course’s department.
How a cross-source answer works
Each system is queried within the person’s access
Nexatron sends each part of the question to the system that holds it. Each system answers with user-level access: Nexatron inherits the requesting user’s existing permissions in that system.
Results are joined inside your workspace
Nexatron combines each system’s results in an isolated step inside your tenant when the question is asked. Nothing has to be consolidated into a warehouse first, and there is no pipeline to build.
The queries come back with the answer
The answer carries the generated query for each system and how many records matched, so a reviewer can check which system supplied which figure and repeat the check later.
Joins follow links found at setup
Nexatron joins on the links setup found between the systems, and says how many records matched. If no record matches, it says so and marks the figures as uncertain.
Currencies are never added up as they are
Amounts in different currencies are converted with one system’s own exchange rates where a usable rate source exists, and otherwise shown side by side with the reason.
Longer than a single-source answer
These answers take longer than single-source ones.
More on how it works and its limits: Cross-source analytics and the guide to cross-source analytics without a warehouse migration.