Objective
TeamDynamix has the capability to build comprehensive and informative reports for many aspects of the platform. This guide will provide an overview of the features and serve as a starting point for building custom reports in TDNext. This is not a comprehensive guide, but rather an introduction to the types of reports that can be created and the information sources reports are built on. Technicians are encouraged to explore the reporting functionality and create reports useful to them.
Procedure
Step 1 - Select Report Type
- Select the University IT Tickets tab.
- Pressing the + Report button will bring the following screen up:

Select the type of report you would like to generate. The types (sources) of reports are listed below. A "Ticket Report" will be used for this example:
- Knowledge Base Report - This allows you to create custom reports based on Knowledge Base articles in the Client Portal.
- Knowledge Base Feedback Report - This allows you to create custom reports based around Knowledge Base Feedback in client portal applications.
- Location Rooms Report - This allows you to create custom reports based on Location Rooms in asset/ticketing applications.
- Locations Report - This allows you to create custom reports based on Locations in asset/ticketing applications.
- Ticket Report - This allows individuals to report on tickets.
- Ticket Tasks Report - This allows individuals to report on ticket tasks, workflow work steps, and maintenance activities associated with tickets and service requests.
These report types affect the sources that will be used for information in the report. Select the type that best resembles the report desired. The report type (source) cannot be changed later.
Step 2 - Building A Report
- After selecting a report type, you will be met with the New Ticket Report screen. Regardless of report type, your screen should resemble the one below.

Overview of Fields
- Name - The title of the report.
- Description - Short explanation of the function and purpose of the report.
- Columns - The fields that should be included in the report. These will change based on the report type (source) selected.
- Filtering - Criteria that must be met for certain fields.
- Order - The order that items appear in the report. (If applicable)
- Maximum Rows - The number of rows (data entries) that will be returned when the report is run. Consider restricting this value to only return the items of interest.
- Report Folder - Specify where the report should live. Select the option that best fits the report being created.
- Visibility - Specify whether a report should be visible to the creator, everyone with TDNext access, or members of specific groups.
- Chart - Allows a visible representation of the data to be generated. Most suitable for categorical data.
- Desktop Delivery - Specifies the format for displaying the data generated in the report.
- Email Delivery - Allows specified recipients to receive a copy of the report via email.
Specifying Columns to Report On
- The core of the report is the selection of which fields should be included in the report. It specifies what information will be shown by the report and how it is formatted. In the report builder, fields can be modified, sorted, aggregated, for formatted. This works in conjunction with filtering to create a report that shows the desired information from the tickets/tasks/objects.
- Suppose a report is built to display the number of tickets created for the Service Desk within the last week by status. The fields can be set as shown:

- In this report, fields included are Ticket Count, which returns the quantity of tickets, and status, which returns the status (New, In Process, Resolved, etc.) of those tickets.
- The Ticket Count field will be restricted in the filtering section of the report.
- Add as many or as few columns as desired. Keep in mind the readability of the report may be diminished if too much data is included.
- Consider breaking large reports into multiple smaller ones for easier readability.
Filtering Results
- Since this report is designed only to be applied to a specific group, you will need to add filters, so it only reports on individuals in a certain group.

- Here, the group(s) that you want to run the report on have been selected, and a time filter only reports on the last 30 days of activity.
- Checking the 'Prompt' box will cause the report to ask for the group to report each time the report is run. This may be desired for some general-purpose results.
Charting
- Charts may be desirable for reports that provide a high-level overview of performance indicators or other statistical data. Each chart has a type (bar, line, pie, gantt), name, and value. The name field will be used as the independent variable, while the value field will be used as the dependent variable. Looking back at our example, we can see that Primary Responsibility is used as the name, and Average Create to Resolve is the value.

Finished Report
- After saving and running the report, the information will be displayed in the format selected. The completed example is shown here:

Notes
For those familiar with writing SQL queries, you can think of the reporting functionality in a similar manner. The reported columns are similar to the SELECT statement, specifying what values should be returned, and the filters are similar to the WHERE statement, specifying what criteria the selected items should meet.
For more information on TDNext reporting or questions relating to reports, please contact the OIT Service Desk.