v3.4.0

Data Model 2 (DM2) - The Next Evolution

Important

As of version 3.0, the MyGeotab API Adapter solution has begun its evolution to using a new data model. It is expected to take several months from the initial version 3.0 release to port-over the various Geotab entity types that are currently supported. Once complete, the existing data model and the Data Optimizer will be deprecated after a reasonable period to provide integrators time to modify any integrations that they need to migrate to the new data model.

For more information:

• IMPORTANT: Version 3.x - Data Model 2 (DM2)
• Data Optimizer Deprecated (Capabilities Moved to Core API Adapter in Version 3.x)
• MyGeotab API Adapter DM2 — Solution and Implementation Guide

Notes

• Self-contained deployments are packaged in zip files - the names of which are prefixed with "MyGeotabAPIAdapter_SCD_" (for the MyGeotab API Adapter) or "MyGeotabAPIAdapter.DataOptimizer_SCD_" (for the MyGeotab API Adapter Data Optimizer) 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.
• If using Oracle for the adapter database, the Oracle.zip file contains the scripts associated with this release.
• For the Data Optimizer database, the SQLServer_DataOptimizer.zip file contains the scripts associated with this release.

The following resources are available for further information:

• MyGeotab API Adapter - Solution and Implementation Guide (guide)
• MyGeotab API Adapter DM2 — Solution and Implementation Guide (guide) 🆕
• MyGeotab API Adapter - Data Optimizer - Solution and Implementation Guide (guide)
• MyGeotab API Adapter (presentation)
• MyGeotab API Adapter and Data Optimizer (presentation)
• MyGeotab API Adapter - Guide for Deploying to Microsoft Azure (guide)
• MyGeotab API Adapter - Developer Overview (presentation)
• MyGeotab API Adapter — How to Add a Data Feed (guide)
• MyGeotab API Adapter - Expanding on the Data Optimizer (presentation)

Upgrade Instructions

NOTE: This build includes changes to the schema of the adapter database.

• To upgrade an existing installation of the MyGeotab API Adapter solution from version 3.3.0 to version 3.4.0, see MyGeotab API Adapter — Upgrade Guide — from v3.3.0 to v3.4.0 [PUBLIC].
  • If using the original data model, refer to the Upgrading to v3.4.0 with Original Data Model section.
  • If using Data Model 2 (DM2), refer to the Upgrading to v3.4.0 with Data Model 2 (DM2) section.

Changes in This Release

For information on changes introduced in this and prior releases, refer to the Change Log section(s) in the relevant document(s) below:

• Change Log - MyGeotab API Adapter - Data Model 2 (DM2)
• Change Log - MyGeotab API Adapter - Original Data Model
• Change Log - Data Optimizer (Only available with API Adapter Original Data Model

Change Summary

Changes in this release are summarized below with "DM1" denoting changes that apply to the original data model and "DM2" denoting changes that apply to Data Model 2 (DM2).

• [DM2] Added BinaryData2 table with associated data feed.
• [DM2] Added BinaryData Queries section to the guide.
• [DM1, DM2] Updated NuGet packages to the latest stable release.
  • Geotab.Checkmate.ObjectModel updated from version 11.62.237 to 11.68.266.
• [DM1, DM2] Updated version to 3.4.0.0.