Learn more about

A higher-education institution was preparing to move its on-premises Ellucian Banner environment to Ellucian SaaS. As part of that migration, it also needed to modernize a custom enrollment reconciliation process that kept section and cross-list enrollment counts aligned with actual student registrations. The existing process depended heavily on the on-premises Banner database. It read Banner […]

As a higher-education institution prepared to move Banner to Ellucian SaaS, it had to determine how to preserve a custom eligibility process that depended heavily on the on-premises Banner database. The process identified which students qualified for a term-based benefit and recorded that eligibility as a student attribute, a Banner record value used here as […]

A higher-education institution relied on a custom billing process in Ellucian Banner, its higher-education enterprise and student information platform, to calculate student balances, generate statements and distribute them through TouchNet for electronic billing and DATAMATX for paper billing. The customization existed because the delivered Banner integration with TouchNet did not provide the required prior and […]

A higher-education institution relied on a custom third-party sponsor billing process in Ellucian Banner to calculate charges covered by external sponsors and prepare billing output for its TouchNet third-party billing workflow. Moving this capability to Ellucian SaaS required rebuilding the Banner-side billing engine around Ellucian Data Connect, Ellucian’s integration platform for creating and managing data […]

When an Ellucian Spec API SQL query needs parameter values or criteria based filtering, choosing between ::param:: and %%AND_FILTER%% determines what kind of SQL substitution is required. ::param:: supplies a value at a predefined position in the SQL, while %%AND_FILTER%% represents an optional SQL condition generated from the request criteria. Using the wrong mechanism can […]

When an Ellucian Data Connect integration needs to create a new Banner employee job-detail record through the Ethos employee-job-details/batches endpoint, the request still requires an id even though the new record does not yet have a real GUID. This creates a practical implementation question: what value should the batch payload send when the operation is […]

Producing the correct data is only part of an Ellucian Data Connect integration. The result also has to reach the receiving system in the format that system expects. A report, audit, or error file may require a specific delimiter, extension, header row, filename, or delivery destination. When multiple integrations need the same kinds of output […]

An Ellucian Data Connect pipeline may accept reason codes, employee classifications, or other runtime values that represent reference data maintained in Banner. These values cannot always be validated locally. A parameter may be present and have the correct format, but that still does not prove that the code actually exists in Banner or belongs to […]

Ellucian Data Connect is designed to support integrations that move and transform data between systems. Framework v3.1 is version 3.1 of Ellucian’s extensibility framework for Data Connect pre-built integrations. It provides reusable pipeline and sub-pipeline patterns, together with defined extension points for integration-specific behavior. The framework provides reusable baseline behavior for common integration concerns, so […]

Some Ellucian Data Connect pipelines need to process two related collections in sequence, but nested forEach loops are not supported. This post explains how to complete the first loop, preserve its payload, run a second loop, and merge the second-loop results back into the original records. It is part of our Ellucian Data Connect tips and implementation patterns series and belongs to its Pipeline […]

Reimplementing on-premises integration logic in Ellucian Data Connect is rarely a direct code conversion. Existing processes may rely on sequential operations, shared message state, reducer behavior, runtime parameter rules, Banner and Ethos API operations, legacy Oracle logic, Spec API SQL, report formatting, and file-delivery behavior that must be represented explicitly in a Data Connect pipeline. […]

ABCloudz modernized an existing McGraw-Hill ALEKS score import for an institution moving from on-premises Ellucian Banner to Ellucian Student powered by Banner. McGraw-Hill ALEKS is an online learning and assessment platform that helps educators understand each student’s knowledge and learning progress. The institution already used ALEKS scores in its Banner student records, but the existing […]

Universities cannot afford delays or manual work when student health insurance data has to move between systems. In this project, the ABCloudz team automated the full bidirectional integration between Ellucian Banner SaaS and Arthur J. Gallagher, the university’s insurance partner, while replacing Dell Boomi jobs with native Ellucian Data Connect pipelines.  For the customer, this project was not only part of the move from […]

Moving to Ellucian Banner SaaS does not erase academic logic. It just refuses to run it the old way. That was exactly the situation here. The institution already had working logic that updated module outcome related values based on student grading data. Academic teams trusted it. The rules were established. The process was already doing […]

For institutions leaving on-prem Colleague behind and moving into Ellucian SaaS, the experience often feels like landing a plane on a different runway. Same destination, very different approach. Third-party integrations are usually where that difference becomes most visible. This story centers on the Colleague SaaS integration with Blackbaud Raiser’s Edge NXT. Raiser’s Edge is where […]