Scorecard History Tracking Using TONS of SFDC Storage
None
We are currently tracking the history of changes to our Scorecards. This is very important to us since we have a couple Scorecards that are updated manually and we want to know who the last person was to make the update and when. However, enabling scorecard history uses a MASSIVE amount of SFDC storage. Over 6 months with 7 Scorecards and 2,500 customers, the Scorecard history used 4GB of SFDC data. Salesforce charges a ridiculous $3,000/GB/year for storage! So in 6 months we racked up an additional $12,000 in recurring annual fees with Salesforce.
We changed the history tracking down to 48 hours instead of 12 hours, but that still puts us at 2GB/year -- $6,000/year in additional SFDC storage costs. We are also rapidly expanding our customer base, which going to make this number grow even more.
The feature request here is to allow history tracking with time periods greater than 48 hours. This could substantially cut down on data usage. We would be fine with tracking the person who last updated a scorecard and a timestamp on a weekly or even biweekly basis. That would bring SFDC storage costs down to a more reasonable level and give us the visibility we need. Thanks in advance for your consideration!
We changed the history tracking down to 48 hours instead of 12 hours, but that still puts us at 2GB/year -- $6,000/year in additional SFDC storage costs. We are also rapidly expanding our customer base, which going to make this number grow even more.
The feature request here is to allow history tracking with time periods greater than 48 hours. This could substantially cut down on data usage. We would be fine with tracking the person who last updated a scorecard and a timestamp on a weekly or even biweekly basis. That would bring SFDC storage costs down to a more reasonable level and give us the visibility we need. Thanks in advance for your consideration!
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.
For the cheapest option available, you could use a data client like DemandTools or dataloader.io (there's a limited free version of this) to setup 2 separate routines: 1) an Export of the field history for that particular day/week 2) a routine that takes those ID's and then deletes them from your SFDC history table. That way you're essentially offloading the data storage to another place. However, although this is a great cheap method - this approach stores the data in csv files typically - so it makes it harder to trudge through the data if you want to know which Scorecard got changed, by who, and when.
Could you please help me with answers for the following questions so that we have a through understanding of the situation at hand?
Sumesh
The manual scores are only updated once every 2-4 weeks and only for about half of our accounts. The scorecard history is in our 360 views and account widget. We have a ton of reports with Scorecard data as well.
Josh
I've sent you an email in regards to this post. Kindly respond.
Thanks,
Sumesh
Thanks,
Scott
Just to confirm, you're utilizing the scorecard history on the Customer 360 page, right? If so, then the box you need to check is the "Load Snapshot to Engagement Every Week" box (this writes records to the Usage Data object in Gainsight).
The Enable History Tracking box can be unchecked. It does not write historical values, but rather writes records to the Scorecard History object (this data is not used for trending historical data that you see on the Customer 360 graph).
Let me know if you have any questions.
Scott