Reports come in many different shapes and sizes. When I addressed this topic almost two years ago (Are There Different Types of Reports?) Power BI dashboards were in their infancy. Now that’s all anyone wants to talk about!
There are too many different types to mention, but here are a few:
Why would you opt to use one over the other? This could be a long philosophical question, but the short answer is: the report type chosen should best display the information to the end user.
The long answer boils down to the same answer, but personal preference comes into play too. Do you create a pie chart, donut chart or a choropleth map? Is there a wrong answer to this question? I don’t think so.
The same is also true with this question:
-Do you create one report to rule them all or break it into smaller, easy-to-read chunks?
Other factors to take into consideration when running the report:
-Does the report take 15+ minutes to generate?
-Is the text too small to read?
-Will the report be real-time or a point in time?
To select the most appropriate report type, you need to review both the report request and the expected results.
Report Styles – Dashboard and Count Reports
Dashboard and Count reports tend to have one or more visual aid, additionally they will sometimes have a table to help explain the data being shown. They are intended to be used to quickly report on an item. For example, how many patches (by classifications) are installed versus not installed?
Report Styles – List Reports
List reports tend to be drill down reports from a Dashboard or Count report. A List report will provide more details about a particular item within the Dashboard or Count report. These reports are great because they answer questions such as, “Which computers need a particular software update?”
Report Styles – Detail Reports
Although these reports are not that different from List reports, a Detail report tends to provide even more information about an item. For example, it will provide information about all of the software updates on a computer. These reports are excellent at answering this kind of question, “I know this computer is missing software update KB 3164398, but what other software updates is this computer missing?”
At a basic level, a Scorecard is another type of Dashboard or Count report. A Scorecard differs by generally measuring your environment against a set threshold or Service Level Agreement (SLA) value. These types of reports help ensure that you meet your SLA levels by letting you know when more effort is needed. For example, after 24 hours, the SLA is supposed to have 85% of all computers with the latest software update. When the SLA is above 85%, the color is green, between 75% and 85% the color is yellow, and below 75% it is red.
Choropleth Maps tend to display a number of values in an area on a map. Examples being how many computers are missing two or more software updates by postal code or city.
No matter your ConfigMgr reporting needs, turn to Enhansoft to help you find the right fit for your Business Intelligence (BI) needs. We provide you with helpful and easy-to-read reports. If you don’t see what you are looking for then talk to us to see how we can help you solve your problem.