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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / GP 2015: Comma separat...
Microsoft Dynamics GP (Archived)

GP 2015: Comma separation error in exporting SmartList to Excel

(0) ShareShare
ReportReport
Posted on by Community Member

Hello,

We're currently running GP 2013 and I recently found the following problem: When exporting a Manufacturing module SmartList to excel using the "Excel" button, values that contain a comma are not properly exported. For example, I exported a Manufacturing Picklist SmartList with a "Required QTY" column containing values such as "1,200". The smartlist shows the comma in the number 1200.

When exported to Excel, the value for that cell is just "1". It appears that there a comma delimiting problem in the export function. Has this issue been resolved in a later version/bugfix?

Thanks,

Chris

*This post is locked for comments

I have the same question (0)
  • Praveen Kumar RR Profile Picture
    Praveen Kumar RR 1,552 on at

    Hi Chris,

    Hope you tried setting up the Format of Require QTY column to Numeric manually....

    If not, suggest you to try this.

    Thanks,

    Praveen

  • Community Member Profile Picture
    Community Member on at

    Praveen,

    Are you talking about a setting in GP or in Excel? By the time it gets to Excel it is too late - the data is lost. You can change the format in Excel but only numbers ahead of the comma are present in the cell. The rest is lost. "1,200" in the SmartList exports to "1.00" in Excel.

    Whether it is a numeric or a text field, I think that it is a bug if GP exports something different than what is displayed in GP. If it's a text field, the cell in Excel should read "1,200" just like it does in the SmartList.

    The export function does appear to handle commas appropriately for other fields like "Component Item Description."

    Thanks,

    Chris

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

    Hi Chris,

    GP 2016 has corrected many of the bugs that occurred with currency & date values in SmartList to Excel export.. I'm not aware of issues with QTY fields, but there are some DEX.ini settings you could test to see if it improves the export.. This goes back to GP2010, but was still valid for 2013.

    dynamicsgpblogster.blogspot.ca/.../undocumented-dexini-switch-cuts-down.html

  • Community Member Profile Picture
    Community Member on at

    I just realized I misspoke in the text of my post. We're running GP 2015. Is there a detailed list of fixed bugs available somewhere?

    It sounds like the only way for me to report the bug or even find out of this bug is fixed is by using up a support ticket.

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

    Hi Chris,

    You may also want to check the regional settings of the user's workstation where the smartlist export takes places.. I've seen funky things going on when not using a standard US English setting... especially when it comes to decimals and date formats.

    On Customer Source when going into the download section of the various GP versions, there should be a list of the bug fixes since the last release... If you can't find it there, then you're next stop would be to check the MS Connect site (requires registration, but is free to everyone). This site is used to report feature improvement and bugs (for some products). Most likely if it's a bug, the support call to Microsoft will be free of charge.

  • Rochelle Mausteller Profile Picture
    Rochelle Mausteller 773 on at

    Chris,

    I am also experiencing this problem.  Were you able to find an answer?

  • Community Member Profile Picture
    Community Member on at

    We just upgraded to Dynamics GP 2016 and that resolved the problem.

  • Rochelle Mausteller Profile Picture
    Rochelle Mausteller 773 on at

    Chris,

    Thanks for your response.  I'll follow up with what I found.  We added the following to the dex.ini file and it resolved the problem with the comma.

    SmartlistEnhancedExcelExport=TRUE

  • Suggested answer
    adeel333 Profile Picture
    adeel333 487 on at

    A quick solution is to add following line in DEX.INI at the end:

    SmartlistEnhancedExcelExport=TRUE

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

#2
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans