Announcements
We have a Dynamics GP 2018 installation with Workflow. When sending out email attachments through Workflow the filename has a bunch of whitespace after the file extension and then an underscore.(e.g., Filename.pdf _) When the attachment is received it can't be opened with most email programs. The user has to save the attachment stripping off the excess beyond the file extension. Looking at the SQL 2014 database the Table dbo.coAttachmentItems has a column named fileName which is a char(255). My understanding of char is that it requires in this case a 255 character file name and will fill the unused characters with white/blank spaces to reach the 255 character setting. I may be way off, I am not a database guy. Some email clients will handle the attachment just fine. For instance the IOS version of Outlook recognizes the attachment as a pdf and allows me to open it. The desktop version of Outlook as well as G-suite(gmail) doesn't strip off the blank spaces and the underscore so it doesn't recognize the file type. Is this an isolated incident or has anyone seen this before? I tried deleting the dbo.coAttachmentItems table and recreating it with the fileName column as a varchar with no success. Is there something in the Workflow settings I can change to fix this or is this an SQL issue? Any assistance with this would be greatly appreciated. Thank you
*This post is locked for comments
I didn’t ever find a solution to this using our G-suite email accounts. I had no problem with Office 365 accounts. I have not done anything with Workflow since July but I am just getting back to it now. Our Office manager spoke with a consultant that was familiar with this issue and thinks he can fix it. He says it is a setting in the software. We are switching from G-suite to Office 365 anyway so I am not going to spend any more time on it. If I am able to get the fix out of the consultant I will share it with you. Stephan Kline, thank you for your help.
Hello,
I think you're somewhat on the right path for this in looking at the varchar option in the coAttachmentItems table. The trouble is that if the attachment was brought into or modified in GP with those extra spaces and the underscore, changing the column to varchar would have no impact.
To see if that is the case in the Filename column, set the Results to File (.RPT), and then run a simple select statement on the coAttachmentItems table. Once you have the file, open the results using a simple text editor (Notepad++ is what most folks use) and see if the spaces and underscore are present. If they are, that will at least eliminate the possibility that the spaces/underscore are being added by your Workflow and leaves you looking at how Doc Attach is being used or modified. Some questions to keep in mind:
Are the source filenames being modified during the attach process in GP?
Does the issue still occur without any 3rd Party customizations?
If you change the Default Location in the Doc Attach configuration (i.e. to another location on your local workstation), does the issue still occur?
Do the source filenames also contain the spaces/underscore?
Ultimately, the destination email server client (G-suite, Outlook) is a non-factor if those are attachments are leaving GP with the spaces/underscore in place. Hopefully this gives you a little more insight into the next areas you can look at!
Hi, did you finally solve this issue?? i have the same trouble.
Best regards
André Arnaud de Cal... 291,359 Super User 2024 Season 2
Martin Dráb 230,370 Most Valuable Professional
nmaenpaa 101,156