Help & Support
Elevate Your Agents with AgentExchange Solutions
Easily enhance Agentforce with pre-built AI solutions from AgentExchange. Browse, install, and deploy agents, actions, and apps directly into your environment. Tell Me More
Have Questions?
Enhanced Field History Tracking
Supercharge Salesforce OOTB Field History Tracking
- Industries
- EnergyFinancial ServicesHealthcare & Life Sciences
- Business Need
- ProductivityIT & AdministrationAnalytics
- Requires
- None
- Compatible With
- Sales CloudService CloudHealth Cloud
Track more data types, including Rich Text, Long Text Areas, etc. Enjoy searchable & sortable history with flexible activation through Flows or Apex triggers. Use your own custom history object for tailored tracking solutions with UI provided
Rating
Reputation
MVP
Recognized by Salesforce for their leadership, expertise, and generosity
Top Reviewer
Contribute reviews that encourage conversation and help others make informed decisions
Ranger
Lifelong learners who have earned the Ranger rank or higher on Trailhead
Showing 10 of 19 Reviews
Wont log for non-admins
Cannot for the life of me get it to log for non-admin users. Have added the permission set, have even added the apex classes and all objects to the base user profile and nothing gets me there. Logs errors saying Object or Field Access Issue in EnhancedFieldHistoryDomain.getAuditConfig Logging as an admin works just fine. Flat out refuses to log as a standard user.
Good app for history of fields
I like it vey good app!
App works great except for few glitches
1) In addition to permission sets provided, we had to explicitly add permissions for certain objects not listed in documentation. 2) Attempt to de-reference error probably due to field deletion but there is no troubleshooting steps in document. Please add steps for troubleshooting and setting up new users.
Great tool, with a couple of "howevers" hence the 4*
However 1 - the documentation could be improved. There does not seem to be a record triggered flow to "update" when setting up from scratch, so the Add / Update the object triggered flow was a bit of a red herring, unless I missed something - but I ha to create the flow However 2 - at first I created the flow on "Update" and everything worked. However I have since tried it on create or update (according to GPT the code in the APEX does not cater for 'oldRec' not existing when creating a new record) so I think the documentation should be specific in what type of flow should be created
Cart Item Object
Is it possible to track changes to CartItem fields? Does the app support this object?
Does this track user object history
Does this app allow you to track field history changes on the user object?
works on Experience Cloud too
I needed to add access rights to a bunch of objects incl. 'Field Configurations', but it worked on Experience Cloud as well.
Does not work with AccountPlan object
This was pretty easy to set up, but I just noticed it does not work with the Standard AccountPlan object. Will this have support for this standard object soon?
Data Retention
How many years of data history can this package store? Is it the same as Salesforce's data retention period of 18–24 months?
Good, but lacks polish
It seems OKish at first, but then there are some weird design choices and lack of polish: 1) It would be much better if we could track and deploy Field Configuration as custom metadata, instead of custom object. 2) Tracking is enabled automatically to all fields, and we have to disable it, where it would make more sense to have explicit selection of fields to track. 3) Documentation could use some clarity on the Flow Actions - there are 2 actions with no user-friendly labels or help texts, you don't know what it asks for in "action" input. 4) Enhanced Field History tracking component does not show out of the box field history tracking, so we need 2 related lists on a page. Also, it doesn't follow SLDS, doesn't the same styling as standard related lists 5) Provided permission set for users do not have permission to create Field History records, so it doesn't work in Flows 6) Bug Form is not published....
User must have EnhancedFieldHistoryUser permission set assigned, then in flow Action = EFH__API_EnhancedFieldHistoryTrackRec Object for NewRec = Case Object for oldRec = Case newRec = Triggering Case objName = Case oldRec = Prior Values of Triggering Case and then you have to add their custom history view on page layout
Can perhaps update the rating to reflect the actual capabilities of the app.