#Reports & Dashboards103 debatiendo

Hi folks, 

I think it was a problem with Scheduled Jobs - I'm not sure what got weird in there, but I deleted the relevant ones and after 24 hours he isn't receiving the error anymore. 

Thanks, 

Erica

Hi C B - you've diagnosed it exactly: the snapshot filters to open-only, so closed deals fall out and a WoW comparison can't tell a win from a loss from an aged-out row. Here's the pattern for all three questions. 

Q1 - extend capture for recently-closed deals: change the snapshot source criteria from 'open only' to 'open OR closed in the last N days'. If you snapshot with a scheduled Flow, filter the Get Records to IsClosed = false OR CloseDate >= TODAY() minus 60. If you use a native Reporting Snapshot, set the source report filter to 'Closed = false OR Close Date = LAST N DAYS:60' (filter logic 1 OR 2). Recently-closed deals then keep getting captured through the trend window and naturally age out once their close date passes 60 days - so you get WoW continuity without hoarding every closed deal forever. 

Q3 (the important one) - flag win vs loss from the snapshot alone, no live lookup: capture the disposition ON each snapshot row at capture time. Add IsClosed and IsWon checkboxes to your Pipeline Growth Snapshot object and populate them when you write the row - or a small formula field 'Disposition' = Open / Won / Lost derived from the captured Stage. Because it's stored on the snapshot, the report reads it directly - no cross-object lookup to the live Opportunity Stage needed. Then bucket/group the WoW change by that captured disposition, so a deal that drops out because it was Won is categorized as a win, and only a genuine Closed Lost shows as a real pipeline decrease. 

Q2 - native Historical Trend Reporting: it does not have the drop-out problem (it retains a deal's history for the retention window whether or not it closed), so it's worth a look. The trade-offs: it's limited to a rolling retention window (default ~3 months, configurable), tracks only up to ~5 fields, and the 'Opportunities with Historical Trending' report type/format is fairly rigid (matrix, a handful of snapshot dates). Great for 'what did this deal look like X weeks ago', but for bespoke WoW logic plus longer retention the custom object is more flexible - once you fix the source filter from Q1. So use HTR if 3 months and its report format is enough; otherwise keep your object and just widen the capture criteria and store the disposition. 

Net: widen the source filter to include recently-closed deals, and stamp IsWon/IsClosed (or a Won/Lost/Open formula) onto every snapshot row - that combination kills the phantom drop and lets the report separate wins from losses with no live lookup. Hope that helps!

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.

Same issue, even tried Rename Tabs and label but there is no Prospect rating or Rating. 

Hey Nupoor, 

Great that you're looking to give back, a few solid places to start: 

1. Complete the "Pro Bono Basics for Salesforce Professionals" trail on Trailhead first, it's specifically designed to prepare volunteers like you and helps you figure out where your skills fit best before you commit to a project 

2. Salesforce's Impact Exchange (evolution of the old Pro Bono Program) is the main channel connecting volunteers with nonprofits/educational institutions looking for Salesforce help, worth checking there directly 

3. This community group itself (

Opportunities) is actively used by nonprofits posting real project needs, keep an eye on new posts here, and don't hesitate to post specifically saying "1.5 years experience, AI certified, available for X hours/week" since specificity gets more responses than a general intro post 

4. Join your local Nonprofit or Higher Ed Trailblazer Community Group, a lot of pro bono matching happens informally through these local meetups rather than a central job board 

5. Since you're AI certified specifically, mention that clearly when reaching out, nonprofits are increasingly interested in Agentforce/AI use cases but very few volunteers have that skill yet, it's a strong differentiator for you right now 

One tip: many nonprofits prefer volunteers to have (or be working toward) the Nonprofit Cloud Consultant certification, not required to start volunteering, but worth knowing if you want to specialize in this space long-term. 

Reference: