/build/static/layout/Breadcrumb_cap_w.png

SQL Query Broken in v13

We have long used Custom Ticket Rules to create regularly scheduled tickets. The setup for this is based upon this article: https://www.itninja.com/blog/view/scheduling-ticket-creation. This recommended sql query, for pulling the email address used to submit tickets, is no longer working:

select
"servicedesk" as EMAILCOLUMN

It seems as though directly referencing the email address of a queue is no longer supported. Instead of returning the email address for the queue, it simply returns the word, "servicedesk". Honestly, I'm not sure how this query ever worked; I'm guessing there was some sort of hard-coded variable system that returned the right value?

I've implemented the following query as a workaround:

SELECT HD_QUEUE.Alt_Email_Addr AS EMAILCOLUMN
FROM HD_QUEUE
WHERE Name = "Help Desk"

I'd prefer to use the original method, though, as it is easier to incorporate into more advanced queries, since it doesn't require pulling data from a table (and thus having to join tables).

Anyone have any guesses as to what has changed? Any ideas for a better way to pull the email address for a queue?


0 Comments   [ + ] Show comments

Answers (2)

Posted by: fmello 1 year ago
Posted by: TheNinja 1 year ago
Senior White Belt
0

I reviewed the schema changes, and didn't see anything that would apply in this instance.

After some more digging, I now believe this isn't an SQL issue at all, but an email routing issue. Before, if you tried to send to "servicedesk", as in this example, it would just tack on the email domain (part after the @) and send it through. It's not adding the domain anymore, so you have to specify the entire email address.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ