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)

Smart List - excel export issue

(0) ShareShare
ReportReport
Posted on by

Greetings all,

I am getting errors when I export a smart list from GP to Excel.  We are hosted on Azure.  My Smart List is for 1099 preparation and includes the vendor name, ID, address, etc...  When I export to excel I get the following:

  1. We found a problem with some content in '2016127-111734.xlsx'.  Do you want us to try to recover as much as we can?  If you trust the source of this workbook, click Yes.
  2. I click Yes.
  3. I get another message that says "Excel was able to open the file by repairing or removing the unreadable content."
  4. When I look at the excel file, some of the addresses, not all, have been truncated and only show the building or house number.

I don't know if this is a GP issue, an excel issue or Azure issue.  The data looks correct when it's in GP.

Thank you for your guidance.

Lisa

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    Hi Lisa,

    As strange as it sounds, this looks like some content of your data cannot be handled properly by Excel once the SmartList has exported it.. I recently had a case where a smartlist was causing issues and Excel refused to open the file with a similar error message. It turned out that some non-printable characters had been added accidentaly into a Vendor Name field during a PO creation.. GP made no problem to accept the data, but Excel couldn't interpret it. Check your data for cleanness..

  • Community Member Profile Picture
    on at

    You are probably onto something.  Most of the vendors were set up this year using integration manager.  We set up a new company.  I'll look into it.  Thank you.

  • Community Member Profile Picture
    on at

    Hi M. Bucher,

    I'm relatively new to this. I was wondering where I could get a list of the char which EXCEL is not able to handle ?

    We have the same problem and since I am no IT guy ... I'd relly appreciate the help.

    My client is "pasting" many things in SOP and I think we have a serious data cleanness problem.

    Thanks in advance.

    Olivier

  • Verified answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    Bonjour Olivier,

    I'm not aware of a specific list of 'characters' that Excel can read or not.. That would be an office forum topic.. What I know for sure, is that many companies are doing copy/paste data entry from various sources... the worst are the Web content that often 'hide' characters that are not screen readable, but used by a web page (like carriage-return and line-feed codes), which often are located in the lower ASCII table set.. (under the value Hex20)... those are usually non-printable characters.

    see references on Wikipedia : commons.wikimedia.org/.../File:Ascii-codes-table.png

    I've had a case where someone pasted a product description from a web page into the GP requisition system and it was causing all sorts of issues after that.. It took quite some time figure out where the culprit was and how it came into the system.

    My general advice to all users when copy/pasting strings from an external source, is to use the notepad as intermediate staging, thus the non-printable characters are usually left out (or at least show up as a strange sign).

    Once it's in the database, it becomes hard to spot and elimination is usually only possible thru the back-end with a SQL update command.

    Here's a forum discussion on SQL Server Central on how to possibly write a function to remove "unprintable" characters :

    www.sqlservercentral.com/.../Topic860321-338-1.aspx

  • Community Member Profile Picture
    on at

    Thx a lot for the tip! Got us on the right track.

    With ITs, we checked at the situation and seems like ASCII under 32 are mostly unprintable.

    We'll run an update on our comment table for the character we encountered. The situation is from an historical transaction. Can't do much about it applicative-wise.

    Thx for the forum your pointing at. I'll make sure to take a look at it.

    Kind regards,

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
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans