Free and Premium Microsoft MB-280 Dumps Questions Answers

 Creating a flow to update the Status Reason of the business process flow table record to " Finished " and the Status to " Inactive " upon opportunity closure ensures that the business process flow is marked as complete. This triggers the calculation of duration values.

 This solution explicitly handles the process completion state, which guarantees that the business process flow duration is recorded even if the opportunity is won prematurely.

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.

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.

In Dynamics 365 Sales, security roles control access to different forms, views, and records. To ensure that each department can only access their respective custom forms and views, you should assign security roles to the forms and views. This allows you to restrict users based on their department so they only see the forms and views relevant to them.

How it works:

Edit the form properties → Assign the form to specific security roles.

Edit the view properties → Restrict views based on security roles.

Ensure users have the correct security roles → Users in Department A will only see their assigned forms and views, and the same applies to Department B.

To display the active stage of the business process flow (BPF) in the Pet table view, the active stage must be stored in a column within the Pet table. Since the Onboard new pet BPF is linked to the Pet table, a cloud flow can be used to fetch the active stage from the BPF and write it into a newly created column on the Pet table.

Once the data is available in the Pet table, the next step is to modify an existing view. Since the Active Pets view is already being used in the system, modifying this view by adding the newly created column ensures that the relevant data is visible. Saving the edited view as a new one and sharing it with the founder completes the requirement.

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.

To identify duplicate records, you need to configure both duplicate detection rules and duplicate detection jobs.

Since Terra Flora requires identifying duplicate pet records across various fields, creating three duplicate detection rules is likely necessary to cover different columns (such as name, breed, and dietary requirements) in the Pet table.

One duplicate detection job is sufficient to run these rules concurrently, scanning the database for duplicates across the specified columns. This job can be scheduled or run manually.

Option B is correct as it ensures comprehensive coverage with three rules addressing various fields and one job to manage the duplicate detection process.

References from Microsoft Documentation:

For guidance on setting up duplicate detection jobs and rules, refer to Detect duplicate records in Dynamics 365.

Understanding the Statuscode and Statecode Columns:

In Dynamics 365 Sales, opportunities have two primary columns related to their status: statecode and statuscode.

The statecode defines the primary state of an opportunity (e.g., Open, Won, Lost).

The statuscode provides more granular reasons associated with each primary state. For example, within the " Open " state, you can have various reasons such as " In Progress, " " On Hold, " etc.

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.

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.

Correct:

* After you save a Power Query data source, you have to manually trigger the initial refresh process.

* You can add additional tables to the data source using Get Data functionality in the Power Query.

Incorrect:

* After you save a Power Query data source, you have to manually trigger the initial refresh process.

* You can only add additional columns to the dataset in Power Query before the data source is created in Customer Insights - Data.

* You must create a separate Power Query data source for each table you wish to ingest.

Note:

* After you save a Power Query data source, you have to manually trigger the initial refresh process.

For Power BI users, refreshing data typically means importing data from the original data sources into a semantic model, either based on a refresh schedule or on demand. You can perform multiple semantic model refreshes daily, which might be necessary if the underlying source data changes frequently.

* You can add additional tables to the data source using Get Data functionality in the Power Query.

When using Power Query in Dynamics 365 Customer Insights - Data, you have the flexibility to add additional tables to your data source through the Get Data functionality. This allows you to manage multiple tables and sources efficiently within a single Power Query environment.

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.

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.

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.

In Dynamics 365 Sales, unit groups define how products are sold in different quantities. The base unit is the smallest unit of measure in a unit group. Since customers now want to buy widgets individually, the smallest unit (Each) should be set as the base unit for all other units (Box, Case, and Pallet).

 When an email is tracked in Dynamics 365 from a delegated mailbox, the primary mailbox owner is set as the owner of the tracked email. This means that if an assistant sends or tracks an email on behalf of another user, the email’s ownership will reflect the primary mailbox owner rather than the delegate.

 This behavior ensures that activities are correctly associated with the user who owns the mailbox, aligning with the ownership structure in Dynamics 365.

Dynamics 365 Sales, Define and track your sales goals

Define rollup queries

Rollup queries are used to define the records that should be included in the goal rollup. Rollup queries are created for each goal rollup field. For example, you could create a goal metric that measures all invoices closed within a specific period. You could then create a rollup query to show invoices that are owned by a person, or raised for customers in a territory.

Goals roll up from the bottom of the goal hierarchy to the top, with Dynamics 365 rolling child goal totals into their parent goal totals. Goals at the top of a hierarchy reflect a summation of all the goals in the organization.

You can only query one entity type in a query, but the query builder helps you make a query as simple or as complex as you need. As you fine-tune your query, you can test the results.

Incorrect:

Not B: Define rollup fields

Rollup fields are used to calculate the actual and in-progress values for a goal metric.

Not D: Set goal metrics

Goal metrics let you define how a goal will be measured. For example, a sales team ' s performance can be measured based on the number of leads they get or the revenue amount.

Understanding the Requirement:

The company needs to apply a separate flat rate discount for preferred customers on specific products. This discount varies depending on the customer’s country or region.

A Discount List in Dynamics 365 Sales is used to apply specific discounts on products under defined conditions.

Solution - Creating a Discount List:

A Discount List can be tailored to preferred customers and configured to apply discounts based on specific products and customer attributes, such as their country or region.

Using a Discount List ensures flexibility and control over the discount structure, allowing the organization to manage regional variations in pricing for preferred customers.

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.

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

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.

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.

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.

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.

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

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.

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

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.

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.

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.