By using this website, you agree to our Terms of Use (click here)
In order to allow me to focus on Consulting (click here) and Courses (click here), I continue to review all posts here in the Forums, but, in general, I'm only personally responding to posts that I mark as #AcumaticaTnT (click here). For Questions (click here), others may respond, or you can post over at Community.Acumatica.com (click here).
Sincerely,
Tim Rodman
Hello,
I'm trying to automate SnapShot creation with API.
I have an issue at the very first step when calling the 'scheduleLockoutCommand' action on SM203510 screen.
Although I receive the "204 : The operation that has been initiated by the action has completed or was not created." code, Acumatica does not enter in maintenance mode.
I have the same with the 'exportSnapshotCommand' action on SM203520 screen: code 204 but no snapshot created.
Does anyone tried this kind of API calls ?
Any help is welcome.
Hi Laurent,
When you initiate a lockout the system will wait a minimum of 20 minutes before locking. Is it possible it is accepting the lockout command, but is then in the 20 minute grace period, before locking? I am quite interested in using the API calls to do this as well, so I can pair it with a Microsoft Flow to automate the process.
If I get some spare time, I'll have a look on my side. I already have Flows built for other functions through the API, but hadn't considered using it for this.
Cheers.
Hi Stewart,
I'm working on a french edition of Acumatica, called Flex. With this release, the manual lockout is immediat, but it doesn't change anything here.
The weird thing I've noticed is that as for all actions, you still have to pass an entity ID, which is pointless.
For instance this array doesn't throw any error :
{"Entity":{"anyKey":{"value":"anyValue"}},"parameters":{"Reason":{"value":"test"}}}
Still searching, I'll post here any good results I'll find.
Thanks.