#Reports & Dashboards100 人がディスカッション中

Hi, @Aviral Trivedi

Nice to meet you. 

I'm still relatively new to Tableau, but I hope a fresh perspective might be helpful. 

I'd like to share some feedback on the

dashboard. 

I liked the overall design. The Spotify theme makes the dashboard visually appealing, and using Spotify data immediately caught my attention because it's a topic many people can relate to. Also, it's impressive to see how dominant Taylor Swift is in the results. 

• I liked how the colors were aligned with the Spotify brand.
• The navigation using icons for Overview, Content, and Geographic was clear and easy to understand at a glance.

2. Chart Choices

• In the Content page, I wasn't entirely sure what the crosstab was intended to show.
• On the Overview page, I also found the Trend Line difficult to interpret. It wasn't immediately clear what insight I was supposed to take away from it.

3. Navigation / Drill-Down Flow

• The overall navigation and filters were intuitive and easy to use.
• One thing I felt was missing was more interaction between charts. I would have enjoyed being able to click on a category or value and explore the data in more detail.

4. Anything That Feels Unfinished

• The "Trend Line of Plays by Month" appears almost completely flat, so at first I wondered whether the visualization was still a work in progress or whether the underlying values genuinely have very little variation.

Overall, I enjoyed exploring the dashboard. Thanks for sharing it! 

Hi Fletcher, 

Standard Lightning report scheduling (Subscribe) does not have a Start/End date option like Classic does. Per official Salesforce docs, the Lightning Subscribe flow only lets you set a frequency, delivery time, recipients, and optional conditions, there's no field to specify a schedule end date:

Workarounds: 

- Keep using Classic Schedule Report for reports that need a hard end date. Classic and Lightning subscriptions can coexist, this isn't deprecated. 

- In Lightning, manually delete/unsubscribe the report subscription once the period ends 

- Use Scheduled Flow or Scheduled Apex to programmatically delete the report subscription record on your target end date, if you want it automated 

Reference for Classic scheduling with Start/End (for comparison):

No native Lightning equivalent exists yet for the End Date field specifically.

Hi @Chirag Chakraborty

This is expected behavior with "with or without related records" report types not a bug or misconfiguration. 

Why it happens: When A has no related B records, the join still produces one result row for that A record (with all B fields null), so it counts as 1 in the grouped subtotal. The report is counting rows, not counting non-null B records. 

• Instead of subtotaling on a generic count, subtotal on a specific B field (e.g., B's Record ID or Name) using Record Count in the summary. Some report builders let you choose "Row Count" vs count-of-a-field - count of a specific child field still won't fix it directly, since Salesforce's summary "Record Count" always counts rows, not non null field values.

The more reliable fixes: 

1. Add a filter: B: ID not equal to blank - this excludes the phantom join rows entirely, so A records with zero children don't appear in the grouped count at all (they'll simply be absent, not shown as 0).
2. If you need to see A records with zero B's explicitly (shown as 0, not omitted): standard reports can't easily distinguish "1 phantom row" from "1 real row" in the subtotal you'd need a workaround like a formula field on B that always evaluates true when B exists, then summarize that formula field instead of raw Record Count.
3. Alternative: build this as a matrix report or use a roll-up summary field on A (Count of B) if this is a recurring need a roll-up avoids the report-join ambiguity entirely and gives you a real 0 when there are no children.

Quick check: filter your existing report to A.Id is not null AND B.Id is not null and compare subtotals if the inflated total drops to the correct count, that confirms this is the phantom row cause.