#Reports & Dashboards108 debatiendo

I'm glad you're figuring this out. Your data and/or LOD calc needs to be cleaned up as it is not returning a single value per user (see image below). But to fix your user counts you need to change the CNT(User) on the License Matrix sheet to CNTD(User) to count distinct users.

DZV can only use static values, i.e. a parameter, or a { FIXED } LoD at the level of the workbook (no Dimensions). So, not all Boolean fields will show in the DZV selection. Filtering is also carried out too late, i.e. you can't apply DZV based on filters, so your COUNTD() > 0 won't work. 

I would switch your [Mission ID] filter to be a Set (then you'd have your worksheet filters as being in our out of that set, visually indistinguishable from a normal Dimension filter). For the DZV, because Sets are 'independent' (they don't inherently do anything like filtering) you could then have

{ FIXED: COUNTD( IF [Mission ID Set] THEN [Milestone Rank] END) > 0 }

Essentially, I'm moving your filtering inside the COUNTD, looking at every row of data and checking if the rows that match the Mission ID have a Milesone Rank. Across the entire dataset, it checks if that count is greater than zero, giving one, workbook level Boolean value. 

Having the > 0 inside the { } is important, but I never remember why. If you have { .... } > 0 you will not be given it as a choice in the DZV list of fields. 

@Nancy Cerkvenik

The "Campaigns with Campaign Members" standard report type will display a row in the results of a report for each Campaign Member record that meets the filter criteria - regardless of being related to a Contact or Lead. You'll have access to basic details about the member - name, title, company, email, phone, address. 

You can re-create the same configuration with a custom report type. Choose "Campaigns" as the primary object. Then on the second page, relate "Campaign Members" as object B using 'Each "A" record must have at least one related "B" record' option. If needed, edit the custom report type layout, click the "+ Lookup Fields" button, change "Fields Related To" to "Campaign Members" and traverse the Contact and Lead relationships to bring in more details from those parent records. I highly recommend organizing the Contact fields into their own section and the Lead fields into their own separate section to make it clear which object the field lives on (since many fields share the same label and API name).

We all start somewhere, and I think this is a good effort at making an interesting and structured dashboard, with your navigation being good, and your main page having a good number of KPIs, so not overloading the user. My points below are mostly based around deciding what the question is that you're trying to answer with each chart, but I think there are a few things wrong with individual elements, that you need to be careful of (especially Top N and the Order of Operations). Below is my (personal opinion) feedback, which you're welcome to ignore, should you so desire, sorry it's long. 

I find trend (line) charts that combine multiple years confusing. Your chart suggests an amazing trajectory of sales, no matter which year(s) you select. It doesn't illustrate that, every January, there is a catastrophic drop in sales (compared to December). In my opinion, your chart doesn't show a trend when you have all years selected, you're comparing "Octobers" (plural) with "Septembers" (and the other months), which is a discrete date comparison and I'd plot as a bar chart. It's only a trend when one year is selected, because then all the months are in sequence, but because you're only showing your users Jan to Dec, you're misleading them into believing that sales just keep going up and up. Your chart omits this line at the end of every year, which feels kind of important:

On your map, you've highlighted that Mongolia has the lowest sales at $£3.1K, but the mark on the map is NULL (no sales), and if I mouse over Papua New Guinea, it has sales of $1.9K, suggesting that after you've labelled the chart you've changed the filters. Make sure any annotations are correct, because they're pretty static

On your Performance per Sub Category chart, I don't know what a red bar and a green bar mean: it's not the size of the bar; if it's the profit margin, you have the number labels displayed as red (which you appear to be using to mean "bad"?), but against green bars (and is a profit margin of 15.3% "bad"? in the industry I'm in we'd bite your hand off for that). Equally, the actual profit from phones and accessories is about the same, so if the message you want to convey is about good versus bad profit margin, I'm not sure this chart makes that point clear. The main message of a chart shouldn't be one of the secondary preattentive attributes of a chart.

If I mouse over, I can deduce that it's the record count, but your user isn't told that anywhere. 

Finally (sorry), on your shipping delay hotspots, you have the same colour meaning multiple different values, becuase you're using a dynamic legend. If you change the year, the dark red means anything between 5 and 7 days, but visually, Pakistan in 2023 (5 days) is as bad as Cambodia in 2025 (7 days), despite Cambodia having 40% longer delays, on average. For this chart, I would use a static range, where anything beyond my target, e.g. 3 days, is red. As it stands, if the business was transformed, and the longest delay was 1 day, that would still be considered "very bad red".

Hi Deepak, 

Thank you for taking the time to answer. 

To answer your clarification, we need

, the latest Case per Account for each Campaign List Name. The same Service Account can take part in more than one campaign, and each campaign's report has to show that customer's latest Case within that campaign, even if they have a newer Case in another campaign.  

Two follow-up questions:  

1. Your reply seems to have been cut off after "You could raise it as:". Could you share the requirement wording you had in mind? 
    

2.  Since this solution also updates the previous Case automatically, is there anything we should ask our development team to check, so that it works reliably and doesn't affect our agents' daily work or other processes in general?

Thanks again, 

George 

Hi @Rupesh Mohare

Yes, the Report Type can affect the record count. It’s not simply because the standard report type contains multiple objects; the relationships and “with/without” settings defined in the report type can determine which Lead records are included. 

I would compare the standard and custom report types, especially their object relationships, standard filters, and filter logic. Also ensure the report and SOQL are running with the same user/access context. 

So, the 40 vs. 45 difference is likely related to the report type’s record scope/relationships, rather than SOQL returning incorrect data.  

Hope This Helps!!

Hi Lena, 

Yes, removing API Enabled would impact the Salesforce Mobile App, since the mobile app requires API access. So I wouldn’t use that permission alone as the control for this requirement.  

A better approach is to keep API access for the users who need Salesforce Mobile and use API Access Control to restrict API access to only approved/allowlisted connected apps. Salesforce supports this model specifically for limiting API access while allowing approved apps.  

For report extraction, also control the Export Reports permission separately. Removing that permission prevents users from exporting report data, while folder sharing and report/dashboard permissions can be used to restrict access to sensitive content. 

I’d therefore treat this as multiple layers: API Access Control + Report/Folder permissions + Export Reports + subscription/access controls, rather than disabling API access entirely.