By
Mendy Green
July 15, 2025
•
20 min read
Tutorials
Fundamental Skills
8 Guidelines for better HaloPSA Reporting
HaloPSA reporting is a common stumbling block for MSP teams and it’s no wonder why. With decades-old naming conventions, SQL complexity, and inconsistent column naming, most folks give up before they get started.
But if you’ve worked the helpdesk, you already have the most important skill: troubleshooting.
At Rising Tide, we lean into that mindset. These 8 guidelines—developed by Mendy Green—are how we train team members to creatively and confidently troubleshoot their way through the HaloPSA database. This isn’t a ruleset: it’s a survival guide built from lived experience, experimentation, and a lot of Ctrl+F. The following is also available to view on a video from Mendy linked here: https://youtu.be/1h3lMqIQbXY.
Guideline 1: FAULT Is a Ticket
Halo uses the term “fault” instead of “ticket.” That’s a legacy holdover from NetHelpDesk, Halo’s predecessor. If you see “fault,” translate it in your head to “ticket.”
🛠 Real Example: When writing a report, select from the faults table to get ticket data—even if you're working with projects, opportunities, or tasks. They're all stored as faults.
Guideline 2: ACTION Is a Note or Entry on a Ticket
Every email, time entry, and status change lives in the actions table. If something happened to a ticket, it’s here.
🛠 Real Example: Time entries, incoming/outgoing emails, status changes, and internal notes all show up in actions, joined to tickets via fault ID.
Guideline 3: Understand Table Prefixes
Most tables prefix their column names based on the table itself. That prefix tells you where the data originated.
🛠 Real Example: In the site table, SArea refers to the client (Area). In the user table, USite points to the site ID. If you see a column like QHID, that’s the primary key from quotation header.
Guideline 4: Primary Keys Get Reused Across Tables
Once you know a table’s primary key, look for it in other tables to understand relationships.
🛠 Real Example: area, site number, UID, and fault ID show up across multiple tables. If you know a device’s DID, you can filter by it and join against other asset-related tables.
Guideline 5: Use the Reporting Module to Search and Learn Faster
Skip loading massive reports. Use the Fields tab to explore column names and understand structure before you ever hit preview.
🛠 Real Example: Mendy uses Fields to inspect columns like OutcomeID, ActionByUNum, or SDeliveredBy to identify their function—without ever loading a full dataset.
Guideline 6: Utilize “Open Report Data Source” to Reverse Engineer
Halo’s online report repository is a goldmine. You don’t even need to install a report—just open the data source and see how it’s built.
🛠 Real Example: When Mendy didn’t know how a report generated “Month Created,” he opened the data source and saw how CONVERT was used to format the date. Instant clarity.
Guideline 7: Use the "Database Tables & Columns" Report—But Always Filter First
This built-in schema reference report lets you search by table or column name—but don’t run it raw. Filter by table or field name first or it’ll crash your browser.
🛠 Real Example: Mendy uses this to find terms like “Azure Tenant” and locate where clients are mapped. It’s a last-resort treasure map—useful but slow.
Guideline 8: Use Real Values to Discover Field Names
If you know a real-world value (like an asset tag), pull that entity with SELECT * and search for it. That’ll reveal the column name you’re after.
🛠 Real Example: Mendy didn’t know which field stored an asset’s tag—until he filtered device by ID, Ctrl+F’d the tag, and found it was stored in INVNO (inventory number).
Conclusion
You don’t need to master SQL overnight to get value out of HaloPSA. You just need to lean into what helpdesk techs do best: problem-solve with what’s in front of you.
These 8 guidelines aren’t about perfection. They’re about being clever, resourceful, and creative with the tools you’ve got—and turning reporting from a weakness into a strength.
I'm passionate about IT, driven by a dual love for solving complex problems and a commitment to transforming the stereotype of technical support into a positive and enjoyable user experience. For over 13 years, I've been deeply involved in the MSPGeek community, lending my expertise to various Managed Service Providers (MSPs), while also serving as the CTO at IntelliComp Technologies.
My journey in the tech world is fueled by a passion for teaching others. I find great satisfaction in imparting problem-solving and critical thinking skills, and offering practical guidance during the troubleshooting process. It's this enthusiasm for mentorship and improvement that led me to my current venture.
Today, as the founder of Rising Tide, I'm focusing on the MSP industry, dedicating my time to coaching and assisting both individuals and businesses. At Rising Tide, we're not just about providing solutions; we're about nurturing growth, fostering innovation, and building a community where everyone can rise together. Whether it's through hands-on problem solving or strategic planning, my goal is to make the IT experience not just efficient, but also empowering and enjoyable
See some more of our most recent posts...
By the [run]Book: Episode 4
By the Run Book dives into HaloPSA v2.192 — from holiday approval tweaks and smarter contract scheduling to AI suggestions, new security controls, and Robbie’s Quick Ticket app for lightning-fast ticket logging.
Read post
In Episode 4 of By the Run Book, the team digs into HaloPSA v2.192 with a mix of technical deep-dives and practical tips for MSPs. Robbie and Mendy walk through improvements in holiday approvals, contract schedule plans, and important security updates like webhook authentication. They also explore quality-of-life changes in ticket type restrictions, AI suggestions without an AI license, and new admin mode controls. To wrap up, Robbie demos his “Quick Ticket” browser extension for lightning-fast ticket creation without breaking your workflow. Whether you’re streamlining internal processes, tightening security, or speeding up ticket logging, this release has something to improve your day-to-day.
Watch Now: By the [run]Book: Episode 4
Robbie's Quick Tickets: Halo Quick Ticket - Microsoft Edge Addons
Multiple minor improvements to Holiday Approvals | v2.192 #948186 | 3:55
- Shows balance in days/hours instead of decimals
- Approval screen now displays holiday details
- Fix for approval from holiday record failing
Multiple minor changes to improve Contract Schedule Plan functionality | v2.192 #947953 | 7:01
- Easier setup for scheduled contract work
- Tracks allocated vs. remaining hours
- Still manual for recurring hour replenishment
Federated credentials update endpoint | v2.192 #937555 | 13:40
- API endpoint to update federated credentials more easily
Quotation Config: remove whitespace from signature image | v2.192 #937347 | 14:30
- Option to trim white background from customer signature images
Ready for Invoicing filter applies to other billable entities | v2.192 #937175 | 17:17
- Top-level Customer criteria now carry over to other billable entities
- Ignores other non-applicable filter criteria
Integration and webhook improvements | v2.192 #936110, #936402, #936998, #936862, #936739 | 19:34
- Various integration updates including webhook authentication
Charge Rate restrictions at Ticket Type | v2.192 #933938 | 22:17
- Restrict allowed charge rates for specific ticket types
AI Suggestions without AI integration | v2.192 #923472 | 24:48
- Use AI Suggestions feature without enabling AI integration
Admin Mode security improvement | v2.192 #909530 | 31:55
- Requires 2FA to enable Admin Mode
- Adds audit logging of activations
Load Balance limits by Team | v2.192 #898859 | 35:52
- Limit tickets assigned via load balancing per team
Forecasting Module improvements | v2.192 #883797 | 36:00
- Enhancements to AI-based forecasting for tickets, hours, and reports
Enabled for Instances option | v2.192 #882671 | 39:05
- Limit notifications, webhooks, and runbooks to specific instances
Disable editing of config-tracked entities | v2.192 #882664 | 39:32
- Prevent editing config-tracked entities directly in production
Sprints for config tracking | v2.192 #882648 | 40:26
- Group config changes into deployable sprints
Filter ticket types on New Ticket screen by group | v2.192 #858227 | 41:40
- New ticket screen can be filtered by Ticket Type Group
Show/hide more User system fields in Screen Layout Profiles | v2.192 #856243 | 47:20
- Added more User fields to show/hide controls
Add new Contacts on Opportunities | v2.192 #840296 | 47:46
- Add contacts directly from existing opportunities
Owners and Assets in article query builder | v2.192 #836009 | 48:06
- Owners and Assets now reportable in article queries
Added $-LOGGEDINAGENTSIGNATURE variable | v2.192 #831158 | 48:15
- Variable for logged-in agent’s signature
Unit prices in Product Bundles on Quotes | v2.192 #823474 | 48:53
- Show per-unit price when group quantifier enabled
Restrict creation of new article tags | v2.192 #822558 | 49:48
- Only allow selecting from existing article tags
Primary agent, secondary agent, and account manager as additional agents | v2.192 #821136 | 49:57
- Option to add these roles as additional agents when logging a ticket
Countersign Quotations | v2.192 #820956 | 53:04
- Allow countersigning of quotations before finalizing
Prefix for $ variables with data | v2.192 #793305 | 53:55
- Prefix only appears if variable contains data
Halo Quick Ticket extension demo | 55:21
- Robbie’s Edge/Chrome extension for quick ticket creation
- OAuth setup with Halo, select fields, and complete on creation
By the [run]Book: Episode 2
HaloPSA 2.188 introduced runbook triggers via chat, smarter billing rules, and cleaner settings layouts. In this recap, Mendy and Connor unpack key updates, link to demo timestamps, and flag risks like the still-unruly HubSpot sync. This is your practical guide to deploying the new features with confidence (and a few extra guardrails).
Read post
HaloPSA version 2.188 brought a variety of usability and backend enhancements—from runbook triggers in chat to finer-grain billing logic and cleaner settings layouts. In Episode 2, Mendy and Connor walk through these updates, troubleshoot common gotchas, and share the kind of real-world implementation advice you can only get from people deep in the trenches. They also made a point to mention a few times to add feature requests at ideas.halopsa.com
Watch now: https://youtube.com/live/6tjM4SGOcB4
Busy MSP? This guide recaps the episode’s major updates, links you to key moments in the video, and flags anything that might deserve extra caution in deployment.
Join us July 22, 2025 for Episode 3, where we'll start to cover v2.190!
Trigger Runbooks from Chat | v2.188 #838526 | 3:14
Chat flows can now kick off integration commands—including runbooks. Embed chat on your website or in Teams, and let Halo handle the routing. You could:
- Run diagnostics
- Route to support teams
- Automatically open categorized tickets
⚠️ Be careful what runbooks you expose publicly—especially if they modify data.
Notification Sound Customization | v2.188 #820304 | 6:58
You can now toggle the notification sound on or off—but the visual popup still appears. You still can’t upload custom sounds, and notifications can get out of hand across tabs.
💡 Bonus tip: You can suppress sound notifications per rule, but they may still clutter the alert pane.
WebSocket Notifications (Beta) | v2.188 #839402 | 8:02
Enable WebSockets for faster, real-time alerts instead of using the default polling (heartbeat). This reduces delay in receiving internal or backend alerts.
Backend Service Monitoring Logs | v2.188 #840002 | 9:13
Debug runbooks, automations, email failures, and integration issues using the new service monitoring pane. It logs each backend action so you can pinpoint where workflows failed.
🔍 You no longer need to email Halo support for log digging—huge time-saver.
Travel Charge Rate Flexibility | v2.188 #843591 | 15:25
You can now set separate rates for time and distance in a single travel charge entry. Perfect for billing both mileage and technician transit time in a single step.
Email & Settings UI Reorganization | v2.188 #839711 | 21:22
Settings like mailboxes, templates, and rules have been reorganized into distinct tabs instead of being buried under “General.” More logical, but prepare for some retraining of your internal muscle memory.
Auto-Expire Contract Logic | v2.188 #842066 | 25:50
Set a contract status to auto-expire when the end date passes. A scheduled task now flips expired contracts to “inactive” if configured.
⚠️ Hidden contracts can cause trouble—pair this with automated tickets or alerts to track renewal conversations.
Item Group Accounting & Billing Defaults | v2.188 #844350 | 33:00
You can now:
- Prevent PO receiving or invoice creation at group level
- Exclude groups from accounting sync (useful for test/staging items)
Connor and Mendy share tips for keeping messy product catalogs from polluting QuickBooks/Xero.
Client-Specific To-Do Groups | v2.188 #847221 | 51:57
To-do groups can now be restricted to specific customers. Use this to tailor onboarding checklists, project tasks, or compliance processes.
⚠️ Only one customer per group for now. Feels clunky, but it’s a start.
Clone Billing Templates | v2.188 #849112 | 52:32
Quickly duplicate complex billing logic with a new “Clone” button. Ideal for MSPs using multiple templates per client or those needing custom combinations for each contract type.
Advanced Billing Rule Matching | v2.188 #850203 | 54:23
Billing plan rules can now reference:
- Ticket custom fields
- Action fields
- Agent properties
Use this to get laser-precise about when a contract or billing model should apply.
New Custom Field Storage Options | v2.188 #853900 | 1:04:20
Choose between traditional storage (custom fields added to core tables) or a new “separate table” method. The latter avoids bloating system tables—but still stores multi-selects as comma-separated strings (ugh).
Quote XLS Import Profiles | v2.188 #855612 | 1:18:27
You can now import vendor quote spreadsheets directly into Halo quotes. Set up mappings for Cisco, Dell, or distributor quote templates and save serious time.
OAuth via Custom Developer Apps | v2.188 #856711 | 1:21:52
You’re no longer stuck using Halo’s shared apps. Bring your own app registration to limit scopes, improve auditing, and align with internal security policy.
Recurring Invoice Proration Simplification | v2.188 #857744 | 1:24:33
A new setting condenses prorated adjustments into a single invoice line (instead of two). Easier to read—but harder to debug.
🔍 Consider leaving this disabled unless your team fully understands the logic.
HubSpot Integration Tweaks (and Pain) | v2.188 #859011 | 1:31:35
The HubSpot sync continues to be... challenging:
- Doesn’t respect new “Accounts & Prospects” model
- Overwrites domains and duplicates clients
- Inconsistent inbound behavior
Proceed with extreme caution or disable it entirely.
By the [run]Book: Episode 3
This HaloPSA release may not grab headlines, but it delivers smart backend fixes for billing, approvals, and project automation. From delegate ticket approvals to proration-ready invoices and improved QuickBooks syncing, it's a solid batch of quality-of-life upgrades for fast-moving teams and structured orgs alike.
Read post
This release didn’t come with any headline grabbers—but for those deep in Halo, it delivered a handful of quality-of-life improvements and some thoughtful backend fixes. Below are the features worth your attention, especially if you're in billing, approvals, or building project automation.
Watch here now: https://youtube.com/live/WGnJXYeSxN4
Features Reviewed
Delegate Approvals for Tickets | v2.190 #830512 | 2:28
Ticket approvers can now assign delegates directly from the agent app ticket detail screen. Great for ITSM or structured orgs, but less relevant for fast-moving MSPs unless you're running approvals regularly.
Manual Proration Made Invoice-Ready | v2.190 #823611 | 4:18
A new checkbox on manual proration entries lets them show up in the invoicing screen immediately. Particularly useful for mid-cycle adjustments to annual billing, like licensing or domains.
Zero Draft Invoice Handling | v2.190 #819999 | 6:41
Halo will now ignore draft invoices created in Xero, preventing clutter and accidental syncing. You'll need to enable this in the Xero integration webhook settings.
Receive Stock Before PO Approval | v2.190 #829771 | 9:04
You can now receive items before a purchase order is approved. Risky for strict workflows but may fit fast-paced environments where hardware urgency overrides red tape.
Auto-Issue Items from Actions | v2.190 #837101 | 10:21
Set up actions to issue specific inventory items without user selection. Makes fixed-fee tickets more maintainable. Bug alert: doesn't yet work with quick actions—still requires a workaround.
Ticket ID in PDF Template Item Tables | v2.190 #837112 | 12:39
PDF templates can now pull the associated ticket ID into item tables—helpful for clarity in documentation, reporting, or client-facing PDFs.
Read-Only Appointment Subjects | v2.190 #829744 | 17:43
Admins can lock appointment subjects to match the ticket/project. It’s a small control that helps standardize records across large teams.
Editable Invoice Line Contract Links | v2.190 #823492 | 20:41
You can now edit the contract tied to a specific invoice line—especially valuable if you're tracking profitability across services with multiple contracts.
Prevent RMM from Changing Device Types | v2.190 #821917 | 24:58
ConnectWise RMM imports won't overwrite an existing device type anymore, assuming you check the new box.
QuickBooks Name Collision Workaround | v2.190 #829321 | 26:05
Halo now checks for matching item names before syncing, and links them rather than creating duplicates. A clever patch for a QuickBooks API issue.
Ticket Type as Rule Outcome | v2.190 #831422 | 27:28
You can now set ticket type via rule outcomes. Great for automating triage flows or conversions between types during lifecycle changes.
Team Custom Fields in Details Tab | v2.190 #831994 | 31:13
You can finally surface custom fields tied to teams directly in ticket details. Limited use cases for now, but it’s a step toward richer internal data visibility.
Granular Attachment Permissions | v2.190 #829812 | 32:36
Admins can now control who can view, edit, upload, and download attachments—down to the ticket type and role level.
Track Completion of Sales Lines | v2.190 #832113 | 33:58
Sales order lines can be manually or automatically marked as “Complete.” Adds helpful clarity, especially when you're tracking partial progress across installs or shipments.
Runbook Execution Modes (Parallel/Sequential) | v2.190 #830301 | 35:27
Control how runbooks trigger: run steps in parallel for speed or in series to avoid conflicts and ensure data accuracy.
Column Profiles for Invoices & Quotes | v2.190 #834755 | 44:01
Column profiles now work on sales orders, quotes, and invoices. You can personalize the data you see—and what you hide—for cleaner views.
Runbook Stats Tab | v2.190 #830996 | 35:27
Basic run metrics are now visible in a tab. Not yet robust for reporting, but a decent glance for usage and debugging.
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword. And join us on August 5th for a show with Robbie and Mendy: https://youtube.com/live/ApiYEmWJsPU!