Portfolio Slicer Refresh Issues

Overview

If Portfolio Slicer does not refresh correctly, the cause is usually one of these:

  • report layout problems in Excel
  • data type or data quality problems in source tables
  • missing or mismatched external files
  • performance limits caused by workbook size, report design, or environment

This page focuses on the most common refresh-related problems and the checks that usually solve them.

Problem: “A PivotTable report cannot overlap another PivotTable report”

This error usually means one or more reports expanded beyond the space available on the worksheet.

Common causes include:

  • too many Account values
  • too many Allocation values
  • report filters being reset so the report returns much more data than expected
  • an invalid or future minimum date causing unexpected layout growth

What to Check

  1. Confirm that report-level filters were not reset to All.
  2. Review reports that are intended to stay filtered, especially time-based and transaction-heavy reports.
  3. Check whether your workbook now contains more categories than the report layout can comfortably handle.
  4. Confirm that MinDate is valid and not in the future.

Practical Notes

This error often appears on pages with many PivotTables close to each other. If one report grows unexpectedly, it can collide with the next one.

In practice, the quickest checks are:

  • look for report pages where slicers or filters were reset
  • review yearly, monthly, and transaction-heavy pages first
  • check whether a recent change caused many more rows than before to appear

What Usually Fixes It

  • restore worksheet or report filters to their intended values
  • reduce the number of visible rows returned by large PivotTables
  • reduce or reorganize excessive Account or Allocation categories if the layout cannot handle them

Problem: “AttributeID = TransID doesn’t exist”

This error usually means Portfolio Slicer could not load the Transactions table into the data model correctly.

Common Causes

  • the first special system row in Transactions was deleted or edited incorrectly
  • column values do not match expected data types
  • a date or numeric value cannot be interpreted correctly by Excel or Power Pivot in your local environment
  • one or more rows contain malformed values copied from another source

What to Check

  • confirm the first system record still exists if your version expects it
  • confirm the Transactions table is ordered properly if required by your workflow
  • check for invalid dates
  • check for text values in numeric columns
  • check decimal separator issues in your locale
  • check for accidental spaces or malformed values in important numeric fields

Practical Notes

If this error appears after editing the transaction table, start by checking the most recently added or pasted rows.

Also review the Excel table data entry page. Invalid dates, broken numeric values, or accidental blank rows inside the table are common reasons for refresh failure.

What Usually Fixes It

  • restore the required system row if it was removed
  • correct invalid dates or numeric values
  • re-check copied or imported transaction rows carefully
  • remove accidental blank or partially blank rows inside the table

Problem: Refresh Is Very Slow

Refresh time depends on:

  • number of symbols
  • number of transactions
  • number and complexity of reports
  • Excel version and environment
  • whether cash tracking and other heavier calculations are enabled

Large models will naturally refresh more slowly, but extremely slow refresh often points to an avoidable bottleneck.

Things to Try

  • make sure Excel is fully updated if you are using an older environment
  • reduce the number of large reports shown without filters
  • use selective refresh options where supported
  • test with smaller visible report slices before expanding filters
  • keep report filters on yearly or transaction-heavy sheets reasonably narrow
  • validate performance using a small baseline scenario first

Workbook Design Tips

Performance often improves when you:

  • keep rarely used reports filtered down
  • avoid showing unnecessarily large transaction result sets
  • validate one page at a time when troubleshooting
  • simplify the active report scope before assuming the model itself is broken

Troubleshooting Order

When refresh fails, this is a good order to work through:

  1. Confirm the external files exist and look valid.
  2. Confirm symbol and currency naming matches between Excel and external files.
  3. Review the Transactions table for invalid data.
  4. Review other workbook tables for invalid dates, empty rows, or wrong data types.
  5. Check whether reports are trying to display too much data.
  6. Try the refresh again after correcting the smallest obvious issue first.