Automation lets you use the capabilities and features of Microsoft Office products, such as Microsoft Office Word or Microsoft Office Excel, in your Microsoft Dynamics NAV 2009 application. In this walkthrough, you will implement Word Automation from a Customer Card in the Classic client and RoleTailored client. You will set up the Customer Card so that if the customer has bought goods for more than LCY 2,500 during the past year, then the user can click a menu item or action to automatically create a letter in Word that offers the customer 3% discount. The letter will include information about the customer, such as the customer's name and the address, and the name of the contact to whom you will address the letter.
About This Walkthrough
This walkthrough illustrates the following tasks:
Creating a template in Word that will be used for Word documents that are created from the Classic client and RoleTailored client with Automation.
Creating a codeunit and declaring the Automation variables that are required for using Microsoft Office Word Automation.
Writing C/AL code in the codeunit to instantiate the Automation object that creates a Word document from a template.
Adding C/AL code to the Automation codeunit to transfer data from a table record to a Word document.
Calling the Automation codeunit from a menu item on a form or an action on page.
To complete this walkthrough, you will need:
Microsoft Dynamics NAV 2009 with a developer license.
The CRONUS International Ltd. demo data company.
Microsoft Office Word 2007 or Microsoft Word 2003.
Where to Get the Information for the Letter
Most information that you need to transfer to Word is in the Customer table. The Customer table contains a FlowField called Sales (LCY) that contains the aggregated sales for the customer. For this walkthrough, you are learning about Automation, so you use the existing value. In a real customer installation, you would need to set up an appropriate date filter to get the sales for the past year only.
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. This information is contained in the Company Information and User tables.
Where to Place Automation Code
You put all code in a separate codeunit that is called from a menu item on the Customer card. You must consider the following issues when you are deciding where to place the code that uses Automation:
The Automation server must be installed on the computer that compiles an object that uses Automation. 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. We recommend that you isolate code that uses Automation in separate codeunits.
Performance can be an issue if extra work is needed to create an Automation server with the CREATE system call. 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).
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. In this walkthrough, you are not putting the Automation code on the customer card but are isolating it in a separate codeunit. 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.
You can work around this problem. If Word is already open when it is called from the code, then the running instance is reused. You can manually open Word or do not close Word after creating the first letter.
Using Word in This Example
You will extract and transfer data one customer at a time. You also will initiate this processing and the subsequent processing in Word from the customer card. This approach to mail merge is different from a mail merge that you can achieve with C/ODBC, which is better suited for bulk processing when creating a large number of letters.
You will insert fields into the Word template and give these fields convenient mnemonic names that correspond to the names of the C/SIDE record fields that you are using.
To make this work, your C/AL code must make two extra calls to Microsoft Office Word. You must call the ActiveDocument.Fields.Update method before using the fields. After you have transferred all the information, you must call the ActiveDocument.Fields.Unlink method. This ensures that you can successfully use the Word fields as placeholders.
In addition, while you can name the fields Customer or Address, you must reference them by indexing into the Fields collection of the document. This can make the C/AL code harder to understand.
Creating the Word Template for Use by Automation
First, you create a Word template that you will use to create letters to customers that qualify for a discount. To create the template, you add mail merge fields for displaying data that is extracted from Microsoft Dynamics NAV 2009 that you want included in the customer letter, such as the customer's name, contact, and total sales.
To create the template
Open Word and create a new document.
Click where you want to insert the fields.
In Word 2007, on the Insert tab, in the Text group, click Quick Parts, and then click Field.
In Word 2003, on the Insert menu, click Field.
In the Categories list, select Mail Merge.
In the Field names list, select MergeField.
In the Field Name box under Field Properties, type Contact. This field will display the name of your contact person at the customer site as taken from the Customer table.
Repeat steps 2 through 5 to add the remaining fields as follows:
Field name Description Underlying table
The name of the customer.
The address of the customer.
The total amount that the customer has purchased from you.
The name of your company.
The name of the person generating this letter.
Save the Word document as a template with the name Discount.dot at C:\Documents and Settings\All Users\Templates or a folder of your choice.
Creating the Codeunit and Declaring the Variables
The next step is to create the codeunit that calls Word and creates the letter.
To create the codeunit
In Object Designer, click Codeunit, and then click the New button to create a new codeunit.
On the View menu, click Properties to open the Properties window of the codeunit.
In the TableNo field, click the AssistEdit button to open the Table List window.
In the Table List window, select the Customer table, and then click OK.
To declare the variables
On the View menu, click C/AL Locals, and then click the Variables tab.
On a blank line, type wdApp in the Name field and set the Data Type field to Automation.
In the Subtype field, click the AssistEdit button. The Automation Object List window is displayed.
In the Automation Server field, click the AssistEdit button.
In the Automation Server List, select Microsoft Word 12.0 Object Library if you are running Word 2007 or Microsoft Word 11.0 Object Library if you are running Word 2003, and then click OK.
From the list of classes in the Automation Object List, select the Application class, and then click OK.
Repeat steps 2 through 6 to add the following two Automation variables:
Name Data type Subtype Class
Microsoft Word 11.0 or 12.0 Object Library
Microsoft Word 11.0 or 12.0 Object Library
Add the following variables.
Name Data type Subtype Length
Writing the C/AL Code
Before you start writing the C/AL code that uses Automation, you must do some initial processing. You start by calculating the Sales (LCY) FlowField. Then, you check whether the customer qualifies for a discount. Finally, you retrieve the information from the Company Info and User tables that you use to fill in some of the fields in the letter.
To write the C/AL code
In the C/AL Editor, enter the following lines of code.
CALCFIELDS("Sales (LCY)"); IF ("Sales (LCY)" < 2500) THEN EXIT; CompanyInfo.FIND; UserInfo.GET(USERID);
To create an instance of Word before using it, enter the following line of code.
CREATE(wdApp, FALSE, TRUE);
This statement creates the Automation object with the
The first Boolean parameter in the statement (
FALSE) tells the
CREATEfunction to try to reuse an already running instance of the Automation server that is referenced by Automation before creating a new instance. If you change this to
TRUE, then the
CREATEfunction always creates a new instance of the Automation server.
The second Boolean parameter in the statement creates the Automation object on the client. This is necessary to use this codeunit on a page in the RoleTailored client.
If you do not use this codeunit in the RoleTailored client, then you can use the statement
CREATE(wdApp);instead. For more information, see .
Enter the following lines of code to add a new document to Word that uses the template that you designed earlier. If required, replace
C:\Documents and Settings\All Users\Templateswith the correct folder path to the template that you defined in the procedure .
TemplateName := 'C:\Documents and Settings\All Users\Templates\Discount.dot'; wdDoc := wdApp.Documents.Add(TemplateName); wdApp.ActiveDocument.Fields.Update;
Addmethod of the
Documentscollection requires that you pass the path to the template by reference, you must set up the
TemplateNamevariable to hold this information. You will get a compilation error if you put the path into the call as a literal string.
Documentsproperty returns a Documents collection that represents all open documents. You can also see that the Documents collection object has an Add method, and that the Add method has the following syntax.
expression.Add(Template, NewTemplate, Document Type, Visible)
expressionis a required argument, and it must be an expression that returns a Documents object. All the arguments are optional. You will use
Templateto open a new document that is based on your template.
For the syntax in the C/AL Symbol Menu, note that the Documents property returns an object of type DOCUMENTS, which is a user-defined type. The property returns a Documents class or IDispatch interface. This information helps the compiler perform a better type check during compilation. The following statement can also pass both the compile-time and the run-time type checks.
wdDoc := wdApp.Documents.Add(TemplateName);
Addmethod returns a Document class. While you did not need to declare a C/AL variable for the interim
Documentsclass, you have declared a variable for the
The third line contains a call that must be made to ensure that the template works as intended.
Transferring Data to Word
Now you can transfer the actual data from the Customer record to the placeholder fields in the Word document.
You have set up the first three fields in the template so that they can contain the contact, name, and address of the customer and you can transfer the data.
To transfer data to Word
Transfer the data by adding the following lines of code.
wdRange := wdAPP.ActiveDocument.Fields.Item(1).Result; wdRange.Text := Contact; wdRange.Bold := 1; wdRange := wdAPP.ActiveDocument.Fields.Item(2).Result; wdRange.Text := Name; wdRange.Bold := 1; wdRange := wdAPP.ActiveDocument.Fields.Item(3).Result; wdRange.Text := Address; wdRange.Bold := 1;
You cannot use the fields directly as variables and make an assignment such as
Fields.Item(3) := Address. Instead, you use the
Resultproperty of the field. This property returns the result of the field as a range. You place this range in the
wdRangeAutomation variable that you declared.
You then set the
Textproperty of the range to the desired values, which is the name of your contact person and the name and address of the customer. Finally, you add bold formatting.
The data you are transferring must be in text format. If it is not in text format, then you get a compilation error.
wdRange.Textexpects arguments to be of type BSTR, which maps to either Text or Code. This means that any data that is not Text or Code must be converted before it is passed to Word. To convert a field to
Text, you use the
FORMATfunction. All the fields that are transferred in this step are in text format, so no conversion is needed and the
FORMATfunction is not used. However, in this example, you also need to transfer the
Sales (LCY)field, which is a
Decimalfield. To see how to convert the
Sales (LCY)field, go to the next step.
To transfer and format the data from the
Sales (LCY)field, add the following code
wdRange := wdAPP.ActiveDocument.Fields.Item(4).Result; wdRange.Text := FORMAT("Sales (LCY)"); wdRange.Bold := 0;
For more information about the
FORMATfunction, see .
To transfer the information from the Company Information and User tables, ad the following code.
wdRange := wdApp.ActiveDocument.Fields.Item(5).Result; wdRange.Text := CompanyInfo.Name; wdRange := wdApp.ActiveDocument.Fields.Item(6).Result; wdRange.Text := UserInfo.Name;
To complete the processing in Word, add the following code.
wdApp.Visible := TRUE; wdApp.ActiveDocument.Fields.Unlink;
The first statement opens Word and shows you the letter that was created. The second statement makes the fields work as placeholders.
Save and compile the codeunit and give it a number and a name. For this walkthrough, use Discount Letter.
If you are running Word 2007 and you receive an error that states "The variable wdApp::MAILMERGEDATASOURCEVALI is defined more than once", then verify that you have defined the wdApp variable as a local variable, not a global variable.
Although this code will work, you must add a few things to make it complete:
We recommend that you do not use a hardcoded template name. You should keep the template name in a table, and the user should select it from a page. You can then have different templates for different types of letters that you want to send to your customers.
You should add some error-handling code. For example, the
CREATEcall fails if the user does not have Word installed or if the installation has been corrupted. You should check the return value of
CREATEand give an appropriate message if it fails.
The user should get a message if the customer does not qualify for the discount. In the example, the codeunit closes without any message.
Calling the Codeunit from the Customer Card
The final task is to ensure that you can call the codeunit from the Customer Card form in the Classic client and the Customer Card page in the RoleTailored client.
To call the codeunit from the Customer Card form in the Classic client
Open Object Designer, and then click Form.
Select the Customer Card form, and then click Design.
Right-click the Customer menu button, and then click Menu Items.
Select the last line in the list of menu items, and then click Separator to insert a separator line.
In the next line below the separator line, in the Caption field, type the text Word Letter, which will appear in the menu.
In the Action field, click the lookup button, and then select RunObject.
In the RunObject field, click the lookup button, and then select the codeunit that you have created.
Save and compile the Customer Card form.
To call the codeunit from the Customer card page in the Classic client
Open Object Designer, and then click Page.
Select the Customer Card page and then click Design.
At the bottom of Page Designer, right-click a blank line, and then click Actions.
To add a new action, locate the action container with the subtype set to ActionItems.
Right-click the next line after the ActionItems container, and then click New.
In the Caption field of the new line, type Word Letter.
Set the Type field to Action.
With the new action selected, on the View menu, click Properties.
In the RunObject field, type codeunit Discount Letter.
If you saved the codeunit that you created in the previous procedure under a different name, then substitute Discount Letter with the name that you used.
Save and compile the Customer Card page.
The letter that you have just created only contains six fields and no body text. Before you can use this letter in an actual situation, you will need to add some more fields, such as the name and address of your own company, the date, and the currency code, and the main text of the letter. It will also need some formatting to make it look more attractive. If you alter the order in which the fields appear in the template, you must change the numbering of the fields in the codeunit to ensure that the correct data is inserted into the appropriate fields.