Ursa Major Solar uses the custom object Product Development to track Ideas R&D is wording on. A former administrator added the custom object Potential Name with a lookup to Product Development to allow R&D to track names under consideration for those product. The R&D manager recently ran a record and noticed several potential names where the relationship to the Product Development record was missing. The current administrator needs to change this relationship to master detail to ensure a potential name only exists when there is product development.
Which two options are available for altering the existing Potential Name records for the deployment of this change to be successful?
Choose 2 answers
Move any Potential Name records with blank lookup fields to the recycle bin or assign any Potential Name records with blank lookup fields to an existing record from Product Development are two options available for altering the existing Potential Name records for the deployment of this change to be successful. Changing a lookup relationship to a master-detail relationship requires that all child records have a parent record. Therefore, any Potential Name records that have blank lookup fields to Product Development need to be either deleted or assigned to a valid Product Development record before changing the relationship type
An administrator has been tasked with sending an email notification to all project team members when project status is changed to Allocated. Project teams contain users from different departments and different roles.
How should an administrator ensure the proper users will receive the email?
Public groups let you share records with a set of users defined by criteria such as role, profile, or individual users. You can use public groups as recipients for email alerts in workflow rules or process builder. Reference: https://trailhead.salesforce.com/en/content/learn/modules/administration_essentials_for_new_admins_in_lightning_experience/administration_essentials_for_new_admins_in_lightning_experience_security_sharing
Ursa Major Solar (UMS) wants to identify customers that need to install a new solar panel monitor system it recently released. UMS tracks the installed products as Asset records that art related to the Account. Sales management has asked the administrator to create a report for users.
What is the recommended method for the administrator to meet the requirement?
A cross filter with WITHOUT logic is a method for creating a report that shows accounts that are missing certain related records. A cross filter is a filter that lets you include or exclude records in your report based on related objects and their fields. You can use cross filters to create reports on accounts with or without opportunities, contacts, cases, or other related objects. In this case, you can use a cross filter with WITHOUT logic to show accounts without assets that have a certain product name or code. This way, you can identify customers that need to install a new solar panel monitor system. Reference: https://help.salesforce.com/s/articleView?id=sf.reports_cross_filters.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.reports_examples_cross_filters.htm&type=5
The administrator at Cloud Kicks recently replaced several case workflow rules with a single before save flow. Since this change, some cases are routing In unexpected ways.
What could be the cause or the charges to routing?
Multiple automation tools have been used and the automation is executed in a different order. This could cause some cases to route in unexpected ways, because the before save flow might override or conflict with the assignment rules or other automation tools that run after the record is saved. The administrator should review the order of execution and ensure that the flow logic is consistent with the other automation tools. Reference: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger_order.htm&type=5 https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm
What should an administrator use as an alternative to a Process Builder to expedite the time required to update the records?
A before save flow trigger is a type of flow that runs before a record is saved and can update the record without any additional actions or database operations. This can expedite the time required to update the records and improve performance. A before save flow trigger can be used as an alternative to a process builder that updates the same record that triggered it. Reference: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_triggers.htm&type=5
Laura Rodriguez
22 days agoWilliam Wilson
1 month agoJohn Rivera
2 months agoSharon Davis
2 months agoNathan Turner
3 months agoSarah Campbell
3 months agoElizabeth Miller
3 months agoLinda Wright
2 months agoAnthony Scott
2 months agoBrian Miller
2 months agoElroy
4 months agoDalene
4 months agoDanica
4 months agoRaina
4 months agoLaura
5 months agoAllene
5 months agoNgoc
5 months agoKing
5 months agoFernanda
6 months agoKanisha
6 months agoSalena
6 months agoMarguerita
6 months agoAdelina
7 months agoLourdes
7 months agoJeniffer
7 months agoLouann
7 months agoMariko
8 months agoGlen
8 months ago