PDF MB-280 Study Guide

Here’s the correct sequence to configure a new Customer Insights - Journeys form to handle lead duplicates automatically, as per the requirements:

Create a new form:

Start by creating a new form within Customer Insights - Journeys. This is the initial step to set up a form that will capture new leads.

Select a form template:

Choose a template that best fits the purpose of the form. This provides a structure for the form fields and layout, streamlining the setup process.

Set the form target audience to leads:

Since the form will be capturing lead information, specify that the form’s target audience is “leads.” This will ensure that the data is processed and stored as lead records.

Set the form duplicate records strategy to the audience default strategy:

Define how duplicate records are managed. First, apply the default duplicate record strategy for leads. This sets an initial strategy for managing duplicates.

Publish the form:

After completing the setup and configuring the necessary options, publish the form to make it available for use.

Additional Context:

The Create a custom matching strategy and Set the form duplicate records strategy to the custom form matching strategy steps are optional and can be used for further refinement if the default strategy does not meet specific requirements for matching leads based on certain criteria.

By following these steps, you ensure the form is configured for capturing leads and manages duplicates effectively based on the default duplicate record strategy.

Microsoft Dynamics 365 References:

Set up a Customer Insights - Journeys form

Duplicate Detection Rules in Dynamics 365

BDM1 has a reminder setting for close dates that are coming up within the next 21 days, as configured in the system. Given that BDM1 logs in on June 3, 2024, here’s how to determine which opportunities will be highlighted in the "Close date coming soon" reminder cards:

Calculate the Reminder Period:

With a 21-day notification period, any opportunities with close dates on or before June 24, 2024 (21 days from June 3), will trigger a reminder card in the assistant.

Evaluate Close Dates for Opportunities:

London Office:Scheduled to close on June 4, 2024, which is within 21 days from June 3.

Toronto Office:Scheduled to close on June 12, 2024, which also falls within the 21-day reminder period.

Mexico City Office:Scheduled to close on June 18, 2024, within the 21-day reminder period.

Seattle Office:Scheduled to close on June 19, 2024, also within the 21-day period.

Based on this,London OfficeandToronto Officeare within the specified period and thus will appear as close date reminders for BDM1.

Microsoft Dynamics 365 References:

Assistant and Insights cards in Dynamics 365 Sales

By applying the specified close date threshold, we can confirm that the reminder cards for opportunities closing on June 4 and June 12 will be displayed to BDM1, which corresponds toLondon OfficeandToronto Office.

To build a trigger-based journey that sends "Getting started" emails when an opportunity is marked as "Won," the appropriate trigger to use is theDataverse record change trigger. This trigger is specifically designed to initiate actions based on changes in Microsoft Dataverse records, which are integral to Dynamics 365.

Here’s the detailed reasoning:

Dataverse Record Change Trigger:

TheDataverse record change triggeris used to initiate journeys when there is a change in a record within Dataverse, such as an opportunity's status.

Since the requirement is to send a "Getting started" email once an opportunity status changes to "Won," this trigger can detect the status update in real-time.

Using this trigger, you can specify the criteria for the journey to start, such as filtering for opportunities with a status of "Won," thus automating the email sending based on this condition.

Why Not Other Triggers?

Custom trigger with lead profile dataandCustom trigger with contact profile data:These are generally used for initiating journeys based on custom events or data points outside of standard Dataverse records, which isn’t applicable here as the journey is triggered by an opportunity status change, a native Dataverse record.

Email Link Clicked Interaction Trigger:This trigger is used to follow up after an email link is clicked, which does not align with the scenario. The journey must start based on an opportunity status change, not email interaction.

Microsoft Dynamics 365 References:

Create and manage trigger-based journeys

Work with Dataverse triggers in journeys

By using theDataverse record change trigger, you ensure that the journey aligns directly with the sales process and automatically sends the "Getting started" email when an opportunity reaches the "Won" status, as requested by the global sales lead.

To enable the digital sales team's request to use Copilot for summarizing changes to lead records, you need to ensure that they have the necessary permissions and access to the required features. Here’s how to proceed:

Assign the Sales Copilot User Role:

Dynamics 365 Copilot in Sales is a feature that assists users by providing insights and summaries based on data within the system.

To allow the digital sales team to access and utilize Copilot's capabilities, they must have theSales Copilot user roleassigned. This role enables users to interact with Copilot and benefit from its AI-driven functionalities such as summarizing changes and insights in records.

Microsoft Documentation Reference:Dynamics 365 Sales Copilot Setup

Grant View Audit History Permissions:

TheView Audit Historypermission is essential for team members to access audit logs, which is necessary for reviewing and summarizing changes made to lead records.

Enabling this permission will allow the digital sales team to view a history of modifications in lead records, thus allowing them to generate summaries based on this audit trail.

The View Audit Summary permission specifically lets them see summaries of audit data, which complements Copilot’s functionality by allowing Copilot to access detailed change history for summarization.

Microsoft Documentation Reference:Security Roles and Privileges

By implementing these two actions, the digital sales team will have both the necessary access to Copilot features and the required permissions to audit lead record changes, enabling them to leverage Copilot for summarizing changes to leads effectively.