* All customers that live in Paris.

Customer profile data has address information.

* All customers that have made more than ten online purchases.

Incorrect:

Not Data tables [Not available for Quick Segments]

Not Enrichments [Not available for Quick Segments]

Note:

Quick segments let you build simple segments with a single operator quickly for faster insights. Quick

segments are only supported in environments for individual customers.

Create a new segment with quick segments

1. Go to Insights > Segments.

2. Select New > Create from.

Select the Profiles option to build a segment that is based on the unified customer table.

Select the Measures option to build a segment around measures you have previously created.

Select the Insights option to build a segment around one of the output tables you generated using

either the Predictions or Custom Models capabilities.

3. In the New quick segment dialog box, select an attribute from the Field dropdown.

Etc.

Reference:

https://learn.microsoft.com/en-us/dynamics365/customer-insights/data/enrichment-hub

https://learn.microsoft.com/en-us/dynamics365/customer-insights/data/segment-quick

To build a trigger-based journey that sends "Getting started" emails when an opportunity is marked

as "Won," the appropriate trigger to use is the Dataverse 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:

The Dataverse record change trigger is 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 data and Custom 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 Reference:

Create and manage trigger-based journeys

Work with Dataverse triggers in journeys

By using the Dataverse 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.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/MB-280/page_8_img_1.jpg

Delete: Currently set to "Cascade All," which is causing the issue of deleting the pet records when the

Contact record is deleted. This should be changed to "Restrict" to prevent deletion if related Pet

records exist.

Reparent: Since any active bookings should be updated when the Pet's primary owner is reassigned,

the Reparent option should be set to "Cascade Active" instead of "Cascade All" to ensure that only

active bookings are updated, not inactive ones.

Correct:

* : From the email settings in the Advanced settings, you migrate email router data from server-side

synchronization to Dynamics 365 app for Outlook. [See step 1 below. Use Server-side

synchronization]

* You test the email configuration and enable the mailboxes for the Dynamics 365 App for Outlook

designated users. [Yes, see step 2 below]

Incorrect:

* Within the system settings and email configuration, you set Process Email Using to Dynamics 365

for Outlook. [No, set this to Server-side synchronization. See step 1 below]

Note:

Deploy and install Dynamics 365 App for Outlook

Step 1: Set the default synchronization method

To use Dynamics 365 App for Outlook, you need to set server-side synchronization for your email

processing.

1. From your app, go to Settings > Advanced Settings.

2. Go Settings > Administration and then select System Settings.

3. Select the Email tab, and set Process Email Using to Server-Side Synchronization.

Step 2: Test email configuration and enable mailboxes

Enable and test your user mailboxes so they can use Dynamics 365 App for Outlook.

Reference:

https://learn.microsoft.com/en-us/dynamics365/outlook-app/deploy-dynamics-365-app-for-outlook

 While transforming the first row to be used as headers and defining column types are necessary

steps, the solution does not address removing rows with high proportions of nulls. Rows with

significant null values can interfere with the quality of the unification process in Customer Insights -

Data.

 Therefore, this solution does not fully meet the goal as it does not handle data quality issues caused

by null values.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/MB-280/page_9_img_3.jpg

The configurations in the Salesperson security role will determine the access and visibility the carer

has to the "Corgi meet-up" business process flow. The carer should be able to view and interact with

specific business process flows on the Pet records based on the permissions configured by the

founder.

Business Process Flow Access Configuration:

The image shows that the "Salesperson" security role has the "Create," "Read," "Write," "Delete,"

"Append," and "Append To" permissions set for the "Corgi meet-up" process.

The green circle indicates permissions at the Organization level, meaning the carer can access all

records associated with the "Corgi meet-up" business process flow across the entire organization.

Visibility of Business Process Flows on Pet Records:

Since the carer has these permissions at the Organization level, they will be able to see all business

process flows related to pet records that have been set up by the founder.

In this case, the answer provided in the image indicates that the carer will be able to see business

process flows that were created by both the founder and new flows initiated by the carer themselves

on the Pet records.

Switch Process Dialog Visibility:

The switch process dialog will allow the carer to select from multiple business process flows that are

applicable to a given record.

According to the selection options provided, if both the "Corgi meet-up" and the "Onboard new pet"

flows are available, and they are configured to be accessible by the Salesperson role, the carer should

be able to see both flows when using the switch process dialog. This aligns with the provided answer

choices, which indicate that both flows are visible when switching.

Reference from Microsoft Documentation:

Microsoft’s official documentation on configuring Security Roles in Dynamics 365 provides detailed

guidance on setting permissions for different entities and processes. More information can be found

in the Dynamics 365 security model documentation: Manage security, users, and teams

For Business Process Flow configurations, including permissions and visibility settings, refer to the

guide on Create a business process flow in Dynamics 365.

This setup ensures that the carer has the appropriate level of access to perform their duties,

specifically in handling pet records and business processes like the "Corgi meet-up."

If you have further questions or need more details on this configuration, feel free to ask!

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/MB-280/page_103_img_1.jpg

First Name, Last Name, and Business Unit must be match in both filter.

Additionally Preferred Phone in one of the filters.

Also Email in the other filter.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/MB-280/page_42_img_1.jpg

Retail assistant - Salesperson

The retail assistant can create and update accounts and contacts but cannot edit the product catalog.

The Salesperson role provides access to manage accounts and contacts but does not include

permissions for product catalog management.

Executive - Sales team member

The executive only adds notes to accounts and contacts. The Sales team member role has minimal

access and is appropriate for a user who only needs to add notes.

Territory manager - Sales manager

The territory manager is responsible for forecasting and product management, which aligns with the

Sales manager role, as it includes permissions for managing forecasts and overseeing sales activities.

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 the Sales

Copilot user role assigned. 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:

The View Audit History permission 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.