Here’s the correct sequence to configure a new Customer Insights - Journeys form to handle lead duplicates automatically, as per the requirements:

Create a new form:

Start by creating a new form within Customer Insights - Journeys. This is the initial step to set up a form that will capture new leads.

Select a form template:

Choose a template that best fits the purpose of the form. This provides a structure for the form fields and layout, streamlining the setup process.

Set the form target audience to leads:

Since the form will be capturing lead information, specify that the form’s target audience is “leads.” This will ensure that the data is processed and stored as lead records.

Set the form duplicate records strategy to the audience default strategy:

Define how duplicate records are managed. First, apply the default duplicate record strategy for leads. This sets an initial strategy for managing duplicates.

Publish the form:

After completing the setup and configuring the necessary options, publish the form to make it available for use.

Additional Context:

The Create a custom matching strategy and Set the form duplicate records strategy to the custom form matching strategy steps are optional and can be used for further refinement if the default strategy does not meet specific requirements for matching leads based on certain criteria.

By following these steps, you ensure the form is configured for capturing leads and manages duplicates effectively based on the default duplicate record strategy.

Microsoft Dynamics 365 References:

Set up a Customer Insights - Journeys form

Duplicate Detection Rules in Dynamics 365

To enable the digital sales team's request to use Copilot for summarizing changes to lead records, you need to ensure that they have the necessary permissions and access to the required features. Here’s how to proceed:

Assign the Sales Copilot User Role:

Dynamics 365 Copilot in Sales is a feature that assists users by providing insights and summaries based on data within the system.

To allow the digital sales team to access and utilize Copilot's capabilities, they must have theSales Copilot user roleassigned. This role enables users to interact with Copilot and benefit from its AI-driven functionalities such as summarizing changes and insights in records.

Microsoft Documentation Reference:Dynamics 365 Sales Copilot Setup

Grant View Audit History Permissions:

TheView Audit Historypermission is essential for team members to access audit logs, which is necessary for reviewing and summarizing changes made to lead records.

Enabling this permission will allow the digital sales team to view a history of modifications in lead records, thus allowing them to generate summaries based on this audit trail.

The View Audit Summary permission specifically lets them see summaries of audit data, which complements Copilot’s functionality by allowing Copilot to access detailed change history for summarization.

Microsoft Documentation Reference:Security Roles and Privileges

By implementing these two actions, the digital sales team will have both the necessary access to Copilot features and the required permissions to audit lead record changes, enabling them to leverage Copilot for summarizing changes to leads effectively.

The timeline control in Dynamics 365 allows users to view and interact with activities, notes, and posts associated with a record. To meet Terra Flora’s requirements for displaying specific activities, you need to customize the timeline to show only certain activity types.

Removing All Other Activity Types Except Task, Email, and Phone Call (Option B):

According to Terra Flora's requirements, only Tasks, Emails, and Phone Calls should appear in the timeline for Pet records. Therefore, removing all other activity types ensures that only the relevant activities are shown. This customization is achieved in the timeline settings by unchecking unnecessary activity types.

Unchecking the Posts Option (Option C):

Since Terra Flora specified that posts should not appear on the timeline, you should uncheck thePostsoption under the Record types settings in the timeline configuration. This action removes posts from the view, aligning with Terra Flora’s requirement to exclude posts from the Pet records timeline.

Other Options Explanation:

Unchecking Notes (Option A)would prevent users from adding or viewing notes, which Terra Flora requires.

Unchecking the Activities Option (Option D)would disable all activities on the timeline, which does not meet Terra Flora’s needs as they require Task, Email, and Phone Call activities.

Option Edeals with the display format of notes but does not restrict their visibility, which does not align with the requirement to exclude posts specifically.

References from Microsoft Documentation:

For configuring and customizing the timeline control, refer toCustomize a timeline controlin Dynamics 365 documentation for detailed steps on modifying timeline settings and activity visibility.

Start Auditing:

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

In Dynamics 365 Customer Insights - Data,primary key attributesmust uniquely identify records and be consistent across the data source.

Whole NumberandGUIDare commonly used data types for primary keys because they can uniquely identify records and are natively supported for primary keys in databases.

Stringcan also be used as a primary key if it uniquely identifies each record (e.g., an email address).

IntegerandBooleanare generally not used as primary keys in Customer Insights because they may not provide unique identifiers suitable for all scenarios.

 Server-side synchronizationtypically syncs atequal 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.

Manager on System User Record:

Suggested contactsin Teams can include users directly linked to the individual starting the chat. Themanagerassigned on the user’s system record can be a suggested contact, as this is a common relationship that suggests frequent communication.

Record Owner of the Initiating Record:

Theowner of the recordbeing discussed or acted upon is also likely to be a suggested contact. This is because the owner has primary responsibility for the record and would commonly need to be consulted or informed about actions related to it.

Created By of the Initiating Record:

If the user is theCreated Byfor a record, they are associated with its initial setup or creation. As a result, they may be suggested when actions on that record are taken since they are familiar with its origins.

 Enable Mailboxes:

To use the Dynamics 365 App for Outlook, each user’s mailbox must be enabled for server-side synchronization. This ensures that emails, appointments, and tasks can sync between Outlook and Dynamics 365.

Without enabling the mailboxes, the synchronization won’t be functional, making it a critical prerequisite.

 In Dynamics 365 Sales, when setting up aunit group, you must first define thebase 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 abase 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.