2.20.0 - Table Pagination

March 28, 2025

New Features

  • ItemPath now includes pagination parameters in the URL for Explorer, Logs, and other tables. When you browse a table with many pages and select a page other than the first, the page and pageSize parameters are added to the URL. 

    For example: https://example.itempath.com/explorer/locations?page=4&pageSize=27 would load page four of the locations table with 27 records per page.

    You can adjust either of these parameters (using numerical values) to navigate tables throughout ItemPath. ItemPath does not save custom page sizes, but they will appear alongside the default sizes. This feature is not currently supported for Reports

  • Data Push mappings are now sorted by position when making requests. Although this change won't affect most use cases, it improves scenarios where Data Push must transmit data in a specific order.


Bug Fixes

  • Resolved an issue where only one filter criterion was applied when multiple filters were passed using the same parameter to the Transactions endpoint. The ItemPath API now correctly applies all filters.
  • Fixed an issue that prevented the SSL verification setting in integrations (Data Push, Data Pull, Variance) from applying correctly.
  • Fixed an issue that caused the connection to time out when updating an order while also passing "true" to "allocate" or "deallocate" by improving the order of operations.
  • Fixed an issue that caused the full response for all report row generation API calls to be logged.