The administrator at Cloud Kicks is evaluating the capabilities of Schema Builder to create custom objects and custom fields. The administrator likes the user interface of the Schema Builder, as opposed to the new object and field wizards, but also notices some limitations.
What needs to be configured from the object manager instead of Schema Builder?
Correct Answer: A
While the Schema Builder is a powerful tool in Salesforce for visually creating and managing custom objects and fields, there are certain configurations that must be done in Object Manager rather than Schema Builder.
One of these configurations is enabling field history tracking.
* Field History Tracking:
* Field history tracking cannot be configured directly within Schema Builder. This setting must be enabled from within the Object Manager, where administrators can specify which fields on an object should have their changes tracked.
* Enabling field history tracking involves navigating to the object in Object Manager, accessing the field history tracking settings, and selecting specific fields to track.
* Limitations of Schema Builder:
* Schema Builder is useful for quickly creating custom objects, relationships, and fields, but it does not support all configurations, such as enabling field history tracking, defining object-level permissions, or setting advanced object configurations.
* For these types of configurations, administrators need to return to Object Manager where these settings are available.
Incorrect options:
* Add custom fields to the page layout: This task is typically done within Object Manager, but Schema Builder does allow customization of page layouts to a certain extent through drag-and-drop.
* Make available for Customer Portal: Schema Builder does not control portal availability; however, this is managed through Object Manager settings related to record visibility for portal users.
* Allow Reports and Activities: This setting can be configured in Schema Builder when initially creating an object, but further refinements and permission settings must often be done in Object Manager.
In conclusion, enabling field history tracking requires access to the Object Manager, as it cannot be configured through Schema Builder.
Reference: According to Salesforce documentation, certain object and field configurations, such as field history tracking, are only accessible through Object Manager and not through Schema Builder
Recent Comments (The most recent comments are at the top.)
Correct:
C. Enable field history tracking