During a recent upgrade of a client from Microsoft Dynamics GP 2010 to Microsoft Dynamics GP 2013 we also did a migration of FRx to Management Reporter.
After doing the test upgrade and migration I tested Management Reporter and everything was working fine. However, a month later when I was back on site for the live upgrade and some additional training, I found that Management Reporter was no longer working correctly.
When I tried to open a column definition I received an error:
Management Reporter: The operation could not be completed due to a problem in the data provider framework.
The Dynamics Financial Reporting blog today announced the release of Management reporter 2012 CU8.
Full details can be found at the link above, but here’s a quick summary of some of the new features:
- Dynamic calculated column headers…no more hard coding of Months within the column definition
- Currency translation for Dynamics GP 2013 using DDM Data Mart provider
- Ability to create a side by side balance sheet by using a section break option in row definition
- Option to include line numbers on generated reports
- Ability to set all columns in definition to Autofit by default
- Collection of Excel formatting improvements
Management Reporter 2012 CU8 can be downloaded from here for the US and all other countries here (CustomerSource or ParnerSource login required).
I am pleased to announce that I have teamed up with Packt Publishing and are organizing a give away especially for you. All you need to do is submit a comment below the post and win a free e-copy of Microsoft Dynamics GP 2013 Reporting – Second Edition by David Duncan and Christopher J Liley. Five lucky winners stand a chance to win an e-copy of the book.
Keep reading to find out how you can be one of the Lucky Ones.
This is an issue I came across a few months ago and misplaced my screenshots. Having just stumbled across them on my test Hyper-V server I decided it is still worth posting about.
I was doing some testing on a system with multiple companies created and was looking at a report consolidating figures from all of them into one report. When the report was generated it failed and gave the error message below for several of the companies in the Report Queue Status window:
Period 13 for fiscal year 2013 is not valid for company <company name>. No data will be returned for this company.
I checked the Fiscal Period Setup in Microsoft Dynamics GP for all reported companies and all of them had the same period 13 defined. Management Reporter, as well as reporting errors in the Report Queue Status window, logs errors in the Windows Event Viewer.
I have received a copy of the newly published Microsoft Dynamics GP 2013 Reporting, by David Duncan and Chrisopher J Liley, from Packt Publishing to review. This is an update of a previous book the pair wrote for Microsoft Dynamics GP 2010:
The book covers an extensive range of the reporting tools in, or available with, Microsoft Dynamics GP 2013:
- SmartList Builder including Excel Report Builder
- Report Writer and Word Templates
- Reporting Services Reports
- Analysis Cubes
- Management Reporter
I thought I had posted this a while ago, but searching my blog I can’t find it. A client contacted me recently to report the following error message:
Management Reporter – Can’t connect to the Management Reporter server. Do you want to specify a different server address?
My first step was to try running Management Reporter myself and was able to log in without a problem'; this was on the same Citrix server the client had been trying to log into which ruled it out as being a problem with the Management Reporter services.
The client in question was a member of their internal IT department and had his own Domain account and access to a global Domain administrator account. It was his own Domain account which he had logged into the server with, but this user was not in Management Reporter; it had been configured using the global Domain Admin account to minimise the number of licenses assigned to IT (the client is running Microsoft Dynamics GP 2010).
Once he logged in with the global Domain Admin account he was able to access Management Reporter without any further issues.
I have received a copy of Microsoft Dynamics GP 2013 Reporting to review which I will be doing over the next couple of weeks.
This is an update to the previous edition of the book for Microsoft Dynamics GP 2010, but this one is for the current version:
I’ll be giving it a thorough read and, setting aside my distaste for reporting outside of Management Reporter, I may even follow some of the examples and post a detailed account.
If you don’t want to wait for my review of the book, it can be bought now from Packt Publishing.
With Business Analyzer R5 installed it’s time to take a look.
Clicking the tile will launch the app which will show a Net Income – Summary view and, as is standard in Microsoft apps, a slice of the next part of the app:
I did a couple of posts a while ago on fixing the sample company reports (the first post fixed the Row and Column Definitions and the second the Reporting Tree Definitions), but there has been another issue with them that has been bugging me for a while.
The reports are configured to run for periods around the current system date, which means dates in 2013. But the Fabrikam sample company is in 2017 so the reports return no data. With Management Reporter storing its reports and configuration information on a SQL Server database, it is possible to tweak the reports to run for 2017.
I checked each of the reports to see how what Base period they were using and then worked out what I needed to update to set the reports to run for similar periods in 2017.
A client reported a problem with Management Reporter returning incorrect figures when a link to the Financial Dimensions on the Row Definition had been entered in lower case.
The reports in question had been created in FRx which was rather more forgiving that Management Reporter is for these things. The client had quite a large number of reports which may, or may not, have had segments entered in lower case so the client didn;t want to have to check and update manually.
I again delved into the Management Reporter SQL database and updated the ControlRowCriteria table to capitalise the Low and High values of the link to financial dimensions using the script below:
Low = UPPER(Low)
High = UPPER(High)
LEN(High) > 0
Once the update had been run, the client checked their reports and confirmed that they were now returning the correct figures.