Redesign Report Layout on 3 tier

Belias
Member Posts: 2,998
here's a useful link a colleague suggested me.
It lists some of the features that existed in classic reports, and how to replicate them in RDLC, enjoy!
http://msdn.microsoft.com/en-us/library/dd338753.aspx
It lists some of the features that existed in classic reports, and how to replicate them in RDLC, enjoy!
http://msdn.microsoft.com/en-us/library/dd338753.aspx
0
Comments
-
Very helpful :thumbsup:
It would be even more helpful if there were sections on this list on how to create the pageloop and copyloop. It would be great if there were a section on how to re-create a rudimentary invoice (or shipment, or proforma, order confirmation, something like that) from scratch. Start with nothing, and explain how to build a proper document type report.0 -
Manual NA2009_ENUS_REP_03.pdf
page 27 (chapter Anatomy of the Sales Invoice Report)
i couldn't find time to read it, but i think that it clarifies a lot of questions we have about that damn 206th report0 -
The NA version of the sales invoice is very different from the WW version. I think Daniel is looking for the NA version.
After digging around, the least documented portion is the GetData and the SetData used on the report. On my blog, I described how to add fields to the header portion of the document. It's not an easy process, by the way.Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0 -
Alex Chow wrote:...the least documented portion is the GetData and the SetData used on the report...
Especially the fact that i wanted to print the page number in the body section of the rdlc. I created the setdata in the header, and the getdata in the body: blank textbox, because it seems that the body is rendered before the header :shock:
Moreover, the "Globals!pagenumber" can only be used in the header section, so i couldn't use setdata in the body (because the parameter of the setdata is globals!pagenumber).
i solved it (credits to a colleague of mine, too) by creating a footer section, and i put the Getdata (which is, the page number) in there.
the strange thin is that in the preview you can see the correct page number, but you can't see it in the PRINT preview.
If you save the report as pdf, the value of the getdata function appears in the pdf file. :-k
Last note: Reportitem!<textbox> is visible only in preview mode, but the value disappears in the PRINT preview, and also in the final print (or pdf)
I hope to have explained it clearly (i've not read your blog post, Alex...i probably repeated something, sorry if it is the case)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