Category Archives: Dexterity

Using Script Debugger in Runtime Mode

Posted on by

David explains us about using Script Debugger in Runtime mode.

There won’t be any performance issues obviously as stated by him, but there are some crucial points that we need to think about before enabling it.

Enabling it on live environment is like inviting disaster. I remember I used to do that, but only after all users log off from GP. That particular customer, they don’t work 24/7 which gave me the confidence to enable it on live and disable it back once my troubleshooting was over. I would have been in very deep trouble easily had I not remembered disabling that after my task.

Even a single Dex debug message box would be more than enough to drive a user crazy.

VAIDY

Required Fields – Additional Tip

Posted on by

This one is a simple tip, yet very useful one. Frank reminds us on where and what would be the problem if we don’t see required fields as we wished to.

Now, this one is for developers. If it’s a customization that we have developed and on that if users are not able to see required fields as they wish, then you know what the problem is: Set Required property to TRUE without fail for all fields that are suppose to be REQUIRED and make sure that you have linked the prompts (Link Prompt action) for those fields correctly.

VAIDY

Dexterity Script Profile to solve Performance Issue – David

Posted on by

Waiting for 30 seconds after simply clicking a checkbox is indeed a nasty thing.

David explains us on how to solve Performance Issue using Dexterity Script Profile by taking above issue, reported by some customer.

It’s a detailed post with step by step explanations on how he could solve it.

Must read for all consultants and developers.

VAIDY

Dexterity "Reject Script" Command – David

Posted on by

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.

VAIDY

The Future of Microsoft Dynamics GP Technologies – Mariano

Posted on by

Mariano highlights 5 coolest technologies for Microsoft Dynamics GP in coming years to watch out for. I can’t agree for more, since I am already seeing 3 of the highlighted 5 currently.

Just to list you those technologies:

1. Microsoft Lync
2. Microsoft Silverlight
3. Microsoft Visual Studio Lightswitch
4. Cloud Computing
5. Microsoft Dexterity (yeah you did hear it right)

And to know why the above are cool, check out his post: The Future of Microsoft Dynamics GP: 5 Cool Technologies You Should Watch For (and Learn) in the Coming Years

VAIDY

Issues with GP 2010 SP1 DYNAMICS.DIC – David Musgrave

Posted on by

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

Microsoft Dexterity 2010 R2 – Enhancements

Posted on by

David sums up Dexterity 2010 R2 enhancements and gives us a glimpse of how it’s going to be, referring to Feature of the Day posts from Inside Microsoft Dynamics GP.

Pretty exciting to learn these new features, obviously.

VAIDY

Difference between Saving & Compiling a Dexterity Code

Posted on by

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.

VAIDY

Dexterity Incompatibility with .NET Framework 3.5SP1

Posted on by

This post from Dynamics Confessions blog, informs us about Incompatibility of Dexterity 10.00.320 Build with .NET Framework 3.5SP1.

Those who are working on similar lines, have a look at this article and be informed on what needs to be done in such scenarios.

NOTE: Download Dexterity 10.00.324 Build separately from PartnerSource and install it as soon as you apply GP SP4 on Dexterity. Because this particular Build 324 is the actual SP4 for Dexterity Common Components and Dexterity itself.

VAIDY