Hi all,
I'm wondering if anyone has a solve for importing data that doesn't use Roman characters? For example, accents on letters, Chinese characters.
We are trying to import data from our Shopify account (where any character can be used) into Tessitura, which seems to only allow Roman characters. This is therefore requiring we either rewrite the data line-by-line to replace it with Roman characters, or we do not upload those records.
I'm hesitant to restrict users to only using Roman characters in Shopify, as this data is used for international shipping of purchases etc.
Would love anyone's thoughts, or to hear if anyone is having the same issue!
Thank you!
Anna
Hey Anna,
Do you have an example of the type of characters that are not importing? Characers like è and é should import correctly.
I know there is an issue with characters such as ā - these cannot be entered for a technical SQL reason. I believe there are plans to support this in future but you'd need to reach out to support to see where that's at.
Cheers,
DGH
It sounds like you are trying to save unicode characters in a non-unicode field.
A lot of data that can be found in our database is done so in strings of various lenth ie: varchar like the first and last names that are stored in T_CUSTOMER.
To store extended language values and other unicode data, we'd need to use nvarchar columns to store the unicode range of characters. This changes a bit from SQL Server 19
https://learn.microsoft.com/en-us/sql/relational-databases/collations/collation-and-unicode-support?view=sql-server-2017#Unicode_Defn
Thank you David, appreciate the advice - we'll revisit the accented characters. I've added it to the Tessitura requests!
Thank you Heath!!