Description
When importing transactions, the market/exchange is not correctly resolved from the ticker symbol suffix.
For example, the ticker XMME.DE should resolve to XETRA, but the app maps it to LSE instead. The same happens with XMME.XETRA — the exchange suffix is ignored and a seemingly random market is assigned.
The same issue affects other assets too (e.g. SGLD, SWDA), suggesting the suffix-to-exchange mapping is either not implemented or not working as expected during the auto-resolution step.
Steps to Reproduce
- Prepare a CSV/import file with tickers that include an exchange suffix (e.g.
XMME.DE, SGLD.MI, SWDA.L).
- Run the import.
- In the New Assets review screen, observe the resolved market for each ticker.
Expected Behavior
The market should match the exchange indicated by the ticker suffix:
.DE → XETRA
.MI → Borsa Italiana
.L → LSE
- etc.
Actual Behavior
The resolved market does not match the suffix — an incorrect exchange is shown (e.g. LSE for .DE tickers).
Additional Notes
- Manually remapping via the "Remap" button works as a workaround.
- The issue appears consistently across multiple assets in the same import.
Description
When importing transactions, the market/exchange is not correctly resolved from the ticker symbol suffix.
For example, the ticker
XMME.DEshould resolve to XETRA, but the app maps it to LSE instead. The same happens withXMME.XETRA— the exchange suffix is ignored and a seemingly random market is assigned.The same issue affects other assets too (e.g.
SGLD,SWDA), suggesting the suffix-to-exchange mapping is either not implemented or not working as expected during the auto-resolution step.Steps to Reproduce
XMME.DE,SGLD.MI,SWDA.L).Expected Behavior
The market should match the exchange indicated by the ticker suffix:
.DE→ XETRA.MI→ Borsa Italiana.L→ LSEActual Behavior
The resolved market does not match the suffix — an incorrect exchange is shown (e.g. LSE for
.DEtickers).Additional Notes