An app builder just added a lookup field to Account from the existing custom object, Box.
Which report type is automatically created?
Upon adding a lookup field to Account from a custom object, Box:
D . Accounts with Boxes. Salesforce automatically creates a new report type that reflects the relationship from the perspective of the parent object, in this case, Accounts, showing related Box records.
This new report type enables users to create reports that list Accounts along with their associated Boxes, if any.
An app builder wants to create a custom object and 10 fields.
What should they use to create the object, fields, and relationships quickly from one place?
To create a custom object along with multiple fields and relationships efficiently from a single interface, the Schema Builder is the ideal tool:
A . Schema Builder. This graphical tool provides a drag-and-drop interface for creating and modifying objects and fields in Salesforce, allowing for a visual layout of database schema.
Steps to use Schema Builder:
Go to Setup Schema Builder.
Drag the 'Object' element into the schema area to create a new custom object.
Define the object's properties (e.g., label, API name).
Drag field elements like Text, Number, or Lookup into the object to create fields.
Configure each field's properties according to your requirements.
Connect objects via lookup or master-detail relationships by dragging the relationship fields between them.
Save the layout to create all elements in Salesforce.
For more information, review Salesforce's Schema Builder documentation.
Universal Container's sales reps can modify fields on an opportunity until it is closed.
The sales operations team has access to modify the Post-Close Follow-up Date and Post-Close Follow-up Comments fields after the opportunity is closed. After the
opportunity is closed, the rest of the fields are read only.
How should these requirements be met?
To manage field editability based on the opportunity status:
C . Use field-level security on page layouts with record types to restrict editing fields. This combination allows for different layouts and editable fields based on the status of the record (e.g., closed or open).
Steps to implement:
Create or adjust record types for open and closed opportunities.
For each record type, create a specific page layout.
On the page layout for closed opportunities, set the majority of fields to read-only using field-level security, except for the 'Post-Close Follow-up Date' and 'Post-Close Follow-up Comments' fields.
Assign the appropriate page layouts to the respective record types.
Update profiles or permission sets to use these record types and page layouts accordingly.
This setup ensures that sales reps can modify fields only when the opportunity is open, and the sales operations team can edit specific fields after closure.
Ursa Major Solar (UMS) uses Cases to track customer complaints, an Issue__c object to represent known problems with its solar panels, and a
Case_Issue__c junction object to relate known problems to customer complaints.
Periodically, UMS conducts audits which require the auditing users to view Case _Issue__c records.
Which access levels must be configured to allow UMS users to access Case _Issue_c records?
To ensure auditing users can access records in the Case_Issue__c junction object, the correct data permissions on related records must be established:
D . Read-Only access on Case and Issue__c. Users need read-only access to both Case and Issue__c objects to view associated Case_Issue__c junction object records properly. This is because access to junction object records in Salesforce is determined by the user's access levels to the parent records in a relationship.
Steps to configure access:
Navigate to Setup Profiles or Permission Sets.
Select the profile or permission set of the auditing users.
Under Object Settings, adjust the permissions for Case and Issue__c to at least 'Read-Only'.
Ensure that users have visibility to the Case_Issue__c object itself.
This configuration allows users to view the details of cases and issues as they audit the junction object records.
Which two features can be used to allow users to access Flows?
Choose 2 answers
To allow users access to Flows, Salesforce offers multiple integration points:
A . Quick Action: Flows can be initiated from record pages, the app utility bar, or global actions using Quick Actions. This allows users to execute flows relevant to specific records or global processes.
C . Flow Launcher: A component available in Lightning App Builder that enables users to start flows directly from a Lightning page.
Steps to set up these features:
For Quick Actions, navigate to Setup Object Manager select object Buttons, Links, and Actions New Action Action Type (Flow).
For Flow Launcher, navigate to Lightning App Builder select the page drag the Flow component to the desired section of the page configure it to launch the specific flow.
For more information on integrating Flows, check the Salesforce documentation on Flow Distribution.
Barrie
6 days agoDaniela
18 days agoLai
21 days agoHubert
1 months agoChrista
2 months agoEmmanuel
2 months agoXuan
2 months agoSusana
3 months agoMillie
3 months agoArlean
3 months agoLavonna
3 months agoLaura
3 months agoElke
4 months agoAgustin
4 months agoMerlyn
5 months agoVivienne
5 months agoRenea
5 months agoPercy
6 months agoAudry
6 months agoDion
6 months agoFletcher
6 months agoMalissa
6 months ago