Developing Microsoft Dynamics GP Business Applications – Book By Leslie Vail


DMDGBA

UPDATE: Author of this book, Leslie Vail, has got a post on her blog (Dynamics Confessor Blogspot). Link now added here to her own post: Published at last! Developing Microsoft Dynamics GP Business Applications.

I had the privilege to be a part of the technical reviewing of this amazingly informative book: Developing Microsoft Dynamics GP Business Applications.

This book is penned by one of the most experienced GP personality and multiple times MVP, Leslie Vail. Packt Publishing has published this book.

I strongly recommend this book to all GP developers/consultants who would like to know how to develop anything with regards to Dynamics GP; be it a new feature addition, a feature modification or just a cosmetic enhancement.

Thanks Leslie Vail for this wonderfully written book with every single important concept being covered.

VAIDY

Adding more comment lines to POP Purchase Order – Mariano


Mariano’s latest post explains how to add more comment lines to POP Purchase Order report. The idea is to split the comment text into 80 characters sized fields and then displaying it on separate report sections. I leave you here so you could refer to this awesome piece of post from Mariano. It’s a step-by-step guide on how to do this.

David, way back in 2011, demonstrated a similar approach on his post about adding more comment lines on SOP Documents. It’s worth to remind that post now.

VAIDY

Cross Dictionary Triggers on DEX.DIC


This post is kind of reblogging David’s post, Cross Dictionary Dexterity Development, for just one reason.

We can write cross dictionary triggers on DEX.DIC. I had tried this once, some years ago, and could not succeed. I never got a chance or requirement again that would push me beyond that limit. Looks like that chance is here and now.

And this is certainly the right time for me to reblog this point and the post itself.

VAIDY

Using substring() with Text Fields – David


Back from my vacation, several posts grabbed my interest as a developer. This post from David is one of them.

David explains how to resolve an issue that was found in Sivakumar’s SDT (Support Debugging Tool) based solution. In a nutshell, the issue was with Text type fields and dexterity function substring().

Read it here; Quick Tip: Using substring() with a text field datatype.

VAIDY

Best Practice for Dexterity Version & Build Numbers – David


David’s post, Best Practice for Dexterity Version and Build Numbers, explains a very important concept in chunk creation process.
We must version our products which is very important and also ethical. Small-time Dex developers do not understand this process when they deliver a simple customization. 
I sincerely believe that this post from David would enlighten people about this.
VAIDY

"Illegal Address Field" Error while accessing a Global


This one’s interesting and quite straightforward too.

I had to create a new Global field in my customization. Instead of creating a new field, I added an existing GP field (‘Customer Number’) and wrote my code to assign value and retrieve value as required.

I created the chunk and when my code was executed at run-time, I received the following error message:

At the first look, it’s all correct. I have referred to a Global field which exists pretty much in my dictionary, otherwise it would not have even got compiled in first place.

So what else would be the reason? It’s plain and simple. I created a “new Global field from an existing GP field”. Which means, when I created my chunk, I should have added this resource explicitly to my dictionary, using Transfer Resources Dex Utility option. OR I should have first created a new field itself and then add that to Globals.

Since I didn’t do above, compiler did not find that resource at all in my dictionary or GP’s dictionary (Dynamics.dic) and then threw this error message.

I created a new field itself in my custom dictionary and added that to Globals. Things were perfectly alright.

Sometimes, focusing more on brain draining issues may actually drain your brain. Well, I am serious. Otherwise, how in your opinion I missed this above simple concept?

Update: David has posted a quick tip on why this issue occurs and what is the best possible solution to this.

VAIDY

Access data from other companies from Dexterity


David walks us thru’ how we can access data from other companies from a Dexterity code.

I have never written a code like this in my 8 years of experience. That said, I have not met any requirements that challenged me to write such code. With this, David has eased my (our) efforts in finding how it can be done.

Thanks David.

VAIDY

Issues with GP 2010 SP1 DYNAMICS.DIC – David Musgrave


David informs us about a very strange but critical issue that’s been faced by developers when using GP 2010 SP1 DYNAMICS.DIC dictionary.

This is really critical to be informed about, so all Dex Developers please make sure that you read this post from David, as it also mentions some workaround till a proper fix is released.

Read it here: Unknown identifier ‘DYNAMICS’ or other Constant with GP 2010 SP1.

VAIDY

Dexterity 2010 R2 Supports Microsoft Team Foundation Server (TFS)


That’s a GREAT GREAT news from Microsoft about Dexterity. Inside Microsoft Dynamics GP blog informs us that Dexterity 2010 (v11) R2 will support Microsoft Team Foundation Server (TFS).

What this means? Dexterity supported only Microsoft Visual SourceSafe (fondly called VSS), which has been used under discontinued support from Microsoft. Those who wants to streamline Dexterity Development on their organizations, found it very difficult to use something which is not supported by Microsoft but Dexterity.

Microsoft introduced Team Foundation Server (TFS) which is advanced and very easy to use and maintain. With Dexterity 2010 R2 release, the biggest gap in Dexterity Development history is now filled.

VAIDY