Hi everyone,
We did the point update to v15.2.34 last week (we are RAMP/Hosted). Everything looked fine in testing, and as it was "only a service pack update", I didn't really have any qualms about going to Live. Ever since the live update happened, though... users are getting a TON of daily dashboard emails, even if they weren't subbed to them (I have a RIDICULOUS number of them). Support just told me that that's a defect with the upgrade process, that wasn't mentioned ahead of time, and that the onus is on the dashboard owners to check each dash and unsubscribe people. And today, a 3rd party emailed me saying that they were receiving scheduled reports not meant for them. I checked the report schedule, and their email address is not attached to any current schedules. Has anyone else done this service pack update and had it not go smoothly? We've all talked about the many, many issues with v16 update, but I (mistakenly) thought a small service pack update would be smoother...
I feel like this happened to us, but we're only on v15.2.32 currently. Perhaps it happened with the v16 upgrade of our Dev system?
Our DEV system sent out an inordinate number of emails tied to dashboards during the v16 upgrade but my impression from what Kathleen is describing above is that this is different. Or not. Hopefully TN can weigh in here.
Here's that ticket resolution:
This is Yessenia with Tessitura Support - Thank you for reaching out to the Customer Care line to report the "New Shared Dashboard" emails. It was reported that users have received about 24 emails this morning regarding the shared dashboard. Following our call, I found information regarding these emails. This is directly related to your Development environment upgrade to v16 this morning. These emails can be ignored and/or deleted. Our development team believes this issue is related to a defect that causes these emails to send during an upgrade. We're currently working on a fix to prevent this issue from recurring during future upgrades, and you can follow the progress of this defect as DEV-15872 on our defect list in our help system.