The Microsoft Dynamics CRM Team Blog
News and views from the Microsoft Dynamics CRM Team
Recently I’ve been doing a lot of thinking regarding CRM as a custom application development (App Dev) platform. Many customers and partners have taken CRM and built rich applications which have little to do with Sales, Marketing or Service scenarios. However one thing that most of these apps have in common is: people, work and objectives. In fact the goal of Microsoft CM is: Easy and quick to generate rich applications for work management across people, organizations, processes
So what are some of the benefits of using Microsoft CRM as a custom App Dev platform? Here are some top reasons which spring to mind:
If you have been using CRM to do ‘non-standard’ Sales, Marketing and Service let use know (leave a comment here or reach me through my site)! We are always interested in hearing about our app being used in new and exciting ways.
There is one thing which remains unclear to me. With all good qualities of MCS CRM 3.0 (or Titan) as a development platform, what about transactional support? I mean, in case if single business operation requires several manipulations with different entity instancecs, how can one denote transactional boundary with proper commit/rollback semantics?
It appears that the transactional support question is left un-answered.
It would be great to know if there is a way we can include transactions in CRM programming. To eloborate I want to manipulate a few entities in one call, however, I should be to rollback any updates if any of them fails.
Any help is greatly appreciated