HaloPsa Macros (2)
| Name | Description | Restriction | Compatibility | |
|---|---|---|---|---|
[HaloPsa.Connection:] |
Specifies a HaloPsa Connection. Specifies a HaloPsa Connection to use for the remainder of the report. Unless you are reporting on more than one HaloPsa system, you should not include a [HaloPsa.Connection:] macro in your report. Instead, create a Macro Parameter Default. |
|||
[HaloPsa.List:] |
Retrieves a list of items from HaloPSA. Retrieves a list of items from HaloPSA using the specified endpoint type, and outputs a JArray. With Tickets, the ticket parameters filter the tickets in HaloPSA itself and every page is returned, up to 10,000 tickets; above that the macro fails and asks for a narrower filter rather than returning part of the result. Each ticket is a JObject with HaloPSA's own field names, for example id, summary, status_name, priority_name, tickettype_name, client_name, site_name, user_name, agent_name, team, category_1, dateoccurred, lastupdate, dateclosed and customfields, plus the SLA fields (such as fixbydate, respondbydate, slastate) and timetaken. Dates are UTC, as everywhere in ReportMagic. The ticket parameters can only be used with Type=Tickets. |