Reports with transaction detail are a great way to answer your detailed reporting questions and find key information such as document numbers, posting dates, or individual transactions in their native currency. But maybe, you've been holding back on printing reports at this detail level, worrying that it meant the reports took longer to generate or that the storage for these reports would become unruly.
With RU5, we've reworked how transaction detail is stored, ensuring it's optimized so you can generate many reports with this helpful detail and you won't need to have these concerns.
How did things work before?
Prior to Rollup 5, when you generated a report at the transaction detail level we would store the transactions in the generated report. Generated reports are then stored indefinitely within the Management Reporter database, unless someone manually removes those report versions from the Report Library.
What enhancements were made?
With the changes made in Rollup 5, transaction detail for each report is stored with the data mart database, and no longer duplicated in the Management Reporter database. When a report is generated with transaction detail, we retrieve the appropriate transactions from the data mart when you drill down. This means the size of reports containing transaction detail is significantly smaller and the Management Reporter database will not significantly increase in size as additional reports are generated and stored.
Is there anything that I should do to take advantage of these enhancements?