Dynamics Blogger

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...

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...

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). ...

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 .

While upgrading from Dynamics GP 10 SP1 to SP4, one of my clients have encountered the error below. “The stored procedure Synchronize TableData() of form duSQLAccountsynch : 27Pass Through SQL returned the following results: DBMS: 102, Microsoft Dynamics GP: 0.” This error was surfacing while running utilities and upgrading DYNAMICS database. I’ve not seen this error before. Taking cue from the error message, I thought initially it might be due to non-synchronization of account framework so tried resetting dex.ini file to Synchronize=TRUE, but it didn’t work at all. To understand the probable cause of this issue, I had to rely on dexsql.log file.  The log showed that there is a possible permission issue, so we tried running the GRANT.SQL and DYNSA DB owner scripts on the databases as these were databases restored from Live instance. The same issue continued. The dexsql.log showed that the database upgrade of DYNAMICS is getting interrupted with this error when it is reachin...

We’re quite familiar with this phrase in almost all websites across offering us to store our usernames and passwords so that when we try logging in next time, we just don’t need to enter them again and again thus freeing our time little more. Surprisingly, Dynamics GP 2010 has got a feature similar to this option. In fact, It has not just one but two such options. 1. Remember user name and password – This option when marked, the GP client doesn’t ask you for your credentials and push you to the next screen, Company selection. 2. Remember this company – Now If You’re having 5 companies, and you would be using a particular company most often, You can mark this option so that it will hide this window of company selection as well when you log into GP next time. I find this option more useful when I have even one company. Marking both the options above helps us to just get into Dynamics GP Home screen directly every time we click that tiny cute GP icon on our desktops. Somethi...

In Microsoft Dynamics GP 2010, We can get this error. “ Unable to connect to the Home Page Metrics URL. Please contact your system administrator.” Causes of this error is that you’ve activated the option to use SQL server reporting services Home page metrics under Charts and KPIs’ in Reporting tools setup window (Dynamics GP | Administration | Setup | System | Reporting Tools setup)  and provided incorrect URLs’ in your SQL reporting services setup tab in Dynamics GP. Resolution for this error is 1. Ensure your SSRS is running properly 2. In SQL Server Reporting Tools setup tab in Dynamics GP, Check the URLs’ provided for Report server and Report Manager. The standard path of these reports are provided in Help Manual of Dynamics GP 2010. Until Next Post….