Scheduled Report Issues

I think, if I remember correctly, that the new parameters take effect on the next scheduled run of a report. For example, on that daily report you changed to run at 10:30AM instead of 11AM, it would run as requested on Wednesday, instead of Tuesday because the existent parameters where already in use for the next morning. From what I can garner, you’d have to totally delete the scheduled report and rebuild it for it to take effect immediately.

I may be incorrect in my summation, but I’m pretty sure this is what was communicated to me from someone who is a Network staff member.

Chris

Christopher Cuhel | Database Coordinator

The 5th Avenue Theatre

1308 5th Avenue Theatre, Seattle WA  98101

p 206.971.7916 f 206.292.9610

Seattle's Acclaimed Non-Profit Musical Theater Company

Website |  Facebook |  Twitter |  Youtube

Does anyone else ever find that if you update either parameters or the schedule of a scheduled report that the schedule doesn't acknowledge the update and you have re-schedule the report?

On Monday, I changed an existing scheduled report to run at 10:30am instead of 11am. This is a daily report and I expected the report to run on Tuesday at 10:30am. It ran at the old time of 11am.  The schedule shows the time to run at 10:30, but it seems there's a hiccup somewhere.  The same thing happened again today when I changed some parameters on a different scheduled report, the new parameters were not included.

I've also had this happen in the past to existing schedules where we add someone to the list of emails the report goes out to.  The report still goes out, but not to the additional person we added.

Michele

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Awesome Nick, thank you so much.

So, based on your post in the other thread, if we wanted to push changes to a monthly scheduled report immediately, could we simply delete the entry marked ‘s’ in GOOESOFT_SCHEDULE_QUEUE and it would then re-schedule itself with our changes indicated?

From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Nick Reilingh
Sent: Wednesday, July 29, 2015 5:43 PM
To: Michele Keutsch
Subject: Re: [Tessitura Ticketing Forum] Scheduled Report Issues

We've discussed this in part on the Technical forum -- see my post in this thread: http://www.tessituranetwork.com/Community/forums/t/12115.aspx

As far as the schedule changes go, you really do have to get this right the first time, or end up recreating the schedule. But for changes to email settings (which typically also takes one cycle before updating), it is a bit easier to manage. I wrote a script that updates scheduled request_ids with the current "master" email settings for a given schedule_id. I haven't built it into a utility yet because I'm the only one scheduling reports for the most part, but if you have a SQL person it's pretty easy to use -- just run as-is or replace the @schedule_id with the ID of the schedule you want to update, if you want to be a bit more surgical about it:

DECLARE @schedule_id int = null;

 UPDATE r

 SET r.email_recipients = m.email_recipients,

 r.email_subject = m.email_subject,

 r.email_body = m.email_body

 FROM gooesoft_report_schedule s

 INNER JOIN gooesoft_request m

 ON s.request_id = m.id

 INNER JOIN gooesoft_schedule_queue q

 ON s.id = q.schedule_id

 INNER JOIN gooesoft_request r

 ON q.request_id = r.id AND q.status = 's'

 WHERE (r.email_recipients <> m.email_recipients

 OR r.email_subject <> m.email_subject

 OR r.email_body <> m.email_body)

 AND (ISNULL(@schedule_id, '') = '' OR s.id = @schedule_id)