Geotab Users: To verify your version: go to MyGeotab > Administration > About, and check the build number, (e.g. 5.7.2001 release).
Resellers: Review this post for important changes affecting your customers and note any recommendations. If you have suggestions for improvement, please leave a comment below.
Sign up for Geotab news
Stay up-to-date on what’s new. Please subscribe to the Geotab newsletter to get these update posts emailed to you.
Login page updates
The login page has been updated to improve clarity and make logging in easier.
If you would like to specify a database to log in to, use the Options button in the top left corner to display the database field. The + button, which previously opened the database field has been removed.
Additionally, the Forgot password? option has been relocated below the password field. Simply enter your username, specify the database (if desired) and select Next to display the password field and the Forgot password? option. You can return to the username and database fields at any time by selecting Go back.
New Compliance category on Rules page
For regulatory users where compliance is an essential part of their daily routine, we've added a Compliance rules category to better reflect our core Compliance solutions. The Compliance rules category is no longer in Feature Preview and is now available as part of our standard built-in rules. Customers who use our ELD and DVIR features will find these rules helpful in tracking both fleet and regulatory compliance.
New built-in rule added to Fleet section on Rules page
The built-in rule Vehicle Movement Within Zones is no longer in Feature Preview and has been added to the standard suite of Fleet exception rules. This rule allows you to find events where the vehicle(s) moved exclusively within the specified zone type, without leaving the zone.
Filter zones by zone type in the Map feature
The Map feature now includes filters for zone type, allowing you to display particular zone types for expanded reporting options.
Highlighted Groups can now be saved as a View in the Map feature
On the live Map, you can now select groups you would like to highlight. Go to Map > Views > Save this view to save your selections. This feature allows you to save pertinent views, such as highlighting vehicles by their branch colour, so that they are available by default the next time you open the map.
Purge is no longer in Feature Preview
Purge is now a standard feature in MyGeotab, and no longer requires you to enable Feature Preview in your user options.
Fuel transactions are now an entity you can purge
Fuel transactions have been added to the list of data sets you can purge in your MyGeotab database.
VIN can now be added to Trips Detail report
You can now add VIN to your Trips Detail report. Simply create a custom report, add DeviceVIN as a column header on the data tab, and re-upload the report to your database. The VIN will now be displayed in your report.
Driver information can now be added to the Fuel and EV Energy Usage Report
You can now use custom reports to add Driver information to the Fuel and EV Energy Usage report. To include this information in your report, create a custom report and add the following headers as columns on the data tab:
Once you have added the additional columns, re-upload the report to your database, and the driver information will display as part of the report.
Distance-based columns in the Fuel Fillup report normalized to display values in “Km” for metric users
Previously, this report had used a combination of meters and kilometers. Now, all columns which will exclusively display kilometers.
New dialog when UI options are different from report options
When you change the default options on pages within MyGeotab and try to download an Excel report that has different options configured, you will now receive a popup message asking you which options you would like to use to populate the Excel report.
TimeZone added as header on all reports
TimeZone has been added as a header to the data tab on all Excel reports.
Main menu updates
The following updates were made in MyGeotab versions 1903 and 1904 as well and were previously communicated on Dec 5, 2019.
A new way to Connect!
The new Geotab Community has launched, replacing the previous Geotab Forum. The Geotab Community is an interactive knowledge platform where members can get help, share tips and build knowledge. New technologies including game design elements encourage users to solve problems and earn rewards.
To support this update, the Forums button has been removed, and replaced with a new Community button. You can find the Community menu under Product Guide in the Getting Started & Help menu.
For easier navigation, the Marketplace menu, and all sub-menus have been collapsed into a single item on the main menu.
Updated description for Speed token
Updated the description of the Speed token for templates, explaining that when the Speed token is selected, this is the maximum speed during the time of the exception.
Added a preview button to Messaging page — Feature Preview
Added a button to preview messages before they are sent to the vehicle or driver.
Fixed and improved UX, typos, grammar, capitalization, bugs, accessibility, security and translation errors.
Removal of HardwareId from Device object
The Device property HardwareId has been removed to support decoupling the SerialNumber from HardwareId. It is no longer possible to decode a given serial number to a corresponding hardware ID or encode a serial number by using the device type and hardware ID.
Removing hardware ID means many integrations using older NuGet packages will continue to function normally, but integrations using hardware ID may be accessing a null or nonexistent hardware ID from the JSON payload. As a precaution, you may need to adjust your integration in following ways:
- Do not encode or decode serial from/to hardware ID.
- Do not expect hardware ID to be present in JSON payload.
If using an older NuGet package, do not use the hardware ID of the Device object. It may be incorrect.
New search properties
Added new search properties for UserSearch:
Added "negatable" search of FistName, LastName and Name properties. If the first character of this search property is '!', then the API will know to negate the search logic. For example: field = "!John%", will produce the equivalent where clause: WHERE NOT LIKE John%.
For the User object, using the “keywords” search property returns users that have one of these keywords in their firstName, lastName and userName properties. Keywords support wildcard character (`%`)
Other objects keyword search is available for:
- SecurityGroups (example)
Allows you to search and return results for users who only belong to the securityGroup.
To provide exact values, DiagnosticEngineHoursAdjustmentId
will now be interpolated using trips and DiagnosticIgnitionId
values when a search includes a from/toDate value(s).
Proper support of active from/to dates for TextMessage
Messages that have not been sent by active to date will not be sent.
New map Add-Ins page (BETA)
A new map Add-Ins page available on the SDK page
Added documentation describing field length limits. Added more specific error messages relating to max field lengths from the CreateDatabase method.
Added “IsIoxConnectionEnabled”. (Adds to GO4v3, GO5, GO6, GO7, GO8, GO9).
Removed requirement of “AddInDataId” for search by ID.
Providing “RepairUser” and “RepairDateTime” are no longer supported for unrepaired DVIRDefect.
“DefectList” must be provided when adding a DVIRLog.
Added “WashingtonIntrastate7Day”, “WashingtonIntrastate8Day”, “NoneCanada”, “HosRuleSetCanadaNorthOf60CycleOne”, and “HosRuleSetCanadaNorthOf60CycleTwo”.
Added “MaxPCDistancePerDay to the User property.”
Looking for the last update summary? Read: What's new in Geotab - Version 1904.
Vik Sridhar, Senior Engineering Product Manager
Inshaal Badar, Senior Content Writer
Kelly Tice, Heather Holmes, Technical Writers