Skip to main content

Dynamics AX and project quotations in in .docx format

Just finished an assignment making a tool for Dynamics AX 2012R2 for creating project quotations in word, using AX data.
The customer is an ETO company manufacturing production lines for slaugtherhouses.

The tool should create a quotation file word document (.docx) using a word template (.dotx) prepared in a certain language. This would allow the customer to design the layout of the document in a easy and familiar way.

The spec required the quotation to include

Budgets with detailed information for each sub project of a main project.
Budgets summarized for each sub project of a main project.
Scope of supply, which contains short technical descriptions of the included units on the production lines (sub projects)
Technical descriptions - a section of the document containing listing (only once for each unit/sub project) complete descriptions with pictures of each included unit

The algorithm in short is this:



Now the challenge was that for most itemids in the item forecast of the projects, there exists a word document (product sheet) containing detailed product facts. Each product sheet contains four sections

a title
a short description
a middle long description (containing a picture of the unit)
a long description (containing a picture of the unit)

Depending on the user input in the dialog when running the tool, the tool should extract one or more of the sections of the product sheet (mentioned above), and include the extracted sections in the quotation word document.

I have used a 3rd party component called Aspose. This component allows you to work with several document formats, reading, editing and creating documents, without having to have the software normally used to work with the document format installed. That is, Dynamics AX can actually work with the documents SERVER SIDE without having to have Office installed on the AOS.

So I made a .dll in c# that the x++ code uses for the work to be done with the word files, and the x++ code is made so that we can replace the query with other queries if necessary.

The template setup contains features for

searching the word file for bookmarks for insertion of values
searching the word file for fields for insertion of values

The values that AX can insert are categorized as so:

Ordinary table.field values
Ordinary table.method values
A table of values (that can be Axtable fields og Axtable table methods)
A word document section (an extracted section of a separate word document)
A fixed text

The template can be setup by the user combining the bookmarks/fields to search for in the word document and the type of value to be inserted when found.

When a new template is created, the tool can examine the word template, and extract all bookmarks/fields (discover) so that the user has a basic setup he can use to map the ax fields/methods etc up against which bookmarks/fields should be substituted.
Again Aspose is used to do this.

We have used Aspose in other Dynamics AX projects:

Axapta version 3.0 - where we used Aspose to ensure that print out of .pdf-files was always the same page orientation (potrait) in connection with a AX report output )

Dynamics AX 2012 R3  creating .pdf-files for customer visits with user editable forms to send out to sales personnel - ensuring they can open the file and gather input regardless of hardware platform and being online or not.

Aspose is a good tool when you have to make applications that create or edit .pdf-.files, excel-files, word-files. It can even do imaging and OCR, though I haven't worked with those areas.






Labels:

Comments

Post a Comment

Popular posts from this blog

Suppressing the infolog

Supressing the infolog is often useful in D365FO when augmenting code. When augmenting code using COC (Chain Of Command), you can have new code run either before or after the code you are augmenting. This means that any infolog-messages that the standard application code does, will be shown to the user, even if your augmentation supports a scenario where there must be no infolog-messages. How do you avoid the standard application infolog-messages ? To the rescue comes temporary supression of the infolog. The suppression consists of: 1) Saving the current infologLevel 2) Setting the infologLevel to SysInfologLevel::None 3) Run your code 4) Restoring the saved infologLevel to the infolog For example a table could have a validatewrite-method that validates that you are only allowed to use 3 out of 6 options in an enum-field, and you need to allow for a fourth one. Table a - validateWrite method: boolean validateWrite() {     Switch (this.enumField)     {         boolean ret;         case
Post a Comment
Read more

Dynamics ax 2012 traversing selected records in a form data source

A classical developer challenge in Dynamics AX is to enable a form button when multiple records have been selected in the form by the user. This usually involves writing some form of loop (for or while or do-while) that starts out with calling _ds.getFirst() and continuing the loop as long as _ds.getNext() returns a tablebuffer. Well things got a little bit easier in AX 2012. In AX 2012 you can use the MultiSelectionHelper class. One example is the following that I encountered in AX 2012: Can you make the customer collection letter print out run for each selected collection record in the Print/Post collection letters form (Accounts receiveable / Periodic / Collections / Print/Post Collection letters). If we ignore the possibility for setting up print destination for running each report we can do this in two steps: 1) Change the "Multiselect" property of the "MenuButton" and the "Menuitembutton" in the MenuButton in the form from "Auto&quo
Post a Comment
Read more

Indicating mandatory field in a dialog (RunBase) class.

A classical problem is indicating that a field is mandatory in a dialog, when the field is not bound to a datasource/field in a datasource. Normally fellow developers will tell you that, that is not possible. I found a way to do this. In your Runbase-based class you can implement the putToDialog-method e.g like this: protected void putToDialog() { super(); fieldMask.fieldControl().mandatory(true); } where fieldMask is a DialogField object in your dialog. This will make the field act like it was a mandatory field from a datasource in a form, showing a red-wavy line under the field, and requiring the field to have a value. Attention: Your class has to run on the client.If you set your class to run on the server, you get a run-time error, when the fieldMask.FieldControl()-call is made.
1 comment
Read more