The main question I want to answer is: How useful and timesaving is the tool for Classic-Client-Reports that have to be migrated to NAV2013 (and not to NAV2009).
Did you gather some more information in the past month? I have the same question as I'm asked to look at the product.
My first impression it that is not so usable for us. As we are new to RTC reporting using Reporting services it's quite difficult for us to 'predict' how the grouping must be, which sections need to marked with which sectiontypes etc.. Building the RTC report from the ground up is more time consuming, but the result is that we often adapt the dataset structure to be more usable in reporting services, and the hand-made report is easier and less complex in visual studio, compared to a converted report.
If you use both clients simultaneous, I think it's worth the effort. If, like us, you are doing a onetime conversion to Nav2013 from 2009R2 classic, the situation is more fuzzy.
Hi mvendert,
we have bought the tool and gain our first experiences at the moment.
We have converted some easy reports quite fast with the tool, but with more complex reports we still have difficulties with the points you have listed (grouping, section-types). What I think at the moment is, that we need a bit more experience with the tool.
Probably I can tell you more in a few month.
There is also a good free webcast available (1 hour) : http://channel9.msdn.com/Events/Microso ... sformation
Regarding the standard-function "Upgrade Reports" it's said the following:
“Upgrade is 100% of data and 99% of layout” (00:34:51 h)
Comments
The main question I want to answer is: How useful and timesaving is the tool for Classic-Client-Reports that have to be migrated to NAV2013 (and not to NAV2009).
Did you gather some more information in the past month? I have the same question as I'm asked to look at the product.
My first impression it that is not so usable for us. As we are new to RTC reporting using Reporting services it's quite difficult for us to 'predict' how the grouping must be, which sections need to marked with which sectiontypes etc.. Building the RTC report from the ground up is more time consuming, but the result is that we often adapt the dataset structure to be more usable in reporting services, and the hand-made report is easier and less complex in visual studio, compared to a converted report.
If you use both clients simultaneous, I think it's worth the effort. If, like us, you are doing a onetime conversion to Nav2013 from 2009R2 classic, the situation is more fuzzy.
Do you agree?
we have bought the tool and gain our first experiences at the moment.
We have converted some easy reports quite fast with the tool, but with more complex reports we still have difficulties with the points you have listed (grouping, section-types). What I think at the moment is, that we need a bit more experience with the tool.
Probably I can tell you more in a few month.
The conversion of a NAV2009-RDL-Report to a NAV2013-Report shouldn't be such a big step as there is a standard-function in the NAV2013 Development Environment:
Tools --> Upgrade Reports
Here some posts regarding that function:
- http://mibuso.com/forum/viewtopic.php?f ... de+reports
- http://mibuso.com/forum/viewtopic.php?f ... de+reports
There is also a good free webcast available (1 hour) :
http://channel9.msdn.com/Events/Microso ... sformation
Regarding the standard-function "Upgrade Reports" it's said the following:
“Upgrade is 100% of data and 99% of layout” (00:34:51 h)
Regards,
Blue