Support Namespaced custom fields and Object in field history tracking#737
Merged
amtrack merged 2 commits intoamtrack:mainfrom Mar 6, 2026
Merged
Support Namespaced custom fields and Object in field history tracking#737amtrack merged 2 commits intoamtrack:mainfrom
amtrack merged 2 commits intoamtrack:mainfrom
Conversation
Owner
|
@jrupesh Is this ready for review? |
Contributor
Author
Yes! |
Owner
|
I'm trying to test this. |
Owner
|
My manual testing failed: Install a managed package from AppExchange (https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3A00000FKArSUAX): sf package install -p 04t0b000001XxRDAA0 --wait 30Create a config file {
"settings": {
"historyTracking": [
{
"objectApiName": "lightningbuddy__Actions__c",
"enableHistoryTracking": true,
"fieldHistoryTracking": [
{
"fieldApiName": "lightningbuddy__Docked_Display__c",
"enableHistoryTracking": true
}
]
}
]
}
}And run: ./bin/run browserforce apply -f history-tracking-namespace.jsonOutput: |
Contributor
Author
Ah understood your approach, You cannot modify the managed package's field history. This implementation is done for handling Custom field added through package for Person Accounts. |
|
🎉 This PR is included in version 6.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request: Support Field History Tracking for Packaged Person Account Fields
Summary
This PR enables Field History Tracking for custom fields on the Contact object that are added via managed packages and surfaced on Person Accounts.
Context & Problem
In Salesforce, when Person Accounts are enabled, the Contact object stores field details:
Changes
This implementation provides the necessary logic to toggle history tracking on for these specific field types originating from the package itself.
Key Enhancements:
Allows the following definitions to enable field history tracking,