The SDT has been provided free of charge to Partners and Customers (via their partners) in the Dynamics community since its release in September 2008. The tool and its feature set have come a long way from the public release of build 9 for GP versions 8.0, 9.0 and 10.0.
Just before I left Microsoft, I was writing a series of blog articles about Customising the Company Login window so that you could see the full company name in the drop down list for long company names.
I had shown how to achieve the customisation with Dexterity and with Visual Basic for Applications, but was having problems getting it to work from Visual Studio Tools.
Now and again I get asked how to become a better CRM Developer, so I thought I would create a blog to point people towards and here it is.
1. Decide you want become a better Developer
Improving and becoming a better CRM Developer is a state of mind/attitude, you have to want to get better, you have to strive to be better every day.
It’s like trying to get someone to read a book you like, you can’t make them read that book no matter how good you say it is, it’s only when the person wants to read it.
2. Make a plan
A plan is like a map, if you don’t use a map it’s very difficult to get to where you want to go. A plan is the same for careers and learning skills, you need to identify the skills you want to learn and make…
This post, therefore, is very important for developers and consultants to gear up for this awesome client and understand what they must do to get the existing GP environments to work on the new release post upgrade.
Thanks David for the all important post. It was really crucial for us to understand.
I was in fact awaiting Sivakumar’s post about the new section that he has been working on. I got the privilege to go thru’ this first before his post went public.
Siva’s new section is all about GP 2010 R2 SQL Objects (Tables, DBs, Stored Procedures, Views, etc.). Like the one we have in MS Word documents that can be accessed from GP SDK, this is also an interesting concept and also very informative for all developers out there, who may not have access to SQL Server on a real time.