Our CRM application for SharePoint is made up of Modules (or Lists in SharePoint terminology) each with custom Web Parts that register data or perform a particular function on that data.

As with any other SharePoint site, all data is contained in either the localized Windows “SQL” OS database or housed in another SQL Server instance, location, or Farm.

Our install procedure recommends the creation of a blank or Team Top level site where the automated installer will then place all the necessary files in place including GAC and “common” directory placements.

The philosophy behind the SharePoint CRM is twofold: modular and relational – modular in the choice of Lists and the Web Parts used that make up the final product and relational in the internal relationships that have been programmed at the List and field levels.


The expression “it can be used to create a sub-site” means that when it is installed it becomes the sub-site and then it is used as an application. There is no need to add any other Lists or Web parts unless there is some reason to integrate them with our CRM Application, and not all third party Web Parts and Lists will with work our application out-of-the-box.

Customization Rules

There is a level of customization that can still be done within our CRM Application as long as the rules are followed, particularly as they refer to entries within our Settings File and Side Bar.

Application Upgrades

All Application updates and upgrades are modifications to our developed Web Parts only so as to add functionality. Fields, Display forms and data are not updated during this process.


Our relationship constructs and components mark a departure with how SharePoint processes list data out-of-the-box; as such relationships are not native to SharePoint.


Field level additions are possible both in label and field type designation using base SharePoint columns. Fields may be copied down from list to list and viewed from other list modules to aid in the transfer of data and usability of the CRM Application. Some mapping connections can also be carried out in the CRM Advanced Settings file. Additionally field data may be merged into a common list for reporting purposes.