Migration to Portfolio Slicer v3.x from v2.x

Release Summary

Portfolio Slicer v3.1.0 was released on 2023-02-12.

This release is important because it clarifies the current v3.x architecture and support direction.

Key Release Notes

  • Portfolio Slicer v3.x is intended for Excel 2016 or later.
  • Excel 2010 and Excel 2013 are not the supported path for v3.x.
  • Portfolio Slicer v3.1 does not support generated dividends.
  • The AccruedInterest column remains in Transactions, but is no longer used in calculations.
  • v3.x split the old all-in-one workbook model into separate source and report workbooks.
  • a lighter report workbook is included for faster refresh and lighter usage scenarios.
  • symbols can now be assigned to more than one allocation through the SymbolAllocation table.
  • many DAX formulas were updated.
  • the scripts now include support for reading source workbook data and extracting it into the PSData folder.
  • psConfig.txt includes an ExcelSourceFile section for the source workbook path.

What Changed Architecturally

One of the biggest changes in v3.x is that source tables and reports are no longer bundled into a single workbook in the same way older versions used.

Instead:

  • source data lives in the source workbook
  • report workbooks consume extracted data files
  • multiple reporting workbooks become easier to support
  • lighter report variants can refresh faster than full report workbooks

This makes upgrades and report distribution more flexible, but it also means migration from older versions requires more care.

Migration Notes

If you are moving from an older version to v3.1.x, the practical process is:

  1. back up your old files
  2. install the new version separately
  3. copy table data from the old workbook into the new source workbook carefully
  4. review psConfig.txt, especially PSDataFolder and ExcelSourceFile
  5. run the external data scripts
  6. refresh the new report workbooks and validate the results

Important Reminders for Upgrades

When migrating to v3.x:

  • do not assume workbook tables are identical across versions
  • compare columns before copying data
  • validate the new setup with a small number of reports first
  • treat the first migration as a controlled transition, not a simple file replacement