Hey <a data-id="8083" data-value="mdevol" data-denotation-char="@" href="/user/mdevol" class="text-decoration-none mention">@mdevol</a>, Getting Devices is limited to 5000 results, if you look at the API reference page for it here: <a href="https://developers.geotab.com/myGeotab/apiReference/objects/Device/index.html" target="_blank">Device</a>, you'll see that at the bottom, it has the pagination information. You can implement pagination by following <a href="https://developers.geotab.com/myGeotab/guides/concepts/#pagination" target="_blank">this guide</a> in the documentation. Let me know if that works or if you have any other questions! Thanks, Tucker

Get Device is being limited to 5000 records

+1 to this point. Is there a reason that you're looking for the max version specifically? If it's just to know when to stop asking for results, I would recommend exactly what <a data-id="1145" data-value="LPPapillon-1145" data-denotation-char="@" href="/user/lppapillon-1145" class="text-decoration-none mention">@LPPapillon-1145</a>suggests and simply loop until there are no more to get. For high-activity feeds, the version is likely to be a moving target anyway - you might find the current latest record and have additional records added by the time you're done looping and processing the first batch.

Geotab SDK GetFeed call never reaches max version

<a data-id="8083" data-value="mdevol" data-denotation-char="@" href="/user/mdevol" class="text-decoration-none mention">@mdevol</a> I think its probably best to make a support ticket here and dig into it a little more so we can see whats going on.

Trailer devices with TmpTrailerID set to null

Hey <a data-id="8083" data-value="mdevol" data-denotation-char="@" href="/user/mdevol" class="text-decoration-none mention">@mdevol</a> thanks for reaching out and sorry has interrupted you again let me talk to the team who worked on this and see what they say. I will let you know what I hear from them as soon as I do!

Getting PlatformNotSupportedException when authenticating to GeoTab

In GeoTab.Checkmate.ObjectModel ver. 11.118.421, the following valid Sort constructor call throws an ArgumentException:Sort sortOptions = new Sort(SortField.IdSortField,
						   SortDirection.Asc,
						   null,
						   null);This is because of a logic bug in the following Sort constructor code 	public Sort(string sortBy, SortDirection? direction = global::Geotab.Checkmate.ObjectModel.SortDirection.Asc, string? offset = null, Id? lastId = null)
	{
		if (SortField.ImplementedSortFields.Contains&lt;string&gt;(sortBy, StringComparer.InvariantCultureIgnoreCase))
		{
			throw new ArgumentException("Use existing implementation of ISort for this field");
		}
 
		SortBy = sortBy;
		SortDirection = direction;
		Offset = offset;
		LastId = lastId;
	}In the if statement, SortField.ImplementedSortFields is a string array that contains all the valid sortBy field names, which means that the exception should only be thrown when Contains returns false.  So, for this to work correctly, the return value of Contains should have been inverted, meanting the if statement should look lie this: if (!SortField.ImplementedSortFields.Contains&lt;string&gt;(sortBy, StringComparer.InvariantCultureIgnoreCase))
{
	throw new ArgumentException("Use existing implementation of ISort for this field");
}I've been able to work around this by passing an invalid sortBy value and then changing the SortBy property value Sort sortOptions = new Sort("invalid",
							SortDirection.Asc,
							null,
							null);
 
sortOptions.SortBy = SortField.IdSortField;A possible better implementation would have been to use an enumeration of valid sortable field names.  That way, invalid values can't be passed in, and it would be caught at compile time instead of run time.

Valid Sort constructor call throws an ArgumentException

DvirLogs.Defects is marked as deprecated with the following message - "FB/289474 Need to support it at least for 1805, will be removing this after 1805".  Is this still accurate and if so, what is it being replaced with and when? 

Is DvirLogs.Defects still scheduled to be removed

<a data-id="1044" data-value="EishiFUN" data-denotation-char="@" href="/user/eishifun" class="text-decoration-none mention">@EishiFUN</a> Thanks, I have a very small test app that reproduces this problem if it would be helpful. If you're interested in it, just let me know where to send it.

<a data-id="1044" data-value="EishiFUN" data-denotation-char="@" href="/user/eishifun" class="text-decoration-none mention">@EishiFUN</a> Thanks for the update. I tried to update our project to 4.7.2, but couldn't get it build for non-GeoTab reasons. So, we're holding at 4.6.2 for now. I'll keep an eye out for the fix next week.

<a data-id="1044" data-value="EishiFUN" data-denotation-char="@" href="/user/eishifun" class="text-decoration-none mention">@EishiFUN</a> Ok, thanks

I have 35 Trailer devices that were created on 7&#x2F;27&#x2F;26, but the TmpTrailerID property was not set to an Id value (i.e. null). TmpTrailerID has been marked a deprecated for a long time, but has still been assigned Id values. So has GeoTab started moving away from the TmpTrailerId field or is there another reason these 35 trailers weren't assigned a TmpTrailerID?

<a data-id="1044" data-value="EishiFUN" data-denotation-char="@" href="/user/eishifun" class="text-decoration-none mention">@EishiFUN</a> I have no direct knowledge how these trailers were created, I've reached to see if someone can find out for me. I'll let you know when I have more information.

<a data-id="1044" data-value="EishiFUN" data-denotation-char="@" href="/user/eishifun" class="text-decoration-none mention">@EishiFUN</a> I got a reply back that the trailers were added using the UI.

<a data-id="1044" data-value="EishiFUN" data-denotation-char="@" href="/user/eishifun" class="text-decoration-none mention">@EishiFUN</a> I got the latest GeoTab package that was released on Monday and was able to apply to our code with no issues. So consider this closed. Thanks for the help,

We are using Get with a DeviceSearch to return all the Trailer Devices. However, it is only returning 5000 of the 63000+ Trailers. I have check the documentation and can't find any mention of record limits. The only limits mentioned is number of calls per minute. Can anyone explain why we are seeing this kind of limit? Here is the code being used to make the call <img class="ql-image" src="/forum/plugins/gcs-uploads/files/1791476508374-image.png"/>

page-user page-user-mdevol template-account-profile page-status-200 theme-harmony user-guest

Company

Title

["Integrators Group"]

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

Integrators Group

<a data-id="1044" data-value="EishiFUN" data-denotation-char="@" href="/user/eishifun" class="text-decoration-none mention">@EishiFUN</a> Bad news, this issue is back with the latest GeoTab nuget package 11.143.432. As mentioned above this issues was resolved in the prior nuget package 11.139.528. We are still using .NetFramework 4.6.2. Here is the call we are making into GeoTab: 					await geoTabAPI.AuthenticateAsync(); Here is the stack dump for the latest nuget package: Inner Exception 2: System.PlatformNotSupportedException: Operation is not supported on this platform. at System.Net.Http.HttpClientHandler.set_CheckCertificateRevocationList(Boolean value) at Geotab.MachineSettings.GeneralMachineSettings..cctor() --- End of inner exception stack trace --- Inner Exception 1: System.TypeInitializationException: The type initializer for 'Geotab.MachineSettings.GeneralMachineSettings' threw an exception. at Geotab.MachineSettings.GeneralMachineSettings.get_ApplicationVersion() at Geotab.Checkmate.Web.WebServerInvoker..cctor() --- End of inner exception stack trace --- Outer Exception: System.TypeInitializationException: The type initializer for 'Geotab.Checkmate.Web.WebServerInvoker' threw an exception. at Geotab.Checkmate.Web.WebServerInvoker.get_SharedHttpClient() at Geotab.Checkmate.Web.WebServerInvoker.d__54`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Geotab.Checkmate.Web.WebServerInvoker.d__28`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Geotab.Checkmate.Web.WebServerInvoker.&lt;&gt;c__DisplayClass60_0`1.&lt;b__0&gt;d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable.ConfiguredTaskAwaiter.GetResult() at Geotab.Tasks.TaskExtension.d__7.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult() at Geotab.Tasks.TaskExtension.d__9.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable.ConfiguredTaskAwaiter.GetResult() at Geotab.Tasks.TaskExtension.d__8`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Geotab.Checkmate.Web.WebServerInvoker.d__25`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Geotab.Checkmate.API.d__58.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Geotab.Checkmate.API.d__47.MoveNext()

I'm going a GetFeed for DeviceStatusInfo, but it never returns a ToVersion value that &gt;= to the max version. Before I start looping, I made a call to get the max version which returned a value of 1378535. On the first call to GetFeed with fromVersion set to 0, it returned 7 DeviceStatusInfo records and a ToVersion of 1378497. On the next call to GetFeed with fromVersion set to 1378497, it returns 0 records and the same ToVersion value. At this point, I'm caught in an infinite loop because the ToVersion value is never &gt;= the max version. So, is this a known behavior where it's possible that max version may never be reached? Also, this code runs against multiple GeoTab databases, but this issue only occurs against this one database. If someone can provide an explanation, I would appreciate it.

Any idea when there will be a new release to fix this issue?

Nedávná aktivita

Get Device is being limited to 5000 records

Geotab SDK GetFeed call never reaches max version

Trailer devices with TmpTrailerID set to null