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

 In Dynamics 365 Customer Insights - Data, when using Power Query to ingest data, the Get Data

functionality allows users to add multiple tables from various data sources.

 This flexibility enables users to enrich the dataset by pulling in additional tables that may be related

or necessary for the data unification process.

 Power Query in Customer Insights supports creating robust data flows by allowing multiple tables to

be added within a single data source setup, providing a comprehensive data modeling environment.

Reference: Microsoft Documentation - Use Power Query in Customer Insights

Correct:

* Transform the first row to be used as headers. Define column types to be the appropriate field

types and name the query. Create a full name and full address columns by merging the appropriate

columns if they exist. Select Next and your data is now ready for unification.

The proposed solution effectively prepares the data for unification in Dynamics 365 Customer

Insights - Data. Here’s how each step contributes to meeting the goal:

Transform the first row to be used as headers: This step is necessary to define the column names,

which is critical for accurate data interpretation.

Define column types to be the appropriate field types: Specifying the correct data types for each

column ensures that the data will be processed correctly during unification, maintaining data

integrity.

Create a full name and full address columns by merging the appropriate columns if they exist: This

step enhances the dataset by consolidating relevant information into single columns, which can

simplify data usage and improve data quality. Merging columns helps ensure that users can easily

access essential information without navigating through multiple fields.

Select Next: This indicates that the data transformation steps are completed and the dataset is ready

for the unification process.

Incorrect:

* Define column types to be appropriate field types and name the query. Create a full name and full

address columns by merging the appropriate columns, if they exist. Select Next and your data is now

ready for unification.

Does not address the problem with null values.

* Remove any rows where the primary key is missing, delete any leading or trailing zeros on the

primary key, and name the query. Select Next and your data is now ready for unification.

Problem not related to the primary key.

* Transform the first row to be used as headers, and remove any special characters or spaces from

header row. Remove rows with missing primary keys and name the query. Select Next and your data

is now ready for unification.

Does not address the problem with null values.

* Transform the first row to be used as headers, define column types to be the appropriate field

types and name the query. Select Next and your data is now ready for unification.

Solution removes all rows with null values, which can lead to significant data loss, especially if those

rows contain important information.

It may compromise data quality by eliminating rows, which can impact analysis and insights.

* Transform the first row to be used as headers, remove rows that contain null values, and name the

query. Select Next and your data is now ready for unification.

While the solution includes transforming the first row to be used as headers and naming the query,

the step of removing rows that contain null values is problematic.

Removing all rows with null values can lead to significant data loss, particularly if those rows contain

relevant information.

1. Create a Power Automate flow with a Dataverse "When a row is added, modified or deleted"

trigger.

This ensures that the flow is triggered when an account's client tier changes.

2. Set the table and column conditions for the triggering event.

The trigger should monitor changes to the contoso_clienttier field in the Accounts table.

3. Add a step to call the "Create card for assistant" action.

This step ensures that a custom insight card is created for the assistant in Dynamics 365 Sales.

4. Save and test the flow by manually performing an update.

This verifies that the Power Automate flow is correctly detecting tier changes and triggering the

insight card.

5. Update the insight card item to select the flow.

This ensures that the newly created insight card is linked to the correct Power Automate flow.

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

Automate the Tradeshow Follow-up Process: Implement sequences

Using sequences in Dynamics 365 allows for automating a series of tasks or activities for lead follow-

up. Sequences enable you to standardize and automate follow-up tasks, like sending emails and

scheduling calls, ensuring salespeople adhere to a consistent process without manual intervention.

Implementing sequences is ideal for the follow-up process as it automates the steps and reduces the

reliance on salespeople to manually manage each task.

Reference: Microsoft Documentation - Create and Manage Sequences

Ensure That the Process Applies Only to Tradeshow Leads: Use segments

Segments are used to filter leads based on specific criteria. By using segments, you can ensure that

the automated sequence is triggered only for leads generated from trade shows.

This action targets the automation specifically at the tradeshow leads, ensuring that other leads are

not inadvertently included in this process.

Reference: Microsoft Documentation - Use Segments in Dynamics 365

Ensure Proper Timing of Activities: Set relative due date

Setting a relative due date allows you to define a timeframe between actions in the sequence. For

example, the follow-up call task can be scheduled for one week after the initial email.

This ensures that tasks are executed with the correct timing, aligning with the desired schedule of

following up with potential customers one week after the first contact.

Reference: Microsoft Documentation - Schedule Activities with Relative Due Dates

By implementing sequences to automate follow-ups, using segments to filter for tradeshow-specific

leads, and setting relative due dates for timely task execution, the company can optimize its post-

tradeshow follow-up process and enhance the likelihood of successful customer engagement.

To ensure that the sales forecast categorizes lost deals using more detailed reasons like "Cancelled"

and "Outsold," you need to modify how the opportunity status codes are mapped to the forecast

categories.

Add the detailed lost reasons to the opportunity forecast category option set

This ensures that the system can recognize and categorize opportunities as "Cancelled" or "Outsold"

within the forecast. The forecast category option set must be updated to accommodate the new lost

reasons.

Update the field mappings in the Opportunity Forecast Category Mapping Process workflow

This workflow determines how opportunity status codes map to forecast categories. Updating the

field mappings ensures that opportunities with "Cancelled" or "Outsold" reasons are correctly

classified within the forecast.

Manager on System User Record:

Suggested contacts in Teams can include users directly linked to the individual starting the chat. The

manager assigned on the user’s system record can be a suggested contact, as this is a common

relationship that suggests frequent communication.

Record Owner of the Initiating Record:

The owner of the record being discussed or acted upon is also likely to be a suggested contact. This is

because the owner has primary responsibility for the record and would commonly need to be

consulted or informed about actions related to it.

Created By of the Initiating Record:

If the user is the Created By for a record, they are associated with its initial setup or creation. As a

result, they may be suggested when actions on that record are taken since they are familiar with its

origins.

Reference: Microsoft Documentation - Configure Suggested Contacts for Dynamics 365 and Teams

These selections align with the rules typically used for suggesting contacts in integrated Teams chats,

ensuring relevant parties are automatically suggested based on record associations and user

relationships.

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

Update All User Mailboxes to Sync with Exchange Online:

Since your organization has moved from Gmail to Exchange Online, the first step is to update the

mailbox settings for each user to enable synchronization with Exchange Online. This change in

configuration aligns with the new email server settings, allowing Dynamics 365 to handle email via

Microsoft Exchange Online instead of Gmail.

This step ensures that user mailboxes are correctly configured to communicate with the new

Exchange environment.

Reference: Microsoft Documentation - Set Up Server-Side Synchronization with Exchange Online

Approve Email for All Relevant Users:

After updating the mailbox configurations, it’s necessary to approve email for all relevant users. This

step confirms that the email addresses are verified and allowed to send and receive emails through

Dynamics 365.

This approval step is required to ensure that Dynamics 365 has permissions to access and synchronize

with each user’s mailbox in Exchange Online.

Reference: Microsoft Documentation - Approve User Email for Server-Side Synchronization

Test the Email Configuration and Enable the Selected Email Mailboxes for All Relevant Users:

Finally, testing the email configuration ensures that server-side synchronization is functioning

correctly with Exchange Online. Once the test is successful, enabling the email mailboxes activates

the synchronization for all users.

This step verifies that the settings are correct and that emails can be processed as expected, finalizing

the setup.

Reference: Microsoft Documentation - Test and Enable Mailboxes

By updating the mailbox settings to Exchange Online, approving email access, and testing and

enabling the configuration, you ensure a smooth transition from Gmail to Exchange Online for

server-side synchronization, enabling efficient email communication through Dynamics 365.

 The Query Assist feature in Dynamics 365 Customer Insights - Journeys utilizes natural language

processing to help marketers easily build segments.

 By using simple language, marketers can describe their target audience without needing to know

complex query syntax, making segmentation more accessible.

 This feature is designed to streamline segment creation, allowing marketers to quickly define their

audience with natural language inputs, which is particularly useful for users who may not be familiar

with technical query building.

Reference: Microsoft Documentation - Use Query Assist for Segmentation in Customer Insights

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