But I thought it would be good to document the latest, as my coworkers and others expressed a lot of skepticism when I explained the scenario. They insisted that there must be a logical reason for it. But, alas, there is not any explanation other than it being a Quality Report (confirmed by Microsoft).
Here is the scenario, it assumes that all companies are using the same report set in Management Reporter:
- Create a company in Management Reporter, do not include Analytical Accounting in the company configuration.
- Create a number of reports in the company. All of the reports generate successfully.
- Create a company in Management Reporter (using the same GP database as the company in Step 1), only this time include Analytical Accounting in the company configuration.
- Set the new "AA" company as the default.
- Take an existing report definition (created in the "non-AA" company) and change the company to the new "AA" company.
- Generate report.
- Expected results- report should generate, as the account format is the same (since both companies point to the same GP database) and although analytical accounting is enabled for the current company...you are not required to use any of those segments in the row, column, or tree.
- Actual results- report yields no data
- Open a report definition created in the "non-AA" company
- Do a Save As, and change the company on the report definition to the "AA" company
- Change the building blocks to be building blocks (rows, column, tree) created in the "AA" company
- Generate the report, still no data!
- Only if all building blocks, including the report definition, are created in the "AA" company will the report pull data.
Confirmed with Microsoft that this is resolved in MR 2012, but wanted to share the info...as this definitely had me baffled :)
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.