Transitioning to UTF-8

Question

Hi everyone,
Can any of you share with me how you navigated migrating your realm to UTF-8?
We've only had QB for 2 years, but apparently, UTF-8 wasn't enabled when we started.&nbsp; Over the past year, I'm watching errors pile up because a lot of our data is in written form (vs. hard numbers).
For example, we'll have survey data and even the questions being asked contain apostrophe's and parentheses.&nbsp; QB isn't handling them well, and all of these characters are generating errors.
To correct this, QB Tech Support had me install and run an encoding scanner to identify the errors in our realm, and it looks to be numbering in the thousands; nearly every record and a majority of our fields are flagged as problematic.
Some of the issues I see are that the encoding scanner doesn't tell me "what's" wrong with our data, just that this record or that field is an issue.
QB Tech Support said that to turn UTF-8 on will affect the entire realm AND I need to have all the errors fixed before they do this.
Our staff is inputting data daily; so the number of errors grows daily.
We cannot afford to spend thousands on an external company to help us scrub the special characters.&nbsp; I was debating telling our staff to pause for a long weekend, so I can download the data to excel and do a find and replace function and then re-upload the data...but I'm just worried about breaking or losing data that we need.

Can any of you recommend a better way?&nbsp; What did you do to manage this?

Thank you!!!

Jen------------------------------Jennifer Juhasz FamilySmartBC, Canada------------------------------

jimharrison · Answer

Hi Jennifer,

We are currently on a similar journey. When UTF-8 is enabled and you are using another 3rd party cloud service, like Workato, any non-acsii characters sent to the third party service will cause errors, this is the reason to clear the non-ascii characters. Here is what we are doing to repair the data.&nbsp;

I made a rich text formula field and entered the formula in the link below. The link below describes the formula and also the reference ascii Website where this information can be found. I have since removed several of the ascii characters in that formula that do not throw the error but this will get you started.
What the formula does is display all the characters that will cause an error. You then can build a report and use one of three tools to clean up the data namely: Grid Edit, Find/Replace or (Export-correct-Import). You can test by turning UTF-8 on one App at a time and looking for the black diamond with the question mark. This process has to be done for each table.
Of course if you're not using third party cloud services UTF-8 can be enabled anytime and then the data can be cleaned up when it is discovered but you won't know is hiding behind the black diamond question mark thingy.&nbsp;

Finding non- windows-1252 Characters in Text fields using a formula
https://community.quickbase.com/discussion/finding-non-windows-1252-characters-in-text-fields-using-a-formula#bm7085aeaa-a2e5-46e1-98f5-0185cb476521

Good luck.

------------------------------Jim Harrisontransparency = knowledge + understanding : The Scrum Dudes------------------------------

jenniferjuhasz · Answer

Hi Jim,
Thank you so much for replying!&nbsp; I think your reply was buried in my inbox with all of the other QB discussion threads, and I apologize for the delay in responding to you.
I wasn't aware I can implement UTF-8 on an app-by-app basis; QB Tech Support told me they had to do it at the realm level - which made the project seem far more daunting (because then everything has to be perfect with no new imperfect data coming in).
While I'm not using 3rd party apps that are directly importing to QB; we do use forms on our website to collect data, that I am building into Sync Files in Google Drive and syncing that data weekly.&nbsp;&nbsp;
Once I have enabled UTF-8, when importing data that contains non-ascii characters such as quotation marks, apostrophe's, or parentheses (these seem to be the biggest challenges in our data), will they continue to cause issues (in your experience and opinion)?
Thank you again! This gives me the ability to develop a clear plan of action on how to tackle what otherwise felt like an overwhelming and impossible task.
Take care,
Jen------------------------------Jennifer Juhasz FamilySmartBC, Canada------------------------------

jimharrison · Answer

Hi Jennifer,

Enable UTF-8 per App by going to the App properties=&gt;Advanced Settings and check the UTF-8 checkbox.

Once UTF-8 is enabled all "newly entered" non-ascii characters display normally. The problem is dealing with the "old" non-ascii characters currently in the text fields of your Apps. All those characters need to be replaced or removed.&nbsp;------------------------------Jim Harrisontransparency = knowledge + understanding : The Scrum Dudes------------------------------

jimharrison · Answer

In case someone finds this thread, here is the solution I am using so far.First search the App Exchange for: "Mixed Encoding Scanner". Which will take a App DBID and scan the entire App for non-ascii characters.Once I know where to go, I can decide to either update each record one at a time or use something like the "Special Character Finder" text-formula field and "Find/replace in these records" all the different non-ascii characters identified by the "Special Character Finder" in the field. When the Mixed Encoding Scanner finds a symbol I haven't included in the formula I add another line.&nbsp;I use the manual update when there are only a few records that need to be updated. There is a button that opens all the fields or one field at a time in the Mixed Encoding Scanner. Then Grid Edit and click four times just to activate edit to change the record. One thing I have noticed is when I save, Quickbase asks me to review every change like someone else is editing the record, which I know is not possible. So using Grid Edit takes a lot of effort and can be very frustrating.The second method of using Find/replace in these records is a lot faster. It's annoying that the pop up window is at the opposite corner of the screen so I have to do a lot of mouse traveling. I can edit a lot of records with minimal effort.&nbsp;Improvements I would make to the second option are to locate the pop-up window closer to the more drop down menu, auto refresh the report page on close of the pop-up, allow the User to go back after the Find/replace is complete to perform the next operation instead of having to start at the more drop down menu.I have tried QuNect Razor and that identifies one field at a time one table at a time, I cannot recommend using this tool as it is since it takes considerable time to work through one record if there are multiple fields.&nbsp;------------------------------Jim Harrisontransparency = knowledge + understanding : The Scrum Dudes------------------------------

tylerbrezler · Answer

Just thinking out loud, but if I were to approach this, I would probably use the API to loop through all my apps, and within each app, loop through all my tables, and just convert the string fields of each table to utf-8 on the fly before inserting back into the table. If you have someone on your team that's familiar with python or could hire someone for cheap, they could probably whip something up in an hour or two. &nbsp;Depends on how many tables you have and many records are in each, but the runtime for this could potentially be pretty quick.

Forum Discussion

Transitioning to UTF-8

Finding non- windows-1252 Characters in Text fields using a formula

Related Content

UTF-8 in Gmail Channel

Transition to new/updated form

Mixed Encoding Scanner now available to help identify issues with UTF-8 data

Concerns of Transition from Quickbase to PowerApps

Pipeline to write non-English characters: is it possible without realm UTF-8 setting ?