Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

This document will enable developers to analyze the API and database changes between two versions of ODS / API 3.x releases and access the impact of upgrade. 

Table of Contents

Viewing API endpoint and JSON payload changes

The ODS / API metadata defines the API endpoints and it can be downloaded from the ODS / API metadata endpoints. You can get them either from ed-fi public sandboxes in or from local environment by downloading source code and building both versions one at a time. Downloaded metadata files can then be compared using file comparison tool to extract the metadata differences between the versions.


For demonstration purpose here we will use Visual Studio to format JSON and to compare ODS / API versions v3.2 and v3.3. 

Step 1. Download the JSON metadata for desired ODS / API versions 

Download and 

Step 2. Use Visual Studio to format the JSON metadata file for clarity.

Open the JSON metadata file, Right-click on the file, choose Format Document. Do this for both files.

Step 3. Use Visual Studio to compare the metadata files.

Click View > Other Windows > Command Window and type Tools.DiffFiles followed by the location of both JSON metadata files.


You will see changes highlighted in the editor

Viewing database changes

ODS / API binary releases include sample data sets as Nuget packages at . The sample databases for the two ODS / API versions can be downloaded and compared using schema compare tools like SSDT. 

For demonstration purpose here we will compare database schema for ODS / API versions v3.2 and v3.3. 

Step 1. Download and deploy sample databases a SQL Sever instance

In order to see database schema changes, you will need both v3.2 and v3.3 ODS database versions in a SqlServer instance.  Download database packages for v3.2.0 and v3.3.0 releases. Extract the .bak files from the Nuget packages and use the MS SQL Server Management Studio (SMSS) to restore the databases in your SqlServer instance.

Step 2. Use Visual Studio SQL Server Data Tools (SSDT) to compare schema

Using Visual Studio with SQL Server Data Tools (SSDT) installed, you can perform a database schema comparison between the two database versions located in your SQL Server instance.