Plug-in isolation and statistics

This post is based on the MSDN article Plug-in isolation, trusts, and statistics In Dynamics CRM 2013 Microsoft introduced us with execution of plug-ins and custom workflow activities in an isolated environment also known as a sandbox. Access to the file system, registry ,event log, some network resources and more is prevented in the sandbox

Plugin Trace Log – 2015 (Update 1)

In prior versions developers had to throw exceptions in order to debug and monitor problems in plugins and then view the trace in an ungainly way using downloadable logging file or ,in asynchronous plugins, in tracing information in system jobs.

Deprecated update messages (2015 Update 1)

Prior to the Dynamics CRM 2015 update 1 release ,in order to update special entity attributes special messages were required ,for example you had to use the assign message to change the ownerid attribute of an entity. In current release some of those special messages have been deprecated and you can use the UpdateRequest message

OData endpoint with web resources

In today’s post i want to talk about how you can use the OData endpoint to execute HTTP requests using URI based service to work with Microsoft Dynamics CRM.

Actions

In Microsoft Dynamics CRM 2013 new exciting feature for developers was added to the list of transactional-aware processes (additional to workflows, dialogues and business process flows) name Actions . As you probably know Microsoft Dynamics CRM provide us with OOTB messages for entities such as the CRUD related messages however there are times when the

Business rules enhancements (2015)

The Business rules feature was first introduced in the 2013 version. Business rule gave users the ability to perform simple client-side form validations(Main and Quick Create forms) and actions such as showing,hiding,enabling and disabling fields,Making a field as business required,Calculating the value of a field based on the other fields value, showing error messages based

Nested quick create (2015)

In CRM 2015 we can use the quick create functionality for nested entities. CRM 2013 introduced us with a Quick create forms functionality however once the quick create form opened if we wanted to create a new record of an N:1 relationship record in the quick form we had to move to do it in

Dynamics CRM Search enhancements(2015)

Prior 2015 you if you wanted to perform search but didn’t know on which entity you needed to go through the target entities one by one and perform individual search using the Quick Find Functionality,well, this is not entirely true, this multi-entities search functionality was available since the 2013 release but only for tablets and

Rollup and calculated fields (2015)

Dynamics CRM 2015 introduce us with rollup and calculated fields,a capabilities to perform calculation which could only be done by writing code In prior Dynamics versions. Now power users can define a field with calculated value without the aid of a developer.

Field Level security (2015)

Field level security allows administrator the ability to prevent specific fields on the form from reading and writing. You can restrict access to high business impact fields to specific users and teams. It was first introduced in Dynamics CRM 2011 but was only available on custom fields. In Dynamics CRM 2015 field level security is