• Replies 7 replies
  • Subscribers 415 subscribers
  • Views 290 views
  • Users 0 members are here
Related

Scheduled Report Issues

Michele Keutsch
$organization

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

Parents
  • $organization

    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 at my organization 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 --request
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 --master
		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)

     



    [edited by: Nick Reilingh at 5:49 PM (GMT -6) on 29 Jul 2015]
Reply
  • $organization

    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 at my organization 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 --request
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 --master
		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)

     



    [edited by: Nick Reilingh at 5:49 PM (GMT -6) on 29 Jul 2015]
Children