IE00BKS7L097 is a sythetic ETF. You can try to find a similar physical ETF and use ‘#PPC:[..]’ in the Notes attribute as described here
1 Like
Domicile: I would like to inquire whether it is possible to set up and query the “domicile” field as well. I believe this would be significant for many people. For example, if someone dies with $60,000 in assets with a U.S. domicile, their heirs will have to pay estate tax. For this reason, it wouldn’t hurt to check this as well.
Furthermore, it could be significant from a tax perspective as well, because, for example, in the case of GB and IE domiciles, no withholding tax is deducted, but in the case of DE, NL, and FR, for example, 15% is deducted based on my country’s double taxation agreement…
If this can be implemented, I think it would be a very useful feature.
Domicile is not a taxonomie attribute but a security one.
(Python 3.12.3. I had no issues yet with any python3 version).
I still had the issue with connection errors. For me it looks like something on morningstar side eg. loadbalancer switching to another server or something similar. With the help of AI I changed the requests.get calls to requests_get_with_retry. This works fine for me. If you want I can send you the file
@tommi296: Maybe you can post the code here. I will then integrate it. Sounds like a useful increase in robustness.
see attached zip file. 8 requests.get-calls have been replaced with requests_get_with_retry calls. There are 5 retries with increasing waiting time (5s, 10s, 15s, 20s, 25s). Looks like this:
[ISHARES CORE EM IMI ACC]:
@ Retrieving data for fund IE00BKM4GZ66 from Morningstar API
(Name: “iShares Core MSCI EM IMI ETF USD Acc”)
(Ongoing Charge IE00BKM4GZ66: 0.18%)
(Fund type: “Equity”)
Connection error, retrying in 5s… (attempt 1/5)
portfolio-classifier.zip (20,2 KB)
1 Like
Thank you very much @tommi296.
It is now added to new-api-branch (together with a deletion of cache.sqlite file, if it hasn’t been used in the last five minutes).
2 Likes