Skip to content

Releases: Geotab/mygeotab-api-adapter

v3.10.0

25 Jul 21:08
@sdietz888 sdietz888
v3.10.0
c1b03f7
Compare
Choose a tag to compare
v3.10.0 Latest
Latest

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:

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:

Upgrade Instructions

NOTE: This build includes changes to the schema of the adapter database and the appsettings.json file.

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 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).

Assets 16

v3.9.0

04 Jul 01:19
@sdietz888 sdietz888
v3.9.0
83c62f2
Compare
Choose a tag to compare
v3.9.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:

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:

Upgrade Instructions

NOTE: This build includes changes to the schema of the adapter database and the optimizer database as well as to the appsettings.json files.

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 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).

  • [DM1, DM2] Added Feedback section to the DM2 guide with a link to the MyGeotab API Adapter - Usage Survey which provides a mechanism by which to provide feedback about the MyGeotab API Adapter solution.
  • [DM1, DM2] FIX: Modified stg_Diagnostics2 and Diagnostics2 tables, the Diagnostics table and the DiagnosticsT table:
    • Increased length of DiagnosticName column from 255 to max to accommodate new Diagnostics with long names on the MyGeotab side.
  • [DM2] Added pseudo feed for DutyStatusAvailability along with associated DutyStatusAvailabilities2 table.
  • [DM1, DM2] Modified ExceptionEvent feed - setting IncludeInvalidated, IncludeDismissedEvents and IncludeDeleted all to true (previously, only IncludeInvalidated was set to true)
  • [DM1, DM2] Modified the appsettings.json files (for both API Adapter and Data Optimizer):
    • Renamed “OverrideSetings” to “OverrideSettings” (to correct typo).
    • Made related changes throughout the applications.
  • [DM1, DM2] Added macOS publish profile (to facilitate deployment to macOS systems)
  • [DM1, DM2] Updated NuGet packages to the latest stable release.
  • [DM1, DM2] Updated version to 3.9.0.0.
Loading

v3.8.0

17 Jun 17:56
@sdietz888 sdietz888
v3.8.0
b0fba51
Compare
Choose a tag to compare
v3.8.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:

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:

Upgrade Instructions

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

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 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).

Loading

v3.7.0

23 May 19:10
@sdietz888 sdietz888
v3.7.0
ae9b3df
Compare
Choose a tag to compare
v3.7.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:

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:

Upgrade Instructions

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

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 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).

Loading

v3.6.0

21 May 14:24
@sdietz888 sdietz888
v3.6.0
6e532d5
Compare
Choose a tag to compare
v3.6.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:

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:

Upgrade Instructions

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

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 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 DriverChanges2 table with associated data feed.
  • [DM2] Added handling for database foreign key violations caused by race conditions. Essentially, if Processor B encounters an FK violation exception related to Processor A, Processor B will roll-back and wait until Processor A has completed another iteration (via monitoring the OserviceTracking2 table) before trying the next iteration in which it will re-execute the rolled-back actions.
  • [DM2] Bug Fix: Updated BackgroundServiceAwaiter WaitForConnectivityRestorationIfNeededAsync method to return bool indicating whether wait was needed. Updated relevant v2 services to set feedVersionRollbackRequired based on this bool so that feed version rollback works properly.
  • [DM1, DM2] Enhanced GenericGeotabObjectFeeder:
    • Added Rollback method to simplify updating of LastFeedVersion and LastProcessedFeedVersion properties along with resetting FeedStartOption to ConfiguredFeedStartOption in cases where rollback occurs on the first GetFeed call for a given entity type.
    • Modified services to use the new GenericGeotabObjectFeeder.Rollback method.
  • [DM1, DM2] Updated NuGet packages to the latest stable release.
  • [DM1, DM2] Updated version to 3.6.0.0.
Loading

v3.5.0

30 Apr 13:41
@sdietz888 sdietz888
v3.5.0
638b551
Compare
Choose a tag to compare
v3.5.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:

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:

Upgrade Instructions

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

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 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 ChargeEvents2 table with associated data feed.
  • [DM2] Modified Rules2 table: Added Condition column populated with the hierarchical tree of Condition(s) defining the logic of a Rule in JSON form.
  • Modified FaultDataLocationService2 and StatusDataLocationService2 to include Polly retry wrappers around transactionless bulk updates of database tables to avoid crash in the event of a transient deadlock.
  • [DM1, DM2] Updated NuGet packages to the latest stable release.
  • [DM1, DM2] Updated version to 3.5.0.0.
Loading

v3.4.0

16 Apr 20:46
@sdietz888 sdietz888
v3.4.0
4606681
Compare
Choose a tag to compare
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:

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:

Upgrade Instructions

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

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 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.
Loading

v3.3.0

15 Apr 13:27
@sdietz888 sdietz888
v3.3.0
56234d5
Compare
Choose a tag to compare
v3.3.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:

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:

Upgrade Instructions

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

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 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 ExceptionEvents2 table with associated data feed.
  • [DM2] Added ExceptionEvent Queries section to the guide.
  • [DM1, DM2] Updated the solution from .NET 8.0 to .NET 9.0. If deploying the solution, there are no issues as the solution is self-contained. If copying/cloning the source code to modify the solution, it will be necessary to install .NET 9.0 SDK on the development machine.
  • [DM1, DM2] Updated NuGet packages to the latest stable release.
  • [DM1, DM2] Updated version to 3.3.0.0.
Loading

v3.2.0

04 Apr 19:21
@sdietz888 sdietz888
v3.2.0
1168158
Compare
Choose a tag to compare
v3.2.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:

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:

Upgrade Instructions

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

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 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 Rules2 table with associated data feed.
  • [DM2] Added Trips2 table with associated data feed.
  • [DM2] Added documentation, including query examples for both SQL Server and PostgreSQL, to help with optimally querying the adapter database.
  • [DM2] Modified Database Maintenance Service to pause other services before partitioning the database in order to resolve possible deadlock-related issues.
    • [DM2] Changed WaitTimeoutMinutesForPausingOtherServices from 30 to 5.
  • [DM2] Bug fix: Updated database scripts (SQL Server and PostgreSQL) to remove certain unique constraints on staging tables that can prove problematic:
    • [DM2] Removed: PK_stg_Devices2, PK_stg_Users2, PK_stg_Zones2, UK_stg_Trips2_DeviceId_Start_EntityStatus
    • [DM2] Added: IX_stg_Trips2_DeviceId_Start_EntityStatus
  • [DM2] Modified database cleanup scripts to exclude staging tables from count results.
  • [DM1, DM2] Updated NuGet packages to the latest stable release.
  • [DM1, DM2] Updated version to 3.2.0.0.
Loading

v3.1.0

20 Mar 14:25
@sdietz888 sdietz888
v3.1.0
391dc2f
Compare
Choose a tag to compare
v3.1.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:

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:

Upgrade Instructions

NOTE: This build includes changes to the schema of the adapter database and appsettings.json file.

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 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 Groups2 table with associated data feed and related group columns to the Devices2, Users2 and Zones2 tables.
  • [DM2] Enhanced cache update/refresh process for reference data types by migrating from in-memory application logic to utilizing staging tables with merge procedures.
    • Includes Devices, Diagnostics, Groups, Users, Zones and ZoneTypes.
    • Dramatically improves initial startup performance of the application and is especially noticeable with larger fleets (more data).
    • Also resolves an issue that was encountered on rare occasions where duplicate records got into one of the reference data tables causing the application to crash and requiring manual intervention to resolve.
  • [DM1, DM2] Modified DutyStatusLog feed to include a DutyStatusLogSearch with the IncludeModifications option set to true to include modification history of the DutyStatusLogs.
  • [DM2] Bug fix: Added Polly asyncRetryPolicyForDatabaseTransactions wrapper around database calls using standalone connections (in DatabaseMaintenanceService, FaultDataLocationService and StatusDataLocationService).
  • [DM2] Bug fix: Updated vwStatsForLevel1DBMaintenance in PostgreSQL scripts to only select from the public schema (avoiding a permissions issue when temp tables get selected otherwise).
  • [DM1, DM2] Updated NuGet packages to the latest stable release.
  • [DM1, DM2] Updated version to 3.1.0.0.
Loading