I have a custom object. I enable Track Activities for this custom object and then I create a managed beta. If this managed beta is installed in a new org, the track activities will be enabled for the custom object.

If this managed beta is taken as an upgrade to an existing org, where the track activities for the same object is disabled it will still be disabled post install.

It is important the track activities is enabled, so I was hoping for a way in which this would be done and the user would not have to worry about doing it manually.

Is there any way it could be done?


  • Post install script? – techtrekker Mar 17 '13 at 13:59

It would seem that the following post would apply to your question: Enable or check Chatter Feed Tracking programatically. As there's also a limit on the number of objects that an organization can track the history on, normally 20 fields/object, I'd think that would be a very good reason for the org to have to enable the tracking (I understand that SF will increase it to between 40 - 50 if asked nicely $$$). The admin may need to choose which objects are going to be tracked and disable tracking on another object in order to support your custom object.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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