Converting modified reports/form from vba to Dexterity.

Because of various reasons people are replacing their vba code with dexterity or VSTools and often we got question like how to do this and that in VSTools or dexterity. The best thing to do while replacing your vba code is to hire someone having customization expertise.

Yes , I am not kidding, I believe for someone who don’t have coding experience, even using coding tools are hectic. Since the arrival of web client for Dynamics GP we are reading discussions about moving vba code to other development tools, and sadly I saw people going for VSTools or Custom .NET application trying to do the same functionality with the help of eConnect or similar integration tools but never think about Dexterity for a second, ignoring the fact that moving all the customization on dexterity will let them free from future incompatibility and maintenance issues.

Call it a fear or a phobia, but it is not true that dexterity based customization crashes application, just like vba or VSTools if anything goes wrong you have always an option to go and disable the customization or completely remove it. Dexterity customization if you do changes in GP native windows then they will be inside your product dictionary (just like the vba FORMS and REPORTS dictionaries) and not actually update DYNAMICS dictionary, so by no means your native forms will get updated with dexterity customization.

So, in my opinion to get most out of your ERP, you need to choose your customization tool wisely and for long term and that native tools are always smarter than others.