And they way it is designed it needs to use Code.GetData and Code.SetData. So here we are, NAV 2013 have just been released and standard report 206 is still using Code.GetData and Code.SetData, just like it did in NAV 2009. Here is a screenshot of the header in standard report 206 in just released NAV 2013:Īs you can see a lot of > all over and not really human readable, and it gets worse when opening one of these expression, because the values are just Code.GetData and a number.Īnd here is a screenshot of the header after my changes which I explained in details in this post:Īs you can see now all fields are visible and if you need to make modification it easy to locate where your changes need to take place. Looking at the before and after images should give you an idea what this post is all about. This blog post is pretty long so I would like to show you the header in Report 206 before and after my changes. Actually when I realized that this was possible in RDLC 2008, I was actually crying, because this limitation in RDLC 2005, used NAV 2009, has been a huge pain, at least for me.īut in I this example which I’m about to show you, I will not use this new capability in RDLC 2008. Yes we can now add fields directly into the header in RDLC 2008, used in NAV 2013. Just adding the field in the header will not keep this synchronization, unfortunately. Code.GetData and Code.SetData is used in the header to of the report to keep field values in sync with current sales order currently being printed in the body. The goal with this post is to show how NOT to use Code.GetData and Code.SetData in the one of the most common used Document report in NAV, our beloved 206 report.