Management Reporter – Misspelled Account Categories


This would be second Management Reporter post in a row. This also is about the default reports and how to troubleshoot the issues pertaining to the default reports.

I have an Australian edition of GP installed. Most of the terminologies (such as “Fiscal/Financial”, “Realized/Realised”, etc) are localised in GP. However, default reports in Management Reporter still are in US English, if I am not wrong.

Consider the following default balance sheet row definition:

Screen Shot 2016-02-09 at 04.51.43 PM

I was wondering why balance on this account did not show up on the report. After several minutes, I realised that the account category was misspelled, compared to what’s there in GP. Notice that on the report definition it is “Amortization” with a ‘z’ and in GP it is “Amortisation” with a ‘s’.

After changing the categories with correct ones, by referring to GP, the report started showing the correct figures.

This post is relevant only if you reuse the default reports. It’s irrelevant otherwise.

Happy Reporting!

VAIDY

Management Reporter – This report view contains no data.


I have been working on a Management Reporter project, for which I wanted to install and configure MR2012 CU14 from the scratch.

Completed the server and client installation, completed the Configuration Console processes, imported data from GP2015R2 (sample company) and reached a point where I wanted to test the default reports.

Ran the report and got the following message:

Screen Shot 2016-02-10 at 09.44.58 AM

I checked everything, including the date range, data available in sample company and everything that I could remember. All were perfectly alright.

I was, however, getting some warning messages while the report was getting generated. Messages as follow:

Screen Shot 2016-02-10 at 09.47.43 AM

This one was familiar. When we install management reporter, we get default reports along with it. It’s a nice and easy way to get started with MR, learn the concepts. However, it comes with its own headaches.

To name one (also most important), each default report row definition would have link to both Dynamics AX and Dynamics GP financial dimensions. To a GP consultant’s dismay, AX dimensions link would be placed in a column before GP dimensions link, as shown below:

Screen Shot 2016-02-10 at 09.56.46 AM

Now let’s go back to the warning message. It says:

The row definition contains more than one financial dimensions link. Since the report does not use the row definition for reporting tree option, the report will use the *first* financial dimensions link to generate the report.

The first here being Microsoft Dynamics AX dimensions link. Thereby, rendering all reports with the message shown in the first screenshot on this post.

Alright, so I know the cause now. I know what I must do to get past this message. However, I had no clue HOW to do that. I mean, I know I must remove AX dimensions link column from the reports, but not sure how.

This community forum post answer from Sue tells us how to remove the link column. Too bad, this post was not marked as an answer.

I would, however, like to point to the standard & the easiest method to remove the unused link (in my case AX dimensions link).

  • Either you can go to the Edit menu and click on “Row Links” as shown below:

Screen Shot 2016-02-10 at 10.08.15 AM

  • Or you can also use the tool bar button for “Row Links” as shown below:

Screen Shot 2016-02-10 at 10.06.30 AM

Once you click on “Row Links” from either of the above steps, you should get the following window:

Screen Shot 2016-02-10 at 10.13.02 AM

Once deleted, your report definition would have only one dimensions link, i.e. to Microsoft Dynamics GP link.

Report would then show the data as expected.

Screen Shot 2016-02-10 at 10.16.26 AM

Of course, this would be the case if you want to reuse the default reports. This post would be irrelevant for those who design reports from the scratch.

Happy Reporting!

VAIDY

Happy New Year 2016


To the GP Community:

Happy New Year 2016!

This year is slated with lot of interesting releases for GP impending. I am absolutely as excited as all of you.

Let’s wish this year be an excellent year for Dynamics GP and its success.

VAIDY

GP Upgrade – “Please Select a Company” Message


This one’s quite simple, yet intriguing.

I am working on a test upgrade; from GP2010 to GP 2015 R2. I decided to only take production company databases and left all test companies, for all logical reasons.

After applying GP 2010 SP4, I decided to perform a unit testing. After logging in to GP, I received following message, without having any issues later on. It was just this message:

Company Message

(Above screenshot courtesy: Ugan)

As a thumb rule, I searched on GP community and stumbled across two most relevant forum questions and suggestions.

  1. Please select a company message after company has been selected and logged into
  2. Dynamics GP 2015R2 Upgrade – Please select a company

None of them is answered.

I had a suspicion that this must be something to do with “Remember this company” option on “User and Company” window. I decided to use GP Power Tools (previously Support Debugging Tool – SDT) and SQL profiler to study this message in depth.

As suspected, results pointed to the option “Remember this company”. Now, if you remember what I said earlier, I took only the production companies for test upgrade and not the test companies. Previous consultant who was working with this client had selected a test company as his (SA’s) default company.

Now, you must also recollect that we have a SQL script to clean up missing companies’ affiliation across DYNAMICS database.

I ran the above script on the test environment and logged on to GP. This time, I was required to select a company and the message never appeared back.

Happy troubleshooting!

VAIDY

Changing SQL Server Collation After Installation


I had a necessity to change the collation of newly created SQL server instance from CI_AS to CP1_CI_AS.

To brief you about why this was needed, I wanted to test upgrade GP from version 2010 RTM to 2010 SP3. In order to that, I created a new SQL server instance with collation SQL_Latin1_General_CI_AS. I restored GP 2010 RTM backups on to this newly created server. But later realised that GP databases that I got for 2010 RTM was of collation SQL_Latin1_General_CP1_CI_AS.

There were two options. Either I must change the collation of databases to CI_AS or I must change the server collation itself to CP1_CI_AS. Later seemed to be a better option (for some reason, I wanted to retain the collation on the databases). I was left with changing the collation of server instance.

That’s when I got this link: Changing SQL Server Collation After Installation

I was worried about the whole process but this post saved me loads of time and sweat. Changing the collation was a breeze.

Anybody out there who is looking for the best possible method to change server collation, above is the post you would want to read.

VAIDY

OFF-TOPIC: Windows 10 and Microsoft File Transfer Manager (FTM) Issues (UPDATE)


Dynamics GP - Learn & Discuss

This is my first post from Perth, WA. It’s been an excellent journey and so far so good. More about my Perth life later.

This is something that I never experienced before. When you download any file from PartnerSource or CustomerSource, Microsoft would let you do that only through it’s File Transfer Manager program. If you have that installed already, any download initiation would first invoke this program and then let you set the path/folder to take in that download and etc.

However, when I tried to do that from my new Windows 10 machine, the FTM did not open. I tried to figure that out, but later remembered this same issue happening on my Windows 8.1 machine.

Basically, from Windows 8.1, for some reason, calling the FTM from Internet Explorer worked only on a 32 bit Internet Explorer.

Looks like Microsoft has not fixed that yet. If you are wondering why your FTM…

View original post 55 more words

GP 2010 Mainstream Support Ends Soon


All GP customers, ISVs, VARs and consultants should bear in mind that GP 2010 mainstream support ends on October 13, 2015.

Extended support runs till 2020, however it is strongly advised to upgrade your GP to most recent version (or a higher version on which your other modules/add-ons are compatible with).

You may want to bookmark this complete support schedule on Microsoft’s portal: Microsoft Support Lifecycle – Dynamics GP.

VAIDY