Skip to main content
Solved

Inventory Qty via push notification

  • Mar 18, 2026 8:40 PM UTC
  • 8 replies
  • 126 views
  • Translate All

We are trying to use a push notification to send inventory data from a GI to an outside system. We have created several other push notifications that are working as expected but our inventory push is not.


We are currently using px.objects.in.inventoryItem as our table.

Results tab: InvenotryID, SiteID, LastModifiedDateTime, & QtyOnHand.

Nothing is hitting the push when inventory updates.

 

Thanks,

Best answer by KrunalDoshi

Hi ​@PatrickHarrisonCallMTG,

The key point is that InventoryItem is not where the quantity change is actually persisted.

QtyOnHand is typically coming from inventory/site-specific data (INSiteStatus / related inventory availability data), not from InventoryItem.

Instead of using InventoryItem as the GI's driving table, build the GI around the inventory/site status record and expose InvenotryID, SiteID, LastModifiedDateTime, & QtyOnHand fields. One thing I would also determine whether INSiteStatus is actually updated in a way that the Push Notification engine can detect.

Then configure the Push Notification against these new GI.

Hope this helps!

View original

8 replies

jhalling52
Jr Varsity I
Forum|alt.badge.img+1
  • Jr Varsity I
  • Mar 18, 2026 9:00 PM UTC

Try using the PX.Objects.IN.INSiteStatus table.  All the fields should be the same.  

Translate

Dmitrii Naumov
Community Manager
Forum|alt.badge.img+7

​@PatrickHarrisonCallMTG I’d recommend using Storage Details built-in GI (IN408050 - DB-StorageDetails) 

Translate

Try using the PX.Objects.IN.INSiteStatus table.  All the fields should be the same.  

Thanks Joe, I just tried that and had the same no-push result.

Translate

​@PatrickHarrisonCallMTG I’d recommend using Storage Details built-in GI (IN408050 - DB-StorageDetails) 

Thanks Dmitrii, I tried that as well with no luck. 

This seems simple but nothing we try is working.

Thanks,

Translate

Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • Jul 14, 2026 11:38 PM UTC

Hi ​@PatrickHarrisonCallMTG were you able to find a solution? Thank you!

Translate

No, we did not. Our partner is still working with us to come up with the best option. Thanks for checking in.

Translate

KrunalDoshi
Pro I
Forum|alt.badge.img+9
  • Pro I
  • Answer
  • Aug 14, 2026 10:41 AM UTC

Hi ​@PatrickHarrisonCallMTG,

The key point is that InventoryItem is not where the quantity change is actually persisted.

QtyOnHand is typically coming from inventory/site-specific data (INSiteStatus / related inventory availability data), not from InventoryItem.

Instead of using InventoryItem as the GI's driving table, build the GI around the inventory/site status record and expose InvenotryID, SiteID, LastModifiedDateTime, & QtyOnHand fields. One thing I would also determine whether INSiteStatus is actually updated in a way that the Push Notification engine can detect.

Then configure the Push Notification against these new GI.

Hope this helps!

Translate

Naveen Boga
Captain II
Forum|alt.badge.img+20
  • Captain II
  • Aug 14, 2026 11:20 AM UTC

​@PatrickHarrisonCallMTG I think INSiteStatus may not work in this scenario because the updates to QtyAvail, QtyOnHand, and other related quantity fields are being made to INSiteStatusByCostCenter.

 

Have you tried using INSiteStatusByCostCenter instead and verified whether the Push Notifications are triggered correctly?

 

Translate