An app builder wants to create a formula field on an Account to include data from related Contacts but is unable to find the relationship in the formula editor.
What is a limitation of formulas that could be causing the issue?
The app builder wants to create a formula field on an Account to include data from related Contacts but cannot find the relationship in the formula editor. This limitation occurs because formula fields in Salesforce cannot reference child records directly.
Option A (Unable to reference the child records): In Salesforce, formula fields can reference parent objects but not child objects. In this case, Contacts are child records of Accounts in a lookup relationship, and Account is the parent. This is why the formula editor does not provide access to the child records (Contacts) from the Account.
Option B (A master-detail relationship should be created): While master-detail relationships allow for roll-up summaries, creating a master-detail relationship is not applicable here since the standard Account-Contact relationship is a lookup, and changing it to master-detail is not possible.
Option C (Formula field limit reached on the Account object): This would limit the number of formulas but is not the root cause of the issue described.
Option D (More than 5,000 characters in the formula): This limit refers to formula field complexity, but it does not explain the inability to reference child records.
In summary, the limitation is due to Salesforce not allowing formula fields to reference child records.
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.
An app Builder creates an Account validation rule on the Industry field that will throw an error if the length of the field is longer than 6 characters. Another App Builder creates a workflow rule with a field update that sets the Industry field to Technology whenever the Billing City field is set to San Francisco. What will happen the next time a sales person saves an Account with a Billing City of San Francisco?
The record will not save and the validation rule's error message will be displayed because the field update will violate the validation rule. The validation rule will prevent the record from being saved if the Industry field is longer than 6 characters, and Technology is 10 characters long.
The CRM Manager at Universal Containers has requested that a custom text field be converted to a picklist in order to promote better data hygiene. What needs to be considered before changing the field type? Choose 2 answers
Northern Trail Outfitters (NTO) has created the custom objects Trail and Park in Salesforce to track trails and parks respectively. NTO wants to
track the total number of trails a park has on the park record without writing any code.
Which two actions should an app builder take to accomplish this requirement?
Choose 2 answers
To track the total number of trails associated with a park without writing code, the correct actions to take are:
Use a roll-up summary field on the Park record to show the total number of Trails (B). Roll-up summary fields calculate and display a value in a master record based on the values of fields in a detail record. They are used to count, sum, average, or get the minimum/maximum of values in related detail records.
Use a master-detail relationship between the Park and Trail objects (C). Master-detail relationships are necessary for roll-up summary fields as they allow the master object to control certain behaviors of the detail object and summarize data from those detail records.
A formula field (A) cannot dynamically count related records unless those records are linked via a master-detail relationship, and it cannot alone handle counts across related records without such a relationship. A lookup relationship (D) does not support roll-up summaries unless combined with additional tools like triggers or third-party apps, which involve coding or extra configuration outside standard object setup.
For more details, refer to the Salesforce Help documentation on master-detail relationships and roll-up summary fields:
