This is a reposting of an article Tracy Steere originally wrote on my Developing for Dynamics GP blog.
Hi, my name is Tracy Steere and I work with David Musgrave on the Microsoft Dynamics GP Asia Pacific support team.
A bit about myself, I started working with Dynamics GP as an assistant Accountant in 1997 by October 1997 I had become a Dynamics GP Consultant for a company called TWO inc. in Durban, South Africa. In January 2000 my husband and I moved to the UK on a 2 year working visa, I worked for Partners and end user companies. Two years became four and that became 10 very soon, by this stage we had bought a house and had two lovely children Tiffany (12) and Chad (10). It became very clear the cold of the UK was not for us, with a work transfer with Craig through Microsoft we moved to Sydney. I started at Partners and even went to a different product for a change in pace. Two years ago I applied and got my current role at Microsoft as a Dynamics GP Engineer. That in a nut shell is me.
Recently, I had a case where the Partner was not able to see a currency ID in Management Reporter (MR), we did the normal checks and found that in the multicurrency Setup window in Dynamics GP. There were no Currency ID’s listed.
Working with David, we reviewed the source code and our investigation for the following:
On the Multicurrency Setup window (form MC_Setup), the Translation Currency scrolling window (window TranslationCurrencyScroll) was not populating with currencies.
We then searched the MC_Setup form source code for “fill window TranslationCurrencyScroll” command to locate the script which would populate (or fill) the window.
We found the event script: MC_Multicurrency_Setup_WIN_PRE which contained the following commands:
call GetTranslationCurrencies of form MC_Setup,
fill window TranslationCurrencyScroll;
So we then looked at form procedure: GetTranslationCurrencies of form MC_Setup the only code was in the script was:
inout table MC_Company_Access_TEMP;
This led us to believe that this script was a placeholder that was triggered upon from elsewhere.
So where was the actual code?
We then used the Support Debugging Tool‘s Manual Logging feature to capture logs wen the window was opened. we could see the form procedure being called we also saw the trigger script firing:
10:45:47 ‘MC_Multicurrency_Setup_WIN_PRE on form MC_Setup’
10:45:47 ‘GetTranslationCurrencies of form MC_Setup’, table ‘MC_Company_Access_TEMP’
Also found trigger script:
10:45:47 ‘GetTranslationCurrencies of form mcTranslationCurrency‘, table ‘MC_Company_Access_TEMP’
Now we knew the name of the trigger script, we confirmed that the form mcTranslationCurrency not in core Dynamics.dic. We still did not know in which dictionary the form was located.
So we used the Support Debugging Tool’s Resource Information window to search for form mcTranslationCurrency. We just entered “mcTranslationCurrency” into Form Technical Name Field and it identified that the form is in the product HITB Report (5597).
We then checked with the customer and this product was not installed on their system. The HITB Report is installed by default, but was manually removed as the customer did not use inventory.
We asked for them to re-install the HITB Report product. Once the HITB Report was back in place, the scrolling window populated as expected.
The section of the window where Multicurrency joins to Management Reporter is populated through none other than the HITB Report product (5597).
Yes you got it, if this module is not installed in Dynamics GP, then you will not have any currencies in the Multicurrency setup window.
So the moral of the story is make sure you have the HITB Report product installed if you have Management Reporter.
This article was originally posted on the Developing for Dynamics GP Blog and has been reposted on http://www.winthropdc.com/blog.