Custom fields are extremely useful, but they can also clutter and disorganize your Org, with Impact analysis feature this monster can be tamed and brought back to your will, on-demand and without much effort.

Article outline

  • Prerequisites

  • What we report

  • When impact breakdown is shown as "Data not updated"

  • Actions to take

  • You might be also interested in


  • Registered and verified Elements account

  • Sync'd Salesforce Org

  • Permissions to Org Model

What we report

We display the number of custom fields for all types of objects (standard, custom and managed package objects). We additionally break them down by the impact value

  • You can sort the chart alphabetically by object name or by a number of custom fields.

  • You can filter the bar chart by the type of object as well. 

  • You can sort the chart alphabetically by object name or by a number of custom fields. 

  • You can filter the bar chart by the type of object as well. 

The type of object can be seen by the text after the object name. "Standard" is a standard object. "Custom" is a custom object in the core system. If the object is installed by a managed package, then the namespace is displayed after the object name e.g. Batch Log Map. Q9.

When impact breakdown is shown as "Data not updated"

There are a few circumstances when the bar chart for custom field impact breakdown would display some objects in blue for "Data not updated". This occurs when:

  • The object belongs to a managed package: for standard and custom objects in your core Org we fetch % population data automatically on a weekly basis but you need to fetch this data manually for your managed packages. Once you do that the chart will display custom fields' impact breakdown for objects from the updated managed package.

  • New objects get synced from the core Org: the scheduled sync runs on a daily basis, but we update the % population data for all fields in your core org (excluding managed packages) on a weekly basis because this is a massive task that takes a lot of processing power. As such, if you sync any new objects in-between the weekly % population data update, they will appear as not updated. The solution is to either wait until the start of the next week or to fetch the data manually for the affected objects

TIP If you reach your field maximum limits, you cannot add any more fields. You may be able to upgrade your Salesforce Edition to increase field counts, or you can delete fields. Deleting custom fields is tricky and requires some investigative work: has the field got any data? Where is it used: email templates, page layouts, process builder workflows, etc.?

TIP Fortunately, based on the usage, % population & provided documentation we can streamline your evaluation process by highlighting the low impact custom fields which are the primary candidates for clean-up.

TIP If you manually fetch the field % population data for a managed package, you can also see how impactful are its objects. This can help you decide if the package is worth uninstalling. You can then run a report on managed package impact analysis to understand the implications of uninstalling it. 

You might be also interested in

Did this answer your question?