MB-280 Microsoft Dynamics 365 Customer Experience Analyst Questions and Answers

 Changing the opportunity to an inactive state allows for the calculation of business process flow duration values, as this state transition prompts the system to finalize any duration metrics associated with the process flow.

 Business process flows calculate duration upon completion or transition of the process, so marking the opportunity as inactive triggers the system to calculate these durations.

Understanding the Base Unit in Dynamics 365 Sales:

In Dynamics 365 Sales, the base unit represents the smallest quantity or measurement used to sell a product or service. It serves as the foundational unit within a unit group, which allows you to define how a product can be measured and sold in various quantities.

All other units within the unit group are defined in relation to this base unit. Therefore, it should represent the smallest quantity possible, ensuring flexibility in defining larger units or multiples based on this standard.

Selecting the Base Unit - Why the Lowest Quantity?

Choosing the lowest needed unit ensures that any other units, whether they are multiples or larger groupings, can be accurately calculated in relation to the base unit. This approach allows you to accommodate various selling quantities and ensures precise calculations across different unit types.

For example, if the lowest unit is a single item, you can then configure units such as a dozen, box, or case based on this base unit. This provides consistency and accuracy in pricing and inventory management.

 In Dynamics 365 Sales, currency exchange rates are applied to opportunity records when specific triggers occur. These exchange rates are updated manually on a periodic basis (e.g., once a month) to reflect current currency values.

 Exchange rates are recalculated for an opportunity when there is a change in the status reason (e.g., from open to won or lost). This trigger ensures that the most recent exchange rate is used when key changes occur in the opportunity lifecycle, maintaining accurate currency reporting.

Define a forecast model

Define the entities that must be used to generate the forecast.

1. In the General step of the Forecast configuration page, define the fields that should be used for the forecast.

[Steps 2 to 6 omitted]

7. Select a Rollup to hierarchy relationship.

This step establishes a relationship between the rollup and hierarchy entities. Each forecast template starts with a default rollup to hierarchy relationship:

Choose different values to support your organization's specific requirements if needed.

Note: Select a template

The fastest way to create a forecast is to use a template. The template that you select defines how the forecast groups data.

On the Forecast configurations page, select one of the following templates:

Org chart forecast: Rollup columns and projections are based on your organization's reporting structure. This template uses the Manager field of the User entity for the hierarchy.

Product forecast: Rollup columns and projections are based on the product hierarchy.

*-> Territory forecast: Rollup columns and projections are based on the sales territory hierarchy.

Correct:

* Recalculate the forecast

Incorrect:

* Recalculate the opportunity.

* Update the Opportunity Forecast Category Mapping process.

Note:

Example of forecast recalculation methods

Let's understand the different methods with an example. Consider a scenario where you have a forecast with 4 quarterly periods and an annual period. Assume that you're currently in Q4. The following table shows when and how the forecast data is updated for different scenarios and periods.

--

Dynamics 365 Sales, Recalculate forecasts manually

You want the forecast data to be up-to-date to make informed decisions. Forecast data is automatically recalculated at regular intervals. However, you can trigger a manual recalculation when you want to recalculate the forecast data immediately. You can also trigger a manual recalculation for past and future periods as they aren't automatically recalculated.

Recalculate and refresh forecast data manually

1. Open the forecast. Verify the Last updated timestamp on the command bar to know when the forecast was last recalculated successfully.

2. Select Recalculate data.

A notification appears at the top of the screen, confirming the recalculation. Recalculation happens in the background, and you can continue to work while recalculation is in progress.

3. After the application recalculates the forecast data, a notification appears to refresh the data. On the notification, select Refresh page.

 This solution also includes transforming headers and defining column types, along with creating merged columns. However, it still does not remove rows with a high proportion of nulls. Addressing null values is important for data quality and ensuring accurate unification.

 Without removing rows with many nulls, the data may still have integrity issues that could impact the unification process. As a result, this solution does not completely meet the goal.

Correct:

* Recalculate the forecast

Incorrect:

* Recalculate the opportunity.

* Update the Opportunity Forecast Category Mapping process.

Note:

Example of forecast recalculation methods

Let's understand the different methods with an example. Consider a scenario where you have a forecast with 4 quarterly periods and an annual period. Assume that you're currently in Q4. The following table shows when and how the forecast data is updated for different scenarios and periods.

--

Dynamics 365 Sales, Recalculate forecasts manually

You want the forecast data to be up-to-date to make informed decisions. Forecast data is automatically recalculated at regular intervals. However, you can trigger a manual recalculation when you want to recalculate the forecast data immediately. You can also trigger a manual recalculation for past and future periods as they aren't automatically recalculated.

Recalculate and refresh forecast data manually

1. Open the forecast. Verify the Last updated timestamp on the command bar to know when the forecast was last recalculated successfully.

2. Select Recalculate data.

A notification appears at the top of the screen, confirming the recalculation. Recalculation happens in the background, and you can continue to work while recalculation is in progress.

3. After the application recalculates the forecast data, a notification appears to refresh the data. On the notification, select Refresh page.

Only Roll up and Calculated type columns have the checkbox option for “Show in Trend Chart”, for other types of columns (e.g. Quota column which has Simple type) this checkbox option is hidden as shown below:

Note:

Enhanced configuration is available for the Trend chart and Flow chart within Microsoft Dynamics 365 Sales Insights.

Enable Trend chart using the “Show in Trend Chart” checkbox setting:

The Trend chart is now available as a part of the Predictive forecasting feature.

You need to select/deselect the “Show in Trend Chart” checkbox at the time of configuring the specific column inside the forecast configuration.

Navigate to App settings > under Forecast configurations > Open the appropriate “Forecast configuration” record > navigate to the “Layout” step > under the appropriate column (e.g. Won column) > click on the setting icon as highlighted below:

Only Roll up and Calculated type columns have the checkbox option for “Show in Trend Chart”, for other types of columns (e.g. Quota column which has Simple type) this checkbox option is hidden as shown below:

In Dynamics 365 Customer Insights - Data, primary key attributes must uniquely identify records and be consistent across the data source.

Whole Number and GUID are commonly used data types for primary keys because they can uniquely identify records and are natively supported for primary keys in databases.

String can also be used as a primary key if it uniquely identifies each record (e.g., an email address).

Integer and Boolean are generally not used as primary keys in Customer Insights because they may not provide unique identifiers suitable for all scenarios.

 To make Power BI insights available within Dynamics 365 Sales, specifically contextualized for accounts, you should embed the Power BI report with contextual filtering. This ensures that the report dynamically adjusts based on the specific account record a user is viewing.

 Embedding with contextual filtering enables sales users to see account-specific insights directly within the Dynamics 365 interface, improving accessibility and relevance.

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.jpg

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.

 Transforming the first row to be used as headers, removing rows with null values, and naming the query prepares the data appropriately for unification in Customer Insights - Data.

 By setting the headers and removing rows with high proportions of nulls, the data becomes cleaner and more structured, which is essential for successful unification in Customer Insights. Therefore, this solution meets the goal of preparing the data for unification.

A close-up of a computer screen Description automatically generated

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.

Start Auditing:

Enabling Start Auditing is the primary step to activate auditing for Dynamics 365. This setting ensures that changes to data, including field updates on records, are tracked and logged.

Without enabling this checkbox, no data changes will be recorded, as it is the fundamental requirement for auditing across all entities and fields.

The correct order of actions to create a new custom account plan table with a hierarchical parent-child relationship visualization is as follows:

Create a new account plan table.

Create a 1

self-referential relationship and mark the relationship as hierarchical.

Open the advanced Relationship settings.

Go to the Hierarchy Settings grid view.

Step by Step Comprehensive Detailed Explanation with ALL Microsoft Dynamics 365 References:

Create a New Account Plan Table:

To model account plans for subsidiaries and manage the parent-child relationships, start by creating a new table (entity) named "Account Plan."

This table will store information related to the account plans, and you can define custom fields and settings as needed.

Configure table relationship cascading behavior

The CascadeConfiguration class or CascadeConfiguration complex type) contains the properties representing actions that may be performed on the referenced table in the one-to-many relationship. Each property can be assigned one of the values of the CascadeType enum type.

* Restrict

Prevent the Referenced table record from being deleted when referencing tables exist.

Incorrect:

* Cascade All

Perform the action on all referencing table records associated with the referenced table record.

* Cascade Active

Perform the action on all active referencing table records associated with the referenced table record.

* Remove Link

Remove the value of the referencing column for all referencing table records associated with the referenced table record.

Adding Columns to the Active Onboard New Pet View (Option B):

To display the current active stage of the "Onboard new pet" business process flow, you need to ensure that the Active Onboard new pet view includes relevant columns from the Pet table, specifically those tracking process flow stages.

Creating and Adding a New "Onboarding Stage" Column (Option D):

Creating a column such as "Onboarding stage" on the Pet table helps track the active stage of the onboarding process directly within the view. This allows users to see at a glance which stage each pet is in without navigating away from the main view.

Other Options:

Option A (Adding a page) refers to modifying the app's navigation, which doesn’t directly impact the visibility of the business process flow stage.

Option C (All Onboard New Pet View) may not be as relevant if you only need to focus on active onboarding records rather than all records.

References from Microsoft Documentation:

For configuring views and columns in Dynamics 365, refer to Create and edit views.

A close up of a text Description automatically generated

Renaming the Omitted Column to Cancelled:

To rename a column in the forecast layout, such as changing Omitted to Cancelled, you should go to Layout column settings. This setting allows you to customize how columns appear in the forecast view, including renaming columns to better match your business terminology.

Renaming within Layout column settings will directly change how this column is labeled in the user interface for clarity and consistency with business terms.

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.

A white background with black text Description automatically generated

Opportunity Updated Today is Not Included in the Chart: Update roll-up settings

The roll-up settings control how frequently the data is aggregated and included in the goal metrics. If an opportunity updated today is not appearing, it likely indicates that the roll-up process has not yet captured the recent data change.

By updating the roll-up settings, you can adjust the frequency or manually trigger an update, ensuring that all recent updates are reflected in the chart.

A white background with black text Description automatically generated

Date Field - Actual End:

The Actual End date field is typically used to mark when an activity, such as an outgoing call, is completed. Since the sales manager wants to measure completed outgoing calls, using Actual End ensures that only calls finished within the fiscal year are included in the goal measurement.

This setting will align with the requirement to track activities finished within a specific time frame (January - December).

Show As

Visualize this view

To catch up on scheduled tasks and activities, BDM1 can use specific features in the Dynamics 365 Sales Hub interface. Here’s how they work in this scenario:

Show As:

The "Show As" option allows users to change the view of their current page. BDM1 can use this feature to switch to a timeline or agenda view, which can help display upcoming activities, tasks, and reminders in a format that may highlight pending actions, like the meeting scheduled by BDM2.

When in the appropriate view, reminder cards for tasks and meetings can surface based on relevance and priority.

Visualize this view:

The "Visualize this view" option helps BDM1 to see an overview of upcoming tasks, scheduled meetings, and associated records in a graphical format.

This visualization can be particularly useful for identifying key upcoming events like the meeting BDM2 scheduled, as it provides a clear summary of upcoming activities, aiding in prioritization and catch-up efforts.

Microsoft Dynamics 365 References:

Using assistant cards in Dynamics 365 Sales

Configuring views and visualizations in Dynamics 365

By selecting these options, BDM1 can effectively access and view the assistant card related to the scheduled meeting, facilitating a quick catch-up on all pending activities.

A screenshot of a chat AI-generated content may be incorrect.

1. Create a trigger-based journey that triggers on changes to the contoso_clienttier field.

Since the "Welcome" email should be sent when an account first enters any client tier, a trigger-based journey is required. The trigger should activate when the contoso_clienttier field is updated with a value.

2. Select the frequency as a one-time journey where newly added members can start at any time.

A one-time journey with newly added members ensures that each new primary contact will enter the journey when their account first gets assigned a tier.

3. Add the journey steps.

After defining the journey type and trigger, the necessary email steps (sending the "Welcome" email) must be added before publishing.

A screenshot of a phone Description automatically generated

Determine the Price of the Product Bundle: Use the lunch bundle price

Since the lunch bundle is predefined at $200.00, the price for the bundle should be set using the lunch bundle price. This ensures that any associated products (Sandwich, Napkins, and Soda) are automatically included in this price, simplifying the process for the sales staff.

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 Office and Toronto Office are 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 to London Office and Toronto Office.

A screenshot of a computer Description automatically generated

The correct order of actions to set up a product catalog, including the ability for sellers to apply quantity discounts, is as follows:

Create units.

Add products.

Create price lists.

Add price list items.

Create discount lists.

Create Units:

Start by defining units (e.g., each, box, dozen) for your products. Units specify how products are measured and sold, which is essential for setting pricing and discounts.

This step ensures that all products have consistent units of measure before adding them to the catalog.

A screenshot of a computer AI-generated content may be incorrect.

BDM2 is a contact of interest for → both the London Office and Toronto Office opportunities.

BDM2 is a sales team member for all Northwind Traders opportunities, meaning they are involved in both the London Office and Toronto Office opportunities.

BDM3 is a contact of interest for → the Toronto Office opportunity.

BDM3 owns all Northwind Traders opportunities except those owned by BDM1. Since BDM1 owns the London Office opportunity, BDM3 is only involved in the Toronto Office opportunity.

Client Contact2 is a contact of interest for → the Toronto Office opportunity.

The Toronto Office opportunity lists Client Contact2 as the primary contact, making them a contact of interest for that opportunity.

Client Contact1 is a contact of interest for → the London Office opportunity.

The London Office opportunity lists Client Contact1 as the primary contact, making them a contact of interest for that opportunity.