Edited by GGrou-2019
Doesn't the SDK obect model match one-to-one to the GeotabAdaptor database Schema ? e,g., DVIRLogs table does not contain AuthorityAddress as specified in Geotab Developers (SDK Manual). If we need these properties in the GeotaAdaptor database what should be done ?
You need to be logged in to reply to this post and participate in the Geotab Community discussions.
Hi @GGrou-2019,
The Data Dictionary section in the MyGeotab API Adapter guide shows all of the tables and columns included in the adapter database by default. The MyGeotab API contains close to 70 different entity types and some of the columns on some of those entity types are arrays of other entities. Depending on which combination of entities and properties are used for a given downstream integration, the optimal schema might look somewhat different. It is not practical to include every entity type and property in the API Adapter. Instead, the aim is to include the most commonly-used entities and properties. Additionally, entities are sometimes modified with new properties added over time.
If there is an entity type or a property thereof that is missing from the API Adapter database, it is possible to log a ticket through your normal support channel and this will get added to a backlog. However, there is no guarantee that any requests will be advanced and no guarantee on timelines. By providing the MyGeotab API Adapter as an open source solution, Geotab is able to help integrators potentially save countless hours in development effort at zero cost while providing the opportunity for integrators to use the solution as a base and modify the source code to customize it to meet their exact needs. This is the second option available to those seeking to have the solution customized in short order.
I hope this helps.
Steve
Hi @GGrou-2019,
The Data Dictionary section in the MyGeotab API Adapter guide shows all of the tables and columns included in the adapter database by default. The MyGeotab API contains close to 70 different entity types and some of the columns on some of those entity types are arrays of other entities. Depending on which combination of entities and properties are used for a given downstream integration, the optimal schema might look somewhat different. It is not practical to include every entity type and property in the API Adapter. Instead, the aim is to include the most commonly-used entities and properties. Additionally, entities are sometimes modified with new properties added over time.
If there is an entity type or a property thereof that is missing from the API Adapter database, it is possible to log a ticket through your normal support channel and this will get added to a backlog. However, there is no guarantee that any requests will be advanced and no guarantee on timelines. By providing the MyGeotab API Adapter as an open source solution, Geotab is able to help integrators potentially save countless hours in development effort at zero cost while providing the opportunity for integrators to use the solution as a base and modify the source code to customize it to meet their exact needs. This is the second option available to those seeking to have the solution customized in short order.
I hope this helps.
Steve