#Reports & Dashboards132 debatiendo

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 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!

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.

This can be done by creating the below calculation, using LOOKUP() function:For now, both July and August are in the view just so you can see that July's data for Quantity now lives in August's 'date', as shown above.  But, we don't want to have to select two month's data at a time and yet, two month's of data MUST be in the view. somehow. 

So, we then change the Order Date filter that you originally had into again, a Relative Date filter, again displaying only most recent two months, as I did before:

Then, the question remains, how to show just the current month, but only with last month's data in the current month.  Again, another filter.  BTW, both of these are Table Calculations, so certain fields must be in the view somewhere in order for them to all function correctly and display correctly.  The new calculation will now filter the above result to only the last row in the view:

As to it being automatic and adjusting for next month, it should based on the Relative Date filter..it would automatically adjust to September and pick up August's data. And so on. 

If this response answered your question, please mark it as an Accepted Answer? 

This way, others searching for similar solutions will find the answer faster in the future.

Best, Don Wise (Tableau Ambassador)