Microsoft Dynamics NAV Style Sheet Tool v1.1

Administrator
Member, Moderator, Administrator Posts: 2,506
Microsoft Dynamics NAV Style Sheet Tool v1.0
The Style Sheet feature in Microsoft Dynamics NAV 5.0 has been enhanced with a new tool that allows you to easily and without programming knowledge create and modify style sheets in Microsoft® Office Word.
The release of Microsoft Dynamics NAV 5.0 introduced the option to export any form (apart from matrix forms) from Microsoft Dynamics NAV to Microsoft Office® Word and Excel®. By simply clicking a button, Microsoft Dynamics NAV will generate an XML document that works in conjunction with an XML style sheet that passes the requested information to either Word or Excel.
Seven style sheets are included in Microsoft Dynamics NAV. You can read about these in the White Paper ‘Creating XML Style Sheets for Data Export from Microsoft Dynamics NAV 5.0’. However, if you want to create more style sheets or modify an existing one, you need to have knowledge of XML and C/AL programming in order to add the relevant data elements.
To simplify this process, a style sheet tool has been created that does not require programming knowledge. The first version of this tool will support the export of data to Word, and this means that the only skill required to create additional style sheets is some end-user knowledge of Word.
The Microsoft Dynamics NAV Stylesheet Tool supports integration to Microsoft Word 2003 and Microsoft Word 2007.
It consists of a fob file and a user guide.
Note: To be able to use the tool, a license update is required.
http://www.mibuso.com/dlinfo.asp?FileID=869
Discuss this download here.
The Style Sheet feature in Microsoft Dynamics NAV 5.0 has been enhanced with a new tool that allows you to easily and without programming knowledge create and modify style sheets in Microsoft® Office Word.
The release of Microsoft Dynamics NAV 5.0 introduced the option to export any form (apart from matrix forms) from Microsoft Dynamics NAV to Microsoft Office® Word and Excel®. By simply clicking a button, Microsoft Dynamics NAV will generate an XML document that works in conjunction with an XML style sheet that passes the requested information to either Word or Excel.
Seven style sheets are included in Microsoft Dynamics NAV. You can read about these in the White Paper ‘Creating XML Style Sheets for Data Export from Microsoft Dynamics NAV 5.0’. However, if you want to create more style sheets or modify an existing one, you need to have knowledge of XML and C/AL programming in order to add the relevant data elements.
To simplify this process, a style sheet tool has been created that does not require programming knowledge. The first version of this tool will support the export of data to Word, and this means that the only skill required to create additional style sheets is some end-user knowledge of Word.
The Microsoft Dynamics NAV Stylesheet Tool supports integration to Microsoft Word 2003 and Microsoft Word 2007.
It consists of a fob file and a user guide.
Note: To be able to use the tool, a license update is required.
http://www.mibuso.com/dlinfo.asp?FileID=869
Discuss this download here.
0
Comments
-
Great, it seams very nice, however i have got a quesstion. Maybe I am missing something. It seams that Table Relationships work only for the "Base Table". For instance if you want to create a template for Sales order you can attach the Customer Table to the Header and get Customer's Info but i could not find a way to attach the Item table to the lines to get Item information. Am I missing something?Best Regards,
Oleg0 -
Does anyone knows how to export pictures to these templates?
Example, Company LOGO or Item Pictures?0 -
wwestendorp wrote:Does anyone knows how to export pictures to these templates?
Example, Company LOGO or Item Pictures?
Hi wwestendorp
did you find out how to export Item Pictures?
Or does anybody else know how to do that?
It would be really great if someone could tell me how to export pictures.0 -
Hi,
How can I make a link with some tables.
Example :
Item Card with :
table for sales prices
table for purch prices
Comment
When I do this, only the first table is multi-line. The others don't work.0 -
I use the tool to make a exerise for item card. But when click "Send Option" and select the "item card", and click "Send", I only see the origin mail merge. the tag still on document. and does not change to the real item data. Can anyone tell me whick step should I notice?0
-
If I understood you correctly you followed all the steps in the guide to create style sheet, but instead of a Word document with item data, you got a Word document with the original merge fields?
I've seen something like that happen on rare occasions, but when trying to reproduce it just doesn't wan't to do it.
One way I've solved it myself, was to export the definition and merge docs, delete the definition in NAV, and then re-import the documents and have the system generate a new style sheet - this seems to work . . .
What's even more funny is that if you the delete the item defintion in the system and try to do exactly the same steps as when you originally created the first definition - the error does not show up!!??
Hope this helps.0 -
wwestendorp wrote:Does anyone knows how to export pictures to these templates?
Example, Company LOGO or Item Pictures?
As the normal way I mean as described in the whitepaper
LnZ0 -
Microsoft Dynamics NAV Style Sheet Tool v1.1
The Style Sheet feature in Microsoft Dynamics NAV 5.0 has been enhanced with a new tool that allows you to easily and without programming knowledge create and modify style sheets in Microsoft® Office Word.
The release of Microsoft Dynamics NAV 5.0 introduced the option to export any form (apart from matrix forms) from Microsoft Dynamics NAV to Microsoft Office® Word and Excel®. By simply clicking a button, Microsoft Dynamics NAV will generate an XML document that works in conjunction with an XML style sheet that passes the requested information to either Word or Excel.
Seven style sheets are included in Microsoft Dynamics NAV. You can read about these in the White Paper ‘Creating XML Style Sheets for Data Export from Microsoft Dynamics NAV 5.0’. However, if you want to create more style sheets or modify an existing one, you need to have knowledge of XML and C/AL programming in order to add the relevant data elements.
To simplify this process, a style sheet tool has been created that does not require programming knowledge. The first version of this tool will support the export of data to Word, and this means that the only skill required to create additional style sheets is some end-user knowledge of Word.
The Microsoft Dynamics NAV Stylesheet Tool supports integration to Microsoft Word 2003 and Microsoft Word 2007.
It consists of a fob file and a user guide.
Note: To be able to use the tool, a license update is required.
The following issues have been corrected in version 1.1:
- If a Header or Footer was specified, the Style Sheet Tool ignored them.
- If a long option strings was defined for a field, the user received a text overflow error message.
- When changing local languages, the Style Sheet tool only looked for a '.' instead of the local language decimal separator.
- When you create the mail merge document, the Style Sheet Tool would ignore the landscape orientation.
- If you have created a table relationship and the value being looked up doesn't exist, the style sheet won't load. If you close down NAV then you would get an error indicating that the value couldn't be found.
- When using page numbers (page x of y), then all pages come out as page 1 of 1
http://www.mibuso.com/dlinfo.asp?FileID=869
Discuss this download here.0 -
Hi,
what does "Note: To be able to use the tool, a license update is required." excatly mean? I know how to update a license, but do I have do pay for it in this case?
Cheers,
Bob
edit: It's free.0 -
It uses new objects, so the customer license need to be updated (for free).0
-
I'm using Style Sheet Tool v1.1 (StyleSheetToolW111.fob dated 10/29/07)
Relates to replies in this thread from
SRAD750Example :
Item Card with :
table for sales prices
table for purch prices
Comment
When I do this, only the first table is multi-line. The others don't work.
and
zeninolegIt seams that Table Relationships work only for the "Base Table". For instance if you want to create a template for Sales order you can attach the Customer Table to the Header and get Customer's Info but i could not find a way to attach the Item table to the lines to get Item information. Am I missing something?
Also relates to another similar topic with subject:"Multiple multi lines in style sheets" http://mibuso.com/forum/viewtopic.php?t=23007&start=0&postdays=0&postorder=asc&highlight=style+sheet&sid=76729974b89d6c5e5a0e74c7514d366f
I've debugged and diagnosed the reason. NAV incorrectly creates a beginning TR tag(beginning of table) and ending TR tag(End of table) when building the XML node for the table. It does not account for two tables within a single style sheet. So the result is a table with a begining TR and ending TR with the end of the first table and begining of the second sandwiched in as text.
Workaround is to modify the XML. You need to create a style sheet with table 1 as you would normally. I'll call this "MAIN". Create the second table as a basic empty table with no merge fields. Save it. Then create another style sheet with just the second table formatted the way you want. I'll call this one "Second Table". Save it, then open (xslt file) in XML editor. Copy the table node from "Second Table" and paste it over the table node in "MAIN". Save.
This solution would need to be duplicated every time the Style Sheet is modified via Word, which is what the client will no doubt use. Not a great solution unless you have a style sheet that doesn't change often and you have someone willing to get their hands dirty doing a little XML editing.
Hopefully, MS will fix this issue in coming releases of the Style Sheet toolkit.Jon Long - ArcherPoint
MCP - Dynamics NAV0 -
I have some problems with Microsoft Dynamics NAV Style Sheet Tool v1.1
I have used it for export sales quote on Ms Word.
I have created some table relation to a new table ( > 50000 - MyTableName) but when exporting the fields are not recalculated for this table - it comes : «RELATION_MyTableName» and not the value. The others relations to standard tables work... Is that normal? Is there some work around?
Thank you very much0 -
The other problem is that if I insert a MergeField in Page Footer - for example: «Sales_Header_No», it comes updated when I have the Word Document on screen but when I make a print preview of a print on printer it shows the variable name «Sales_Header_No» and not the value of Document No.
The same merge field out from page footer is printed correctly.
Thank you very much0 -
I have the same problem with multiline tab, only the first multiline tab is show..
I've test your solution but what .xslt file I have to modify ?0 -
Bromann wrote:If I understood you correctly you followed all the steps in the guide to create style sheet, but instead of a Word document with item data, you got a Word document with the original merge fields?
I've seen something like that happen on rare occasions, but when trying to reproduce it just doesn't wan't to do it.
One way I've solved it myself, was to export the definition and merge docs, delete the definition in NAV, and then re-import the documents and have the system generate a new style sheet - this seems to work . . .
What's even more funny is that if you the delete the item defintion in the system and try to do exactly the same steps as when you originally created the first definition - the error does not show up!!??
Hope this helps.
I've got the same problem. Tried your suggestion but nothing helps.
Have anyone other suggestions?0 -
I have the same. Even doing everything as in UG.
See screenshots for proof.
Every table/field like in UG
Making even mail merge like in UG
Choosing just created style sheet for item with filled all neccessary fields
... And got bad luck
Tried to use created and exported style sheet to xslt.
Configuring
... still bad news...
Why does not it work?
[upd] lolz, just noticed I posted step6 instead of step5 screenshotIt is hard to swim against self bloodstream... (c) Old, experienced kamikadze.0 -
Another problem i am facing that Style sheet transfers everything in Text only.
Like Quantity, Amount fields are also transferred as Text. After exporting data in excel, i can't perform any integer or decimal function in excel.... ](*,)
Please do needful help...0 -
mahesh wrote:Another problem i am facing that Style sheet transfers everything in Text only.
Like Quantity, Amount fields are also transferred as Text. After exporting data in excel, i can't perform any integer or decimal function in excel.... ](*,)
Please do needful help...Regards,
Arturs Gedvillo
CTO0 -
andy76 wrote:The other problem is that if I insert a MergeField in Page Footer - for example: «Sales_Header_No», it comes updated when I have the Word Document on screen but when I make a print preview of a print on printer it shows the variable name «Sales_Header_No» and not the value of Document No.
The same merge field out from page footer is printed correctly.
Thank you very much
I have the same problem and I stil haven't figured out how to solve it, does anybody know how to face this point?
Thank you!!0 -
I have a problem with the Style Sheet Tool v1.1 in NAV 5.0.
I would like to export data from a form that has more than 200 fields to Word file.
I selected the fields to export in Style Sheet Card, but when I click Open Mail Merge and when Word opens I can't see all the fields I selected, I can see and use only 51 caption and 12 values.
Does anyone know what the problem could be?0 -
natalija_nav wrote:Does anyone know what the problem could be?No support using PM or e-mail - Please use this forum. BC TechDays 2024: 13 & 14 June 2024, Antwerp (Belgium)0
-
Thank you very much on your answer!0
-
Luc Van Dyck wrote:The max. number of data fields that can be used in Word is 63 ... but I'm unable to find a reliable source for this statement. I only found some postings in various forums describing this issue.0
-
natalija_nav wrote:Do you know if this limitation can be corrected in any way so I can export more data?No support using PM or e-mail - Please use this forum. BC TechDays 2024: 13 & 14 June 2024, Antwerp (Belgium)0
-
In our solution, I have implemented the multi-multiline modification from this website, but there remains the limitation of only being able to link to the base table.
Now I have, after some effort, managed to partially lift that limitation, so that I can now link tables to non-base tables (e.g. link Resource to Salesperson to Customer to Sales Header, etc.); this, however, is limited to non-multiline tables.
Has anyone managed to crack this for multiline, e.g.: link Item to Sales Line (multi) to Sales Header?0 -
Hello,
I saw a lot of same problem that merge fields are not parced (replaced by actual value) - did any found solution?
I have the same problem now with Office 2007 + NAV5.0 + StyleSheetToolW111.
It is interesting tha I have tested it on other machine Win7 + Office2010 + NAV2009 (installed) + but used NAV5.0 client + StyleSheetToolW111 - it was working, BUT then I tried to install Office2007 (it still was working untill I change template) unistall Office2007 try to generate new Word template in F680 - now new template is not correct as well. So it seems that some Office library is not working as expected and process prepare buggy StyleSheet...
Any ideas?
Thanks in advance.Jurijs Staubs
Navision developer, (3 years in NAV)0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions