UPDATE: Now the servers are up and running. (Added 09/25/2009)
UPDATE: Now the servers are up and running. (Added 09/25/2009)
1. Ensure You are tweeting on a regular basis with useful tips or articles about MS Dynamics
2. If you have any RSS Feed of your blog, You can automate the posting of it using certain Applications like Twitter feed.
3. Ensure you frequently check for other guys out there on twitter whose interest is MS Dynamics too. You can search them using Twitter search Find People.
4. Ensure you mark them to Follow and be followed by them as well
5. Now the most important tip comes. How can we ensure your tweets appear in the results when someone searches for MS Dynamics? We have certain common keywords being used on MS Dynamics to ensure it get indexed that way and returns results when someone searches the same. Here are the common keywords you must be using to ensure your tweets can be found easily.
1. Ensure all your tweets are prefixed or suffixed with #Dynamics. This will ensure whenever someone searches for Dynamics or MS Dynamics, your tweets would appear in those results.
2. Inc case you’re posting a Dynamics CRM related tweet, Use #Dynamics CRM. This will ensure your tweets appear in the results when someone searches for Dynamics CRM.
3. In case of Dynamics GP, the most common keyword being used is #DynGP. So, Use the same in your tweets on Dynamics GP.
4. For Dynamics AX, the keyword to be used is #Dynamics AX.
5. For Microsoft, We can use #Microsoft.
We’re not seeing much activity on other Dynamics products unlike the above that are quite active in Twitter or may be I’m not aware of the activity.
Follow this link in Developing for Dynamics GP Blog having the latest download information for Dexterity and other tools compatible with Dynamics GP 10 SP4.
I’m quite busy working on my new portal MSDynamicsWire.com in the past week that led to being slow in my blog writing and I hope my blog readers would excuse me for that. In this article I’d talk about a call that I received during this morning from one of my clients seeking a clarification on the maximum decimals allowed for exchange rate entry.
Their query is what are the maximum decimals allowed in Dynamics GP while entering an exchange rate during transaction entry. Maximum decimals are critical especially for currency exchange houses or banking institutions where the foreign currency activity would be higher. A one decimal change would lead a huge variation in revaluation or realized gain/loss. The answer for the maximum decimals allowed for an exchange rate in Dynamics GP is 7. Users have to be cautious in entering the decimals since any entry beyond 7 decimals would lead to a complete mess up of the exchange rate as you could see in the example above that a rate of 1.1234567 for JPY currency. If a decimal, say 8 is added to the rate, the rate would become 11.2345678. Assume the difference it makes?? Huge, Isn’t it?
PDF Version of the press release can be viewed here in this link http://www.prlog.org/10340248-announcing-the-launch-of-msdynamicswirecom.pdf.
Of late, I’ve been working on Cashbook Bank Management module for a client. As part of the setup, I marked Post through Payables management and post through General Ledger as you can see in the below screenshot.
If you observe, the GL Posting date is set to pick up by Transaction. So, While testing the transaction flow of payments in CBM, everything was going fine until the posting of payment. After posting, when I got to see the Manual Payment Journal, I observed there is a work message that says below.
“Batch Information is invalid. This Transaction contains errors. It won't be posted”
Then I went to see what’s the status in Payables Batch. The CBM batch that I just posted is again lying as a batch in Payables Batch. I tried posting the same and it posts fine without any errors. Now, its turn with GL Batch. Went to see if the GL posting has done at least. No, This is again standing as a batch in GL. Posting the same completed without any errors. This flow is the same for all transactions. Finally, went to Microsoft support inquiring on the status of this message. I just came to know that this is a known bug scheduled to be addressed in Compliance 2009 release expected in November 2009. The only workaround for this issue is to use the GL posting Date Batch option instead. For those who would want to know the specific bug details, Here is the information.
54193 --The "Post Through Payables Management" option at the checkbook level in the Bank Management Options window is ignored if you are using "GL Posting Date From Transaction" in CBM.
Say you have Analytical Accounting installed in your system and assume you have multiple companies within the Dynamics GP Application. Now, You have activated Analytical Accounting in one or some of the companies and not all the companies. However, You’d see that Analytical Accounting Posting Journal prints every time you post a transaction in companies for which Analytical Accounting is not activated though installed.
This is not an issue or a bug and it is by design. In order to avoid this coming up every time we post the transaction, we can go to Posting setup and unmark the AA Posting Journal in each series we’d want to avoid the same.
Couple of days back, I was trying to apply service pack 9(184.108.40.20611) to my current FRx installation which was at SP5. I have Analytical Accounting Add-in installed as well. I downloaded the SP9 from customer source that has AA Add-in. Ran the setup and it looked to be going smoothly until the below error surfaced in the end.
“ The form is not of a legal path” . When I click further it goes on to say below
If I then go to Report Designer and try to open the same, I get Run-time error91. I have tried everything I could but it still remains the same. Then, came a great support from my favorite Dynamics GP partner forums, Greg Byer has ensured all he could do to help me get past the error. Initially, it was diagnosed that the error might be due to some DLL files not registering properly. So, I was guided to download a batch file from partnersource that is intended to tell us of any DLLs failing to register(KB 848210). However, this batch file looks to be more automated that we cannot see the errors in specific. Then, Greg has actually provided me with another batch file that actually goes and register each DLL and tell us anywhere if a specific DLL fails to register. I ran the batch file keeping the same in my FRx program folder, then I got to see each DLL getting registered while it was struck with this error in specific
“LoadLibrary (windows/system32/msxml4.dll) failed - A DLL initialization routine failed."
Then, I searched for msxml4.dll file in system32 folder, registered that file manually. Then went to see if I’m seeing the error again. No. It worked this time. Sometimes, when a particular DLL fails to register properly, We cannot easily identify which DLL is causing issue for us. However, possessing this batch file actually help us resolve the issue much faster. It’s quite handy. Anyone would want to get the file, Please e-mail me at my contact address. I’d be happy to share the same with you guys.
I’m starting this Blog Carnival–I by picking up the article from Developing for DynamicsGP authored by David Musgrave. David provides us a brief but interesting information about the Smartlist Alternate lookup windows versus Dynamics GP original lookup windows. Here is his article Why do my Lookup windows look different.
The Dynamics GP Blogster, Blog authored by MVP Mariano Gomez. Mariano presents a valuable tip for Dynamics GP Developers in his post. He talks about how Dexterity can be enhanced to allow long physical names. Do not want to wait further reading this interesting tip? Here you go, Mariano Gomez’s Dex – Enabling Long physical table names.
Gloria Braunschweig who blogs on Dynamics GP on her Computeration Dynamics blog presents us with the GL Journal Types article that explains various Journal types. Interesting piece here comes for you Use Journal Types to your advantage.
Microsoft announced that it will discontinue the Microsoft Dynamics Mobile – Server components and Microsoft Dynamics Mobile – Device components will be removed from Partnersource and the Microsoft Dynamics Mobile CAL will no longer be available for ordering effective August 31, 2010. The announcement can be accessed by partners following the link here. This strategic decision to discontinue the current development of Microsoft Dynamics Mobile is made in line with broad availability of partner-developed mobile solutions built on these or similar technologies.
What it means for the customers and partners? Customers need to choose from Microsoft Dynamics Mobile solutions developed by other certified partners.
Earlier, I reported in my post Couple of Known issues in Dynamics GP10 SP4, some bugs that were discovered post SP4 release by Microsoft. Now, an updated smartlist dictionary must fix these issues, according to a blog post published on Developing for Dynamics GP.
For more details on this Fix, Please follow the link here.