[SalesForce] Retention of field history data

Do you know if there is a limit to the amount of data stored when tracking field history?

I know there are a limit of 20 fields per object, but in the limits table, I can't find anything about the actions to log for each fieldhttps://help.salesforce.com/HTViewHelpDoc?id=limits_general.htm&language=en_US

so, do you know if there is any limit? or is something like, the log can be considered a file and enters into the file limits or something?

Best Answer

The word "actions" can mean several things at the moment in the Force.com platform, but I'll take this question to be focused on the retention of actual logged changes made for a given record.

Currently the retention policy for field history is permanent. But this is likely to change in the future.

The first attempt at controlling retention of field history took place about a year ago, where field history was intended to be kept for 18 months. This blanket policy proved too inflexible for many salesforce.com customers, and so the move to implement this was reversed until a more flexible process could be defined.

In Winter 14 a pilot program to allow customers to define specific retention policy for field history changes was begun and is continuing today as per the release notes of Summer 14.

In the Summer 14 release notes the following is stated about this pilot program:

As the first part of a larger data life cycle management initiative, salesforce.com is continuing the pilot that began in Winter '14. Use the Salesforce Metadata API to define a retention policy for your field history. Then use the REST API, SOAP API, and Tooling API to work with your archived data.

There is also a link provided for the pilot implementation guide for any customers who would like to learn more about the pilot.

Related Solutions

[SalesForce] the best workaround for the 20 field history tracking cap

Create an object called AccountHistoryTracking and fields like APIName__c,OldValue__c,NewValue__c then create a fieldset on Account called'HistoryTracking' with the fields you want to track on Account and then write below code to track history on account.This way you don't need to worry about history tracking limit per object.

trigger AccountHistoryTracker on Account (after update) {

    final List<Schema.FieldSetMember> trackedFields = 
        SObjectType.Account.FieldSets.HistoryTracking.getFields();

    if (trackedFields.isEmpty()) return;

    final List<AccountHistoryTracking__c> fieldChanges = 
        new List<AccountHistoryTracking__c>();

    if(!trigger.isUpdate)
        return;

    for (Account newAccount : trigger.new) {

        final Account oldAccount = trigger.oldmap.get(newAccount.Id);

        for (Schema.FieldSetMember fsm : trackedFields) {

            String fieldName  = fsm.getFieldPath();
            String fieldLabel = fsm.getLabel();

            if (newAccount.get(fieldName) == oldAccount.get(fieldName))
                continue;

            String oldValue = String.valueOf(oldAccount.get(fieldName));
            String newValue = String.valueOf(newAccount.get(fieldName));

            if (oldValue != null && oldValue.length()>255) 
                oldValue = oldValue.substring(0,255);

            if (newValue != null && newValue.length()>255) 
                newValue = newValue.substring(0,255); 

            final AccountHistoryTracking__c accountHistory = 
                new AccountHistoryTracking__c();

            accountHistory.name         = fieldLabel;
            accountHistory.apiName__c   = fieldName;
            accountHistory.User__c      = newAccount.Id;
            accountHistory.ChangedBy__c = UserInfo.getUserId();
            accountHistory.OldValue__c  = oldValue;
            accountHistory.NewValue__c  = newValue;

            fieldChanges.add(accountHistory);
        }
    }

    if (!fieldChanges.isEmpty()) {
        insert fieldChanges;
    }
}

Best Answer

Related Solutions

[SalesForce] the best workaround for the 20 field history tracking cap

Related Topic