You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When importing, if the thesaurus does not contain items in the current UI language, the import fails. It should fallback to using the CSV language for all languages.
Moreover, after a failed attempt at importing, it won't allow to re-import the corrected CSV because despite the failed import the thesaurus is created and it is detecting the new import as a new creation, giving a uniqueName error. Either not save the thesaurus, or properly update the front-end so it becomes a saved thesaurus and the operation becomes an update instead of a creation.
The text was updated successfully, but these errors were encountered:
Current UI language should have no influence in what is being imported. The import thesaurus flow should just take into account the CSV contents. The only thing that could impact is the default language configured, but nothing else. Can you provide de CSV being imported?
Two glitches depending on the backend:
The text was updated successfully, but these errors were encountered: