Error Output

[rkqkq9bxfv-maker]

I get the following error for cells where NAV prices usually returned the correct value:

Exception: Request failed for https://lt.morningstar.com returned code 401 (line 118).

Any advice on how to resolve this?

[zallek]

Looks like the extension is no longer authorized to call Morningstar API :(

muFunds/src/sources/morningstar.js

Line 58 in bfa3ddf

let url = 'https://lt.morningstar.com/api/rest.svc/klr5zyak8x/security/screener';

[ruffle-b]

Same here. Happened some time today :-(

Is this an easy fix? muFunds is great and it would be a shame if it stopped working.

[joseballester]

Hi all, thanks for reaching out! I just deployed a new version that uses another API, but only works for ISINs and Morningstar IDs of some asset types (e.g. I believe ETFs are not supported). This fixes most cases, but I still need to see what is the actual coverage and if we can improve it somehow.

[No1squashfan]

I am having the same issue with nearly all of my Australian funds - just a handful still working with the same formula. The error occurred overnight. Any hope of a fix?

[kevpio]

Mine had the same problem which you've appeared to have fixed now, however, they are now returning prices in £ not in pence as before (100 pence to a pound) not a problem as it's an easy fix in my sheet but wanted to let you know.

[ruffle-b]

FWIW, same experience as kevpio. muFunds is now returning values but in pounds not pence. Maybe a Morningstar change?

Thanks for the fix.

[jvaughan]

An issue I'm having with the recent change:

"SPDR MSCI All Country World UCITS ETF" Has ISIN IE00B44Z5B48, but this defaults to the EUR trading currency version instead of the GBP that I need.

I was previously able to use the SEDOL code "B6WFJC9" to get data for the GBP version but this now returns "Error: Asset not found."

Fund details: https://www.ssga.com/uk/en_gb/intermediary/etfs/spdr-msci-all-country-world-ucits-etf-acc-spyy-gy

It would be great if there's some way to get SEDOL codes working with the new implementation.

[zallek]

this defaults to the EUR trading currency version instead of the GBP that I need.

@jvaughan yesterday change is a quick fix with drawbacks and limitations as explained by joseballester.

As a temporary workaround, you can consider converting eur to gbp using GOOGLEFINANCE("CURRENCY:EURGBP"). It won't be 100% correct because of spread between exchanges but should be good enough unless you manage billions :p

[jvaughan]

@zallek

@jvaughan yesterday change is a quick fix with drawbacks and limitations as explained by joseballester.

As a temporary workaround, you can consider converting eur to gbp using GOOGLEFINANCE("CURRENCY:EURGBP"). It won't be 100% correct because of spread between exchanges but should be good enough unless you manage billions :p

Thank you! I hadn't seen that suggestion.

This comes very close to the right number (J17 is the ISIN, I17 is unit quantity):

=(VALUE(muFunds("nav", J17)) * I17) * GOOGLEFINANCE("currency:USDGBP")

(The default value is for USD, not EUR as I first thought)

[rkqkq9bxfv-maker]

Hi all, thanks for reaching out! I just deployed a new version that uses another API, but only works for ISINs and Morningstar IDs of some asset types (e.g. I believe ETFs are not supported). This fixes most cases, but I still need to see what is the actual coverage and if we can improve it somehow.

Mine is working perfectly again today, thanks for the fix

[joseballester]

Hi again! I just deployed a new version that should work with all the asset types muFunds used to support before yesterday, but please let me know if you find anything weird going on these days.

@No1squashfan could you please check if it now works with your Australian funds?

Regarding the GBX/GBP issue noticed by @kevpio and @ruffle-b, sorry for the inconvenience. The new API returns prices in GBP instead of GBX and I hadn't thought about it. Now a combination of APIs is used (one as fallback of the other), one returning GBP and the other GBX, but I've added the code to always return GBP from now on.

Regarding the ETF search by SEDOL issue by @jvaughan, now it should be working. However, I'd suggest using the Morningstar ID of the specific ETF listing as asset identifier (more info in the first point here), as it will be more reliable in case we have to change the API we use again.

Thanks all for your feedback!

[jvaughan]

Regarding the ETF search by SEDOL issue by @jvaughan, now it should be working. However, I'd suggest using the Morningstar ID of the specific ETF listing as asset identifier (more info in the first point here), as it will be more reliable in case we have to change the API we use again.

Thanks all for your feedback!

@joseballester Working well with the morningstar ID (0P0000TSEK in this case).

Thanks!

[kevpio]

It really is not a problem the prices coming back in GBP, it makes more sense anyway than GBX. Nice job!