It’s important to note that Dynamics GP 2016 is out of mainstream support in July 2021 so that version will not receive any further year-end updates for regulatory changes, so you will need to organise an upgrade to the latest version next year.
Word experienced an error trying to open the file.
Try these suggestions.
* Check the file permissions for the document or drive.
* Make sure there is sufficient free memory and disk space.
* Open the file with the Text recovery converter.
(C:...transaction Edit List.docx)
I did some research and found there was a recent post on the Dynamics GP Support and Services Blog where they covered this same issue. The blog post was only four days ago and they acknowledge the issue is ongoing and offer the workaround of downgrading Microsoft Office to work around the issue (I did this recently when sending emails using MAPI caused Dynamics GP to crash).
The problem does not just affect the Word template reports from Workflow Batch Approval emails, but also the Word templates used for sending purchase or sales orders, remittances and so on. For the non workflow Word templates, you could reconfigure the templates to use PDF, or one of the other formats, instead of Word, but, unfortunately, this option is not available for the batch edit lists.
Following the initial report, we’ve had a number of other clients report the issue, so it may be worth preempting problems and block Office updates for Dynamics GP users until a fix is in place from Microsoft.
There appeared to be no pattern on which approval emails either did or did not include the Word template; a user would receive the Word template on to emails, then not on the third, but again receive it on the fourth.
Doing some searching online found a post by Rob Klaproth of Armanino where he had the same issue and confirmed that there is a known issue logged with Microsoft whereby when the user submits a document for approval, and clicks submit on the comment box before the Word template has finished generating the email will not include the Word template.
The workaround for this issue is to make sure that users wait until the Word template has finished processing, as shown by the Template processing message at the bottom of the main Microsoft Dynamics GP window. If they wait until this processing has completed before hitting submit, the Word template will be included on the notification email.
This issue affects all of the edit list Word template attachments through all of the Workflow approval types.
The twenty-third new feature is Email POP PO Other Form. This feature makes the Purhcase Order Other Form available for email.
My hands on with the feature was somewhat abbreviated when I discovered that there was no default Word Template available. While technically allowing a PO to be emailed using the Other Form, the lack of a default Word Templates means that there is a large amount of effort involved to make it available.
To create a new Word Template, you need to use the Word Template Generator to create a Word Template from the Report Writer XML and then format the resulting template; this is a long, complex and difficult to process to do in order not to break the template so email, or even the Word Template itself, doesn’t get broken.
At some point after this, and I am not sure in which version, the ability to email the reprinted remittance was introduced:
Microsoft Dynamics GP 2013 R2 saw the introduction of the Workflow 2.0 (which was the subject of my fourth book. Workflow 2.0 was enhanced further in both Microsoft Dynamics 2015 R1 and R2, and is again being improved in Dynamics GP 2016 R1.
This time, the enhancement is a twofold one. Firstly, the Batch Edit lists have a default Word Template and, secondly, this can be emailed to the workflow approver:
The main features of are:
- Workflow Batch Approvals now have a default Word Template for the following edit lists:
- General Ledger Batches
- Payables Batches
- Receivables Batches
- Can be emailed to approver for complete information before approving
I think this feature will prove to be popular with those clietn using Workflow approvals as an approver will always want s much information before approving as possible. This will likely be of great interest when Workflow approvals are being used.
To help the client make the transition from the old to the new, I created an SQL script to transfer the email addresses from the table, RM00106 (RM Statement Emails) used by the old Adobe Writer to the SY01200 (Address Email Master) used by the Email Documents functionality.
After a couple of fruitless minutes checking the modified report and creating a new version of the Word template without success I started wondering about already open applications. In particular MS Word itself was already running with an unrelated document open.
I closed down all open Word documents and, in Template Maintenance (), clicked the Modify button; when the Word template opened the new fields were showing in the XML schema.
This is something I have experienced before without being able to pin down why which caused..shall we say…a certain level of frustration. I’m not sure why having Word open caused the XML schema not to be refreshed when creating a new document, I am pleased that at least I can void the problem by making sure all open instances of Word are closed before starting.
Everything appeared fine during development and initial testing. Fine that is until we tried producing a batch of twenty remittances which produced the following two error messages: