v4.0.0

Important

As of version 4.0, the MyGeotab API Adapter solution has been fully migrated to Data Model 2 (DM2). The original data model and the Data Optimizer have been deprecated and removed from the solution effective January 2, 2026.
Anyone still using the original data model and looking to upgrade may refer to the following sections in the now deprecated original guide:

• IMPORTANT: Version 3.x - Data Model 2 (DM2)
• Data Optimizer Deprecated (Capabilities Moved to Core API Adapter in Version 3.x)

Notes

• Self-contained deployments are packaged in zip files - the names of which are prefixed with "MyGeotabAPIAdapter_SCD_" followed by the target Runtime Identifier (e.g. "win-x64").
• If using SQL Server or Azure SQL for the adapter database, the SQLServer.zip file contains the scripts associated with this release.
• If using PostgreSQL for the adapter database, the PostgreSQL.zip file contains the scripts associated with this release.

Here are some videos to help get started quickly and augment the documentation below. While SQL Server is the database of choice in these videos, the processes are similar for PostgreSQL, so the videos are still relevant regardless of the database provider chosen.

• ▶️ How to Download the MyGeotab API Adapter (3:25)
• ▶️ How to Set Up the MyGeotab API Adapter Database (4:20)
• ▶️ How to Deploy and Configure the MyGeotab API Adapter Application (8:15)
• ▶️ How to Start the MyGeotab API Adapter Application (2:15)
• ▶️ How to Upgrade the MyGeotab API Adapter (7:11)

For more detailed information, refer to the official guide and presentation:

• MyGeotab API Adapter DM2 — Solution and Implementation Guide
• MyGeotab API Adapter (presentation)

Upgrade Instructions

NOTE: This build includes changes to the appsettings.json file.

• To upgrade an existing installation of the MyGeotab API Adapter solution from version 3.14.0 to version 4.0.0, see MyGeotab API Adapter — Upgrade Guide — from v3.14.0 to v4.0.0.

Changes in This Release

For information on changes introduced in this and prior releases, refer to: Change Log - MyGeotab API Adapter - Data Model 2 (DM2)

Change Summary

Changes in this release are summarized below.

• DEPRECATED THE ORIGINAL DATA MODEL. Related changes include the following:
  • Removed the Data Optimizer. Its capabilities are included (and vastly improved) in the API Adapter’s Data Enhancement Services.
  • Removed v1 database scripts.
  • Removed the VSS Add-On. This was an extraneous feature that was not ported over to DM2.
  • Removed Azure deployment scripts. The scripts were designed for DM1 and would not work with DM2 as a result of database partitioning complexities. Similar Azure deployment scripts supporting DM2 may be added in the future.
  • Modified the appsettings.json file:
    • Removed the UseDataModel2 setting.
    • Removed the DebugData section (DebugData is not supported in DM2).
  • Cleaned-up the solution by modifying code as needed and removing items no longer needed as a result of the above.
  • Updated README.md file.
  • Updated NuGet packages to the latest stable release.
    • Geotab.Checkmate.ObjectModel updated from version 11.83.265 to 11.98.302.
  • Updated version to 4.0.0.0.

Feedback

Help us prioritize future efforts and better understand how the API Adapter is used! If you would like to provide any feedback about the MyGeotab API Adapter solution, please feel free to complete the 100% voluntary MyGeotab API Adapter - Usage Survey.