From Van Nguyen

Hello team,

BioRad is the 2nd client that have requested that we process the import files with encoding type UTF-8. MRTX was the 1st one that requested this in November.

Company Template Name: _Employee Data New Hires
File date: 3/16/2018
Filename: EmployeeCensus.txt

Employee: Marcella Gordon
Incorrect Address imported into Workterra: 12 O’Neil Ct.
Correct Address that should've been imported into Workterra: 12 O'Neil Ct.

When I manually opened the file using the TextPad application, I saw the address with the invalid special characters. 12 O’Neil Ct.

When I manually opened the file using the NotePad application, I saw the address without the invalid special characters, 12 O'Neil Ct.

I've requested for the client to temporarily remove the special characters for now, but they refuse to do that. They want us to be able to process the import files using encoding type UTF-8.

Note from Bio-Rad's IT department:

From: Balakrishna Reddy <balakrishna_reddy@bio-rad.com>
Date: Mon, Mar 19, 2018 at 12:10 PM
Subject: Re: FW: Bio-Rad - MHN - failure - special character in address
To: Julie Bates <julie_bates@bio-rad.com>
Cc: Maricel Chesney Edpao <maricel_chesney-edpao@bio-rad.com>, Maria Fonseca <maria_fonseca@bio-rad.com>
Hi Julie

I am not sure how WorkTerra opened the file and which tool they are using to open the file from fTP server.

Workterra needs to open the file in a tool which supports UTF-8 format.. If not, you will see the data as shown below. We use Notepad++

Also we don't have any insights on how workterra program is designed to read the data from FTP server side. We had the same issue from another vendor and they have changed their Decryption logic to read the file as UTF -8 and it resolved their issue

Satya,Vinayak Kulkarni,Prashant Samal