Many things are changing with the introduction of the Microsoft Dynamics 2013 SDK. With a host of changes and even some tools being removed you need to know how things have changed if you are a developer. Even if you just employ a developer this can be an interesting and perhaps eye opening article for you.
First let us go over things that are being removed. There are no more plug-ins or client-side scripting. There are no more custom workflow activities and the 2007 web services are gone. There is no longer any ISV folder support for web applications and the Solution Down Level Tool is gone. There are many reasons for this. One of them is that the Microsoft Dynamics framework now has many of these features built in without having to add it on the side. Another big reason is security problems. Some of these features had security vulnerabilities of various types.
Clients now have a better API that is easier to understand and use all around. These include things such as new page options and better utility options. Things such as getclient, etc. The first area in which the SDK has improved is in giving information to those running the server. You can gather a large amount of information about what clients are using your program and where. You can also do this more easily due to the wealth of information on each page. You can also better track your clients in one window. You can not only find out that someone is using a system but see their purchase history. This allows you to see even more patterns within the system. You can even use it to find out more information about your workers themselves. This allows you to better set up a work environment for them as well.
Of course despite the things that went away you still have a wide variety of options for customizing your database. You can still create custom menus in order to track certain projects and fiddle with windows. You can still manage the people using it as usual. The controls however are quite specific as if you want to change a certain state of data you would need the exact name. Custom filters are still around but now you can be much more specific with them when putting together your Microsoft Dynamics system. You do still have to watch out for adding options to too many entries at once. You can still add features to improve the functions of the program used as accounting software for associations.
You also cannot always insert event handlers in every situation. This is to keep users from changing too many things at once and causing damage to the system in the long run. All of these are of course set up to work on a mobile network and be accessed from anywhere eventually. This is very important due to the long-term strategy that Microsoft has. They want to allow you to develop things from anywhere in the world as long as you have sufficient clearance. Open development is here with us.