The historical prices for this fund seem to be 100x what they should be (~£320 instead of ~£3.20). I’ve tried changing the currency to GBX (Penny Sterling), but that still has the historical prices at 100x their true value (~32k GBX).
Capitally is showing me 99% losses for my holdings of this fund because of this!
This appears to be a recent error, as I’ve been using this asset in Capitally for a while and the historical prices have been correct all previous times I’ve looked (i.e. up until some time in the last week).
One more thing I also noticed is that the asset price page is using the currency symbol for Polish złoty (zł) - see screenshot. Not sure if that’s relevant.
Thank you, I’ll check as it seems that the data provider switched the currency mid-flight
I’ll need to protect the system from this happening in the future…
IN the meantime, you can try clearing the data cache (Settings → Analysis → Clear), so the prices are fetched again. They should do it automatically in such case, but clearly didn’t. Let me know if it helped.
The “zł” on the chart is a bug - I’ll fix it as well.
I’ve reset the asset’s history and it should be fine now. It should be enough you refresh (eg. via browser or from the top-right menu), but if not, then reset the cache again.
Hi again, I’m bumping this old thread because I’ve hit the same problem with a different asset now: GB00B7KVX245 (ASI Global Smaller Companies Fund Platform 1 Accumulation).
This fund got delisted a few months ago so there’s no discrepancy between historical and current prices this time, but the prices shown are still 100x higher than they should be.
When I held this fund in the past past, I recorded trades in Capitally with prices around 1.80 GBP (looking through my broker’s dealing history shows these same prices).
Capitally recently started showing the historical prices of this fund as ~180 GBP, which is affecting the profit/loss numbers for my portfolio.
Sorry to be awkward, but another one has just popped up today since I last commented: GB00B0ZJ5S47.
It’s another delisted fund, but interestingly, I only marked it as delisted in Capitally this morning and the pricing issue seems to have appeared afterwards. I probably marked the previous fund as delisted a few weeks ago after the 1.48.0 update and the pricing error appeared shortly after that too.
Is there any chance that marking an asset as delisted is somehow causing this?
To test the reverse, just now I’ve tried unchecking the “Mark as delisted from exchange” option and clearing the data cache, but it’s not resolving my issue.
No, it’s not. This marking is there for you to acknowledge that the prices won’t be updated anymore (both so you know something is delisted, but also to quickly find any data issues).
Data provider is constantly shifting between their own data providers, looking for the best source, but it looks like they sometimes loose control over GBP/GBX pricing. I’ll let them know.
