Hello,
One of my power users is leaving at the end of the month and owns a fair number of reports that will need to continue after their credentials are inactivated. Is it possible to transfer ownership of a report schedule to another user or does the report simply have to be rebuilt?
Perhaps someone has a creative way for handling scheduled reports in the interest of business continuity when dealing with staff turn over!
Thanks!
Tim,
There are SQL ways to accomplish your first paragraph, but I have never done that before, so I will leave that to those who have to comment on the best way to accomplish that.
Regarding the second part to your question, per PCI compliance, you cannot have a user that is shared between active users, and they leave you are not going to want to have James Anderson login using John Smith's "jsmith" login information (plus that is just not the best idea in general). However, at our organization we created an additional login whose access is specifically limited to scheduling reports with general login information like "repsched" and a reports scheduling user group. When that staff member then leaves, that user is then given to the new staff member in addition to their regular user thus allowing the reports to transfer without affecting PCI compliance (I think, if I am wrong, someone let me know). They do have to File\Relogin when they want to schedule a report, but that is a small price to pay, and you get used to it pretty quickly.
Of course... this solution only works well if you have a limited number of people who schedule reports. If you have a lot of people who schedule reports, this would become a more difficult solution.
John
Hi Tim - yes, I have done that before with some SQL code. I'll try to find the code I use and get that to you.
Thanks John! I was not exactly clear where the PCI compliance line falls in regards to something like this. I will think further on using a separate login going forward but, since we are on RAMP and they will be moving to single login using our unique RAMP user credentials this may not be feasible long term.
David,
That would be amazing! I stumbled across another thread but the code there doesn't seem to make updates where I am expecting them.
It may not in the long run, no, but who knows? You might want to ask someone at RAMP/Tessitura about that, though, as I believe there will still be ways to relogin to different user groups for those who have access to more than one, so it would make sense for them to be able to log in as a second user if they had that, too. At least, that is how my mind thinks of it.
Hi Tim,
Here's what I use to change owner schedules, I've used it a couple times with success. It's based off old forum posts and edited just a bit.
declare @newowner char(8) = 'cbauer', --set as userid @usergroup char(8) = 'DEV', --UG_id @scheduleid int = 124 --id of schedule, visible in Tess
update gooesoft_requestset user_id = @newowner, ug_id = @usergroupwhere id=(select request_id from gooesoft_report_schedule where id=@scheduleid)
Hi Tim - it looks like Dorothy and Brian posted code that updates gooesoft_request. This is similar to what we do and should work.
Thanks everyone! This is perfect and will definitely get me where I need to be.