By
Mendy Green
July 15, 2025
•
20 min read
Tutorials
Fundamental Skills

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.
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.
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.
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.
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.
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.
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.
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.
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.

This discussion guide is part of Rising Tide’s Fall 2025 book club, where we’re reading The Go-Giver by Bob Burg and John David Mann.
If you’re just joining us, here are a few pages you’ll likely benefit from:
In Chapter 7, "Rachel," we learn more about Rachel and about the characteristics that Pindar finds valuable.
Use these open-ended prompts to guide reflection and conversation. Remember, there are no right answers!
Rising Tide helps MSPs and service-focused teams build better systems: the kind that align people with purpose.
Every Friday at 9:30 AM ET, we host Rising Tide Fridays as an open conversation for MSP owners, consultants, and service professionals who want to grow both professionally, technically, and emotionally. In Fall/Winter 2025, we’re walking through The Go-Giver, chapter by chapter.
If that sounds like your kind of crowd, reach out to partners@risingtidegroup.net for the Teams link.
Bring your coffee and curiosity…no prep required.

If you’ve already read Book Clubs, Conversations, and Curiosity, you know that at Rising Tide, we don’t host book clubs for the sake of reading. We use them as an excuse to talk, to listen, and to practice curiosity together.
The Go-Giver by Bob Burg and John David Mann is the first book that we've chosen to explore together in this way. Each week, we’re reading one short chapter together and using a few open-ended questions to spark real conversation: no lectures, no wrong answers, just reflection.
Below are our discussion prompts for Chapter One: “The Go-Getter.”
They’re written for teams like ours: busy, service-minded, sometimes too practical for their own good...who want to slow down long enough to notice what these stories have to teach.
How this guide is different from others you'll find online: We keep it chapter-focused. Every set of questions focuses only on the current chapter so there is no foreshadowing, no jumping ahead, no “we’ll get to that in Chapter 7.” The goal is to slow down and savor the smaller ideas that get lost when you rush to the big themes, and we're going to make sure that team members that are "behind" have enough data points to connect the dots and contribute even if they're not caught up to the current reading.
Use them however you like. Whether you’re reading along with us or just looking for a fresh team conversation starter, we hope these questions help you stretch a little, think differently, and see something new in yourself or your work.
If you tweak or add questions, tell us at partners@risingtidegroup.net. We’ll keep improving this tool for other MSP teams.
In this chapter, we meet Joe, a go-getter who doesn't seem to be getting what he's going for. We are also introduced to his coworkers: Melanie and Gus, who help connect him with Pindar, or the Chairman, who agrees to tell Joe the huge trade secret that will surely be his key to success.
Creatures of a day! What is anyone?
What is anyone not? A dream of a shadow
Is our mortal being. But when there comes to men
A gleam of splendour given of heaven,
Then rests on them a light of glory
And blessed are their days. (Pindar, Pythian 8)
Want to hang out in these conversations with the Rising Tide team? We meet Fridays at 9:30 AM ET to talk through important business, technological, and communal developments, and for the next 14ish weeks, The Go-Giver! If you’re an MSP owner, consultant, or service professional who wants to grow your team’s emotional intelligence alongside your technical skill, you’re welcome here.
Reach out to partners@risingtidegroup.net for the Rising Tide Fridays Teams link. Bring your coffee and curiosity: no prep required.

Like many MSPs, Rising Tide invests in our people through access to books, trainings, conferences, and certifications. At its core, this is not education for education’s sake: rather, we believe the best technical work starts with curiosity, and we consistently seek ways to foster curiosity as a skill. You see, we think the best solutions come not just from curiosity about technology, but curiosity about each other, about our clients, and about our community. We want to be known as people who ask better questions, understand others' perspectives with clarity, and are always hungry for more. We believe that personal growth will always drive technical and professional success for our team, and as a result, our clients.
So how does a business foster curiosity? Curiosity is not something you learn from an SOP, a certification, or a conference. It’s something you develop by creating the time and space for yourself and your people to feel safe to speak up, to ideate, to build, and to iterate.
We are doing our best to build a culture of curiosity and progress in as many ways as possible, not just through structured education, but in choosing tools, conversations, and activities where we can intentionally seek to learn from and about each other and the world around us. The last part is very important at a core level: we believe every person brings a different background, toolkit, and perspective that strengthens and deepens our own, even — or especially! — when we disagree.
As a fully remote team of 6, this can be pretty difficult to do since we can’t go out for lunch or have regular physical touchpoints other brick-and-mortar businesses may enjoy. So, one of the standard ways we cultivate this is through scheduled daily and weekly team conversations where we review customer issues, books or videos, conferences attended, or other interesting things we’ve seen that we want to share.
Most recently, we chose to essentially start a book club where we would read The Go-Giver by Bob Burg, together, and to invite clients and friends to review it with us on a weekly call. It was important to us that as a team expectation, we should make sure no one felt the demand too great on top of weekly work expectations. Thus, we decided on reading one chapter (7-10 pages) a week, to make sure that it felt accessible to everyone. (Reading ahead is absolutely allowed and encouraged, but we will only discuss one chapter a week!)
The next question for a book club is: how do you facilitate conversation in a way that allows for people to share what was meaningful to them, or to join in the conversation even if they didn’t get a chance to read? In preparing for our book meetings, I sought out online resources with simple chapter-by-chapter discussion questions. However, as a very easy read, it seemed that most questions online covered concepts that spanned multiple chapters, which encouraged reading ahead and missing perhaps some smaller ideas worth savoring in each chapter.
Honestly, we figure we’re not alone in this desire to have simple questions and to walk carefully through conversations, so we've decided to share our own discussion questions, chapter-by-chapter! These questions are written without consideration for future chapters of the book and are meant to help bring in conversation about the topics and themes specifically covered in the given chapter. These questions are open-ended and if you’re facilitating, we encourage you to take the stance of no-wrong-answers, just as an impartial listener. You never know what perspectives or fresh ideas may come out of conversation.
Check out The Go-Getter Chapter One Discussion Questions here.
We’ll continue to add discussion questions and commentary on the book club as we move forward. Next things I’d like to try is to offer facilitation to a team member who has read ahead, to help them stretch their muscles of asking questions and building conversations. What other ideas should we tie in?
Want to hang out in these conversations with the Rising Tide team? We meet Fridays at 9:30 AM ET to talk through important business, technological, and communal developments, and for the next 14ish weeks, The Go-Giver! If you’re an MSP owner, consultant, or service professional who wants to grow your team’s emotional intelligence alongside your technical skill, you’re welcome here.
Reach out to partners@risingtidegroup.net for the Rising Tide Fridays Teams link. Bring your coffee and curiosity: no prep required.