We’re running ES 10.2.500 and having issues with our warehouse analytics dashboard after bulk inventory updates. I used DMT to import around 15,000 inventory adjustments this morning, and the import completed successfully with no errors in the DMT logs.
However, our analytics dashboard still shows yesterday’s inventory levels even though the base inventory tables have the updated quantities. I’ve checked the PartBin table directly and confirmed the new on-hand values are there:
SELECT PartNum, BinNum, OnHandQty, LastCountedDate
FROM Erp.PartBin
WHERE PartNum = 'WH-2024-001'
-- Shows updated qty: 2,450 units
But the dashboard widget for “Real-Time Inventory Levels” is still displaying 1,820 units (the old value). We have several warehouse managers relying on these dashboards for daily operations, and this is causing confusion about actual stock levels. Is there a specific ETL job or analytics refresh process that needs to run after DMT imports? The dashboard worked fine with manual inventory adjustments through the UI.
Thanks for the quick responses. I found the Analytics Administration screen, but I’m not seeing a clear “Refresh” button. Is it under a specific menu path? Also, would this need to be done after every DMT import, or can we schedule it to run automatically after our nightly import jobs?
I noticed you mentioned checking the PartBin table directly. That’s good verification, but keep in mind the analytics layer aggregates data from multiple sources including PartBin, PartTran, and InventoryQtyAdj tables. Sometimes discrepancies occur if the transaction history hasn’t been fully processed. Make sure your DMT import is also creating the corresponding PartTran records for audit trail purposes, otherwise the analytics calculations might not match your expected results.
One thing to watch out for - if you’re running multiple DMT imports throughout the day, you don’t want to trigger the analytics refresh after each one because it’s resource-intensive. Consider batching your imports and scheduling the refresh to run once after all imports complete. We set ours to run at 6 AM after our overnight import batch, and it works perfectly. The analytics pipeline can handle incremental updates much better than constant full refreshes.