Quick tip for MR, unlike FRX it will not always warn you to save changes when logining out, there is a Tick box under tools options which alows you to set MR to warn you.
The tick box is " Display confirmation before exiting Management reporter"
Showing posts with label Management Reporter. Show all posts
Showing posts with label Management Reporter. Show all posts
Thursday, 25 August 2011
Management reporter not warning me to save.
Hi Folks
Quick tip for MR, unlike FRX it will not always warn you to save changes when logining out, there is a Tick box under tools options which alows you to set MR to warn you.
The tick box is " Display confirmation before exiting Management reporter"
Quick tip for MR, unlike FRX it will not always warn you to save changes when logining out, there is a Tick box under tools options which alows you to set MR to warn you.
The tick box is " Display confirmation before exiting Management reporter"
Monday, 8 August 2011
Management reporter migration wizard (FRx)
Hi folks, another quick Management reporter tip.
We have now done a fair few Management reporter upgrades/migrations from FRx. originally we had a few issues with the migration tool. However in the latest release (sp2) this now functions a lot better. However it will not bring across account sets or security. these will need to be re added manually.
We have now done a fair few Management reporter upgrades/migrations from FRx. originally we had a few issues with the migration tool. However in the latest release (sp2) this now functions a lot better. However it will not bring across account sets or security. these will need to be re added manually.
Management reporter and segment names
Hi folks its been very busy here of late and so the blog has taken a back seat ( if you want to know why we have been so busy type "Calyx touchstone" into bing and see what you get).
Anyway there are a few tips and discoveries to catch up on,
If the account segments in Dynamics GP aren’t named (so called segment1, 2, 3, etc) and you write your reports in MR with this format, if and when at a later date you decide to name your segments to something else (location, division etc), the reports will come back with no data.
To get round this you can do an edit/ replace on segment1 (2,3) with whatever your new segment descriptions are and your Management reporter reports will then function again, these do not update dynamically in MR when you change them in GP.
Anyway there are a few tips and discoveries to catch up on,
If the account segments in Dynamics GP aren’t named (so called segment1, 2, 3, etc) and you write your reports in MR with this format, if and when at a later date you decide to name your segments to something else (location, division etc), the reports will come back with no data.
To get round this you can do an edit/ replace on segment1 (2,3) with whatever your new segment descriptions are and your Management reporter reports will then function again, these do not update dynamically in MR when you change them in GP.
Thursday, 17 February 2011
FRx Management Reporter migration Wizard and Office versions 64 bit v 32 bit
Hi folks, here is a situation we have come across with the Migration wizard for FRx Management reporter for Dynamics GP 2010.
Simply stated the issue is this:
The old FRx databases are Microsoft Office Access databases and so the migration wizard needs certain parts of office connectivity to be able to read and convert the old spec sets into the new FRx Management reporter for Dynamics GP 2010 formats (which are now stored in SQL tables).
FRx Management reporter for Dynamics GP 2010. will only install the components for the operating system it is sat on, so if you are 64bit , it will use the 64 bit Microsoft Office 2010 Access components and if you are 32 bit it will use the 32 bit Microsoft Office 2010 Access components. not a problem so far I hear you cry.
Well now factor in the fact that the new word office template email functionality for Dynamics GP 2010 does not work on the 64 bit version of Microsoft Office 2010 and to get round this a lot of partners are installing the 32 bit version of Microsoft Office 2010 onto 64 bit operating systems in order to use the email functionality in Dynamics GP 2010. Couple this with the fact that if you have FRx Management reporter for Dynamics GP 2010 on a 64 bit operating system it will only use the 64 bit Office components, add the fact that you can not have 64bit office components on a machine that already has 32 bit office components and you have a problem. The Migration wizard will not be able to read the Access database.
So there you have the issue , of course it is easily solved simply do the migration on a machine with all 64 bit components (one you are not intending to use the email functionality from) and you will avoid this issue.
This is definitely a case of forewarned is forearmed.
Simply stated the issue is this:
The old FRx databases are Microsoft Office Access databases and so the migration wizard needs certain parts of office connectivity to be able to read and convert the old spec sets into the new FRx Management reporter for Dynamics GP 2010 formats (which are now stored in SQL tables).
FRx Management reporter for Dynamics GP 2010. will only install the components for the operating system it is sat on, so if you are 64bit , it will use the 64 bit Microsoft Office 2010 Access components and if you are 32 bit it will use the 32 bit Microsoft Office 2010 Access components. not a problem so far I hear you cry.
Well now factor in the fact that the new word office template email functionality for Dynamics GP 2010 does not work on the 64 bit version of Microsoft Office 2010 and to get round this a lot of partners are installing the 32 bit version of Microsoft Office 2010 onto 64 bit operating systems in order to use the email functionality in Dynamics GP 2010. Couple this with the fact that if you have FRx Management reporter for Dynamics GP 2010 on a 64 bit operating system it will only use the 64 bit Office components, add the fact that you can not have 64bit office components on a machine that already has 32 bit office components and you have a problem. The Migration wizard will not be able to read the Access database.
So there you have the issue , of course it is easily solved simply do the migration on a machine with all 64 bit components (one you are not intending to use the email functionality from) and you will avoid this issue.
This is definitely a case of forewarned is forearmed.
Subscribe to:
Posts (Atom)
Posts
