* 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.
Reference: Microsoft Documentation - Create Unit Groups and Units
Benefits of Using the Lowest Needed Unit:
Configuring the base unit as the smallest measurable unit enables flexibility and supports various sales scenarios without restrictions. It simplifies the management of units and ensures that other unit variations align correctly in the product catalog.
By setting the base unit to the lowest quantity needed to sell the product or service, you establish a robust foundation for building out the unit group and accommodating different sales quantities in Dynamics 365 Sales.

Explanation:

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] Reference:

Requirement Analysis:
The organization is collecting lead data from two sources: a web form created in Customer Insights - Journeys and manual entries by sales users. This setup could lead to duplicate entries if a lead is submitted through the web form and then entered manually by a sales user afterward.
To ensure data integrity and avoid duplication, it is essential to implement a mechanism that identifies and manages duplicates automatically.
Solution - Enabling Duplicate Detection:
In Dynamics 365, duplicate detection can be configured to alert users or prevent the creation of records that already exist based on certain criteria (such as email).
By enabling duplicate detection based on email addresses, the system will compare incoming lead data with existing records and prompt users if a duplicate is identified. This feature will ensure that leads collected from different sources are not duplicated unnecessarily.
Steps to Enable Duplicate Detection for Leads Based on Email:
Navigate to Settings > Data Management > Duplicate Detection Rules in Dynamics 365.
Create a new Duplicate Detection Rule for the Lead entity. Specify that the system should check for duplicate records based on the email field.
Publish the rule and ensure it is activated.
After activation, this rule will prompt users whenever a duplicate email is detected, either from the Customer Insights - Journeys web form or manual entry by sales users.
Reference:
Benefits of Using Duplicate Detection:
This approach does not restrict users from creating leads but ensures that duplicate entries are flagged, allowing users to review and decide whether to proceed.
It maintains data cleanliness by preventing unnecessary duplicates while ensuring all valid leads are captured from different sources.
By implementing this solution, the organization can effectively manage potential duplicate leads, keeping the data clean and accurate across both Customer Insights - Journeys and Dynamics 365 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.