MB-280 Exam Dumps : Microsoft Dynamics 365 Customer Experience Analyst

The correct order of actions to create a new custom account plan table with a hierarchical parent-child relationship visualization is as follows:

Create a new account plan table.

Create a 1

self-referential relationship and mark the relationship as hierarchical.

Open the advanced Relationship settings.

Go to the Hierarchy Settings grid view.

Step by Step Comprehensive Detailed Explanation with ALL Microsoft Dynamics 365 References:

Create a New Account Plan Table:

To model account plans for subsidiaries and manage the parent-child relationships, start by creating a new table (entity) named " Account Plan. "

This table will store information related to the account plans, and you can define custom fields and settings as needed.

Dynamics 365 Sales, Define and track your sales goals

Define rollup queries

Rollup queries are used to define the records that should be included in the goal rollup. Rollup queries are created for each goal rollup field. For example, you could create a goal metric that measures all invoices closed within a specific period. You could then create a rollup query to show invoices that are owned by a person, or raised for customers in a territory.

Goals roll up from the bottom of the goal hierarchy to the top, with Dynamics 365 rolling child goal totals into their parent goal totals. Goals at the top of a hierarchy reflect a summation of all the goals in the organization.

You can only query one entity type in a query, but the query builder helps you make a query as simple or as complex as you need. As you fine-tune your query, you can test the results.

Incorrect:

Not B: Define rollup fields

Rollup fields are used to calculate the actual and in-progress values for a goal metric.

Not D: Set goal metrics

Goal metrics let you define how a goal will be measured. For example, a sales team ' s performance can be measured based on the number of leads they get or the revenue amount.

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.

References from Microsoft Documentation:

For guidance on setting up duplicate detection jobs and rules, refer to Detect duplicate records in Dynamics 365.