Salesforce Exam CRT-211 Topic 7 Question 83 Discussion

Actual exam question for Salesforce's CRT-211 exam

Question #: 83
Topic #: 7

Cloud Kicks uses a dashboard with multiple components based on Account, Case, and Opportunity reports. The system administrator adds a dashboard filter on Account Owner. When filtering the dashboard by Account Owner, records are now missing from several Opportunity components.

What is the recommended way for the system administrator to resolve this issue?

AAdd a cross-filter to the Opportunity source reports.

BUse a custom report type for Accounts with or without Opportunities.

COn the Opportunity components, change the equivalent field.

DCreate a joined Accounts and Opportunities report for the components.

Show Suggested Answer

Suggested Answer: C

The equivalent field is the field that matches the dashboard filter field on the source report object. For example, if the dashboard filter is on Account Owner, then the equivalent field on the Opportunity object is Opportunity Owner. Changing the equivalent field ensures that the dashboard filter applies correctly to the Opportunity components. Reference: https://help.salesforce.com/s/articleView?id=sf.dashboard_filters.htm&type=5

by Dorothy at Feb 09, 2024, 03:22 AM

Limited Time Offer

25%

Off

Get Premium CRT-211 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Paz

6 months ago

Personally, I'm leaning towards option A. Cross-filtering is a classic solution for this kind of issue. Plus, it's the most '90s-sounding option, and we all know the '90s were the golden age of dashboard design.

upvoted 0 times

Mary

5 months ago

Yeah, I agree. It's a classic solution and it sounds like it would work well in this situation.

upvoted 0 times

...

Maxima

5 months ago

I think option A is the way to go. Cross-filtering should fix the missing records.

upvoted 0 times

...

Selma

6 months ago

Creating a joined Accounts and Opportunities report for the components could also be a good way to resolve the issue.

upvoted 0 times

...

Elsa

6 months ago

I believe changing the equivalent field on the Opportunity components might be the best solution.

upvoted 0 times

...

Nina

6 months ago

But wouldn't using a custom report type for Accounts with or without Opportunities also work?

upvoted 0 times

...

Kimbery

6 months ago

I think the system administrator should add a cross-filter to the Opportunity source reports.

upvoted 0 times

...

Jennie

6 months ago

Hold up, why not just create a joined Accounts and Opportunities report for the components like in option D? Seems like that would do the trick.

upvoted 0 times

Levi

5 months ago

I agree, let's go with option D.

upvoted 0 times

...

Glory

5 months ago

Yeah, that sounds like a good solution.

upvoted 0 times

...

Colton

5 months ago

I think creating a joined Accounts and Opportunities report could work.

upvoted 0 times

...

Eura

6 months ago

I agree with Glory, adding a cross-filter seems like the best option here.

upvoted 0 times

...

Daisy

6 months ago

Using a custom report type for Accounts with or without Opportunities in option B seems like a clever workaround. I might give that a shot.

upvoted 0 times

...

Jacklyn

6 months ago

Hmm, I'm not sure about that. Changing the equivalent field on the Opportunity components in option C sounds like it could be worth a try.

upvoted 0 times

Brigette

6 months ago

Creating a joined Accounts and Opportunities report for the components in option D might be the best solution.

upvoted 0 times

...

Devora

6 months ago

Maybe adding a cross-filter to the Opportunity source reports in option A could also help.

upvoted 0 times

...

Carmelina

6 months ago

Maybe adding a cross-filter to the Opportunity source reports in option A could also help.

upvoted 0 times

...

Detra

6 months ago

I think option C could work, changing the equivalent field on the Opportunity components.

upvoted 0 times

...

Tess

6 months ago

I think option C could work, changing the equivalent field on the Opportunity components.

upvoted 0 times

...

Delsie

7 months ago

I think B) Use a custom report type for Accounts with or without Opportunities might work too.

upvoted 0 times

...

Kattie

7 months ago

I think option A is the way to go. Adding a cross-filter to the Opportunity source reports seems like the most straightforward solution.

upvoted 0 times

Ezekiel

6 months ago

D) Create a joined Accounts and Opportunities report for the components.

upvoted 0 times

...

Delmy

6 months ago

C) On the Opportunity components, change the equivalent field.

upvoted 0 times

...

Sherrell

6 months ago

A) Add a cross-filter to the Opportunity source reports.

upvoted 0 times

...

Phillip

6 months ago

That makes sense, it's a direct solution to the problem.

upvoted 0 times

...

Nieves

7 months ago

I agree, adding a cross-filter to the Opportunity source reports should fix the issue.

upvoted 0 times

...

Marica

7 months ago

I disagree, I believe the solution is D) Create a joined Accounts and Opportunities report for the components.

upvoted 0 times

...

Glory

7 months ago

I think the answer is A) Add a cross-filter to the Opportunity source reports.

upvoted 0 times

...