While I have been successfully able to use "toDate" to specify a range of dates when searching for exception events as recently as Thursday, May 28, GetFeed now appears to return the number of events specified in resultsLimit regardless of whether the exception occurred after the specified "toDate." I do not have issues specifying "toDate" using Get.
You need to be logged in to reply to this post and participate in the Geotab Community discussions.
Hey @TLand-10632,
I'm not 100% sure, but I didn't think GetFeed ever worked with a ToDate. The documentation said it only supported a FromDate and only on the first request, and afterwards to use a fromVersion, but there's a chance it was just accidentally supported and recently removed. Either way, if you have a ToDate, you should be using a Get instead of a GetFeed I would think. What is the use case you had for using GetFeed with a ToDate?
Thanks,
Tucker
Thank you, now that I think about it, it's very possible that I was getting all exceptions to the present, but it took a short enough time that I didn't notice.
I was advised that because of the size of our fleet (20K+ devices) and the large volume of exceptions generated, GetFeed with a low resultsLimit would be a more efficient way to get the information from 100K+ exceptions per week. I was having sporadic difficulty with timeouts using Get, and I was hoping that I could use GetFeed to more reliably pull a week's worth of exception data. I was hoping to use toDate so I could get only the target week's worth of exceptions, but it sounds like checking the last date of each GetFeed call will be the way to go?
Yes GetFeed is more efficient for that, but Get also just had pagination added recently which can be combined with the propetySelector to have pretty efficient requests that kind of act like a GetFeed but within a certain date range. You could also try that if you wanted. Otherwise, I'd say do what you're doing and just monitor the result set for the end date you're looking for and stop looking at results after that.
You also might want to look at the API adapter if you haven't. Then you could feed your data into your own database and query the data from there. For large fleets like yours we typically recommend that method to our customers when they're trying to set something like that up.
Thank you for the suggestions, I will look into them!