I have DeviceHub configured successfully with printers, but when I add a usb scale it exceeds the API request limit all on its own after a minute or two.
Seems like devicehub is updating the SMScale table with the scale weight, but then forgetting to log itself out after??
Does anyone have any ideas? TY!!
Best answer by rosenjon
Acumatica might want to reconsider it’s use of rate limiting for the API. What exactly is achieved by this?
I have found that logging in and out programmatically in-between calls(synchronous) solves any problems like this, including if you only have a single user.
But honestly, what is Acumatica incentivizing here with this strategy? Making API based calls to the database flaky so that systems don’t work right and customers get mad and move to a different product? What are they worried about? If you had unlimited REST API calls, maybe you could build your own front end and not have to pay Acumatica? Does anyone think that’s going to happen?
What is the strategy here? Licenses are tied to REST API calls, and therefore we’ll incentivize the purchase of more licenses? Why not just sell an appropriate number of concurrent REST API licenses, and then customers can decide what they need, rather than this opaque and error prone system?
+7As far as I know this has been fixed in the new version of the product. Which version do you have? Could you try the latest version?
Do we need to update Acumatica in order for this feature to work?
+7it looks like you have a recent version.
I think it worth creating a support case for investigation.
Hi
Hey
No I have not found a solution
thank you
Acumatica might want to reconsider it’s use of rate limiting for the API. What exactly is achieved by this?
I have found that logging in and out programmatically in-between calls(synchronous) solves any problems like this, including if you only have a single user.
But honestly, what is Acumatica incentivizing here with this strategy? Making API based calls to the database flaky so that systems don’t work right and customers get mad and move to a different product? What are they worried about? If you had unlimited REST API calls, maybe you could build your own front end and not have to pay Acumatica? Does anyone think that’s going to happen?
What is the strategy here? Licenses are tied to REST API calls, and therefore we’ll incentivize the purchase of more licenses? Why not just sell an appropriate number of concurrent REST API licenses, and then customers can decide what they need, rather than this opaque and error prone system?
+7Also, we cannot reconfigure hardware on the fly, so we cannot do the after the fact consumption based billing here.
If you have any ideas on how to make that more user friendly I invite you to share the ideas in https://community.acumatica.com/ideas
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
