Known Portfolio Slicer Limitations

Overview

Portfolio Slicer is flexible and powerful, but it does have important limits. Understanding those limits early helps avoid confusion during setup and ongoing use.

Current Limitations

Maximum Reporting Currencies

Portfolio Slicer supports up to three reporting currencies.

If your workflow requires more than three reporting currencies, Portfolio Slicer will not be a good fit without custom changes.

Cost Basis Complexity

Cost basis calculations have known limitations in some complex transaction histories.

In particular, if a symbol is sold partially many times between complete disposals, the built-in cost basis logic may produce results that require manual review or an override-based workaround.

If cost basis accuracy is critical for your workflow, review the dedicated guide:

How to track cost basis

Legacy Excel Behavior

Some older version-specific documentation describes behavior related to Excel 2010 and Excel 2013, including limitations around changing external data locations.

Those topics are mainly relevant for legacy users and should not be treated as the primary path for new Portfolio Slicer installations.

Practical Advice

Portfolio Slicer works best when you:

keep symbol naming consistent across Excel and external files
validate data gradually instead of loading everything at once
review unusual cost basis scenarios carefully
keep backups before major changes or upgrades

If You Need a Workaround

For difficult cost basis scenarios, one documented workaround is to calculate values externally in Excel and populate override fields rather than relying only on the default built-in logic.

See the detailed discussion in:

How to track cost basis