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.



Dexterity "Reject Script" Command – David

David’s recent post on reject script command in Dexterity has got some really crucial information about it’s scope and usage.

After 7+ years of Dexterity experience, I did learn something which I had not in the past. MUST READ for any Dex developer.


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.


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.


Difference between Saving & Compiling a Dexterity Code

I was quite taken back by this very difference of Saving a Code and Compiling a Code in Dexterity.

Alright, let me explain.

I was demonstrating a customization my team yesterday and I had to change some code to show a Window on a Button Click event. The only code I had to change in that event script was to add the following statement:

open window [Window_Name];

And even a Non-Dexterity developer would tell us that the above statement do not contain any error, unless the window [Window_Name] do not exist at all. But in my case it did.

I SAVED the code and closed the Project. Created a Chunk and deployed it. To my confusion, the code piece that I added never worked. I was confused to say the least. Why not? I did add the code and created the chunk.

That’s where I made a mistake. I SAVED the code instead of COMPILING it. Only when we compile a Dexterity Code, it gets effective. Saving the code won’t affect the business logic and it would not have reflected in the chunk on that portion.

So, SAVING a code is totally different from COMPILING a code.


Temporary Tables in Dexterity – David

Excellent post for all Dexterity Developers.

David walks us thru’ the Temporary Tables concept in Dexterity. It explains the types of Temp. tables and when to use what type.

Another simple and complete reference post from David for all of us.

Read it here: Working with Temporary Tables in Dexterity.


DexSense – Intellisense For Dexterity – Tool Updated

Before anything, this one’s got to be first.

For all of us, Dexterity Developers, this excellent tool is a boon. This tool has got an update and the new version is v1.8.

David’s article here for more details: Intellisense for Dexterity – DexSense 1.8 Released.
Mariano’s addendum here: Intellisense for Dexterity… the gift that keeps on giving.

Do start using it if you are already not. It certainly saves tons of time in typing.