Dynamics CRM 2015 Enhanced Business Rules

Introduced in Dynamics CRM 2013, Business Rules enable logic execution to be applied to databases using in built tools which avoids the need, and expense, of writing custom scripting.

Improvements in the Dynamics CRM 2015 Update is a refresh to Business Rules which fixes this these restrictions and adds wider functions.

1. Business Rules can now be executed on the server (previously client side only)
2. Business Rule Scope should be set to Entity when building the rule
3. Ensures your rule will fire when no matter how records are updated and not only via the form
4. Synchronous and would be visible real time
5. Set default values on record creation (e.g., all your Leads are generated in the United States so you can default the country on the Lead record when records are created)
6. Added If.. Else If.. Else support
7. Ability to combine expressions using And/Or

There are a set of limitations that everyone should be aware of:

1. Cannot support nested if.. else
2. No grouping of expressions in a condition
3. Expressions can be combined either using And, or using Or, but not both
4. Still single entity only (no ability to reach out to related records)

Queue

Queues are instrumental in organizing, prioritizing, and monitoring the progress of your work while you are using Microsoft Dynamics CRM.

The following information pertains to queues:

1. All customizable entities can be enabled for queues. 
2. Queues may be public or private. Private queue items are only visible to the members of the queue.
3. A private queue is automatically created for each new user or team.
4. A queue can contain multiple entity types, such as tasks, emails, or cases.
5. A queue contains information about the user who is working on a particular queue item. This helps you manage your resources more efficiently and helps to prevent duplication of work. 
6. Queues can be enabled for workflows and audit. This helps improve productivity and track the entity and attribute data changes for future analysis and reporting.

Filtered views

The benefits of Filtered views are

Filtered views won’t break after patches, services releases and maybe upgrades
Security is embedded in the view
All the column names are in lower case
Filtered views are automatically created and updated for custom entities
Datetime fields are held in datetime and UTC
Drop down values are held in filtered views


Problems with Filtered Views

1. filtered views can be performance and they have been known to run slowly.

a. One of the reasons for the slow speed of filtered views is you cannot apply indexes to the tables.
b. Another reason for poor performance is the filter view connects a number of tables together.