Can we update the text in the hover to enable Scorecard History Tracking to clarify that it will consume a lot of SFDC Storage space and can we write an article on GS Go which specifically addresses this feature and identifies what it does and does not do?
Several customers have wracked up huge SFDC storage fees due to activating this feature without understanding the impact and we don't have a document to clarify.
https://community.gainsight.com/gainsight/topics/scorecard-history-tracking-using-tons-of-sfdc-stora...
Scorecard History Tracking - Storage Consumption
None
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Even looking at the post shared I feel like we could find a better custom solution using SFDC's standard field history functionality on our scorecard fact and/or rules & usage table to record daily through rules and comparisons if a field was updated on scorecard fact and create our own "change tracking" table in MDA or another SFDC object much more efficiently without risk of incredibly high SFDC storage.
If we don't have a good use case for this option in our configuration, I think we should remove it from the UI. I've only seen it create major cost issues and confusion for customers over the last year.
We are building a new version of scorecards 2.0 on MDA for the winter release and this functionality as it exists will not be present in the new version. For new customers, the scorecard available will be the new one and we will look at phasing out the feature for existing customers as well.
Thanks
Abhishek S