#Reports & Dashboards120 diskutieren mit

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.

Hello @Donna McKell

You can create two separate filters on the Order Expected Date field and combine them using Filter Logic. 

- Open your report in the Edit mode and go to the Filters pane. 

- Add the first filter for your start date: 

   Field: Order Expected Date 

   Operator: greater or equal (which handles the "inclusive of each" requirement) 

   Value: 01/11/2026 

- Add the second filter for your end date: 

   Field: Order Expected Date 

   Operator: less or equal (inclusive of the end date) 

   Value: 31/01/2028 

- Click Add Filter Logic (underneath the filters list). 

- Enter the logic combining both filter numbers with an AND operator: 

  Example: 1 AND 2 

- Click Apply, then Save and Run your report.

You are on the right track - what you sketched IS the pattern, and the feature is Reporting Snapshots (Setup, Reporting Snapshots). Stage Duration is a live days-in-current-stage value that Salesforce does not historize, which is why Opportunity Trends only ever shows today's number. Snapshots let you capture it on a schedule and trend it yourself: 

1. Source report: a tabular or summary report of open opportunities with Stage and Stage Duration, filtered to open. 

2. Target custom object: create one with fields mirroring the columns you want to keep, plus a Snapshot Date field. 

3. Reporting Snapshot: map the report columns to the custom object fields and schedule it daily or weekly. Each run writes point-in-time rows stamped with the run date. 

4. Trend report: build it on the custom object - Group Columns by Snapshot Date, Group Rows by Stage, summarize Average of Stage Duration. Exactly the matrix you described. 

Two caveats: snapshots only capture going forward (no backfill for dates before you start), and each run loads up to 2,000 rows, so keep the source filtered to open opps. Historical Trending is the other option but it is limited to a few fixed fields and about 3 months and does not cover Stage Duration well, so Snapshots are the right tool here. 

if this helps, please mark it as the Best Answer so it helps the next person - thanks 🙂

1. On the Reports tab, click New Folder.
2. Name the folder. The folder name must be unique across all report and dashboard folders.
3. Click Save.

Hi @Courtney Smith, 

 I’d first check the “View My Team’s Dashboards” permission. Without it, the Change option for “Viewing As” may not be available. Also verify that the dashboard is configured to Let dashboard viewers choose whom they view the dashboard as .  

Thank You.