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

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

Happy to share what has worked for me. I would actually split your problem into two tools, because 'the forecast number' and 'what moved in the pipeline week-over-week' are best served by different native features: 

For WoW deal movement (your actual goal): before maintaining a custom snapshot, look at two native options that keep closed deals in the dataset: 

- Pipeline Inspection: its 'Changes Since' pipeline-changes waterfall shows exactly what moved between two dates, amount increased/decreased, stage changes, close-date pushes, and deals that closed Won/Lost. That is the week-over-week story you built the snapshot for, without the open-only fall-off (Enterprise+ with Sales Cloud). 

- Historical Trend Reporting (the 'Opportunities with Historical Trending' report type): natively snapshots Amount/Stage/Close Date daily for the trailing ~3 months and lets you compare across dates in one report, no custom object to maintain, and closed deals stay in the data. 

For the forecast number itself: Collaborative Forecasting (Forecasts tab) rolling up by forecast category (Pipeline / Best Case / Commit / Closed) against quota and role hierarchy. If you have Sales Cloud Einstein, Einstein Forecasting adds a predicted-to-land number and Opportunity Scoring to weight deal health. 

Methodology I lean on: Collaborative Forecasting for 'where will we land,' Pipeline Inspection or Historical Trending for 'what changed and why since last week,' and Opportunity Scoring to weight the pipeline. That combo answers WoW movement AND the landing number without hand-rolled snapshots. 

3rd-party, if native is not enough: the revenue-intelligence platforms, Clari, Gong Forecast, Aviso, Mediafly (InsightSquared),

, all do pipeline-change waterfalls, WoW deltas, and AI forecasting on top of your Salesforce data. Teams usually move to these when they want rep-level forecast submissions plus inspection plus analytics in one place. 

Honestly, if Pipeline Inspection is available in your edition, I would try its change view first, it may let you retire the custom Pipeline Growth Snapshot object entirely. 

If this helps, please mark it as the Best Answer so it is easy for the next person to find. Thanks :)

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:

Ran into this every quarter when we spun up regional copies of the same dashboard.

Save As gives you a new dashboard pointing at the old reports, which is almost never

what you want. 

What we did before: Save As on all the reports into the new folder, clone the

dashboard, then click through every component swapping the source. An hour if the

dashboard is big. 

I eventually built a Chrome extension to do it, copies the dashboard and its reports

and connects them up.

https://sf-report-manager.com/clone-salesforce-dashboard-with-reports.html

It's mine, so obviously biased. The manual route above is fine if it's a one time thing.

Hi Erick - the fact that a manual Excel export is clean but the subscribed one has a blank row under the header, everything shifted down one, and the last row dropped points squarely at the subscription's file generation, not your report or query. 

A few things to check / try: 

1. Groupings vs format: if this is a Summary report (grouped), the subscribed export often renders an extra structural/blank line that a plain export doesn't. Try a Tabular version of the same report (no groupings) as the subscription and see if the blank row and the shift disappear - that tells you the grouping rendering is the culprit. 

2. Subscription row handling: subscribed/attached results have their own limits and formatting, separate from a manual export, so a blank row consuming a slot can push your last row (row 3) off the end. That matches the 'shifted down + last one missing' symptom exactly. 

3. Confirm it's the platform: reproduce with a tiny 2-3 row report. If the blank-row-and-shift is consistent, this has the hallmarks of a known formatting quirk in subscribed report files rather than anything you configured - worth searching Salesforce Known Issues, and logging a case with the before/after files so Support can reproduce it. 

Workarounds if you need clean output now: 

- Subscribe at the Dashboard level instead of the report, or 

- Use an Analytic Snapshot / a scheduled data export, which don't go through the same subscribed-report formatting. 

If you can share whether the report is Tabular or Summary, and how the subscription is set up (attach results vs embedded), I can help narrow it down further. 

Hope that helps track it down!

Hi @Kathy Latiolais DeGlandon

Looks like this is due to Salesforce's new

).   

Salesforce began enforcing this in production on

to complete a step-up MFA challenge before the export completes. 

What to check/do 

1. Confirm the running user's MFA setup. Go to Setup → Users → find whatever user PeekLogic runs as (its named/integration user). Make sure it has a registered MFA verifier, or at minimum a valid email/phone for verification.
2. Look at Identity Verification settings in Setup for the "periodic step-up authentication for reporting/printing" toggle CertifyCRM points to — this is org-wide and worth knowing where it lives even if you don't disable it.
3. Ping PeekLogic support directly. Ask whether they've adapted their export logic to avoid tripping the anomaly model.
4. If it's blocking a business-critical monthly deliverable, this is legitimate grounds to log a case with Salesforce.

Hope this helps.