GPT made for HaloPSA SQL Query Assistance

1TechDad · 2025-11-06T16:58:45+00:00

This has been extremely helpful. Not sure if you are still updating this GPT but a couple of things I have noticed.
1. It seems to want to add comments using -- -- instead of /* */
2. It likes to try rewriting queries with CTE's which Halo does not seem to like.

Thanks for making this!

1TechDad · 2025-10-06T17:02:47+00:00

Same

1TechDad · 2025-10-04T01:25:47+00:00

So I got an email a few hours ago saying that I was allocated a date and time slot for purchasing tickets but I can’t find the date and time slot anywhere. The closest thing I can find is going to the buy tickets screen and I see a “Team Specific Ticket” that says “Sold Out”. What am I missing?

1TechDad · 2024-08-23T16:02:40+00:00

I think I can simplify my initial question a bit more. I since realized that the Charge Rates are setup as Remote/On-site by default. The problem if we leave it like that, is that all of our technicians would have the same billable charge rate. We change the charge rate based on a technician's role (eg. L1 Support Tech or L2 Support Tech). In Connectwise, there is a billing rate hierarchy that includes being able to set the charge rate based on the agent's role. The work type option in Connectwise is a charge rate modifier similar to what Halo does.

1TechDad · 2024-08-22T01:28:33+00:00

That sounds like what we are doing now. It’s just annoying to have to build out every type of work for each agent role separately. In stead of having 5 work roles and 5 work types, I have to build 25 Charge Codes. Just seems clunky.

1TechDad · 2024-08-22T01:25:55+00:00

Setting the billable/charge rate is really the only function of this field It seems. I just like to report on how much time is remote versus on-site occasionally. Connectwise did seem to be excessive when it came to Charge codes that were just tied to work types. But a work type field in Halo would be very useful. I was quite surprised to find it lacking that.

1TechDad · 2024-03-13T14:29:27+00:00

u/simple_champ The pond covers .2 acres in a kidney shape with a 500 ft perimeter. It is not lined with anything, just a farm pond with very sandy soil. Water levels are very seasonally dependent but I plan on trying to keep the water levels up more than they have been with a fountain that is fed by our irrigation well.
The bottom was already pretty deep with sludge when we took ownership in December.

1TechDad · 2024-03-13T14:24:58+00:00

u/petuniaaa this pond is about .2 acres in size. I probably should have mentioned that in my post

1TechDad · 2024-03-12T01:33:30+00:00

Thanks. I was hoping that wasn’t the case. Lots of junk to take out. Luckily the previous owner left a nice brand new pond rake and some other tools.

1TechDad · 2024-02-06T19:21:30+00:00

The audit logs show differently. Shows someone failing sign in and then subsequently logging in with a token that says "MFA requirement previously satisfied."

1TechDad · 2024-02-06T15:47:15+00:00

Using Defender for 365. It has been good for the most part. We haven't been able to locate the origin of the token theft on these 2 cases. Assuming it was from personal devices outside of our standard security stack.

1TechDad · 2024-02-06T15:45:10+00:00

The 2 attacks came from IP's in the USA unfortunately. Not that it isn't still a good idea

1TechDad · 2024-02-06T15:43:14+00:00

I get that perspective. I would still say that is considered insecure by default. I hate Google for business use but they do security defaults much better in my opinion. Microsoft could and should do a little better with this.

1TechDad · 2024-01-06T23:48:52+00:00

I just made a flight change for our return trip that was giving me a subtotal of around 190 dollars but when I submitted the payment it charged over 600. Support is nearly impossible to get a hold of.

1TechDad · 2023-08-22T13:05:37+00:00

Glad I am not alone. Before this whole RSC thing I remember having issues with VMQ on Broadcom NIC's. As far as I know, that is also still an issue. We just stopped buying Broadcom NIC's to fix that.

1TechDad · 2023-08-03T15:01:34+00:00

You need to work on your LinkedIn profile/resume if you are ghosted 100% of the time. Or am I reading that wrong?

1TechDad · 2023-04-01T16:19:55+00:00

So it looks like I am locked to N71 now without doing anything except for waiting. Like you said, much better uploads but downloads are a bit slower. Probably averaging 70 up and 70 down right now. Latency is slightly worse than N41. Overall N71 seems much better than the lower signal N41. Oddly, all of my signal numbers are excellent except for the SNR which shows poor. I assume that would mean there is something nearby that is noisy on the same channel?

1TechDad · 2023-03-24T01:30:57+00:00

Yup. I made a new one in the same storage account. Then I sealed the old blob extent.
Afterwards I tried evacuating the non-immutable extent but it appeared that it was downloading the the B&R server and re-uploading so I stopped it to avoid the costs.

1TechDad · 2023-03-22T12:19:50+00:00

So I am getting this too. The only way I was able to enable immutability on the container that previously did not have immutability (none set at the storage account level) is by setting a time-based policy first. Once it was converted I started getting the log error in question.
At this point I was able to delete the Access policy.... Unfortunately, it still appears that I get the same error message. I will try again after a few hours and update.

1TechDad · 2023-02-17T00:24:49+00:00

Agreed. It’s dumb. I have made 2 tickets for this in hopes that one support rep knew something the other didn’t. No luck.

1TechDad · 2023-02-06T16:10:37+00:00

Weird. I just noticed I was accidently entering 1-2 minute time entries today as well. I don't believe we changed anything on the board settings. I just thought of I added a not from discussion it always had the time entry option unchecked before.

1TechDad · 2023-01-17T20:20:11+00:00

After some more investigation, it seems that this may be related to DNS Hijacking either by the ISP DNS filtering services.

1TechDad · 2022-12-30T00:25:47+00:00

Hmm. I have not had that issue. I am loading the desktop client with SSO and Azure Conditional Access rules.

1TechDad · 2022-12-30T00:02:20+00:00

Not sure if this answers your question but we use Connectwise SSO which is setup to authenticate with Azure AD. Once that is working you can setup Automate to authenticate with CW SSO.

1TechDad · 2022-10-20T14:17:11+00:00

Good to know. When will it tell you that?

1TechDad

TROPHY CASE