* 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.
Reference: Microsoft Documentation - Configure Filters in Forecasts
Benefits of Using Filters:
Filters provide flexibility to customize the forecast view, allowing for detailed segmentation of opportunities based on specific conditions.
This approach ensures that the forecast reflects only the opportunities that are relevant to your defined criteria, which in this case is opportunities that have " sold. " By using additional filters, you can effectively control which opportunities are included in your forecast, aligning it with specific business needs and improving forecast accuracy.

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.
Reference: Microsoft Documentation - Business Process Flow Limits

Explanation:

* 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.
Reference: Microsoft Documentation - Configure Forecast Layout and Column Settings Deleting the Lost Column from the Forecast:
To remove a column entirely, such as the Lost column, you should adjust the Forecast configuration. This configuration setting allows you to add or remove columns from the forecast grid.
Modifying Forecast configuration affects the structural aspects of the forecast, such as which columns are included, based on what is necessary for reporting and analysis.
Reference: Microsoft Documentation - Configure and Manage Forecasts
By utilizing the Layout column settings for renaming columns and the Forecast configuration for adding or removing columns, you can tailor the forecast layout to meet specific business requirements, ensuring the forecast view is both relevant and easy for users to interpret.

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.
Reference:
https://learn.microsoft.com/en-us/dynamics365/outlook-app/deploy-dynamics-365-app-for-outlook
Topic 1, Contoso Ltd.
Background information
Contoso Ltd. has started a new division that provides janitorial services to businesses.
The sales teams for this division are using a dedicated instance of Dynamics 365 Sales.
Contoso Ltd.'s sellers are becoming accustomed to Copilot in Sales and Sales Insights features. They have identified several desired enhancements.
System configuration
The base currency for all opportunities in the system is US dollars (USD). The administrator has NOT enabled installed premium Sales Insights features. All users have Premium licenses. Contoso Ltd. uses Exchange Online for email.
Only three default insights cards are turned on:
1 Close date coming soon
2. Meeting today
3. Upcoming meeting
The system administrator has set the following days before notifying me value for the Close date coming soon card to 21 days.
Contoso Ltd. has also just set up Dynamics 365 Customer Insights - Journeys for marketing automation. No segments or customer journeys have been defined yet. Dynamics 365 Sales and Customer Insights - Journeys both share the same instance of Microsoft Dataverse.
Copilot in Dynamics 365 Sales settings
The following screenshots show the configured fields for opportunity settings summaries and recent changes in Copilot.

Business development managers
Contoso Ltd. has 30 business development managers (BDMs) across its sales teams. Each BDM is responsible for selling janitorial services to new and existing clients. All BDMs are assigned the sales manager security role in Dynamics 365 Sales.
Any 8DM can own an opportunity, even if a different BDM owns the client account record. Any other BDMs assigned to work on the opportunity will be included in the opportunity record's sales team. Opportunity records owned by a BDM will never include any additional client stakeholders other than the named contact for the opportunity.
The BDMs have been told to document all client communications in Dynamics 365, but they frequently exchange emails with client contacts through Microsoft Exchange WITHOUT tracking them in Dynamics 365.
Digital sales team
Contoso Ltd. has a digital sales team that comprises 10 junior sales resources who focus on lead qualification and conversion to opportunities. Members of this team are assigned a single custom security role named Digital seller that is a copy of the standard Salesperson role. View audit history and view audit summary permissions are disabled.
The team currently receives leads from an online form on Contoso Ltd.'s website. Many online lead submissions end up being duplicates, and the team manually reconciles the duplicates by comparing last name, email address, and phone number for all submitted leads.
Clients
Contoso Ltd. has a digital sales team that comprises 10 junior sales resources who focus on lead qualification and conversion to opportunities. Members of this team are assigned a single custom security role named Digital seller that is a copy of the standard Salesperson role. View audit history and view audit summary permissions are disabled.
The team currently receives leads from an online form on Contoso Ltd.'s website. Many online lead submissions end up being duplicates, and the team manually reconciles the duplicates by comparing last name, email address, and phone number for all submitted leads.
Client tiers
Clients are grouped into tiers based on annual revenue as calculated in a system outside Dynamics 365 Sales. Clients receive different levels of ongoing service and support based on their tier assignment Annual revenue values for accounts and corresponding tier values are written to Dynamics 365 through a nightly batch process. Client tier values are only updated when they change, and tier value will always be blank for accounts with no calculated annual revenue.
The tier structure is:
* Tier A - annual revenue greater than or equal to $10,000,000 USD
* Tier B - annual revenue greater than $5,000,000 USD and less than $10,000,000 USD
* Tier C - annual revenue greater than $0 USD and less than or equal to $5,000,000 USD The tier label is stored in a custom text field named Client tier(contoso_dienttiei) that contains only a single letter or is blank.
Northwind Traders account
There are three BDMs who frequently work together on large opportunities.
* BDM1 is the account owner for Northwind Traders, a multinational client.
o BDM1 owns all Northwind Traders opportunities with estimated revenue greater than or equal to 51.000,000.
* BMD2 and BDM3 are assisting BDM1 with several opportunities for Northwind Traders in different cities.
o BDM3 owns all other Northwind Traders opportunities. BDM3 is NOT a sales team member for any of the opportunities BDM1 owns, o BDM2 is a sales team member for all Northwind Traders opportunities.
Client Contact1 is the primary contact for the Northwind Traders' account. There are two other client contacts with whom the Northwind account team regularly engages - Client Contacts and Client Contact3.
BDM1 and the Northwind Traders account
BDM1 has been on vacation for two weeks. During vacation, BDM1 did NOT log into Dynamics 365, and BDM2 made the following updates to several open Northwind Traders opportunities.

BMD2 also scheduled an internal meeting with BMD1 for the day they return to discuss a request from the primary contact for the account The meeting has the "London office' opportunity as its regarding value.
Desired enhancements
The global sales lead requests the following enhancements:
1. A "Welcome' email should be sent to the primary contact (or an account when the account first enters any client tier. This email should only be sent to the primary contact once.
2. Account owners should receive immediate notifications in the assistant in Dynamics 365 Sales when accounts change tiers. The notifications should include the account name and current tier.
3. A "Getting started" email should be sent to the main contact associated with an opportunity when the opportunity status is set to "Won."
1. The email should include a link to a custom onboarding form where the contact can supply information required to start the janitorial services for a given location.
2. If the contact does NOT click any links in the email, a follow-up email should be sent
4. All emails between BDMs and client contacts should be available for relationship analytics KPIs. Emails sent by other users outside of Dynamics 365 should NOT be included in the KPIs.
The digital sales team lead requests the following enhancements:
1. The ability for team members to use Copilot to summarize changes to lead records.
2. Replace the current online form used by their team to capture new leads. The new form should automatically handle duplicates using the rules the team currently applies manually.