You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: dynamics-gp/installation/word-templates.md
+18-16Lines changed: 18 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -426,27 +426,29 @@ Make regular backup of your word template as you are working, in case you make a
426
426
## Error message The template you selected cannot be added to this report
427
427
428
428
1. Can you modify a pre-existing template and import without the error? If yes, it could be something with the file you are trying to import, see #7 below.
429
+
1. Open up the xml file that you generated with notepad. Look at the top of the xml.
429
430
430
-
2. Open up the xml file that you generated with notepad. Look at the top of the xml.
431
-
In the dictionary node, if you see a line like this: <Main Path="C:\GP2018\">Dynamics.dic</Main>
432
-
Then the xml has been generated on the original, not modified report.
433
-
If you see something like this: <Main Path="C:\GP2018\">Dynamics.dic</Main>
Then that means that you generated the xml on a modified (in report writer) report.
436
-
The versions also have to match and if this is an alternate report then that could also cause a problem.
437
-
You will also want to check the xml name. It should be something like this: XMLNAME="SOP Blank Picking Ticket Order Entered" (example report)
438
-
Now you know the report name and whether it's modified or original, go into the Template Maintenance window and be sure to choose the report that matches the XMLNAME and either original/modified.
431
+
If you see a line like the following in the dictionary node, then the xml has been generated on the original, not modified report:
432
+
433
+
`<Main Path="C:\GP2018\">Dynamics.dic</Main>`
439
434
440
-
3. Rule out the Logo on the report and if that is causing an issue.
435
+
If you see something like the following lines, it means that you generated the xml on a modified (in report writer) report.
436
+
437
+
`<Main Path="C:\GP2018\">Dynamics.dic</Main>`
441
438
442
-
4. Make sure the form is set to compatibility. Always check the box to Maintain compatibility with previous versions of Word before saving. Only available the first time the document is saved.
6. Verify the XML file is connected to the correct report format.
441
+
The versions also have to match and if this is an alternate report then that could also cause a problem.
442
+
443
+
You will also want to check the xml name. It should be something like this: `XMLNAME="SOP Blank Picking Ticket Order Entered" (example report)`
444
+
445
+
Now you know the report name and whether it's modified or original, go into the Template Maintenance window and be sure to choose the report that matches the XMLNAME and either original/modified.
447
446
448
-
7. If you received this template package from an email, there is a chance the email security systems can potentially remove or block XML resources.
449
-
Many email security filters scan attachments for potentially harmful content, including XML files, which can be flagged or removed if they are deemed suspicious or contain malicious code.
447
+
1. Rule out the Logo on the report and if that is causing an issue.
448
+
1. Make sure the form is set to compatibility. Always check the box to Maintain compatibility with previous versions of Word before saving. Only available the first time the document is saved.
449
+
1. Make sure the file is unlocked.
450
+
1. Verify the XML file is connected to the correct report format.
451
+
1. If you received this template package from an email, there is a chance the email security systems can potentially remove or block XML resources. Many email security filters scan attachments for potentially harmful content, including XML files, which can be flagged or removed if they are deemed suspicious or contain malicious code.
450
452
Open the file and check the XML resource connected to the template, if it is missing, that will cause the error.
0 commit comments