Geotab Data Connector troubleshooting

I can connect and see the data schema, but there is no data for a specific vehicle or device.

Ensure that you have the appropriate view permission for the vehicle or device on your MyGeotab account. If permissions are correct and the data is still blank, no activity for that vehicle or device was recorded for the specified time period.

What is rate limiting?

Rate limiting protects the stability of the Geotab Data Connector by limiting the number of requests per user per minute. If you reach the limit, wait before refreshing your data sources. Different tables may have different limits, but the general limit is 100 requests per user per minute.

I am on an older version of Power BI, Tableau, or Excel. Can I still use the Data Connector?

As long as your tool supports OData feeds, the Geotab Data Connector should work. However, the Data Connector is only tested on the latest versions of Power BI, Tableau, and Excel. Issues with older versions may not be eligible for support.

I am using a BI tool that is not listed. Can I still use the Data Connector?

The Geotab Data Connector officially supports only Power BI, Excel, and Tableau. Geotab cannot guarantee compatibility with other tools, even if they support the OData protocol.

Where does VIN data come from?

VIN data in Vehicle KPI and Vehicle Metadata comes from the VIN field on the asset page (from Data Connector version 2 onward). This is usually the VIN read by the telematics device. If the VIN field was manually edited on the asset page, the edited value is reflected in both tables. If certain vehicles do not report VIN through the diagnostic port, work with your Reseller and Geotab to open a Vehicle Data Request (VDR).

I am not seeing odometer readings for some vehicles.

This occurs when a vehicle does not communicate odometer data to the telematics device through the diagnostic port. The Geotab Data Connector does not capture manually-entered or edited odometer entries in MyGeotab. If certain vehicles do not report odometer data through the diagnostic port, work with your Reseller and Geotab to open a Vehicle Data Request (VDR).

The difference between minimum and maximum odometer does not match GPS distance.

GPS distance is aggregated from MyGeotab Trips using a combination of GPS and odometer fallback. The difference between minimum and maximum odometer represents carry-forward odometer readings and may differ from GPS distance due to missing odometer reports or spiked odometer values from the vehicle.

I do not see EV range and state of health fields in the monthly Vehicle KPI table.

EV range and state of health fields are only shown when the last-observed VIN during the month is an EV. The data reflects the latest estimate within the local calendar month.

I use SAML/SSO to log in to MyGeotab. Can I use the same credentials in the Data Connector?

No. The Geotab Data Connector only supports basic authentication. You must either switch your MyGeotab authentication type from SAML to basic authentication, or create a new MyGeotab account with basic authentication to connect to the Data Connector.

Where is yesterday's data for predictive safety tables?

Predictive safety data requires benchmarking against fleets, vehicles, and drivers across Geotab's network, which results in a lag of up to 2 days in safety-related metrics and predictions. Data is refreshed daily but with up to a 2 day lag.

"Unable to connect: We encountered an error while trying to connect. Details: OData: We were unable to detect required payload information."

This is a known Power BI issue caused by an empty response payload due to insufficient view permissions. Ensure you have the appropriate view permission for the vehicle or device on your MyGeotab account.

How do I change my authentication credentials?

To change credentials for the Data Connector server in Power BI:

1. Select File in the ribbon menu, then select Options and settings.

2. Click Data source settings.

3. Select the relevant Data Connector access URL and click Edit Permissions.

4. Click Edit under Credentials. Use Data sources in current file to update credentials for a single PBIX file, or Global permissions to update credentials for all PBIX files on the local machine. Credentials are saved locally and are not stored in the PBIX file.

The remote server returned an error: (400) Bad Request

Check your credentials: the username must be in the format <MyGeotab Database Name>/<MyGeotab Username>. Also verify that the access URL is correct, including any $search date range parameters.

The remote server returned an error: (401) Not Authorized

Check your credentials: the username must be in the format <MyGeotab Database Name>/<MyGeotab Username>.

The remote server returned an error: (404) Not Found

Check the access URL. This error indicates the requested resource or table does not exist.

The remote server returned an error: (406)

Check the access URL. This error indicates the Data Connector server in the URL does not match your MyGeotab database.

OData: Request failed: The remote server returned an error: (412)

This error indicates you have not subscribed to the Geotab Data Connector. See Geotab Data Connector requirements for instructions on how to enable the Add-In.

OData: Request failed: The remote server returned an error: (416)

The data request is too large and exceeds the Data Connector limits. Reduce the amount of data by using narrower date range filters. See Filter Data Connector data by date range.

OData: Request failed: The remote server returned an error: (429)

You have sent too many requests in a short period of time. Wait a few minutes before refreshing your data sources. The general limit is 100 requests per user per minute.

OData: Request failed: The remote server returned an error: (500)

The Geotab Data Connector service is temporarily unavailable. Try again later. If the error persists, contact customer support.

OData: Request failed: The remote server returned an error: (503)

The MyGeotab authentication service is temporarily unavailable. Try again later. If the error persists, contact customer support.

OData: The Property {0} does not exist on type {1}.

There has been a change in the Data Connector's metadata. Clear the data cache in Power BI: select File, then Options and settings, then Options. Under Global, select Data Load, scroll to Data Cache Management Options, and click Clear Cache. Restart Power BI before refreshing your data connections.

[DataFormat.Error] We cannot return the data produced by this query because of its complexity.

You have sent too many requests in a short period of time. Wait a few minutes before refreshing your data sources. The general limit is 100 requests per user per minute.

The remote server returned an error: (400) Bad Request

Check your credentials: the username must be in the format <MyGeotab Database Name>/<MyGeotab Username>. Also verify that the access URL is correct, including any $search date range parameters.

The remote server returned an error: (401) Not Authorized

Check your credentials: the username must be in the format <MyGeotab Database Name>/<MyGeotab Username>.

The remote server returned an error: (404) Not Found

Check the access URL. This error indicates the requested resource or table does not exist.

The remote server returned an error: (406)

Check the access URL. This error indicates the Data Connector server in the URL does not match your MyGeotab database.

OData: Request failed: The remote server returned an error: (412)

This error indicates you have not subscribed to the Geotab Data Connector. See Geotab Data Connector requirements for instructions on how to enable the Add-In.

OData: Request failed: The remote server returned an error: (416)

The data request is too large and exceeds the Data Connector limits. Reduce the amount of data by using narrower date range filters. See Filter Data Connector data by date range.

OData: Request failed: The remote server returned an error: (429)

You have sent too many requests in a short period of time. Wait a few minutes before refreshing your data sources. The general limit is 100 requests per user per minute.

OData: Request failed: The remote server returned an error: (500)

The Geotab Data Connector service is temporarily unavailable. Try again later. If the error persists, contact customer support.

OData: Request failed: The remote server returned an error: (503)

The MyGeotab authentication service is temporarily unavailable. Try again later. If the error persists, contact customer support.

OData: The Property {0} does not exist on type {1}.

There has been a change in the Data Connector's metadata. Clear the data cache in Excel: select the Data ribbon tab, then click Get Data. Under Get Data, select Query Options. In the Query Options dialog, select Data Load, scroll to Data Cache Management Options, and click Clear Cache. Restart Excel before refreshing your data connections.

Unable to access OData URL {0} with server response 400

Check your credentials: the username must be in the format <MyGeotab Database Name>/<MyGeotab Username>. Also verify that the access URL is correct, including any $search date range parameters.

Unable to access OData URL {0} with server response 401

Check your credentials: the username must be in the format <MyGeotab Database Name>/<MyGeotab Username>.

Unable to access OData URL {0} with server response 404

Check the access URL. This error indicates the requested resource or table does not exist.

Unable to access OData URL {0} with server response 406

Check the access URL. This error indicates the Data Connector server in the URL does not match your MyGeotab database.

Unable to access OData URL {0} with server response 412

This error indicates you have not subscribed to the Geotab Data Connector. See Geotab Data Connector requirements for instructions on how to enable the Add-In.

Unable to access OData URL {0} with server response 416

The data request is too large and exceeds the Data Connector limits. Reduce the amount of data by using narrower date range filters. See Filter Data Connector data by date range.

Unable to access OData URL {0} with server response 429

You have sent too many requests in a short period of time. Wait a few minutes before refreshing your data sources. The general limit is 100 requests per user per minute.

Unable to access OData URL {0} with server response 500

The Geotab Data Connector service is temporarily unavailable. Try again later. If the error persists, contact customer support.

OData: Request failed: The remote server returned an error: (503)

The MyGeotab authentication service is temporarily unavailable. Try again later. If the error persists, contact customer support.

Unable to connect to the server: Deadline Exceeded

Your connection has timed out. Reduce the amount of data by using narrower date range filters. See Filter Data Connector data by date range.