You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: It would be nice if there was an option to pull field-level reporting and see which fields are not being utilized or underutilized.
Describe the solution you'd like
It would be nice if, under the Developer Tools or Deploy Metadata/Compare, there was an option to pull a Field Usage report for any given object.
It would be really awesome if you could compare between two Orgs and be able to have it tell you from both sides which fields are not being utilized. This would be especially helpful for when you're trying to do Org merges and need to help drive decisions around what should be kept or what can be deprecated.
The text was updated successfully, but these errors were encountered:
@dagamier - thanks you for the ticket.
Salesforce doesn't provide great tools to be able to achieve this without downloading all the metadata in the org and inspect it, which isn't reasonable with the way Jetstream is currently architected.
Salesforce does have the dependency API but unfortunately this only works custom metadata, so there is no way to see field dependencies when they are used with other custom objects so it ends up making the data pretty much useless because it is such a part of the full picture.
I will leve the ticket open as a good idea in case something becomes available in a future SFDC release
Description: It would be nice if there was an option to pull field-level reporting and see which fields are not being utilized or underutilized.
Describe the solution you'd like
It would be nice if, under the Developer Tools or Deploy Metadata/Compare, there was an option to pull a Field Usage report for any given object.
It would be really awesome if you could compare between two Orgs and be able to have it tell you from both sides which fields are not being utilized. This would be especially helpful for when you're trying to do Org merges and need to help drive decisions around what should be kept or what can be deprecated.
The text was updated successfully, but these errors were encountered: