In Dynamics 365 Customer Insights, during the unification process, the primary key must be unique for each record. The following data types can serve as a primary key:
Whole Number: Whole numbers are frequently used as primary keys, particularly when generated as sequential values.
String: Strings can be used as primary keys, especially when they represent unique values, such as codes or identification numbers.
GUID: A Globally Unique Identifier (GUID) is commonly used as a primary key in systems like Microsoft Dataverse, ensuring a unique value for each record.
Other options like Integer are not typically used independently of the Whole Number data type, and Boolean values cannot serve as primary keys since they can only have two possible values (True/False), which would not meet the uniqueness requirement for identifying records.

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:

* Changing the opportunity to an inactive state allows for the calculation of business process flow duration values, as this state transition prompts the system to finalize any duration metrics associated with the process flow.
* Business process flows calculate duration upon completion or transition of the process, so marking the opportunity as inactive triggers the system to calculate these durations.

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

When configuring suggested contacts for a new connected chat in Dynamics 365, the following user roles can be utilized as rules for suggesting contacts:
The user assigned as your manager on your system user record: This is a logical option, as it allows the system to suggest contacts that are in the user's direct reporting line.
The Record Owner of the initiating record: This user is directly associated with the record being discussed or worked on, making it relevant for suggestions.
The Created By of the initiating record: The creator of the record may also have pertinent insights or context about the record, making them a suitable candidate for suggestion.