List v3: Querying for records that contain non-Latin1 characters result in "Error: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range" - Known Error

List v3: Querying for records that contain non-Latin1 characters result in "Error: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range" Description When querying for records that contain non Latin1 characters, Turkish 'ı' for example, in a List form with v3 List enabled,see the following error occurs:

angular_includes_1.4.jsx?v=10-25-2017_1637:109 Error: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range. at Object.getFilterString (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:10705) at Object.getChannelRW (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:10708) at initChannel (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:10798) at Object.initList (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:10782) at Object.register (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:18943) at Object.reInitialize (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:18973) at _updateRecordWatcherManager (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:15156) at Object.fn (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:15137) at r.$digest (VM6620 angular_includes_1.4.jsx?v=10-25-2017_1637:133) at r.$apply (VM6620 angular_includes_1.4.jsx?v=10-25-2017_1637:136) Also, the records that are returned are not necessarily expected.

Steps to Reproduce

Ensure that List v3 list is enabled: glide.ui.list_v3.enable system property is set to true.

Create a new Incident with the Short Description: "ık Holding". (Copy and paste this text as it contains Turkish character at the beginning.)

Query for the new incident by searching for 'Short Description starts with ı', either using filter or column header.

The following error appears in the browser console:

angular_includes_1.4.jsx?v=10-25-2017_1637:109 Error: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range. at Object.getFilterString (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:10705) at Object.getChannelRW (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:10708) at initChannel (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:10798) at Object.initList (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:10782) at Object.register (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:18943) at Object.reInitialize (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:18973) at _updateRecordWatcherManager (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:15156) at Object.fn (VM6622 js_includes_list_v3.jsx?v=10-25-2017_1637&lp=Thu_Nov_16_13_35_18_PST_2017&c=4_49:15137) at r.$digest (VM6620 angular_includes_1.4.jsx?v=10-25-2017_1637:133) at r.$apply (VM6620 angular_includes_1.4.jsx?v=10-25-2017_1637:136) If you disable List v3 list and repeat step 3, no error occurs.

The same records are returned, but 'ı' appears to be substituted for 'i' so this query also returns unexpected records.

Add a new report to the homepage named 'Incidents starting with ı' and set the filter to "short description starts with ı", and any Type value.

An incorrect number of records is displayed, and the error occurs when the homepage loads with the report present.

Drill down with List v2 enabled.

Note that the incidents display.

Re-enable List v3 list and repeat this step.

The error occurs again when the report is loading in the homepage but also, when drilling down on the report, the incidents are never displayed and the loading circle just runs ad infinitum.

Workaround After carefully considering the severity and frequency of the issue, and risk of attempting a fix, it has been decided not to address this issue. We do not make this decision lightly, and we apologize for any inconvenience. If you have any questions regarding this problem, contact ServiceNow Customer Support .