I want to change my custom reports time frame just before executing them, using the XML API.
Here is how I proceed:
The first step works fine, I see the time frame modification in the web interface and the config logs.
But when I pull the results, the new time frame is not taken into account. It seems that the "running config" time frame is used, instead of the one in the "candidate config".
How can I manage to make it work without doing a commit ?
Solved! Go to Solution.
Unfortunately the system requires that you commit the custom report changes prior to being able to invoke them using the API, unlike the 'run now' function in the gui.
Ok, too bad the API doesn't mimic the GUI behavior.
Any chances the commit requirement will be lifted in a next version ? Or that the "starttime" and "endtime" parameters are going to be supported when requesting custom reports through the API ?
On another note, it seems you have edited some lines out of your post, about committing through the API being possible since v4.0.2.
I didn't try it out nor found any documentation about it. Is it ready for "prime-time" ?
Yes... I ammended my post because the commit API feature is officially in version 4.1 which is in beta testing currently. Have you checked out the updated Perl Package for interacting with the XML API? There are many useful libs to simplify scripting efforts...
Current version is located here:
I will take a look to see if <period> will be supported with custom reports....
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!