Trading212 - Wrong ticker being used

[pvieira84]

So I have bought some shares of ISIN IE00B4L5Y983 which has different tickers depending for example on the Exchange/Currency.

In my t212 file, I have this:

The ticker is EUNL. But sidekick is using a different ticker:

I tried to used the config file to change this but none of the below additions worked for me

Can you shed some light on how can I get these activities imported with ticker EUNL.DE?

[VibeNL]

I suspect we have a 'cache' issue, or a previously matched issue. Your first mapping (IE00B4L5Y983) should be the correct one. ISIN is used as the identifier in Trading212.

Did you restart the container after setting the mapping and did you correctly configure the config file to be used?

Otherwise, could you please try the following:

• Stop the container
• Make sure the config contains the mapping
• Remove the comment of the IWDA.AS symbol (Admin Control -> Market Data -> Search the ETF/Stock). Make the comment empty should be fine.
• Restart the container

Could you let met know if the issue is resolved 😄 , otherwise i'll have to investigate further.

[VibeNL]

To help I have added some logging in the latest version of the container

[pvieira84]

So I've followed the steps and what happened was that the app updated the comment to what it was again i.e. "Known Identifiers: [IE00B4L5Y983]"

Then I tried a different approach and the result was different as well.

• deleted the activities
• deleted the symbol from Market Data
• recreated the container

It now created the activities associated with ticker IWDA.L - this is what I have in the logs:

This is my current config:

[VibeNL]

I can see from the first screenshot that your config file is not being read 'mappings #0'

Could you check the path to the config is being set correctly?

[pvieira84]

This is what I have set. It's in the same folder of the import files

[VibeNL]

That looks correct 👍🏻. just to rule it out (if you are running Linux), is the casing correct?

[pvieira84]

it is:

[VibeNL]

I was afraid of that. Will add some extra logging in the coming weeks to try to explain what is going wrong 😅

[VibeNL]

Created a pull request for the logging, the first statement I added should at least confirm that the default config is used. Could you install that version and share the log?

[pvieira84]

Well, your PR helped me find the issue.

Logs: 2024-03-08T08:55:41.190483278Z warn: GhostfolioSidekick.Configuration.ApplicationSettings[0] 2024-03-08T08:55:41.190523769Z No (valid) configuration file found at /import/config.json. Using default configuration.. Error was '"' is invalid after a value. Expected either ',', '}', or ']'. Path: $.settings | LineNumber: 6 | BytePositionInLine: 2.

It happens that my json was not valid :S A comma was missing

After fixing the JSON: and

There's still an issue though - before testing I deleted the activities pointing to the wrong ticker but now even though the mapping is correctly identified, the activities are not getting imported at all (for my mapped EUNL ticker) . I have a couple of these fails in the logs, don't know if it means something

[VibeNL]

Glad to hear you have found the issue.

Regarding the other issue, I may have broken something with the last refactoring. Hopefully the new master it is fixed. If not, could you please open a new ticket :)?