I'm sorry, but somhow I can't seem to find the report-functionality anymore. Is it hidden somewhere or has this feature been dropped in 12 ?
Scripting might be a bit hard to start with, but just as you says, what you are looking for can be achived with a script.
In the next update (will be available during this weekend) you can for example select an artist, select All tracks and then create a list with all of the albums the artist comes from.
From the next release you will also be able to get all data from the database via SQL from a script, meaning that you can access all data that's exsting.
Possibly we might create one of these reports during the next week to demonstrate the usage of SQL from scrips and publish in the scripts forum.
>>What I still don't look through at the moment is, where - meaning on which view, and based on what selection - the scripts should work.
This is up-to how each script is written and therefore up to the author to include information about in the script.
Unfortunately this might not clear in the current scripts, sorry for that but they are still work-in-progress.
It works like this because data can be fetched in various ways via the script engine:
-All albums in the active view (if it contains albums)
-All artists in the active view (if it contains artists)
-All albums in the database (possibly filtered also via a script)
-All artists in the database (possibly filtered also via a script)
Some scripts (housekeeping scripts for examples) completely ignores which view you are in so it is not always view/selection dependant.
We will make sure that this is more clear for the default scripts.
>> The latest script ArtistList for example only works, when you are in the artist detailed view,
No, that's not correct. It works for any view showing artists for example the artist view, where it accepts filtering (try to reduce the number of items with filters).
It also works from search results (artists page), genre page (artists page) for example.
>>It's very hard to find out with trial and error (which I did during the weekend) when a script can be applied, and when it will just produce empty output.
>>Shouldn't the scripts work on all views?
Please see above, we will fix this and also add these to the script guide lines that it should be mentioned where the script can be used from.
The thing is that the scripts allows for much more functionallity than just working with files/albums/artists which makes scripts powerful, versatile but also a little complex.
Hope this clarifies it a bit more.
Thanks for your feedback Michael.
We are testing a solution right now to fetch the current albums (or even artists) for the actual view.
Out of curiosity, can you please let us know a little more of how you are using todays "Print reports"?
-Which type of reports are you printing?
-Which destination format (PDF, Excel etc) are you using?
-What are you using the reports for?
Any additional information are welcomes, the more we get to know, the better we can create the new reporting engine.
Thanks in advance.
Thanks for your additional information Michael, we will take this information with us when we will analyse the requirements for implementing this feature.
Btw. is it anything you especially missing in todays Print report feature?
The old feature "Print Report" is currently not available in Helium 12.
We have not migrated that tool since it was very old, and it was not a feature that was well used when we did our survey about one year ago.
That does not mean it is gone forever though, if it will get requested, we will of course prioritize it.
Other lists such as text-files, HTML reports, CVS lists and such can be generated via scripts in Helium 12.
Two templates are included with the installer and these can be customized easily to show the preferred data.
A first version of this script can be downloaded from here:
Please note that Helium 12 version 14184 is required to run this script.
The styling is very basic, feel free to improve it further.