Creating the Word Template for Use by Automationįirst, you create a Word template that you will use to create letters to customers that qualify for a discount.
#Microsoft word templates letter code#
This can make the C/AL code harder to understand. In addition, while you can name the Customer or Address fields, you must reference them by indexing into the Fields collection of the document. This ensures that you can successfully use the Word fields as placeholders. After you have transferred all the information, you must call the method. You must call the method before using the fields. To make this work, your C/AL code must make two extra calls to Microsoft Office Word. You will insert fields into the Word template and give these fields convenient mnemonic names that correspond to the names of the record fields that you are using. You also will initiate this processing and the subsequent processing in Word from the customer card. You will extract and transfer data one customer at a time. You can manually open Word or do not close Word after creating the first letter. If Word is already open when it is called from the code, then the running instance is reused. Performance can be improved by putting the code on the customer card because you do not have to open and close Word for each letter that is created in the session. In this walkthrough, you are not putting the Automation code on the customer card but are isolating it in a separate codeunit. These two issues may clash, and you will have to make some tradeoffs that are based on the actual context in which your code will be used. If the Automation server is to be used repeatedly, then you will gain better performance by designing your code so that the server is created only once instead of making multiple CREATE and CLEAR calls). Performance can be an issue if extra work is needed to create an Automation server with the CREATE system call. We recommend that you isolate code that uses Automation in separate codeunits. If you must recompile and modify an object on a computer that does not have the Automation server installed, then you must modify the code to compile it again. The Automation server must be installed on the computer that compiles an object that uses Automation. You must consider the following issues when you are deciding where to place the code that uses Automation: In this walkthrough, you put all code in a separate codeunit that is called from a menu item on the Customer Card page. This information is contained in the Company Information and User tables. You also need to retrieve the information about your own company that you will use in the letterhead and in the greeting of the letter. In a real customer installation, you would need to set up an appropriate date filter to get the sales for the past year only. For this walkthrough, you are learning about Automation, so you use the existing value. The Customer table contains a FlowField called Sales (LCY) that contains the aggregated sales for the customer. Most information that you need to transfer to Word is in the Customer table. Where to Get the Information for the Letter Microsoft Word 2013 or Microsoft Word 2010. Microsoft Dynamics NAV 2018 with a developer license. To complete this walkthrough, you will need: Writing C/AL code in the codeunit to instantiate the Automation object that creates a Word document from a template.Īdding C/AL code to the Automation codeunit to transfer data from a table record to a Word document.Ĭalling the Automation codeunit from an action on a page.
#Microsoft word templates letter windows#
This walkthrough illustrates the following tasks:Ĭreating a template in Word that will be used for Word documents that are created from the Microsoft Dynamics NAV Windows client with Automation.Ĭreating a codeunit and declaring the Automation variables that are required for using Microsoft Office Word Automation. The Microsoft Dynamics NAV Web client does not support automation.
0 kommentar(er)
