My Photo

Search The Blog



Bookmark and Share
Blog powered by TypePad
Member since 01/2004

Disclaimer

  • The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway. All postings and code samples are provided 'AS IS' with no warranties, and confers no rights. © Copyright 2008

Sponsored Ads

CRM Development

The World of Development - XRM Dilemnas

Windows 2008 changes the world of the bundled VPC when it comes to Microsoft Dynamics CRM.

If you consider that the current Microsoft offered CRM VPC contains: Windows Server 2003, Microsoft Dynamics CRM v4 and SQL 2008, SharePoint, Performance Point, Microsoft Office (Word, Excel, Outlook being key), Office Communication, Dashboards, Scorecards, reporting and so much more.

We end up with a pretty sweet bundle!

Now replace Windows Server 2003 with Microsoft Windows Server 2008 - What happens to Outlook integration within the VPC to Dynamics CRM?

The world changes right? So anyone have any suggested this is what we are doing inputs?

Active Directory Groups

Tying Active Directory Groups to Microsoft Dynamics CRM security roles - Now there is a thought. 

Quote of the Week

"For your next CRM Solution, consider breaking the project into [much] smaller phases and evolving in a phased approach, rather than doing it all at once." Steve Noe, Biz IT Pro

    in his article An Evolutionary Approach to CRM Implementations

New SDK - Have you really thought about this xRM concept?

There is an update to the Microsoft Dynamics CRM software developer kit (SDK) which can be downloaded. One of the key things to keep in mind is that Microsoft Dynamics CRM is designed to be extended, changed, updated, and worked with using the highest level skills available. It is not just an application, it is a whole new way of solving business problems with technology.

The Microsoft Dynamics CRM Development Center

Are you thinking about using Microsoft Dynamics CRM as a development platform? Have you checked out the new Microsoft Dynamics CRM Development Center on MSDN?

When does a developer consider the CRM Framework?

If you do not know Dynamics CRM and yet you get applications and .NET here are some things to think about. 

If you are looking at a project consider these two big picture questions.

1) Does the project require the need to track any type of relationships?

If yes then the CRM Framework is definitely something to consider. These relationships can include relationships between two people, relationships between companies, relationships between a person and a company, relationships between things, relationships between animals, relationships between parts and a final product, relationships between things and people,  and more.

2) Does the project require the need to automate and/or document process?

If yes then the CRM Framework is definitely something to consider. These automated processes can include  standardizing the steps  that need to happen to get a project done. Scheduling and completing specific steps, historical reference to the completed steps, the application of specific steps to specific people. The tracking of specific steps associated with a specific person. The automation of alerts and notices and more.

Additionally there is another core reason why including CRM as part of your development might make a lot of sense. This core reason is that built within the Dynamics CRM framework is a multi-layered configurable security system that helps you control who can do and who can access what and pre-built authentication options. Items you do not have to write. You also have the long term upgrade and update support from a maturing product, the development control and the CRM SDK. AND .. the added features that you might not have time to write such as duplicate checking, User Friendly Reporting, Integration to MS Office and layers of data import options.