Salesforce Platform-App-Builder - Salesforce Certified Platform App Builder (SP25)

Roll-up summaries allow MAX, MIN, SUM, COUNT, and AVG functions on numeric fields from child records related by a master-detail relationship. Roll-up summaries are limited to master-detail relationships and cannot be used with lookup relationships. An object can have up to 40 roll-up summary fields, not 25. An object can have up to 25 relationship fields (master-detail or lookup), not 20.

The inability to create a Roll-Up Summary field in this context can be attributed to:

B. The organization has Advanced Currency Management enabled. When Advanced Currency Management (ACM) is enabled, it affects how currency data is managed and aggregated, impacting the functionality of roll-up summary fields that involve currency amounts across different records.

To address this limitation, consider using custom reporting or a custom solution like a trigger or a scheduled batch class to manually calculate and update the total.

For more information on limitations with ACM, consult Salesforce's help article on Advanced Currency Management.

Update the organization-wide defaults and create a criteria based sharing rule are two actions that an app builder should complete to implement the change of moving to a more restrictive sharing model while allowing the Sales team to access all account records with the sales record type. Updating the organization-wide defaults can set the baseline level of access for accounts, and creating a criteria based sharing rule can grant additional access based on record type. Updating the Sales profile and creating an owner-based sharing rule are not necessary or sufficient actions for this change.

Create a validation rule that uses the PRIORVALUE function is how an app builder can meet the requirement of preventing users from increasing the value of Estimated Hours after it is set. According to the Salesforce documentation, “PRIORVALUE returns the previous value of a field.” The validation rule can compare the current value and the prior value of Estimated Hours and display an error message if the current value is greater than the prior value. Creating a formula default value for the custom field, creating a formula field that uses the PREVGROUPVAL function, and creating a validation rule that uses the ISCHANGED function are not valid or correct solutions for this requirement.

 Create a master-detail relationship between the parent and child object with a roll-up summary field that filters on the status field is the recommended method for the app builder to achieve the request of rolling up sales metrics to an opportunity for only Detailed.Sales__c records that have their picklist status set to Active. According to the Salesforce documentation, “Roll-up summary fields calculate values from related records, such as those in a master-detail relationship.” A roll-up summary field can filter on a field value of the child records and sum up only those records that match the criteria. Utilize the AppExchange to download a third-party application that can roll up the sales dollars with the appropriate filter, create a lookup relationship between the parent and child object with a roll-up summary field that filters on the status field, and utilize Apex code to roll up the desired amounts are not valid or necessary methods for this request.

 An app builder can go to two places to see a list of available custom Lightning components in their org:

Lightning App Builder: This is a tool that allows an app builder to create and customize Lightning pages using drag-and-drop components. The app builder can see the list of custom Lightning components in the Custom section of the Lightning Components pane1.

Lightning Components in Setup: This is a setup menu that allows an app builder to view, create, edit, and delete custom Lightning components in their org. The app builder can see the list of custom Lightning components in the Lightning Components section of the Setup menu2. Option A and B are not places where an app builder can see a list of custom Lightning components.

 The best feature to use to ensure consistent case priority entry is Path. Path allows users to see key fields and guidance for each stage of a process, such as a case lifecycle. Path can also enforce data quality by making certain fields required at each stage. See [this article] for more information on Path.

The two steps that should be suggested to meet these requirements are to select insert null values in settings and to use Data Loader to update leads using the CSV file. Selecting insert null values in settings will allow Data Loader to overwrite existing values with null values. Data Loader is a tool that can import, export, update, or delete large amounts of data.

The import wizard only allows values to be imported into a dependent picklist if they match the appropriate controlling field. This ensures data integrity and prevents invalid values from being imported. Custom picklist fields can be either controlling or dependent fields. This allows the app builder to create custom dependencies between custom picklists. Checkbox fields can be controlling fields but not dependent fields. This allows the app builder to create dependencies based on checkbox values, such as true or false. Multi-select picklist fields can be dependent picklist fields but not controlling fields. This allows the app builder to create dependencies based on multiple values selected in a multi-select picklist field. Standard and custom picklist fields can be dependent fields, but not all standard picklist fields can be controlling fields. Some standard picklist fields, such as Lead Status or Opportunity Stage, cannot be controlling fields because they are used in other processes, such as lead conversion or sales path

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.

For more information on using record types and page layouts, check Salesforce's documentation on Record Types.