You have added the timeline control to the Pet main form, then saved and published your changes. You need to configure the timeline to display related Pet activities as required by Terra Flor
a. Which two actions should you perform? Each correct answer presents a complete solution. Choose two, NOTE: Each correct selection is worth one point.
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 the Posts option 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 E deals with the display format of notes but does not restrict their visibility, which does not align with the requirement to exclude posts specifically.
Reference from Microsoft Documentation:
You are the Dynamics 365 Sales administrator for an electronics company.
The sales team is having difficulty locating different products in the same category - for instance; all versions of flat screen TV available.
You need to make it easier for the sales team to navigate through products via taxonomy.
What should you use?
Product families allow you to group related products under a common category, making it easier for the sales team to navigate and find products within the same category, such as all versions of flat-screen TVs.
By using Product families, you can organize products into a hierarchical structure that reflects their categorization, enabling sales users to browse and select items more efficiently within Dynamics 365 Sales.
Using product families, you can streamline the user experience and improve navigation within the product catalog by grouping similar products together, which simplifies the search process for sales teams.
You need to build a trigger-based journey to send the "Getting started" emails requested by the global sales lead. Which trigger should you use to start the journey?
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 Reference:
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.
The analytics team at your organization has created Power Bl reports that enrich data about your accounts from Dynamics 365 Sales with data NOT contained in Dynamics 365 Sales. The Power Bl reports are referenced by your executive leadership as the primary source of truth about account success metrics. Sales leadership has requested that sales users can see these insights about the accounts they have access to within Dynamics 365 Sales. You need to enable the insights to be available to sales users in Dynamics 365 Sales. What should you do?
To make Power BI insights available within Dynamics 365 Sales, specifically contextualized for accounts, you should embed the Power BI report with contextual filtering. This ensures that the report dynamically adjusts based on the specific account record a user is viewing.
Embedding with contextual filtering enables sales users to see account-specific insights directly within the Dynamics 365 interface, improving accessibility and relevance.
You need to identify the duplicate pet records, so they can be manually merged by the carer. What must you create?
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.
Reference from Microsoft Documentation:
Tammi
14 days agoLizbeth
1 months agoLeila
2 months agoMerri
3 months agoAdaline
3 months agoLindy
4 months agoCassie
4 months agoMozelle
5 months agoRebbecca
5 months agoJeniffer
5 months agoLawanda
6 months agoCandra
6 months agoAgustin
7 months agoLacresha
7 months agoJaclyn
7 months ago