Tag Archives: Microsoft Dynamics CRM

CRM 2013 Beta: Business Process Flows Part 3

The third part of this post is about extending the business process flow for a single entity, which was discussed in this post, to a multi-entity flow. If you are not sure what a business process flow is in Dynamics CRM 2013, take a look at another post here.

Continue reading CRM 2013 Beta: Business Process Flows Part 3

CRM 2013 Beta: Update On Auto-Save Issues

Just a quick update on the issues I mentioned with “Auto-Save” in CRM 2013 in an earlier post The Dreaded Auto-Save: I think there is hope that the mis-matching titles issues have been resolved and users won’t see this in the final release of the product in October. Microsoft support says they can no longer reproduce this issue in their latest codebase. Let’s hope that really is true! Fingers crossed!

CRM 2013 Beta: Business Rules

Note: CRM 2013 is not due to be released until October 2013. The information provided in this blog might different from the final product.

CRM 2013 provides a new functionality called “Business Rules” (not to be confused with “Business Processes”). It gives non-technical users the ability to do several kinds of client-side validation that require Javascript (i.e. development) in CRM 2011. When I first heard of this functionality I was fairly excited. After all, the less scripts required, the less development required, the less gap to meet; that hopefully means cost-saving for the customer. What’s not to like?

However, I started to play with it in the beta release of CRM 2013 and I found the functionality somewhat incomplete. Let me elaborate in this post….

Continue reading CRM 2013 Beta: Business Rules

CRM 2013 Beta: The Dreaded Form “Auto-Save”

Note: CRM 2013 is not due to be released until October 2013. The information provided in this blog might different from the final product.

Why the title to this post you ask? This is because an auto save functionality means most developers would have to seriously rethink the way they develop their plugins, workflows and client side Javascript to prevent code from triggering excessively of course. That is, more work to do for a developer!

Let’s start by taking a look from the end-user’s perspective.

Continue reading CRM 2013 Beta: The Dreaded Form “Auto-Save”