22,784
Like
Share
Report
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.
For example, if a report was using S-1 to run for the last period, I would need to update it to run for S+40 and if it was set to run for the current period, I would need to change CUR to S+41. All told there were four different period settings used on the different reports and so I produced SQL scripts to update the Report Definitions:
UPDATE
ControlReport
SET
DefaultPeriod = 'S+41'
WHERE
DefaultPeriod = 'CUR'
GO
UPDATE
ControlReport
SET
DefaultPeriod = 'S+40'
WHERE
DefaultPeriod = 'S-1'
GO
UPDATE
ControlReport
SET
DefaultPeriod = 'S+41'
WHERE
DefaultPeriod = 'C'
GO
UPDATE
ControlReport
SET
DefaultPeriod = 'S+43'
WHERE
DefaultPeriod = 'C+2'
GO
One thing to bear in mind, is that the update script above works for this month. You will need to work out how many to add each time you look to run these scripts and update accordingly.
*This post is locked for comments