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

Dynamics 365 Sales, Create and activate assignment rules

You can create and manage sequences and assignment rules through navigating to 'Personal Settings' area if users have sequence manager role.

 Server-side synchronization typically syncs at equal intervals, which can be configured in Dynamics 365. These intervals determine how often data is synchronized between Microsoft Exchange and Dynamics 365 Sales, affecting emails, tasks, and appointments.

 The synchronization frequency can be adjusted by the administrator but operates at consistent, regular intervals by default.

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.

A screenshot of a computer Description automatically generated

The correct order of actions to configure the editing capabilities for the Account records in Copilot for Sales while restricting the "Revenue Forecast" field is as follows:

In Copilot for Sales admin settings, select Forms.

In the settings for the Account table, select Forms.

Select the Account record type.

In the Manage fields section, turn off Allow editing for the "Revenue Forecast" field.

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

In Copilot for Sales Admin Settings, Select Forms:

Start by accessing the admin settings for Copilot for Sales. This is where configuration changes for form accessibility and editing settings are managed. Selecting Forms will allow you to configure specific form-related options for Copilot usage.

In the Settings for the Account Table, Select Forms:

Navigate to the settings for the Account table within Copilot. Selecting Forms at this level allows you to specify which parts of the Account table are editable and visible in Copilot, which directly impacts how users interact with the Account records.

Select the Account Record Type:

Once in the form settings, choose the Account record type that needs to be modified. This is essential for enabling edits to the Account records in Copilot and ensuring that the correct fields are accessible.

In the Manage Fields Section, Turn Off Allow Editing for the "Revenue Forecast" Field:

Finally, within the Manage fields section, disable the Allow editing option specifically for the "Revenue Forecast" field. This action ensures that while Account records can be edited in Copilot, the "Revenue Forecast" field remains read-only, satisfying the requirement from the vice president of sales.

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 References:

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.

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.

 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.

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 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.

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.

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.

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 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.

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).

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.

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.

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.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.

References 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!

The timeline control in Dynamics 365 allows users to view and interact with activities, notes, and posts associated with a record. To meet Terra Flora’s requirements for displaying specific activities, you need to customize the timeline to show only certain activity types.

Removing All Other Activity Types Except Task, Email, and Phone Call (Option B):

According to Terra Flora's requirements, only Tasks, Emails, and Phone Calls should appear in the timeline for Pet records. Therefore, removing all other activity types ensures that only the relevant activities are shown. This customization is achieved in the timeline settings by unchecking unnecessary activity types.

Unchecking the Posts Option (Option C):

Since Terra Flora specified that posts should not appear on the timeline, you should uncheck the Posts option under the Record types settings in the timeline configuration. This action removes posts from the view, aligning with Terra Flora’s requirement to exclude posts from the Pet records timeline.

Other Options Explanation:

Unchecking Notes (Option A) would prevent users from adding or viewing notes, which Terra Flora requires.

Unchecking the Activities Option (Option D) would disable all activities on the timeline, which does not meet Terra Flora’s needs as they require Task, Email, and Phone Call activities.

Option E deals with the display format of notes but does not restrict their visibility, which does not align with the requirement to exclude posts specifically.

References from Microsoft Documentation:

For configuring and customizing the timeline control, refer to Customize a timeline control in Dynamics 365 documentation for detailed steps on modifying timeline settings and activity visibility.