But first, a couple of good blog posts from the Dynamics Corporate Performance Management Team regarding FRx migration to Management Reporter and row linking.
What I was surprised to learn is that when you have row linking on a tree in FRx, it impacts the migration in more ways than one. Not only does it remove the row linking from the tree (which would be expected), it also does not migrate the GL linking in all of the row formats there were linked in the tree. For example...
The tree has a summary and three branches:
- Dept 1
- Dept 2
- Dept 3
- Summary: Row format A
- Dept 1: Row format A
- Dept 2: Row format B
- Dept 3: Row format C
And it is not enough to simply remove the row linking in the tree in FRx prior to migration, as unassociated rows will not migrate. So you would have to associate the rows with another catalog for them to migrate properly. A little prep work to consider if you use row linking in FRx. Then you can address the report design (the blog post above on advanced reporting has some ideas) to achieve similar results to row linking.
Christina Phillips is a Microsoft Certified Trainer and Dynamics GP Certified Professional. She is a supervising consultant with BKD Technologies, providing training, support, and project management services to new and existing Microsoft Dynamics customers. This blog represents her views only, not those of her employer.