Here is an example of code to get stripped down contact and account forms. This code is placed in the onLoad event of the respective forms. Note: this is not supported, but a common way to hide left navigation links on specific entities (since normal site map customization does not affect these). The other method we typically employ is to remove access from many users to some functions they will not touch (like Cases if an organization is not taking advantage of the Services components). However, this is a fail-safe way in cases where permissions do not control access or if a new group/permissions are issued and someone accidentally gets to see certain links the organization has already decided not to use.

/////////////////////////////////////////////////////////////////////
// Hide areas within navigation
var navQuotes;
var navOrders;
var navInvoices;
var navService;
var navContracts;
var navListsInSFA;
var navCampaignsInSFA;
var nav_NA_SFA;
var nav_NA_CS;
var nav_NA_MA;

navQuotes = document.all.navQuotes;
navOrders = document.all.navOrders;
navInvoices = document.all.navInvoices;
navService = document.all.navService;
navContracts = document.all.navContracts;
navListsInSFA = document.all.navListsInSFA;
navCampaignsInSFA = document.all.navCampaignsInSFA;
nav_NA_SFA = document.all._NA_SFA;
nav_NA_CS = document.all._NA_CS;
nav_NA_MA = document.all._NA_MA;

if (navInvoices != null) { navInvoices.style.display = “none”; }
if (navOrders != null) { navOrders.style.display = “none”; }
if (navQuotes != null) { navQuotes.style.display = “none”;}
if (navService != null) { navService.style.display = “none”;}
if (navContracts != null) { navContracts.style.display = “none”;}
if (navListsInSFA != null) { navListsInSFA.style.display = “none”;}
if (navCampaignsInSFA != null) { navCampaignsInSFA.style.display = “none”;}
if (nav_NA_SFA != null) { nav_NA_SFA.style.display = “none”;}
if (nav_NA_CS != null) { nav_NA_CS.style.display = “none”;}
if (nav_NA_MA != null) { nav_NA_MA.style.display = “none”;}
else {
alert(”Navigation not found”);
}

If you have worked with or implemented Microsoft CRM 3.0 (or even previous versions like 1.2), you will know that there are some features that could really help improve the implementation, development, and end-user experiences.

CRM Titan (4.0) has the promise of bringing together some of these features in this third major release of Microsoft CRM (yes, they skipped 2.0). Along with multilingual capabilities, one of the main hot-points is the SaaS offerings. Microsoft CRM will be available in 3 architectural flavors:

• On-Site (Self Hosted) — as done in the past
• Hosted by Partners
• Hosted by Microsoft

The SaaS offerings mean a few very important things. One of those is easier access over the Internet.

Previous versions of Microsoft CRM were known to be “Intranet-friendly”, but almost to a point of “Intranet-only”. With the growth of virtual work environments, many customers do not want to be limited by intranets or VPN’s. Those that had chosen salesforce.com may need to rething their decisions with tighter Microsoft integration and a potentially lower TCO.

Easier access over the Internet also means that the MS CRM world for Partners and software vendors is a bit less of a barrier and I expect we will see more of the much-needed industry verticles begin to arise quickly, among other features that some of the more mature CRM solutions (like salesforce.com have had). I hope you are excited. I would expect to see CRM Titan (4.0) released around November, with some of us Partners already playing around with pre-RTM versions of the software.