Release Notes 5.2
This document provides a description of the technical enhancements to Generate version 5.2 released in December 2022.
RELEASE OVERVIEW
Generate 5.2 requires some additional steps that must be performed prior to performing the Generate upgrade. Below are the instructions for performing the update.
Step 1: Verify Your Web Environments are Running ASP.NET Core 6.0:
IMPORTANT: Generate 5.2 has been upgraded to ASP.NET Core 6.0. Please verify your web environments are running ASP.NET Core 6.0 before installing Generate 5.2.
ASP.NET Core 6.0 Runtime Hosting Bundle download link:
Step 2: Update Connection Strings:
Prior to updating to Generate version 5.2, the state will need to update the connection strings in their appSettings.json file in both \web\config and \background. These files are located on the webserver where Generate was installed.
In those files, there is a “Data” parameter that holds the connection string information. Add the following to each connection string, as noted below:
NOTE: There may be an additional connection string for‘StagingDBContextConnection”. If so, the new parameter needs to be added to that string as well.
"Data": { "AppDbContextConnection": "Server=192.168.01.01; Database=generate; User ID=generate;Password=xxxxxxxxxxx; trustServerCertificate=true; MultipleActiveResultSets=true;", "ODSDbContextConnection": "Server=192.168.01.01; Database=generate; User ID=generate; Password=xxxxxxxxxxx; trustServerCertificate=true; MultipleActiveResultSets=true;", "RDSDbContextConnection": "Server=192.168.01.01; Database=generate; User ID=generate; Password=xxxxxxxxxxx; trustServerCertificate=true; MultipleActiveResultSets=true; Connect Timeout=300;" }
Step 3: Perform the Generate Update
As for typical Generate updates, backup the Generate database, web files, and background files, then log into the Generate UI and perform the update.
State ETL changes:
There is a new staging validation process added as part of version 5.2. It is driven by individual rules written to validate common data issues that would impact the results loaded into the final reports. It is a standalone process that does not, in any way, impact how a state currently migrates data for any report. If a state wants to leverage this process, the validation routine can be executed separately after the staging ETL has been successfully executed. The results are stored in a separate table with all the relevant information needed to research those records. A more detailed explanation of the process and how to use it can be found here in the Generate Staging Validation document.
GENERATE ENHANCEMENTS
The following EDFacts reports were updated in this release.
Type of Impact:
Data – the changes will improve data quality and completeness
User Interface – the changes impact the Generate User Interface and/or migration process
Source to Staging ETL – the changes may require modifications to the SEA’s Source to Staging ETL
Performance – the changes improve the performance of a data migration
Migration – the changes impact a data migration process
Submission Files – the changes may impact submission file(s)
Database – changes to the Generate database structure
Child Count Exiting
FS002
FS089
FS009
Child Count / Exiting / Title III - Handle Multiple records for a person in Person Race during Staging-to-RDS migrations
CIID-5128
Staging to RDS Migration
Discipline
FS005
FS006
FS007
FS088
FS143
FS144
Discipline - Handle Multiple records for a person in Person Race during Staging-to-RDS migrations
CIID-5126
Staging to RDS Migration
Directory
FS029
Resolved "Prior ID" is loading incorrectly from IDS
Resolved Get_OrganizationReportData - joins return multiple rows from the dimension tables Resolved closed schools are missing
Reconstituted and Charter School Status on Submission File Resolved date handling for DimLeas and DimK12Schools
Removed IsApproverAgency column and the supporting logic
CIID-4060
CIID-4680
CIID-4731
CIID-5144
CIID-4678
Data
Grades Offered
FS039
FS039 Grades Offered – developed a process for deleting data from the RDS for Grades Offered FS039 Grades
Offered – resolved Grade list is empty even when data is populated in the database FS039 Grades Offered – resolved
Staging.OrganizationGradeOffered has the wrong metadata for the GradeOffered column FS039
Grades Offered – resolved new staging to RDS for LEAs and Schools joins incorrectly
CIID-4865
CIID-3954
CIID-4019
CIID-5029
Data
General
Standardized the name of the Source to Staging ETL stored procedures for future development.in internal Generate testing databases (no state action required).
CIID-5123
Source to Staging ETL
Resolved Staging-to-DimK12Schools, Staging-to-DimLeas, and Staging-to-DimSeas duplicating records based on join to Organization Types and Organization Location Type in Source System Reference Data
CIID-5131
Source to Staging ETL
Updated RDS Wrapper Scripts to use new Staging-to-DimSeas, Staging-to-DimLeas, Staging-to-DimK12Schools
CIID-5025
Migration
Corrected Staging-to-Fact Discipline issues and improved migration performance.
CIID-5053
Performance
Add automatic rollover of SourceSystemReferenceData mappings for a new School Year to Staging to RDS migrations
CIID-5189
Migration
GENERAL SECTION
Upgrade
ASP.NET
Upgrade Generate from 3.1 .Net Core to 6.0 .Net Core
CIID-4898
Performance
UPGRADE PROCEDURE
Generate 5.2 has been upgraded to ASP.NET Core 6.0. Please verify your web environments are running ASP.NET Core 6.0 before installing Generate 5.2. Make the necessary changes to the AppSettings.json files as defined in the Overview section. Then, follow the standard Generate upgrade process to install version 5.2.
COMPATIBLE SYSTEMS
Generate was tested on the following operating systems and browsers:
Windows 10 Pro
Google Chrome, Version 68 0.3440.106 (Official Build) (64-bit) and Firefox Quantum 61.01 (64 bit)
Last updated
Was this helpful?