This is the third part of a three-part series on the coreBOS reporting system. You can read the first part here and the second part here.

This type of report aggregates the values of a field on a module grouped by a field on another related module.

For example we can get the total sum of invoices grouped by the status of assets

Or the count of support tickets per status and product

Or the count of support tickets with related payments paid and pending...

This functionality is still in an early stage of development. It only supports standard capture fields (uitype10) to establish the relationship and it is the stepping stone upon which we will construct the possibility of creating grouped reports in the system.

This functionality is very similar to what can be done in the My Sites extension but it always opens the URL in a new tab. The main idea is to have a central place for all your users to access their reports, at least the most important ones even if they are reports generated in another application.

Creating a report of this type consists of simply introducing the URL in the input box and indicating if the report needs to know what user is opening it.

Have a look at the next video to see an example using the Metabase integration: we create a report/question in metabase, activate sharing on the question, copy the URL of the question and put it in the coreBOS report definition.

I hope this tutorial has helped you understand better the functionality and limitations of the reporting system.

As a closing note, I leave a few related links from the documentation wiki and a VERY serious nudge for you to dedicate some time to getting Metabase working, it will be well worth every minute you spend.

• User Manual::Report Charts
• User Manual::Reporting
• A trouble ticket report in vtiger CRM

Let me know if I missed some part you would have liked to have seen or simply express your needs in our gitter channel or forum.

Thanks for reading.

Photo by rawpixel on Unsplash rawpixel