null where the report shows zero. Unlike the legacy route-based report, the date range includes crossings by start time rather than overlap, and the Groups filter applies to travel totals as well as material totals. Route-group filters match direct parents only. For an event with metadata naming several zones, the first zone in metadata-id order is used, matching the stored aggregate producer. The legacy report uses its metadata read order, which can choose another zone. These cases can produce different totals from the report. null, but never soft-deleted data. As in the report, the total time and total distance are those driven inside the route's zones, so the total time can be less than the spread time. Units are the report's storage units: solid in grams, anti-ice and pre-wet in litres, rates in kilograms per kilometre (solid), litres per kilometre (anti-ice) and litres per tonne (pre-wet), distances in kilometres and durations as time spans. See MaterialManagementRouteBasedRecord.solidTotal; null values sort lowest. Sorting by primary, routeId or routeGroupId orders by the route or route group name, and a sort by route group puts the routes in no route group last. A column that is null for every row, such as deviceId, leaves the default order unchanged; name, id and then the position among the rows of the same route or route group break ties in ascending order. Page with resultsLimit and resultsOffset, and use WebMethods.GetMaterialManagementRouteBasedCountAsync for the number of rows rather than recounting.| Method | Description | Limit | Period |
|---|---|---|---|
| GetMaterialManagementRouteBased | Limit of 100 requests per 1m. | 100 | 1m |
Loading API Runner...