Does anyone know how processing data with the Push Notifications (SM302000) screen impacts licensing restrictions?
As we all know, when developing external solutions that integrate with Acumatica, we need to keep in mind licensing constraints since Acumatica is licensed on transactions and not on users.
With that in mind, I know that the following are best practices:
- When reading data from Acumatica, use OData instead of an API endpoint because OData calls are not subjected to the Maximum Number of Web Services API Requests per Minute limitation on the License Monitoring Console (SM604000) screen that API calls are subjected to. OData calls are essentially free, at least until the private equity firm that owns Acumatica decides to monetize them 😀
- Keep in mind that any data you write back into Acumatica using the API is subject to the same Maximum Number of Commercial Transactions and Maximum Number of ERP Transactions limitation on the License Monitoring Console (SM604000) screen that you are subject to if you are entering data manually in a screen.
However, what I'm not clear on is the licensing impacts of using the Push Notifications (SM302000) screen in Acumatica which allows you to send a real-time data update to an outside application when data changes inside Acumatica. This is especially useful on master-level data like Stock Items where you want a data change to hit an outside application immediately rather than wait for the next data scheduling interval.
Maybe