https://docs.microsoft.com/archive/blogs/dynamics_financial_reporting/feed.xml All about financial reporting and consolidations for Microsoft Dynamics ERPs Tue, 20 Mar 2018 14:55:08 GMT en-US hourly 1 https://docs.microsoft.com/archive/blogs/dynamics_financial_reporting/updated-management-reporter-cu16-now-available Tue, 20 Mar 2018 14:52:04 GMT https://blogs.msdn.microsoft.com/dynamics_financial_reporting/?p=3755 Hotfixes included in new CU16, also available individually

1. Hotfix 3815274 - Allows children nodes to be rolled up to a parent that contains a Dimension filter. Installing this hotfix, along with a change to MRServiceHost.settings.config, will revert a functional change in CU15 (HF 3714638). This allows customers to use the original functionality before CU15, where nodes can be rolled up to a parent that contains a dimension filter, or the new functionality introduced by CU15, where nodes won’t roll up to a parent that contains a dimension filter.
2. Hotfix 3813390 - User security may be removed during the Companies to Company mapping if there is a SQL Exception. This hotfix will prevent this from occurring.
3. Hotfix 3830316 - Microsoft Dynamics AX only: Allows customers to generate the SPED ECF statement for Brazil (BRA). Customers can export the SPED ECF text file with the changes in records 0000, 0010, 0020, 0021 and 0930 introduced by version 3.0.
4. Hotfix 3840209 - Prevents unnecessary actual and budget records from being created in the data mart when the amount or quantity is zero.
5. Hotfix 3858003 - For Microsoft Dynamics AX 2012 R2: Addresses a performance issue with the Company integration.  For Microsoft Dynamics GP 2018: Addresses an issue with not being able to configure an integration to the GP database.

Hotfixes included in new CU16 only

1. Hotfix 3921111  - Adds support for SQL Server 2017
2. Hotfix 3366688  - Microsoft Dynamics AX only: Prevents a timeout error if you have 100+ dimensions, which caused the initial integration to not complete successfully

The original CU16 and the five hotfixes are still available through links found in the Previous Release and Hotfixes document.]]> https://docs.microsoft.com/archive/blogs/dynamics_financial_reporting/management-reporter-cu16-now-available Mon, 27 Feb 2017 20:29:34 GMT https://blogs.msdn.microsoft.com/dynamics_financial_reporting/?p=3705 quality fixes as well. Here’s a summary of the new Management Reporter CU16 features: ·         HTTPS Support for Server and client components ·         Add Hebrew (he-il) localization ·         Additional fixes for product defects There are a few prerequisites to make sure you have. Management Reporter 2012 CU16 requires SQL Server 2012 or higher. PowerShell 3.0 continues to be required. The Microsoft .NET Framework 4.6.1 is also required, but is no longer automatically downloaded and prompted for installation. For a complete list of prerequisites, review the system requirements. HTTPS Feature Overview This feature provides the ability to use HTTPS with Management Reporter 2012. The use of HTTPS and SSL provides an additional level of security to protect your financial data on your local network, your intranet, or from your cloud-based deployment. This feature enables secure communication with an https:// address when viewing reports in the web viewer, desktop viewer, and when designing reports. This is an optional feature that will require removing and re-configuring the services after an upgrade. HTTPS  or during a new installation. There are a few limitations to the HTTPS feature support, so keep these in mind:

• The HTTPS feature will only work on Server 2008 R2 or later. Configuration will fail on Server 2008.
• The Migration Wizard does not support HTTPS. You can continue to use the Migration Wizard with CU16, but can remove the services and enable HTTPS with your existing database after migration has completed.
• All clients will need a certificate verifying that the server hosting the Management Reporter services is trusted. The certificate will need to be distributed and installed on all clients.The certificate can be a purchased certificate from a certificate authority, a domain certificate from Windows Certificate Services, or a self-signed certificate from the server hosting Management Reporter (a self-signed certificate is not recommended for production).

Server Installation For configuring a self-signed certificate for testing, you can use the following steps: Option 1: Use IIS Manager to create a self-signed certificate This method requires the prerequisite of IIS Manager being installed on the MR Server.

1. Start | Run | inetmgr on the Server
2. Under the machine name double-click on server certificates and click create self-signed certificate
3. Specify a friendly name for the certificate and select the location as personal certificate store

Option 2: Use PowerShell to create a self-signed certificate Note: The flags may be slightly different because parameters may not be different in earlier or later versions of Windows. More information can be found on creating certificates here and here.

1. Open PowerShell and use the following command, replacing the machine name for your local machine
   • New-SelfSignedCertificate -DnsName "ryantest.northamerica.corp.microsoft.com" -CertStoreLocation "cert:\LocalMachine\My"
2. Open Certificate manager (Start | Run | certmgr.msc) or equivalent command to open certificate management in MMC
3. Find the correct certificate. It will have an expiration date of today’s date + 1 year issued by your local machine issued to your local machine
4. Right click and select all tasks |  export. The option selected for export file format should not matter.
5. If prompted, choose whether or not to export the private key, but it is not required
6. If prompted, select to secure the certificate
7. Export to a file on your desktop
8. Click into Trusted Root Certification Authority | Certificates
9. All tasks | import
10. Grab the file on desktop you just exported
11. Agree to place certificates in trusted root certification authorities

Client Installation Install this same certificate on each client machine under personal certificates, and in the trusted root certification authority store

1. Export the certificate from the server using the steps above
2. Copy the exported certificate file from the server to the local client
3. Open the Certificate Manager (Start | Run | Certmgr.msc)
4. Expand into Trusted Root Certification Authority and select the Certificates folder
5. Right-click Certificates, click All tasks and select Import
6. Browse to the certificate file that was exported from the server
7. Agree to place certificates in trusted root certification authorities

In some cases, users can be prompted for authentication more often than required. The following settings can reduce or eliminate these login prompts.

1. Add the Management Reporter server as a trusted site. This can be configured within Internet Options, Security, Trusted Sites. Use the Site button and add the server address while a report is currently open.
2. Configure for automatic authentication. This can be configured within Internet Options, Security, Trusted Sites. Local Intranet options or similar settings with the option selected to use automatic login with current user name and password can be enabled.

  For the Report Designer client, it will continue to connect to the HTTP port for initial connection, but will automatically use HTTPS after connected. For example, if your default HTTP port is 4712, and HTTPS port is 4713, you will enter the following address into the Report Designer client: MRServer:4712 Known Issues SSL cert registrations are not removed on uninstall You may see the below error after multiple installations if there is an active sslcert registration existing for the current SSL port during configuration. You can view and delete these registrations manually with the following commands: netsh http show sslcert netsh http delete sslcert hostname=ryansandtest.northamerica.corp.microsoft.com:4713 Error message: An error occurred while checking existing companies in the Management Reporter application service. Additional information: System.ServiceModel.CommunicationException: An error occurred while making the request to https://ryansandtest.northamerica.corp.microsoft.com:4713/CompanyService.svc. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. Version Information Management Reporter CU16 Release 2.12.16000.17 Note: There are no changes to the data mart schema in this release, so no upgrade to the data mart database will be required. You can view which ERP versions are supported by this release by reviewing our compatibility list here.   You can find the EN-US download for Management Reporter CU16 here: https://mbs.microsoft.com/customersource/northamerica/MR/downloads/service-packs/MROverview Other localizations should be available in the next 72 hours.]]> https://docs.microsoft.com/archive/blogs/dynamics_financial_reporting/management-reporter-2012-cu15-hotfix-4-now-available Mon, 03 Oct 2016 21:23:03 GMT https://blogs.msdn.microsoft.com/dynamics_financial_reporting/?p=3696 Hotfix 1 Hotfix 2 Hotfix 3 This hotfix requires CU15 to be installed first. It can be applied to CU15 RTM, or to CU15 with any previously released hotfix(es). There are updates both to the client and server. The changes will take effect after a reboot of the server. There is no need to reset the data mart integration for these changes to take effect. There are no localized files included in this hotfix, so all locales will use the same hotfix package. Note: If you're using GP2016, you will need to apply HF3 first in order to get the fix for Bug 89680: Unable to create GP integration. You can uninstall the hotfixes from add/remove programs and install HF3 first, then apply HF4.

Bug ID	Title
3771542	Integration fails when collation is different between tempdb and AX database
3768609	CU15 Regression: web viewer - autotext date header not using the regional settings of the service user
3768350	AX DM Companies to Company Integration query slow for integrations with a large number of security roles configured in AX
3767519	Report fails when using a Dimension Value Set in the tree based on MainAccount

For bug 3768609, in order to see @DateLong Autotext without day of week appearing, follow these steps going forward:

1. On the server where the Management Reporter services are installed, verify what user is running the application service.
2. Log on as that user, and open the regional control panel and edit the Long date format to remove day of week.

Note: If using Network service, or another system account you can use the Copy settings button under regional settings to set that default. If there are users with multiple regional settings in your company, use the drop-down list for in regional settings for all applicable languages, and repeat the steps above to remove day of week from these as well. Once these steps are complete, any web viewer user connecting to this server will have their browser's language compared to the languages on the server, and the customized date format will be used for that language. This will require the "all languages" Management Reporter server installation for multiple locales and translations to be installed on the server. The hotfix has been posted to CustomerSource. Hotfix 4 (Hotfix 3780433) is version 2.12.15000.56.]]> https://docs.microsoft.com/archive/blogs/dynamics_financial_reporting/partner-to-host-free-management-reporter-online-user-conference-in-september Mon, 12 Sep 2016 18:41:53 GMT https://blogs.msdn.microsoft.com/dynamics_financial_reporting/?p=3685 MSX Group website.]]> https://docs.microsoft.com/archive/blogs/dynamics_financial_reporting/management-reporter-2012-cu15-hotfix-3-now-available Mon, 11 Jul 2016 07:25:09 GMT https://blogs.msdn.microsoft.com/dynamics_financial_reporting/?p=3655 Bug ID Title 3753112  Dimension filter uses an OR condition instead of AND condition when two or more dimensions are specified in link to financial dimensions 3755023  Dimension filter uses an OR condition instead of AND condition when using a dimension value that does not exist 3754945  GP is performing a count query before actual query, doubling the query cost with data mart 3754947  GP Fact integration slow when posting large Analytical Accounting batches with data mart 3754948  GP data validation not working with GP 2016 3757515  GP integration fails with GP 2016 Dexterity shared components 3757516  GP Yes/No dimensions for Analytical Accounting not integrating correctly with data mart   The hotfix has been posted to CustomerSource. Hotfix 3 (Hotfix 3757498) is version 2.12.15000.56.]]> https://docs.microsoft.com/archive/blogs/dynamics_financial_reporting/resetting-the-management-reporter-data-mart Tue, 28 Jun 2016 15:11:58 GMT https://blogs.msdn.microsoft.com/dynamics_financial_reporting/?p=3361 This shouldn't be the case. There are specific scenarios where a rebuild is required (we’ll talk about them in a minute), but generally speaking, rebuilding the data mart shouldn't be required in most scenarios. In fact, rebuilding the data mart without talking with our support team means if there was an issue, we can’t fix it to make sure it doesn’t happen again. So, when do you need to rebuild the data mart? You will need to rebuild the data mart if: • Your Microsoft Dynamics ERP database is restored from a backup In this situation, the data mart will have transactions that no longer exist in the ERP database and may report incorrect balances. • Copying your production ERP and MR databases into a test environment In this situation, the integration configured for production is hard-coded into the Management Reporter database. If the databases are restored elsewhere, the connections will still be pointing to the test environment. Instead of copying the MR databases into test, you can copy over any reports via a .tdbx export, and can reset the data mart for up-to-date numbers. • Microsoft Dynamics GP - Activating or De-activating Analytical Accounting for reporting in MR If Management Reporter needs to change the type of integration, a reset is required to stop looking at the GL tables and start looking at the AA tables • Microsoft Dynamics GP - Account Category change If an account is moved to a different account category, the account category change won't occur until a transaction is processed for that account combination. It could be an actual or budget transaction, but all related combinations would need to see an update. • Microsoft Dynamics GP - Account Description change If an account description is changed, the new description will not be available until the data mart is reset. The descriptions entered into the row definitions for the account will require a manual update for changes to be reflected. • Microsoft Dynamics GP - PSTL Account tools If any tools are run to change segments or accounts, a reset may be required. Note: I will add more information here once we have additional clarification   Please feel free to leave comments on what you're seeing, but the preferred course of action would be to update to the latest version of Management Reporter, and submit a support ticket to review what issues you are seeing. I will be moderating comments to make sure the discussion stays on track, and to ensure correct and validated information is being shared. If additional issues are found, we'd love to fix those issues. There have been several fixes to issues that previously required a data mart reset to fix. If you are told to rebuild the data mart in the future, please consider this post for additional guidance.   How do I rebuild the data mart (CU15+)? 1. Before starting, make a backup of the ManagementReporter and data mart (ManagementReporterDM) databases before starting. Backups can be helpful in the case of diagnosing why the issue occurred after the rebuild occurs. This process will require a SQL authenticated user (not Windows login user in SQL) and dbo rights to the ManagementReporter and ManagementReporter DM databases.  This process will delete all of data in the data mart tables and remove the integration logs, remove the data mart connection information, and fix the dates for previous generated reports to be able to properly include transaction detail with the ManagementReporter database. 2. Log onto the machine where the MR Server components are installed and open Powershell as Administrator 3. Navigate to the Console folder PS C:\> cd '.\Program Files\Microsoft Dynamics ERP\Management Reporter\2.1\Server\Console\' 4. Import the module PS C:\Program Files\Microsoft Dynamics ERP\Management Reporter\2.1\Server\Console> Import-Module .\Microsoft.Dynamics.Performance.Deployment.Commands.Integration.dll Note: You can get additional help for each of the parameters by running Get-Help Reset-DatamartIntegration -Full 5. Run the below command. You can run get-help Reset-DatamartIntegration for more information. If credentials aren't supplied, you will be prompted PS C:\Program Files\Microsoft Dynamics ERP\Management Reporter\2.1\Server\Console> Reset-DatamartIntegration -Reason BADDATA -ReasonDetail "Restored database from backup" -DatamartDatabaseServer sqlservername -DatamartDatabaseName ManagementReporterDM -DatamartDatabaseUserName sa -DatamartDatabaseUserPassword (ConvertTo-SecureString Thisisapass@word -AsPlainText -Force) -MRDatabaseServer sqlservername -MRDatabaseName ManagementReporter -MRDatabaseUserName sa -MRDatabaseUserPassword (ConvertTo-SecureString Thisisapass@word -AsPlainText -Force) 6. Agree to the below confirmation. It is recommended the process service is stopped, but not required in most cases. WARNING: Resetting the financial reporting data mart will delete all data in the data mart as well as any supporting data in the financial reporting and ERP databases. The Management Reporter 2012 Process Service must be stopped on all machines that it is installed on before continuing. Note: For Microsoft Dynamics AX 2012 customers, GP, and SL customers, no ERP data will be touched during this process. Only data within the data mart and ManagementReporter databases are impacted. Confirm Are you sure you want to perform this action? Performing operation "Reset-DatamartIntegration" on target databases. [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): Y When the process starts, the Configuration Console will display a message that the initial integration is in progress. Once complete, you will see the message change to initial integration is complete. You can review the log of previous reset activity in the Event Viewer with the following steps: 1. Open the Event Viewer 2. Expand Applications and Services Logs 3. Expand Microsoft 4. Expand Dynamics 5. Expand MR-Logger 6. Select Operational The log will contain the date/time, username who requested the reset, and the reason details entered.]]> https://docs.microsoft.com/archive/blogs/dynamics_financial_reporting/clarification-on-management-reporter-announcement Mon, 20 Jun 2016 18:45:05 GMT https://blogs.msdn.microsoft.com/dynamics_financial_reporting/?p=3645 In response to the many questions we have been getting lately in regards to the GP announcement at Amplify, we want to clarify the product positioning for Management Reporter.

1. Management Reporter is the preferred financial reporting solution for Microsoft Dynamics AX, GP, and SL.
2. Management Reporter will continue to be supported through the lifecycle of the ERP versions it ships with.
3. Management Reporter has been renamed to financial reporting in Microsoft Dynamics AX ‘7’.

]]> https://docs.microsoft.com/archive/blogs/dynamics_financial_reporting/sped-ecf-v2-regulatory-feature-for-brazil-now-available-for-download Wed, 01 Jun 2016 03:46:10 GMT https://blogs.msdn.microsoft.com/dynamics_financial_reporting/?p=3635 Version Information Management Reporter CU15 RegF for Brazil – 2.12.15000.56. Hotfix 378213 will be visible in add/remove programs.   The upload to CustomerSource in in progress. You can find the download for this feature in the next few hours here: https://mbs.microsoft.com/customersource/northamerica/MR/downloads/service-packs/MROverview  ]]> https://docs.microsoft.com/archive/blogs/dynamics_financial_reporting/management-reporter-2012-cu-15-hotfix-now-available Fri, 13 May 2016 15:01:48 GMT https://blogs.msdn.microsoft.com/dynamics_financial_reporting/?p=3626 Bug ID Title 3749486- Change Tracking only gets enabled on the first Microsoft Dynamics GP company database 3751976- CU15 Issue - Data is missing on reports when using wildcards or ranges   The hotfix will prompt for a reboot of the server during installation. The hotfix will not change the version number of Management Reporter Server or Client components.   Version History Management Reporter CU15 RTM – 2.12.15001.56 Management Reporter CU15 Hotfix 3749486-3751976 - 2.12.15001.56   The hotfix has been posted to CustomerSource.  ]]> https://docs.microsoft.com/archive/blogs/dynamics_financial_reporting/management-reporter-cu15-printing-in-the-web-viewer Fri, 29 Apr 2016 17:03:40 GMT https://blogs.msdn.microsoft.com/dynamics_financial_reporting/?p=3596

A print icon has been added for quick access to printing

The detail level will be automatically selected based on the level of the report you are looking at. If you want to include additional detail levels, they can be selected as well

By default, printing will default to portrait orientation. This can be changed to landscape when needed

If you want to force the printout to fit the width of the page to a single page, check the appropriate option

Click print to begin generation of the XPS file

You will then be prompted to download an XPS file. You then use Windows 7 or later XPS viewer to open the download and send to the printer. Windows 10 also includes a PDF printer, so if you would like to save the file as a PDF you can download the XPS file and then click File | Print and select the PDF printer.   ]]>