I don’t follow - the historical quote feed in the server response from Yahoo is still in GBX.
If I change the security to GBP to match the latest quote, that will have the opposite problem, and make all historical quotes incorrect? (But the latest would now be correct)
I actually think both the latest and historical prices are in still GBX, and the issue relates to dodgy, well suspect Yahoo json streams, which for some reason now incorrectly informs that the currency for this data is GBP (as indicated in the pic posted by @masterjonny above)… time I moved to another provider!!
Incidentally @masterjonny, if you would instead prefer to continue using Yahoo there’s always the option of pulling in latest quote via the ‘table on website’ method. In terms of that particular L&G fund you would do this by clicking on the ‘latest quote’ tab, selecting ‘table on website’ as the provider then entering ‘Yahooist Teil der Yahoo Markenfamilie’
I actually think both the latest and historical prices are in still GBX
It looks like latest is coming back with the GBP currency code, and GBP price.
I actually wonder if this is intentional from Yahoo as it matches the website behaviour, where the front page with the latest quote is in GBP, but the charting and historical data is still in GBX
If the Yahoo quote pages are powered by the same API that PP is scraping, this might be a deliberate design change on their part so that the value is rounded in the main price, but the higher resolution GBX data still exists for charting and historic prices.
time I moved to another provider!!
Agreed!
Yahoo also did this in February, and rolled back the change a few days later. I’m hoping they do the same this time…
always the option of pulling in latest quote via the ‘table on website’ method
I had no idea that was an option - thanks so much for the pointer!
Yep, big thanks for pointing out that really handy feature.
I’ve got an immense dislike of seeing stuff in GBX and I know now that if I apply a factor of ‘0.01’ this can be converted into GBP - this is like an early Xmas Present !!
I appears as if Yahoo finance has now changed from pence to pounds sterling GBp to GBP, and updated historical tables to reflect this… This totally mucks up the portfolio performance calcs. It doesnt appear to be possible to change the security denomination from pence to pounds once trades have been made within ‘portfolio performance’… Thus a large proportion of all of my securities and trades are now wrong. Any suggestions on how to correct this without starting from scratch with each security?
I would hold fire for a few days to see if they roll it back like the last time this happened, before putting a load of effort in.
A simpler method than redoing the transactions I was going to take is:
rename the current security to append something like GBX on the end
remove the online quote provider
historical prices will still be accurate if you don’t update them
correct the last 2 days or so by hand
sell this entire security
add a new duplicate security for the same fund/stock with online quotes enabled
buy the new one for the identical price and units, just in gbp
This will save having to redo the transactions, so hopefully be much less effort. I have some securities on monthly investments spanning back to 2015, so redoing the transactions is a deal breaker for me.
The downside is this will mess up the IRR calculation for the security, if that’s important to you.
Thanks for sharing the issue - which I’m having as well. Like the idea of “do nothing” and it will fix itself eventually. Otherwise just have some dummy trades to switch between the different versions of the security. Wondering if there are any other options e.g. better data source then Yahoo Finance. There seem to be so many in PP. Also as shown above in German there are these two tabs “Historical Quotes” and “Latest Quotes” - how is one meant to use this? Not sure how to go about getting the JSON URL etc?
I’m a little bit less optimistic about Yahoo returning to delivering GBX. Rather than not be able to use Portfolio Performance I converted those instruments in my portfolio that used Yahoo to use Morningstar using the mechanism that is carefully described in the manual here:
It is a bit fiddly, but with some care I found that it took me a couple of minutes per instrument and works well. If Yahoo do revert then I might revert too but in the meantime I’ll continue with Morningstar.
Fabulous… A solution…
I also think that Yahoo finance are not going to change this back, so the solution you highlight is perfect, as it moves to an alternative data provider, which is much less likely to muck around with pounds and pence again.
To summarise the solution:
Change from Yahoo Finance to Morningstar data.
Use the link provided by JohnBates to follow instructions on creating the URL from the develop tab (you only have to do this for one security, and then change the very last bit for the security code for all of your other securities with this problem. )
The final part, is to add the ‘factor’ at the bottom of the Json to 100, so that the data is converted to pence (if Morningstar is presenting it as pounds rather than pence). If you select the correct denomination on the morningstar code (GBX rather than GBP, then you dont need to use the factor conversion.
Presumably you could do the same thing with the Yahoo finance website, but you might run in to them changing currency units again
Well it’s not an ideal solution cause in industry parlance it’s referred up as “scrapeing”. So guess some would say it’s fine but I for one would say it second best to a proper API
Think my hack will be to create trades that sell existing units of crashed GBX securities with a buy of new GBP one
If Yahoo revert back then I’ll have to delete the trades. Yes from a reporting point of view it’s not that great but will then see…
Just to be clear, you won’t need to include the 100 conversion factor if you are pulling the prices from Morningstar as they are already in GBX (i.e. pence).
No it’s not ideal. Ideally I would be using a proper API and paying for the data. But it is making use of the Morningstar API that they use to populate their own chart, and so it is not scraping the HTML. But if you want to be protected from a change in API or a change in currency, or units of a currency, then you need to pay for the data.
In its defence, I have been using it with some of my securities for 6 months or so and haven’t had a problem. I have also found it to be a little more reliable and punctual than the Yahoo feed.
I was tempted to go down the route that @hkphooey suggested which would be just fine but there were two things that made it less attractive to me. The first was that if Yahoo did revert to prices in GBX I was going to end up with a lot of duplicate securities that would be messy to deal with. The second was that by selling the units and buying them back again I was going to end up with an inflated “realised gains” figure which would annoy me. I’ve already been through that when I sold a number of “accumulation” funds and replaced them with “income” funds which can be done without actually incurring a gain but shows as one in portfolio-performance and I didn’t want to cause that to happen again.
I suppose that everyone has slightly different priorities and so different solutions work for different people.
