MB-280 Questions and Answers

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

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.

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.

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.

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.

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.

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.

 To make a new table, like Locations, visible within the Sales Hub, you need to add it to the App Designer. This involves updating the Sales Hub app module to include the Locations table as a new entity that users can access.

 By adding the table in the App Designer, you ensure it becomes part of the navigation and is available within the Sales Hub application.

 Since the company uses Microsoft SharePoint for document storage, access to documents is controlled through SharePoint permissions rather than Dynamics 365 security roles.

 To restrict document access to only the contracts team, you should update the users list in the SharePoint site where the documents are stored. This involves configuring SharePoint permissions to ensure that only the contracts team (or a specific SharePoint group associated with them) has access to the document library where contracts are stored.

 In Dynamics 365 Sales, when setting up a unit group, you must first define the base unit. This is the fundamental unit of measurement for a product and serves as the foundation for defining related units within the group.

 For the battery manufacturer, defining a base unit (such as a single battery) is necessary before configuring related units for boxes of 12 and cases of 24 boxes, as these will be multiples or related units derived from the base unit.

Requirement Analysis:

The goal is to include only specific opportunities—those that " sell " —in the forecast. This requires the ability to selectively include opportunities that meet specific criteria, such as the status, stage, or type of sale.

Solution - Using Additional Filters:

In Dynamics 365 Sales, additional filters can be applied within the forecast configuration to refine the opportunities included. Filters allow you to specify criteria such as opportunity status, probability, estimated revenue, or any custom field that signifies the opportunity has " sold. "

By setting up filters, you can ensure that only opportunities matching the desired criteria are included in the forecast, providing a targeted and accurate view of expected sales.

Steps to Configure Additional Filters in Forecasting:

Go to Sales > Forecasts, and select or create a new forecast.

In the forecast settings, navigate to Filters and add conditions that define which opportunities are included. For example, you can filter based on status (e.g., only include opportunities marked as " Won " ).

Save and apply the filter settings to ensure only the relevant opportunities appear in the forecast.

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!

 In Dynamics 365, business process flows are limited to 30 stages across all entities within a single process. Since each entity here (Lead, Opportunity, Quote, Order, Invoice) has 10 stages, the total would be 50 stages, exceeding the limit.

 To meet the requirements, you need to reduce the total number of stages to comply with this limitation. Reducing the total number of steps per stage, tables, or steps won’t directly address the stage limit issue.

Requirement: Add the Type of Loss

To track reasons for lost opportunities, including specifics like losses to competitors, you need to provide additional details on why an opportunity was closed as lost.

The Status Reason field can be customized to include specific reasons for the loss. This field is used within the context of the Opportunity entity and allows the addition of options to detail specific loss types.

By modifying the Status Reason option set, you can add various reasons (like " Lost to Competitor " ) which will appear as options when closing an opportunity as lost.

Create an owner team

1. Make sure that you have the System Administrator, Sales Manager, Vice President of Sales, Vice President of Marketing, or CEO-Business Manager security role or equivalent permissions.

2. Go to Settings > Security. In Microsoft Dynamics 365 for Outlook, go to Settings > System > Security.

3. Select Teams.

3. On the Actions toolbar, select New button.

5. Enter a team name.

6. Select a business unit. [Only for Dynamics 365 Sales Enterprise].

7. Enter an administrator.

8. Select Owner in Team Type.

9. Complete other required fields, and then select Save.

If you don’t select the business unit to which the team will belong, by default, the root business unit is selected. The root business unit is the first business unit created for an organization. [Only for Dynamics 365 Sales Enterprise]

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.

Dynamics 365 Sales uses the Opportunity Sales Access Team template to provide access to the opportunity record to all the users connected under the Sales team connection role category. A salesperson who might not have access to a given opportunity record by their assigned security role privileges can still get access when added as a sales team member from this subgrid. This allows the sales team member users to access and work with the opportunity record in Dynamics 365 on a per-record basis. Similarly, when an existing sales team member is deleted from the subgrid, the access to the opportunity record granted via the access team template is also removed.

Note: Use access teams and owner teams to collaborate and share information

When to use access teams

The teams are dynamically formed and dissolved. This typically happens if the clear criteria for defining the teams, such as established territory, product, or volume aren’t provided.

The team members require different access rights on the records. You can share a record with several access teams, each team providing different access rights on the record. For example, one team is granted the Read access right on the account and another team, the Read, Write and Share access rights on the same account.

A unique set of users requires access to a single record without having an ownership of the record.

To update the Opportunity Close form in Dynamics 365 Sales, you need a role that allows modification of system entities, including the Opportunity entity and its associated forms. The System administrator role provides full access to all customization features in Dynamics 365, including modifying forms, fields, and layouts.

Scenario 1: Adding a New Flavor to the Product Catalog

The bakery develops new bread flavors regularly, and these flavors are variations of an existing product (bread).

In Dynamics 365, product properties are used to define characteristics or options of a product, such as flavors, sizes, or colors. Since the bread flavors are variations, they can be treated as product properties rather than separate products.

By creating a product property, you can add new flavors as options under the existing bread product, allowing flexibility without altering the core product structure.