We're using GetFeed to sync ExceptionEvents to a data warehouse. We use includeDismissedEvents and includeInvalidated to make sure we properly pick up on Exceptions that are no longer valid and we can mark them as such to ensure integrity between MyGeotab and our warehouse. We just noticed a case where a new rule was created and the old rule was deleted, and all the previous exceptions from the deleted rule are still there with ExceptionEventStateValidId. Is it expected that with these flags both set to true, Geotab does not send us deleted exceptions that stem from a rule deletion? How can we keep sync for such cases?

GetFeed on ExceptionEvents vs deleted rules in MyGeotab SDK

As part of the long plan to transition trailers under Assets (Device entity), Geotab previously published and shared this document:https://docs.google.com/presentation/d/1C0CBY4qaJKHx3J-fdB-YZzxbilQoleqjv8WsyFIZhEE/edit It covered the changes in Geotab 7 and 8, and then ended up with a brief summary of the next steps (Geotab 9 and 10). By Geotab version 10, the migration was supposed to be finished, DVIRLog.trailer was to be decommissioned in Geotab 9 IIRC and Geotab 10 was supposed to introduce DeviceLink as a replacement to TrailerAttachment. Geotab release 9, 10 and 11 came with no update about this process, and Geotab has been seemingly silent on the updated roadmap that will greatly affect us as integrators. I went back to check the document and slide 43 was changed to mention the Geotab 12 release now, but the plans are not detailed and with the new Geotab release cycle, I'm not even sure Geotab 12 will ever exist. Can we get an update on the plan?How long will the "long" trailer IDs exist and mirror names/groups from the Device entity? How long will TrailerAttachment be supported? How and when will the transition to DeviceLink take place? Please don't keep us in the dark. It will affect multiple add-ins and integrations and we need to plan for it. 

Trailer in API roadmap update?

We use this API to take pictures from the drive app. When we send them out, the resolution and very low. Is there any way to control it? Can we get the original picture in full resolution?

api.mobile.camera.takePicture() resolution

I don't want to spam tickets for mypreview servers, I know things tend to break and that is their purpose. I just want to make sure Geotab is aware that the new mypreview builds completely broke all Geotab Drive add-ins. All the script and style files are attempting to load on the geotab servers even though they are remote from our domains. All add-ins throw an exception when loading. Also if Geotab is working on overhauling the way Drive add-ins are being loaded, I'd appreciate some fore notice.Thanks! 

Geotab Drive add-ins broken on mypreview

We have a Geotab Drive add-in that connects to various TMS platforms. It worked fine in previous cases, but recently we've implemented a connection to a TMS that required X_API_TOKEN header in the request, and another that requires the Authorization header. We implemented this in our add-in with proper tokens. It works fine locally in the add-in generator, it works fine in the online Drive app in the browser, but when going live in production on actual devices, we found only iOS devices could connect to the TMS's. I've investigated, and the XHR calls from the Geotab Drive add-in running on Android will simply not go out. The OPTIONS request goes out, the remote server accepts and allows any header, then Android will immediately launch the error callback without even attempting to make the GET or POST request. If we remove the special header it starts working (but then the TMS refuses the request because unauthorized). I've replicated this on my own server, if I tell Android to send an Authorization header, I see the OPTIONS request come in, but no POST follows. If I instruct the add-in to remove the Authorization header and try again, I see both OPTIONS and POST work. On iOS both scenarios work perfectly. It seems to be a problem between WebView and Cordova I think, same as documented here:https://github.com/Telerik-Verified-Plugins/WKWebView/issues/142Has anyone else attempted or experienced this? I am unable to send a token-secured request from Geotab Drive on Android, and that's a big problem to us right now.

Passing custom headers in Ajax requests in a Geotab Drive add-in?

When you enable Cloudflare edge caching for your add-ins...  

Add-in caching

I appreciate the new callbacks and events that have been added to the Deeper add-ins recently. I have hit a use-case where I need one more. There is a service now to subscribe to map changes (ie: pan or zoom), that provides me with the updated viewport. I need to bind now to when the map is repainted, meaning when the "refresh" button reaches the 20 second countdown and forces a repaint, or when the user manually clicks it to repaint. Can it be added to the list of callbacks? I don't need any params passed it, could look something likeservice.map.attach('painted', () =&gt; {
    //My code here
});I know this would not be triggered on Active Tracking cursor updates, it is not needed here anyway. Thanks!

Need additional Deeper add-in callback

We have a map add-in that fetches COVID-19 heatmap data from our backend services on every viewport change. It mostly works for everyone, but I am seeing LOTS of errors in the logs on our server from requests that received coordinates like this: sw.lat 45.51824379408402sw.lng -73.50593185ne.lat 45.51848435368473ne.lng -73.50593185 In all problematic cases, ne.lng is EQUAL to sw.lng. When we try to convert this to a polygon, BigQuery throws an error because of the the vertices are exactly the same and the polygon creation fails. My question is, is there a known issue in certain MyGeotab versions that either service.map.getBounds() or the service.map.changed callback event would receive incorrect viewport parameters? I have audited the add-in code and I am correctly passing in the ne.lng and sw.lng parameters. I thought it could be a precision level on very close zoom levels in some cases, but it's not. This happens at all zoom levels, even down to zoom level 4 for instance. I am taking additional measures to prevent these calls from even happening client-side and further troubleshoot conditions where this might happen, but as I said the add-in works in most conditions.

Wrong viewport bounds in Map add-in?

We've released our COVID-19 heatmap as a map add-in, and just got a call from one of our clients. Their "Supervisor" users are unable to view it. Nothing shows up. I've investigated if there was a special clearance that would be needed to show Map or "enhanced" add-ins, but can't find any. They have clearances required to view add-ins and add-in data. They can see and use other types of add-ins, but the map add-in isn't even loaded. Is there a way to get them to see it?

MyGeotab clearance for map add-ins access?

I have a client that wants to use a WMS service to add custom maps. Their WMS service requires authentication in the form of basic authorization header. If I just add the WMS map in Geotab I get 401 unauthorized responses when loading tiles. If I just enter the WMS URL in the browser first and enter username/password in the popup there, then the WMS service works and tiles load fine until I close the browser and then the problem arises on the next load.Is there a way to configure the custom map to use basic authentication? Can I input the username and password in the options config for the map? What is the expected syntax?

WMS map with basic authentication

I haven't seen this, but my hunch is that if you were to call again to get the max version, you'd get where you're at now. What call did you make exactly to get the max version? In general, with any GetFeed, the loop we use is if results.data is the same length as resultsLimit, then there are more to fetch. Loop until it's smaller. You should be wary of enforced resultsLimits though, if you use this logic with GetFeed on Device, but your code requests 50000 resultsLimit, the real limit is 5000, so a full page will return 5000. As long as you send resultsLimits equal or smaller than the actual enforced limits as per the documentation, this logic has been fool-proof for all entities across thousands of databases over several years.

Geotab SDK GetFeed call never reaches max version

page-user page-user-lp-papillon-1145 template-account-profile page-status-200 theme-harmony user-guest

Company

Title

["Map Server Updates Group"]

A broadcast-only group for customers and resellers to receive monthly and quarterly Map Server Updates in MyGeotab.

Map Server Updates Group

A broadcast-only group for receiving Geotab integrations news and updates!

Integrators Group

Thanks Joy. We do have a product that handles SSO from a display device to show a real time map with time sensitive alerts. This solves the use-case of customers wanting an operations-center style map on display in an office location. It does not solve the use-case for embedding a live map within a web portal, intranet or other integrated solution. There are other ways to accomplish this. Can you share a bit more of what you're trying to accomplish?

Does a MyGeotab session ever time out for a user? Customer wants to embed a URL of the live map

Thanks for the update Brent. My attempts with DeviceLink date back 1+ year so I don't have any recent conclusions or findings on the matter. At the time we had looked at the available (outdated) documentation about the migration plan (Geotab 9-10-11), confirmed the Drive app was still relying on TrailerAttachment internally and had not yet transitioned to DeviceLink, and decided to defer further testing until we had more guidance. Great news if an updated plan is coming for integrators.

DeviceLink Changes & Implementation Assistance

+1 on wanting more detailed plans and forewarning on Geotab's plans regarding this migration. We've also noticed long ago that DeviceLink is not ready to replace TrailerAttachment yet, and so we've kept multiple integrations relying on TrailerAttachment being there and old trailer ids / trailer entities remaining in place. We need guidance on when DeviceLink will be fully usable as an alternative, and then we need some leeway before TrailerAttachment is fully removed. You need fully support of both entities in the interim while we update multiple products and integrations using it.Thanks for asking <a href="/user/jacob-purvis-1275" data-id="1275" data-value="JPurv-1275" data-denotation-char="@" class="text-decoration-none mention">@JPurv-1275</a>​.

- PreventDriverAccessToSharedDataThis is from the Driver object (subclass of User). The property is called viewDriversOwnDataOnly. Default is false.<img src="/forum/plugins/gcs-uploads/files/069Pd00000UqP65IAF.png" alt="image" /> - SameAsDataAccessGroupsThis isn't a quick toggle. In the API, you need to specify companyGroups and reportGroups, and if isDriver:true you NEED to specify driverGroups. Up to you do decide if you duplicate the companyGroups value in there or if you set it differently.

I would like to know how to access or set certain user/driver fields in MyGeotab via the API.

Here is how to get the support contacts: Example request:<img src="/forum/plugins/gcs-uploads/files/069Pd00000UqkaGIAR.png" alt="image" />Example response:<img src="/forum/plugins/gcs-uploads/files/069Pd00000UrBfDIAV.png" alt="image.png" /> You can see the 3 contact types: "Call", "Training" and "Procurement". None of this is documented or supported. Subject to change and use at your own risk.

No, Button add-ins are only supported in MyGeotab. In Geotab Drive, only Page add-ins are supported.

Can button type Add-Ins be added to the Geotab Drive App?

No, I mean your object on line 40. Your 2nd call (not Authenticate but GetPostedRoadSpeedsForDevice).Yes, I've successfully used this API. You should first fix the credentials issue above, but after that you'll hit another exception with the way you pass in device_id, it should instead be a deviceSearch object as noted in the documentation you linked. Something like:<code> "deviceSearch": {
 "id": device_id
 },
 "fromDate": from_date,
 "toDate": to_date</code>

Assistance with Retrieving Max Road Speed Using MyGeotab API Adapter

You are missing the userName in your credentials object in your 2nd call, it is needed along with the sessionId and database.There is a python package you can use that handles this for you and might be easier: https://github.com/Geotab/mygeotab-python

Don't set an id or a version value when adding an entity. id should not be the device id, it will be a trailerattachment id and the system will generate and return it automatically.

Viimeaikaiset toiminnot

GetFeed on ExceptionEvents vs deleted rules in MyGeotab SDK

Trailer in API roadmap update?

api.mobile.camera.takePicture() resolution