The Reports section includes topics covering working with and troubleshooting reports and advanced reports which are available with Sugar Enterprise and Ultimate editions.
People often ask how to create reports similar to the dashlet concept of "my items" to prevent each user creating a report unique to them displaying their individual data. These redundant reports are not necessary thanks to the "Current User" filter.
Learn how to create a matrix report that displays the sum of opportunities that have a status of "Closed Won" grouped by month for each salesperson.
The following question was recently posed, "Is it possible to find all the contacts in the system that do not have an email address associated to them?" The answer to this question is a good example of using the "Optional Related Modules" setting within the Reports module.
Advanced reports allow users to create custom reports using SQL queries to directly query the Sugar® database for more flexible and extensible reporting. This article covers how to create an advanced report that displays your instance's user accounts and their assigned roles.
Although 'Email Address' appears as a field in several modules (including Accounts, Contacts, Leads, Users, etc.), email addresses are actually stored in a unique database table. Email Address records relate to the modules where they appear as opposed to being direct fields of those modules.
Sugar's Campaigns module can be used to create both email and non-email based campaigns. Email- and newsletter- type campaigns consist of mass emails sent from Sugar® to a relevant set of contacts, leads, targets, accounts, or users. The results are tracked to measure the overall success of the campaign, and you can view the results via the Campaign Status page. For more information regarding campaign statuses, please refer to the Campaigns documentation.
One of the most common use cases for Sugar® reports is to display a list of records and their related module records side by side. But sometimes there is valuable insight to be gained from identifying records that lack a certain relationship. For example, a sales manager may evaluate her team's performance by monitoring the quantity and quality of interactions with prospective customers. In Sugar, a report can be configured to identify records that have no related calls, meetings, or tasks (collectively called "activities").
Advanced reports allow you to create custom reports using one or more SQL statements to query the Sugar database directly. Users with SQL knowledge can take advantage of the advanced reporting capabilities to create direct database queries for more flexible and extensible reporting. This article explains how to create an advanced report that tracks changes made to audited fields.
Sugar® keeps track of user activity so that administrators can spot trends and abnormalities in system usage or performance. Tracker reports can be used to monitor user actions and sessions as well as system performance and queries. Module-based activity reports can also provide insight into how users are engaging with Sugar. This article explains both tracker reports and activity reports as well as how to display them on a dashboard for easy viewing.
In Sugar®, you have the option to email reports directly to you. This can be especially useful for users who must monitor certain activity via reports on a regular basis. This article will cover how to schedule a report so it will be emailed to you every day.
Sugar includes many pre-built tracker reports. You can use these reports to get information on user actions, sessions, performance, and queries. If you believe that your tracker reports are missing data, contact your administrator to confirm that trackers are enabled.
Reports are a powerful tool in Sugar® that give users the ability to review and analyze data across multiple related modules. Occasionally, you may find that a report's results do not match your expectations. This article will help you determine why a report might be missing expected results.
The "All Opportunities by Lead Source by Outcome" report's chart is displaying incomplete data.
If clicking on or attempting to run a report in Sugar produces a blank page, it may indicate a PHP incompatibility, timeout, or memory exhaustion.
Understanding the Reports module in Sugar can provide a user with a powerful data analysis tool. One of the more complicated issues surrounding the proper display of information in a report involves understanding which filter operator to use and when. This document will explain the differences between AND/OR operators and provide some examples of how and when each should be used.
The Define Filters step of the report wizard determines which records the report includes or filters out. Filter groups and operators allow for additional levels of complexity as you combine filters to get the precise result set you desire.
Sugar's Reports module comes with over 100 pre-built, stock reports. When new versions of Sugar are released, the stock reports that are shipped with the release may vary. Some new reports may be added and some older reports may be retired as legacy offerings. Legacy reports are never deleted from an instance during an upgrade, they just cease to be distributed for new installations of Sugar. This article describes the legacy stock reports that may be found in a Sugar instance but are no longer shipped with or documented in the current version of Sugar.
Trackers in Sugar® let administrators and supervisors oversee user productivity and system efficiency. They monitor system performance data, session information, and slow queries as well as the frequency of users' record-save actions and page views (i.e. which modules and records they have accessed). This article explains how to enable trackers, what they are used for, and defines the different types of tracker reports available within the application.
Last modified: 2016-08-31 21:55:16