Skip to content
This repository has been archived by the owner on Sep 13, 2024. It is now read-only.

Data Import Problem with Umlauts #17393

Open
ralphkretzschmar opened this issue Mar 6, 2024 · 4 comments
Open

Data Import Problem with Umlauts #17393

ralphkretzschmar opened this issue Mar 6, 2024 · 4 comments

Comments

@ralphkretzschmar
Copy link

Dear Yetiforce Team,

i'm testing YetiForce 6.5
When i try to import testdata it identifies accounts as duplicates but they are not really duplicates.

Example data (csv-content):

Organisationnames:
Müller
Muller
Möller
Moller

When trying to import these organisation names as accounts it idetifies "Müller" as "Muller" -> false duplicates (in germany we have Ü Ö Ä etc.)

So i can't import such data because of false duplicates

Best regards
Ralph

@ralphkretzschmar
Copy link
Author

After digging more into deep i recognized that it was the config of mysql db.
Sorry for the false report.

Best regrads
Ralph

@ralphkretzschmar
Copy link
Author

Unfortunately its not only the DB i thought i have to convert it to another collation like "utf8mb4_bin" of the DB. but this has negative side effects.
i guess the comparison for accountnames has to be done at code level?

@s2b-git
Copy link

s2b-git commented Mar 8, 2024

Open CSV in Notepad ++ and change encoding to UTF-8 BOM. Save / import

@ralphkretzschmar
Copy link
Author

Thank you @s2b-git a lot your tip, but unfortunately it doesn't work out.

A simple example as well is when you create an accountname "Möller GmbH" and afterwards you can search for "Moller" and it finds "Möller GmbH". This gets even more tricky if you try to import Contacts -> the contacts will be associated to the wrong company.

Best regards
Ralph

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants