Tuesday, 24 September 2013

Style Sheet Tool for Microsoft Dynamics NAV2013

The Style Sheet Tool for Microsoft Dynamics NAV2013 is available in Mibuso Downloads Section.

The Style Sheet Tool for Microsoft Dynamics NAV2013 enhances the Style Sheet feature in Microsoft Dynamics NAV 2013 by allowing you to easily and without programming knowledge create and modify style sheets in Microsoft Office Word.

Changes to Style Sheet tool for NAV 2013.

1.Multi-multiline support is added, so it is now possible to add several multiline records to the style sheet. Note though that records can not be indented, but added sequentially.

2.Setup page is modified to add Open/Save/Send options.

3.In NAV 2009, codeunit 50000 was released for automatic integration of the Style Sheet functionality with pages. Pages were then exported in xml format and modified by running codeunit 50000, to add style sheet actions.

This no longer works for NAV2013, as export /import of objects in xml format is no longer an option. Hence, adding Style Sheet Action (button) to each page must be done manually.

Follow the example below when adding the style sheet action to a page:

i. Add the action to the action designer (under appropriate group) with following properties:

Expanded Type SubType Name Caption
0 Action <Action680> Style Sheets

ii. OnAction trigger should contain following line:


where StyleSheetDataMgt is a variable of type codeunit, 682 (Style Sheet Data Management). 


  1. Hi Mohana,
    I cannot compile CU 680 because of an error message 'Could not load type 'Microsoft.Dynamics.Nav.Integration.Office.Word.WordHelper.'Microsoft.Dynamisc.NAV.Integration.Office, Version=,Culture=neutral, PublicKeyToken=31bf3856ad364e35".
    I have Office 2013 installed on my machine. I then tried to change the wordhelper G/L dotnet variable as well as the wrdmergefile local dotnet variable of CU680 in order to use Office vers but then I get an error message because of wrdmergefile := wrdmergefile.MergeHandler (MergeHandler function does not exist in 7.1).
    Any idea, solution ?

    Kind regards

  2. Try this :

    WordHelper  Microsoft.Dynamics.Nav.Integration.Office.Word.WordHelper.'Microsoft.Dynamics.Nav.Integration.Office, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

    Wrdmergefile  Microsoft.Dynamics.Nav.Integration.Office.Word.MergeHandler.'Microsoft.Dynamics.Nav.Integration.Office, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

    Wrdhandler  Microsoft.Dynamics.Nav.Integration.Office.Word.WordHandler.'Microsoft.Dynamics.Nav.Integration.Office, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

  3. Hi, did someone already make this work for NAV2013R2?


    Jan Jaap Smit

  4. I had the same problem, this worked for me:
    to compile CU 680 after I had to change all references in the CU from:
    "Microsoft.Dynamics.Nav.Integration.Office.Word.WordHelper.'Microsoft.Dynamisc.NAV.Integration.Office, Version=,Culture=neutral, PublicKeyToken=31bf3856ad364e35"

    Microsoft.Dynamics.Nav.Integration.Office.Word.WordHelper.'Microsoft.Dynamisc.NAV.Integration.Office, Version=,Culture=neutral, PublicKeyToken=31bf3856ad364e35