3.4.10 - ItemPath 3 Regression Bug Fixes

September 8, 2026

Improvements

  • The application now provides more space between the environment banner and the page content, making page titles easier to include in screenshots.
  • Report data now limits displayed numeric values to two decimal places when the data is provided as a number.
  • Improves PowerPick Web Services order creation so a stale order-management login session is automatically refreshed and retried instead of immediately failing Data Pull order creation.

Bug Fixes

  • Fixes Data Push log records so they are associated with the correct app, allowing log filtering and reporting by app name to work as expected.
  • Fixes API order creation so location selectors passed by ID work consistently, including Count orders that generate order lines from selected locations.
  • Fixes API material create and update requests so configured Material dynamic fields can be saved and returned.
  • Fixed Count order creation so orders created with location selectors can complete the automatic work order setup instead of failing during work-order-line creation.
  • Fixed task search on Data Pull integration logs so searching can find tasks by their related log descriptions, matching the previous API behavior.
  • Sanitized database connection test errors so failed PowerPick SQL checks no longer expose raw database names, driver details, or SQLAlchemy/pyodbc exception text.
  • Variance report snapshots now use the same merged and filtered variance data as the report table, and variance filters handle grouped, blank, and string-style filters more reliably.
  • Variance reports now apply comparison-column filters and sort direction more consistently when the report includes external variance data.
  • Processed orders in Explorer no longer show Allocate, Deallocate, or Delete actions.
  • Fix snapshot charts so deleting a default snapshot or changing report filters does not leave broken selections or stale chart data.
  • New Data Push and Data Pull integrations are now created as inactive by default so status sorting behaves consistently.