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

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

#BPST Announcing Batch Posting Service Toolkit for Microsoft Dynamics GP


This is going to add tremendous value to many customers out there who integrate transactions to GP.

David Musgrave's Winthrop Development Consultants Blog

David Meego - Click for blog homepageToday, I am proud to announce the upcoming release of a new product from Winthrop Development Consultants.

Welcome to Batch Posting Service Toolkit for Microsoft Dynamics GP for versions GP 2010 (v11.0), GP 2013 (v12.0 including R2) and GP 2015 (v14.00 including R2).

View original post 307 more words

GP2015 R2 Upgrade – “ASI_MSTR_Explorer_Favorites: Number of results columns doesn’t match table definition”


There were couple of exceptions related to GP2015 R2 that I wished to share here. One would be discussed here and other one on the next post.

After upgrading to GP2015 R2, while doing a routine testing, following error message was thrown while trying to open Smartlist:

Screen Shot 2015-07-31 at 6.53.32 PM

Full message as follows:

Unhandled database exception:
A get/change operation on table ‘ASI_MSTR_Explorer_Favorites’ failed accessing SQL data.

Number of results columns doesnt match table definition.

Number of results columns doesnt match table definition.

EXCEPTION_CLASS_DB
DB_ERR_SQL_DATA_ACCESS_ERR

Debugging this error took me to the table Smartlist Favorites Master (ASIEXP81). Strange, however, that number of columns indeed matched.

I remembered this issue happening in GP 10 and GP 2010. Suggested solutions were to run GRANT.SQL on all databases and changing ODBC provider to SQL Native Client. However, in my case, both were already done and confirmed.

To avoid any further delay or issue(s), I decided to backup the records from ASIEXP81, recreate the table using GP SQL Maintenance and push the records back from the backup table.

Resolution: Drop and create the table Smartlist Favorites Master (ASI_MSTR_Explorer_Favorites, ASIEXP81) using GP SQL Maintenance.

Only that, I did not have to reinsert the records. When I opened the Smartlist after recreating the table, it automatically populated all records. Strange, again. But it worked.

Word of caution: Always take backup before you do anything with the data.

VAIDY

#GPPT Welcome to the GP Power Tools Public Beta


#MSDYNGP #GPPT David has released GP Power Tools public beta. Fun time ahead.

David Musgrave's Winthrop Development Consultants Blog

David Meego - Click for blog homepageToday, I am announcing a free public beta of GP Power Tools for Microsoft Dynamics GP versions 11.0 (GP 2010), 12.0 (GP 2013) and 14.0 (GP 2015).

As you know, I have been working extremely hard on getting GP Power Tools for Microsoft Dynamics GP ready for release and now it is time to get some feedback.

GP Power Tools is the next generation replacement for the Support Debugging Tool.

Read on for more details …

View original post 294 more words