Wrong display customer name with special characters

[ndhvu275]

Dear,

I'm using OTRS 3.3.x on CentOS 64 bit, my OTRS is using the customer data backend from the external MS SQL database, the connection via DSN OBDC of Microsoft. But there are something wrong displaying the customer name

My customer name in external database is : Servië Somalië Oekraïne Tunesië
But in AdminCustomerUser screen that is displaying: Servië Somalië Oekraïne Tunesië

12-18-2013 5-44-25 PM.png

Here is my file, customer backend

Code: Select all

# external customer database backend
$Self->{CustomerUser} = {
	Name   => 'VispBossCustomer',
	Module => 'Kernel::System::CustomerUser::DB',
	Params => {
		DSN => 'DBI:ODBC:mssqlvispboss',
		User => 'sa',
		Password => 'Password123',
		Table => 'VW_OTRS_Customer',
		SourceCharset => 'utf-8',
		DestCharset => 'utf-8',
		CaseSensitive => 1,
	},
	CustomerKey => 'customer_id',
	CustomerID  => 'customer_id',
	CustomerUserListFields => [ 'customer_id', 'first_name', 'last_name', 'ISNULL(email_address_1, \'\') + ISNULL(\',\' + email_address_2, \'\')' ],
	CustomerUserSearchFields => [ 'customer_id', 'first_name', 'last_name', 'ISNULL(email_address_1, \'\') + ISNULL(\',\' + email_address_2, \'\')' ],
        ....

Please help me for this issue.

Thanks

Vu Nguyen

[crythias]

what's the coalation of the customer backend?

[ndhvu275]

The collation of customer backend is SQL_Latin1_General_CP1_CI_AS
However, in OTRS system. I can query the right customer data via command line as below

12-19-2013 8-39-39 AM.png

file odbc.ini

12-19-2013 8-43-31 AM.png

[reneeb]

The collation of customer backend is SQL_Latin1_General_CP1_CI_AS

Then you should say in the config that the source charset is latin1 (I don't know the iso-code for that collation atm)

However, in OTRS system. I can query the right customer data via command line as below

The client is responsible for the charset that is used. You said OTRS that the source is utf-8. The client you use on commandline uses the correct charset (either it inspects the collation or it uses a default charset that happens to be the correct one).

[ndhvu275]

Thanks reneeb, my issue was sovled.

There is a small I would like to share with you. In the external customer database, for example the firstname field with varchar(50), but you put the data is longer than varchar(50) (data is Téster-èìhmGiIiVîavyëEvëézAhàoVvXPrýSnLHäLHWéìóapÿ). Then, in the AgentTicketPhone screen, when you search this customer, an AJAX error will happen. So, you need be carefull with the length config of field

Btw, this error is only happen with OTRS on Linux. On WIndows is still OK.

I hope OTRS team can fix this error in the future

Vu Nguyen