FRx to Management Reporter Migration

If you are looking to migrate from FRx to Management Reporter, There is an inbuilt migration wizard in Management Reporter to do the same. I don’t need to specify the steps involved in the migration process as it has been covered in much detail elsewhere on the blogosphere. Here is a perfect link to accomplish the same.

FRx 6.7 to Management Reporter Migration

However, Hold on before running the wizard if you are on Management Reporter RTM edition. If you are running Management Reporter RTM edition for Dynamics GP 2010, you’d run into an error that says 'Windows Authentication is not supported for Microsoft Dynamics GP’. I heard this occurs even if you choose SQL Authentication. If you observe the event logs, it might be like this

  Message: Microsoft.Dynamics.Performance.Reporting.DataProvider.Service.DirectLinkException: Windows Authentication is not supported for Microsoft Dynamics GP ---> Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.GLConnectionException: Windows Authentication is not supported for Microsoft Dynamics GP
   at Microsoft.Dynamics.Performance.DataProvider.Core.TraceManager.Publish(Exception sourceException, Boolean throwException)
   at Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.GP.GLProvider.HandleConnect(EntitySettingCollection settings, CredentialCollection credentials)
   at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystemProvider.Connect(EntitySettingCollection settings, CredentialCollection credentials)
   at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystemConnection.Open()
   at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystem.CreateConnection(SourceSystem system, EntitySettingCollection settings, CredentialCollection credentials)
   at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystem.Connect(EntitySettingCollection settings, CredentialCollection credentials)
   at Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.GLSystem.Connect(Guid providerTypeId, EntitySettingCollection settings, CredentialCollection credentials)
   at Microsoft.Dynamics.Performance.Reporting.DataProvider.Server.DirectLinkService.GlConnect(Guid providerTypeId, EntitySettingCollection settings, StoredCredential credential)
   --- End of inner exception stack trace ---
   at Microsoft.Dynamics.Performance.Reporting.DataProvider.Server.DirectLinkService.GlConnect(Guid providerTypeId, EntitySettingCollection settings, StoredCredential credential)
   at Microsoft.Dynamics.Performance.Reporting.DataProvider.Server.DirectLinkService.ConnectInternal(Guid entityId, StoredCredential credential)
   at Microsoft.Dynamics.Performance.Reporting.DataProvider.Server.DirectLinkService.<>c__DisplayClassa.<Connect>b__5()
   at Microsoft.Dynamics.Performance.Reporting.DataAccess.Server.SecureService.<>c__DisplayClassb`1.<SecureExecute>b__a()
   at Microsoft.Dynamics.Performance.Common.Service.ServiceBase.BaseExecute[T](Func`1 executor)
Component: Microsoft.Dynamics.Performance.Reporting.DataProvider.Server.DirectLinkService
User: DEMOGP\managementreporter

Currently, This is identified as a bug in MR RTM and there is a workaround suggested to get away with this issue

1.      Uninstall MR RTM

2.      Install MR Beta (Server Components and Migration Wizard - https://mbs.microsoft.com/fileexchange/?fileID=0843903d-3544-49f5-af37-3e80ccd0384b

3.      Perform the migration using the beta

4.      Export reports into .tdbx.

5.      Uninstall MR Beta

6.      Reinstall MR RTM

7.      Create companies in MR and then import in reports from the .tdbx file.

(Source: Dynamics GP Forum)


Restrict User Access to Dynamics GP during Maintenance

In SQL server, We have an option to restrict databases to single, restricted user or multi users. When we want all users to connect to database, the status would be Multi_User. In case we have a maintenance plan and expect the other users not log into the database under maintenance, We can set the database to Restricted user or Single user mode.


Restricted user mode allows connections to SQL server through any user ID which is a member of dbcreator, db_owner or sysadmin roles. In other words, Users like “sa” can log into the database and continue with maintenance activities.

I tried to test this option on Dynamics GP Application databases and It seems to work perfect in my tests. I find this useful when I have to do some maintenance routines and do not expect the users to be logged into the application while the maintenance is still on. Once my maintenance routine is complete, I can reset the status to Multi_user mode which then enables connections to Dynamics GP databases.

If we need to restrict users access to Dynamics GP completely including all companies, We can set the restricted user mode on all databases and if we want to restrict access to any particular company, We can always set the database in question to Restricted user mode.

To set the status of databases, We have two options.

1. Through SSMS or

2. Through a Query in SSMS

Through SSMS to set the status,  Right click the database, click properties and click options.


A message pops up to disconnect any open connections apart from SSMS and click yes to it


Prior to this exercise, Make sure your users are all logged out. Once the maintenance is done, come back to the same screen and set the status back to Multi User.

Would expect some feedback from our community just to make sure there is no added risk doing this as i haven’t yet applied this anywhere before.

Note: This is for informative purposes only and do not apply it without proper backups in a production environment. Also Please do not change the status while other users are logged into Dynamics GP and this would adversely affect their active GP session immediately.


Requisition Management Enhancements – When?

I was thinking of much apt title for this post, I couldn’t get one. This post is about some of the pain areas in Requisition Management module for Dynamics GP (BP 3.0 or 4.0 or 5.0 whatever version we are). Because I feel we continue to see the same functionality since the old Business Portal 3.0 for Dynamics GP 9.0, Business Portal 4.0 for Dynamics GP 10.0 or Business Portal 5.0 for Dynamics GP 2010 with few exceptions. Having said that, We also understand there’s a lot of feature enhancements for BP as a whole, Workflows, Web services and Dynamics GP itself that is helping Dynamics GP to withstand as a favorite product to many in terms of choice.

I have implemented Requisition Management module in several places and I must say the product is flexible to implement and a robust functionality than what we could expect from. Yet, I opine that It has certain limitations which has to be addressed at least in the upcoming versions (Though not certain about when it would actually happen).

1. Ability to attach documents with each Purchase Requests- Idea here is to attach any supporting documents related to the request that can establish the valid need of the user for the same which in turn helps the purchasing or Finance departments to make right purchasing decisions. Requisition Management doesn’t support this functionality currently. workaround is to make use of Document library functionality in SharePoint.

2. Requisition Management integration with RFQ- Once any request reaches purchasing department, the purchasing department initiates purchasing process, part of which is RFQ process. A process that Requisition Management doesn’t support currently.

3. Multicurrency Support-  Currently Requisition Management allows users to enter requisitions in functional currency only and no multi currency is entertained.

4. Quantity Field- Quantity field in each Item is limited to 7 characters currently meaning that we cannot enter more than 1000000. Though it is very rare to see requests with more than 1 million in quantity field, yet it is a limitation to be looked into. However workaround is to split the quantities into two line items in this case.

Barring the above exceptions, the module works so intelligently and the biggest advantage I could see is its user friendly interface for entering and approving requests. So is the case with Approval Hierarchy which works for any kind of approval mechanism that is required for and easy to set it for.

Fortunately, Most of the above limitations have already been entered as product suggestions in Microsoft connect. Though we have other third party products integrating with Dynamics GP for Requisition Management, yet, Requisition Management for Dynamics GP module remains the majority choice in terms of cost and value addition it brings to the purchasing process as a whole.

Here is a link pointing to Product suggestions page in Microsoft connect and all I could say is to help strengthen the need to fasten the enhancement timeline for Requisition Management in specific.

Dynamics GP Requisition Management Product Suggestion Link


GPWindow.com: Wonderful Resource

I got to look at this wonderful site this morning www.gpwindow.com while trying to catch up myself to the latest developments in our GP blogging community of late. I must admit I’m very proud of my good friend Jivtesh work on the basic idea of this site and how it is structured to be a one-stop K-base for Dynamics GP resource shoppers. I must say it’s a GP shop with an exhaustive list of items that are available free of cost:). I always like the idea of “aggregation” of data and I personally know how tough it is to aggregate and present the consolidated data in a user friendly formats and structures.

It’s not an easy task to build a database like this specially segment like Dynamics GP which requires subject specific expertise in organizing data.

Jivtesh! Great Effort and Congrats on your great work. Keep going! I’ve already bookmarked the site under my favorites!

Jivtesh has given us a user’s guide for us on how to follow this site. Read here.