mibuso.com
Home› NAV Three Tier

2013 RTM Report design on documents

sbesbe Member Posts: 4
edited 2012-10-11 in NAV Three Tier
I just downloaded 2013 RTM and wonder why the reports sales quote, sales invoice, etc. still use code.setdata and code.getdata in the header.
At the same time, all labels are removed from the new meu, made for this? Does anyone know if this is how the documents should be made in 2013?

Answers

  • ara3nara3n Member Posts: 9,256
    The reason is that the Page Header and footer can only print first or last record. Sales Invoice report will work fine without using getdata and setdata if you are printing a document one at a time. If you are printing multiple invoices then the Page Header will not be the same far all the invoices. That's why they are still using get and set data.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • sbesbe Member Posts: 4
    Thanks for the reply, it makes good sense.
    Now the question is whether the same also applies to labels?
    Why not use labels in the header, and in this way made ​​the report easier to work with in Visual Studio?
  • Alex_ChowAlex_Chow Member Posts: 5,063
    ara3n wrote:
    The reason is that the Page Header and footer can only print first or last record. Sales Invoice report will work fine without using getdata and setdata if you are printing a document one at a time. If you are printing multiple invoices then the Page Header will not be the same far all the invoices. That's why they are still using get and set data.

    Not really. If you don't use getdata and setdata, if one of your invoice is gets to page 2, it will break.
    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 book
  • Torben_Wind_Meyhoff[MSFT]Torben_Wind_Meyhoff[MSFT] Member, Microsoft Employee Posts: 22
    Labels are passed in as parameters and are made once per report execution right after OnPreReport trigger.
    Sales Headers can change the language page by page and labels must be created in the data set to be localized correctly.
    BR
    Torben Wind Meyhoff [MSFT]
    “This posting is provided "AS IS" with no warranties, and confers no rights.”
  • clauslclausl Member Posts: 455
    Take a look at my blog post here for how to simplify Document Reports. We really don't need to use Code.GetData and Code.SetData.

    http://mibuso.com/blogs/clausl/2012/10/03/simplifying-document-reports-in-nav-2013/

    /Claus Lundstrøm
    Claus Lundstrøm | MVP | Senior Product Manager | Continia.com
    I'm blogging here:http://mibuso.com/blogs/clausl and used to blog here: http://blogs.msdn.com/nav
    I'm also offering RDLC Report Training, ping me if you are interested. Thanks to the 700 NAV developers that have now already been at my training. You know you can always call if you have any RDLC report issues :-)
  • sbesbe Member Posts: 4
    Hi, thanks for the replies, I am now somewhat wiser in this area, as it now makes more sense, and I feel ready to really get started with the documents :D
Sign In or Register to comment.