With Microsoft Dynamics GP 2013 coming out soon, the need to migrate from FRx to Management Reporter becomes much more imminent, if you have not chosen to go with another reporting tool. To clarify, if you are upgrading from an older version of Microsoft Dynamics GP to GP2010, you can continue to use FRx a little longer. If you are waiting and going to upgrade to GP2013 instead, you must get off of FRx as you will not be able to use FRx with GP2013. If you want to be able to use Management Reporter as soon as you update to GP2013, you should start planning now.
So what steps should you take prior to the migration?
Review Your Existing FRx Reports – clean up all those unused reports – the fewer reports you have to migrate, the better you will be. How do you do that and how do you know what to clean up? Here are some tips:
- If you are on FRx with service pack 10 or higher, you can click on the “Catalog of Reports” and in the window that opens you can scroll way to the right and be able to see the last “Date Generated” and who it was “Generated By”. This will give you a good idea what reports are being used regularly and which are never used and could be eliminated.
- You can also create a list from the Catalog of Reports window by highlighting all of the reports listed, doing a Ctrl-C, and then pasting into Excel. You can do the same for the Row Formats, Column Layouts and Reporting Trees. Then in Excel you can do some sorting and comparisons to see which of the building blocks in FRx are really not being used and eliminate them. Keep in mind that if you have building blocks that you want to migrate but they are not currently being used in a catalog, you will want to create a catalog with those building blocks or they might not properly migrate.
- Review your Reporting Trees that remain after your elimination above. In Column G, the Acct Mask, review which segments have ampersands (&). In most cases you will have ampersands in the natural (main) segment. If you have ampersands in more than one segment or in a segment other than the natural account segment then you need to identify which catalogs use these trees. These trees are a more advanced design and you may want to recreate these instead of migrating them.
- Also review your trees to see if you have email addresses in column P. You will not be able to email reports from Management Reporter so you will want to start thinking about what you will do differently for reports that have been taking advantage of this feature.
- Once you have a list of your catalogs that you think you may want to migrate, take a closer look at each one. On the catalog’s Building Blocks tab look for the box ‘Use row format(s) and worksheet links from reporting tree’. This again is an advanced design. You may want to recreate in Management Reporter instead of migrating.
- Also review your catalog’s Building Block tab for any boxes that are checked for ‘Effective dates’. These may not migrate properly and you may need to recreate or create additional catalogs for some.
- Before you do the actual migration, take time to familiarize yourself with the dimension sets in Management Reporter. This will help reduce your stress when trying to clean up your reports in Management Reporter once you’ve actually done the migration.
By Barb Schroth, Senior Consultant, with OTT, Inc.,