This is a well-known issue, which is how you mentioned, based on the way the dataset matrix is built between old nav/BC and Reporting Services. It has never been lean. So adding the description 2 field itself will cause these additional lines and the layout has to choose the right one. This is why a variable has to be passed to the Reporting Services engine.
Why are you trying to extend 10074? does it have functionality that 1306 doesn't? ive used report extensions numerous times for 1306 (the standard Invoice Report) and you are able to extend it exactly as you try first time. I
Assuming you actually prepared for the video and did everyting on the fly this would be like a 2hour fix (at least for me) resulting in not wanting to have this "dirty" code in my app anyway. Most would've probably given up after seeing that the TempLines were not marked as protected. And from that point i rather copy the report than have some code that nobody else will understand and page me about.
@@Hougaard When reportextensions are so complicated and time consuming what's the point of spending so much time to add one field. It took you to 30 min. to add one field which was unheard of in older versions of NAV. Microsoft definitely needs to address this issue and make it much easier to build reports.
Come on. This is not a smart approach. We want the clients' report customization to benefit from every future enhancements the standard will get. Or imagine future data structure changes. The copy will get worthless.
This is a well-known issue, which is how you mentioned, based on the way the dataset matrix is built between old nav/BC and Reporting Services. It has never been lean. So adding the description 2 field itself will cause these additional lines and the layout has to choose the right one. This is why a variable has to be passed to the Reporting Services engine.
I prefer ForNAV reports. Gives you the mix of classic NAV report writing structure and the modern layout design.
try changing ApplicationArea or UsageCategory for a report using report extensions... ended up just creating a copy of the standard report.
Why are you trying to extend 10074? does it have functionality that 1306 doesn't? ive used report extensions numerous times for 1306 (the standard Invoice Report) and you are able to extend it exactly as you try first time. I
Sales tax broken down to details.
And report 1306 has a wordlayout (for simple needs)
With VAT support, not sales tax
Assuming you actually prepared for the video and did everyting on the fly this would be like a 2hour fix (at least for me) resulting in not wanting to have this "dirty" code in my app anyway.
Most would've probably given up after seeing that the TempLines were not marked as protected.
And from that point i rather copy the report than have some code that nobody else will understand and page me about.
I just had the general idea of how this could be solved before I hit record :)
🙃I wonder why ForNav was invented
Extend reports is a nightmare.
Can't you just make a copy of the base report and then add any new fields instead of extending the report.
Yes, but then what's the purpose of reportextensions?
@@Hougaard When reportextensions are so complicated and time consuming what's the point of spending so much time to add one field. It took you to 30 min. to add one field which was unheard of in older versions of NAV. Microsoft definitely needs to address this issue and make it much easier to build reports.
Come on. This is not a smart approach. We want the clients' report customization to benefit from every future enhancements the standard will get. Or imagine future data structure changes. The copy will get worthless.
And this is how you hack into some microsoft guy's head and figure out in 30 minutes what most probably took him days to put together =)