A new field is being created on a custom object. However, the app builder does not want the field to up on pre-existing custom report Types. What should the app builder do on the custom field setup to fulfill this requirement?
The correct answer is D. Deselect auto add to custom report type.
When creating a new custom field, Salesforce provides an Auto Add option that can automatically add the new field to applicable existing custom report types. If the app builder does not want the new field to appear on pre-existing custom report types, they should deselect the Auto add to custom report type option during field creation. Salesforce release documentation confirms that Auto Add automatically adds custom fields to custom report types based on that object.
Why the other options are incorrect:
Removing the field from page layouts only affects record-page visibility, not report type availability.
Changing profile visibility or read-only access affects field security, not whether the field is added to the custom report type layout.
===========
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit