Japanese name in Excel header leads to u_[Japanese Name] in column name of import set tableDescriptionWhen including Japanese name in Excel header and trying to import the Excel , then it leads u_[Japanese Name] in column name of import set table which is NOT supported. Manual: https://docs.servicenow.com/bundle/washingtondc-platform-administration/page/administer/data-dictionary-tables/reference/r_DictionaryEntryForm.html Column name:The name can contain only lowercase, alphanumeric ASCII characters and underscores (_). Steps to reproduce 1. Enter Japanese name in Header in Excel 2. Load the Excel then check the import set table showing u_[Japanese Name] in column name Ex: Go to the table and do the easy import.CauseThe char in Excel header is used to create column name internally, so if it contains Japanese char, Japanese char will be used in column name.ResolutionThe following can be only effective for newly created import set. (This is not effective for column names containing Japanese character in existing import set.) 1.Use English name in Excel header to avoid creating Japanese column name. or 2. From Tokyo instance, new property "com.glide.use_column_name_optimizer" was introduced. Regarding the property "com.glide.use_column_name_optimizer": If "com.glide.use_column_name_optimizer" is set to true, then behavior is the following. Even below Excel including Japanese char in the header does not lead to create Japanese column name. For Example, Excel header: 部門 Import set column name will be "u0", not "u_部門" (randomly supported characters assigned not to use Japanese characters anymore). Existing issues with Japanese column name at this moment. Data corruption issue at database level: If the column name includes Japanese char, the column name shows "u_" at database level, so it leads to data corruption issue. For example, there are two column names "u_会社" and "u_部門" but both will be stored as "u_" in databased level, which leads below two issues. 1. Max length issue: there are not the same value of max length between application and database level. - For example, Even when setting 100 as max length in application level , the column only holds 40 chars because the type is defined as 40 at database level. Workarounds: Re-update the max length via System Definition > Tables.(in above cases Set 40 at first and save. Then Set 100 again and save and it should be sync with database level) 2.Create duplicate columns: If there is existing column including Japanese char such as "u_部門"("u_" at database level) then "部門" in the excel header will leads to creating another column. This will lead to creating duplicate column after changing the property as true, which means the system sometimes does not recognize the same column. Existing column label: "部門" Existing column name : "u_部門"("u_" at database level) New column lavel: "部門" New column name : "u_xaa1" Workarounds: Delete both columns via System Definition > Tables. Then do easy import again. or avoid using easy import and use import set(define transform map) instead not to use unwanted column. 3. Column label was not recognized correctly Workarounds: import_attribute_name may be used. Refer: KB0955220 For long term, please consider avoiding Japanese column name leading to several issues. Note that these columns including Japanese name are not supported, so changing the max length of column or column name in database can not be done.