web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Importing Accent Marks

(1) ShareShare
ReportReport
Posted on by

Hello:

Overseas, we have many users with accent marks and tildes over letters of their names.  These names are imported into GP, through Integration Manager, as sales contacts for invoices.

The problem is that, whether the import file is saved as a tab-delimited text or comma-delimited text file, these accents and ultimately the names of these salespeople appear garbled in SQL tables due to the accents and tildes not importing correctly.

Prior to importing these sales invoices, our Finance department will occasionally open up the import file to make any necessary corrections.  When the file is re-saved, afterward, the accent marks and other similar items do not remain intact.  That's what causes the issue.

Our main business analyst "across the pond" who overseas this importing has tried "playing with" ANSI-encoding and Unicode features of saving this file prior to import. 

But, no matter how he does things, the import still has this issue.  As a "backup solution", he has a VBA macro which is able to replace accent letters in names to non-accent letters (i.e. ó to o or ñ to n).  But, this is a workaround, rather than a long-term solution.

Has anyone out there tackled importing data into GP where the names of individuals have accent marks and other special symbols?

Thanks!  Much appreciated!

John

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at

    This is from the end user:

    I have re-written Integration Manager integration from scratch to import TXT files(with correct encoding) instead of CSV but unexpectedly when integration kicks off it still recognizes an import file as ANSI encoded (despite the fact that it is saved as Unicode) and it insert the same weird symbols as in case of CSV file importing.

    In this case I have no other idea what setup piece should be changed to accommodate importing Unicode coded text files.

  • Tim Wappat Profile Picture
    5,711 on at

    It does sound like a classic case of file encoding issues causing the diacritics corruption.

    However, it is a bit strange that correcting the file encoding does not fix the issue.

    If you have a sample before and after file I could look at them for you -if that would help?

     

    Tim

     

  • Verified answer
    Community Member Profile Picture
    on at

    Thanks, Tim, for the offer!

    It looks like, though, we have found a solution for our end user.  Specifically, our end user is going to use the "Remove Dashes" script from Integration Manager's script library as a template.   Again, thanks, for "chiming in" though!

    John

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans