Admin User - 1 month ago
Using the Analytics API enhancements of Winter 20’ we were able to build an app that helps us manage how many subscriptions each user has. While it doesn’t increase the subscription limit, it helped us transition a few of our heavier users back to classic report schedules and vice versa.
We’re not sure if/when Salesforce will increase the number of subscriptions per org. In the meantime, we’ve made the app available on our website as a free trial and the AppExchange as a paid listing. Both versions are nearly identical, with the free version having a limit to how many times you can refresh your data. If you have any issues getting the app to work, please reach out.
Try the app: https://appwafer.com/
View our AppExchange Listing: https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3A00000FAgN6UAL
Jess Jakobovic - 1 month ago
Jim Fehrman Here is my work around for Lightning adoption. Use Lightning for everything and just go back to Classic to "Schedule Future Runs..." when needed. Hopefully users will see the benefits gained in Lightning but then can still go back to Classic for the few features not yet in Lightning.
Jim Fehrman - 1 month ago
Thank you for this explanation @Jess Jakobovic. This helps in understanding the difference between subscribing and Scheduling future runs. I have folks working in Classic and attempting to get them to move to Lightning. It's unfortunate that Classic tools (i.e. Schedule Future Runs) are not moved to Lightning. This makes buy-in more difficult.
Jess Jakobovic - 1 month ago
Aquilas Lim There have always been limits on reports in both Classic & Lightning like there are limits throughout Salesforce on numbers of fields and other processes. These are all so data doesn't overwhelm their system and shut it down. The same 5 report limit per user applies in Classic as in Lightning when using the "Subscribe" feature. When using the "Schedule Future Runs..." feature, which exists only in Classic and not in Lightning, the limits are organization wide. For those you who think you have unlimited reports in Classic, you actually don't. You just work for a large enough organization that you haven't hit your org limits yet. As someone that works for a smaller company, I can assure you there are limits because we have hit them hard. Once they are used up, they are used up for everyone. The disadvantage to "Schedule Future Runs..." versus subscribe is that you can't set conditons with "Schedule Future Runs..."
It sounds like they are thinking about doing something similar to the org limits on "Schedule Future Runs..." in Classic, in Lightning. Why that wasn't something that was incorporated into Lightning from the beginning, I have no idea.
Tricia McGuire - 2 months ago
@Anusha Surepeddi Just to clarify...so as an Admin, if I am tasked with making many reports to go out to many users I must log in as each different user, change to the Classic UI I am totally unfamilair with (we went live in Lightning just two months ago) schedule a report as someone else, and then lose total visibility to the fact that it has been scheduled because I can't report on it? Or I can beg each of my senior executive to users to log in and subscribe to a report themselves, or attempt to train them to schedule reports in a UI they have never seen before, and then have zero visibility to who has scheduled or subscribed to what when they call with issues and expect me to troubleshoot?
I prefer the idea of a large number of subscriptions or scheduled items pe rorg, allocated by the Admin. Users rarely have the will or know how to manage these themselves and when they fail, Admin have to fix them anyway.