Take the 2-minute tour ×
Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It's 100% free, no registration required.

Feel like I am missing the point of Field History Tracking.

Before going any further, here are the Salesforce Limits from the Salesforce Limits Quick Reference Guide date June 2, 2014:

Edition (Fields per object, Field History Tracking per object)

  • Developer (500, 20)
  • Unlimited and Performance (800, 20)
  • Enterprise (500, 20)
  • Professional (100, 20)
  • Group (100, 20)
  • Contact Manager (25, 20)
  • Personal (5, NA)

And here are all the help pages I'm able to find too:

Reviewing the main "idea" page requesting 20 field limit be increased, one user comments:

If you open a case with support, you can get this increased!

Appears that the common increase stated was only to 50, which is more than double the current amount, but still seems like a small amount if you've got 500-800 fields.

Is this the only solution, and if so, are there any third party products or solutions that are free and exceed these limits?

Seems to me that this limit should at the very least be in total, not per object, since currently, if that was the case I'd have more than enough; meaning on the Enterprise version, with the 200 custom objects with 20 tracking fields per object, that would be 4,000 fields being track, yet I have zero plans to create 200 custom objects; the Unlimited and Performance Editions get 2,000 custom objects with 20 tracking fields per object, that would be 40,000 fields being track.

Seems backwards to me, and unable to see a solution without a hack like having a shadow fields that are concatenations, shadow objects with 20 fields per object, asking for a bump to 50 fields via the support request, or using a third-party/custom solution off platform.

Any suggestions, or an I missing the point of field tracking?

share|improve this question

1 Answer 1

up vote 11 down vote accepted

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) {
List<Schema.FieldSetMember> trackedFields =     SObjectType.Account.FieldSets.HistoryTracking.getFields();
if (trackedFields.isEmpty()) return;

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

 List<string> apiNameList = new List<string>();        

for (Account aNew : trigger.new) {

Account aOld = trigger.oldmap.get(aNew.Id);

for (Schema.FieldSetMember fsm : trackedFields) {

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

if (aNew.get(fieldName) != aOld.get(fieldName)) {

String oldValue = String.valueOf(aOld.get(fieldName));
String newValue = String.valueOf(aNew.get(fieldName));
if (oldValue != null && oldValue.length()>255) oldValue = oldValue.substring(0,255);
 if (newValue != null && newValue.length()>255) newValue = newValue.substring(0,255); 

 AccountHistoryTracking__c aht = new AccountHistoryTracking__c();
aht.name         = fieldLabel;
aht.apiName__c   = fieldName;
aht.User__c      = aNew.Id;
aht.ChangedBy__c = UserInfo.getUserId();
aht.OldValue__c  = oldValue;
 aht.NewValue__c  = newValue;

if (!fieldChanges.isEmpty()) {
 insert fieldChanges;
share|improve this answer
Thank you, that's awesome, and able to confirm it works as promised! (In case it's not clear, very happy this issue is now resolved.) –  blunders Jun 9 '14 at 13:20
In case it is of use to anyone, here's how I deployed the trigger; note this deployment was to contacts, not accounts, but the code above works fine, only changes I made was to manually replace "account" references in the code to "contact" where needed. Also, the custom fields I added were, name, apiName, User, ChangedBy, OldValue, NewValue; note: if the fields are marked as required, the code won't work. Lastly, in the code I changed aht.name to aht.name__c before loading it to production via the progress I linked to above. –  blunders Jun 9 '14 at 13:37
I have to track deletions here also. Can someone suggest any way out? –  SFDC_GEEK Sep 10 '14 at 10:56

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.