You’re offline. This is a read only version of the page.
Hello All,
We are looking to upgrade Microsoft Dynamics NAV 2009 SP1 to NAV 2013. In an effort to start the documentation process early prior to the upgrade (next 8 months) - I am looking for a best way to document all of the reports and help determine which are used/not used to further help answer, which may stay/go during the upgrade. Any help on how to best obtain this information would be very appreciated.
Some of the things that I am thinking are:
- Compile list of reports (hopefully there is an easier way to find all of them)
- Question which reports are being utilized to the best capacity, if being used at all
- Unsure yet, how to best document the reports (the level of details) for the integration partner to understand it prior to the upgrade
Any information is greatly appreciated.
Thanks Everyone,
*This post is locked for comments
Hi Brailin,
I know of the product and what it is supposed to do. And that does make sense then.
I am sorry but I don't think I know another NAV add-on for it. It is a rather specialized area (not as easy as your usual run of the mill distribution company :-) ).
Regards,
Cristi Nicola
Cristi and Suresh - Thanks for your answers. Very much appreciated.
Cristi - to answer your question on why stay with NAV 2013 as opposed to NAV 2015+:
Part of the reason why we may possibly stay with NAV 2013 is because we are a not-for profit organization and use fund accounting heavily, which is built on Serenic Navigator. Serenic Navigator is yet to come out with a newer version. Technically Serenic takes the base NAV and adds functionalities (fund accounting, workflows etc.). Are you familiar with the Serenic Navigator product? Is there something just as competitive in the market?
Regards,
Brailin C.
Hi Brailin,
Suresh covered the first question you had.
For the rest there is no magic formula.
In theory, your partner should be able to upgrade all the reports you ask them to with or without an explanation from you simply by looking at the report definition and code (it is part of the upgrade process). The issue with this approach is cost since it is takes a lot more time to do a RTC report vs a Classic one.
My recommendation is to just upgrade (as per above approach) only the MUST reports. In that category I would include things like Pick Ticket, Invoice, Check and other documents like that. I would simply leave out all the analytical reports for after the upgrade.
Once upgraded, I advocate for a "fresh start" approach on the rest: i.e. ask users which reports they would like to have. If that is not feasible (due to number of users or number of existing reports is too high) you can do the triage yourself based on the Report Log and then you should be able to decide which really need to be "provided" again either by brand new report development or upgrade work.
Keep in mind that 2013 and up offer a lot more options in terms of reporting so you may want to consider Power BI and ODATA as options to get data out NAV and report on it.
And also may I ask why you are not upgrading to 2015 or for that matter, since you are still thinking, just straight to 2016 which is due end of this year? Since you are going from Classic to full RTC I see no technical problem for going higher than 2013.
Regards,
Cristi Nicola
Check the below blog
http://blogs.msdn.com/b/nav/archive/2011/06/23/how-to-log-report-usage.aspx
This is a good way to check which reports are use and what capacity.
Regarding documentation not sure what you mean, if you have any customized reports and if you saved the documentation that may help during testing and upgrading it. But thorough testing of the reports after upgrade is the good way to test them.
#1
Sohail Ahmed
2
#1
mmv
2
#1
Amol Salvi
2
Share
Report
All responses (
Answers (
