Lyonel Posted February 23, 2017 Posted February 23, 2017 Hi, I have a bit of a random question... I noticed we can run a report using the API (which is great! ). The output is a run ID. Reusing this run ID, is there a way to download directly into CSV the report programmatically? For example: https://admin.hornbill.com/<instance>/app/com.hornbill.servicemanager/reporting/<Report ID>/reports/<Report ID>_<Run ID>.csv? That would be super useful in terms of integration...
Gerry Posted May 18, 2017 Posted May 18, 2017 @Lyonel When the report is run its data thats created, not the actual report. The data can be pulled down over WebDAV with the required access token but its quite a complex thing to do. I am not sure what form the data is in. @NeilWJ can you shed any light on this? Gerry
Guest Chaz Posted May 19, 2017 Posted May 19, 2017 @Lyonel you can access the report directly with a valid session or with an access token in the header from a URL like this:https://eurapi.hornbill.com/INSTANCENAME/dav/reports/REPORTID/REPORTID_RUNID.csv
Lyonel Posted May 22, 2017 Author Posted May 22, 2017 @Gerry, @Chaz, Thank you so much for coming back to me on this one! This will be very useful when communicating with my colleagues and giving them the direct URL to the report executions, until you come up with a new interface for accessing reports and dashboard from Service Manager
mfoster Posted November 24, 2017 Posted November 24, 2017 I'm sorry to revive a dead thread, but does this method for report retrieval still work? I've been getting a 404 error for reports generated after update 2856.
TrevorKillick Posted November 24, 2017 Posted November 24, 2017 @mfoster The report outputs have been updated to now be generated in https://eurapi.hornbill.com/INSTANCENAME/dav/reports/REPORTID/REPORTNAME_RUNID.csv However older reports will still be accessed from the old path. Ideally reporting::reportRunGetStatus should be used to obtain the file output for a given report run https://api.hornbill.com/reporting/?op=reportRunGetStatus , reportRun->csvLink is populated with the file name of the CSV to maintain backwards compatibility however there is also and array of output files added to support the additional file types now supported in reporting. Kind Regards Trevor Killick 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now