Sunday, November 2, 2014

Data Types - Dynamics CRM 2011

When creating custom fields in Microsoft Dynamics CRM (CRM) what are all the fields data type available ? go through the below link to know about the data types available in Dynamics CRM.

Data Types available with Microsoft Dynamics CRM 2011


New in Dynamics CRM 2015

Hi All ,

Found a blog shared about the new feature introduced in CRM 2015 which will be very helpful for the CRM  consultant to reduce the level of coding  . please check the below link

Calculated Fields Introduced in Dynamics CRM 2015 

Saturday, November 1, 2014

Microsoft Dynamics CRM Software Development Kit (SDK)

    CRM 2013 Software Development Kit (SDK) is for developers, system customizers, and report writers. This SDK documentation contains information for developers writing server side code, custom business logic, integration modules, workflow assemblies, and plug-ins. It provides an architectural overview of Microsoft Dynamics CRM, the entity model, security model, and web services. Sample code and walkthroughs are provided to guide you through the new features. It also contains information for developers customizing the web client or Microsoft Dynamics CRM for Microsoft Office Outlook, including scripting, integration of custom web pages, and sample code

Download Microsoft Dynamics CRM Software Development Kit (SDK) here .

Supported Operating System
Windows 7, Windows 8, Windows Server 2008, Windows Server 2012
    Microsoft Visual Studio 2010, Microsoft Visual Studio 2012, or Microsoft Visual Studio 2013

    Copied from :  Microsoft Dynamics Download Center 

Monday, April 7, 2014

Dynamics CRM 2011 vs AX 2012

So many people asked me the difference between Dynamics Ax and Dynamics CRM.

Found a blog which share the detailed difference between dynamics Ax and Dynamics CRM .

Please check the below link ..

Dynamics CRM 2011 vs AX 2012

Monday, November 25, 2013

CRM 2013 : Actions

Until CRM 4 there were Workflows that could be used for asynchronous processing of business logic, generally used for setting up automated actions and defining sales process in Dynamics CRM.

Since CRM 2011, the workflows became a category under Processes and there was another category Dialogs introduced. Dialogs provided for execution of Dialog scripts to set up process flows for the Salesforce. These could be used to guide the sales people through the sales process using a question/answer format. The Dialog included execution of automated steps like the workflows.

With CRM 2013, the Processes have been extended to now include Business Process Flow and Actions in addition to the categories from the previous versions.


What are Actions

Actions are messages that can defined for an entity. Existing examples messages include Create, Update, Set State, Assign etc. With Actions, the CRM platform has enabled the creation of custom actions for entities to extend the XRM platform. 


Actions are a type of process that is run by using custom code that uses the Microsoft Dynamics CRM web services.If you are not a developer, or if you haven’t installed some solution that uses actions, you won’t be able to do anything with Actions in Microsoft Dynamics CRM 2013. You cannot call an action from another process except indirectly through a custom workflow activity or plug-in that contains the code to call the action.

Actions open a range of possibilities for developers and people who compose business logic. Before Actions, the primary way that developers could implement business processes was limited to plug-ins or custom workflows. With these, developers can perform operations composed of verbs like Create, Update, Delete, Assign, and SetStatus. Developers refer to these actions as ”messages”. Each of these messages is based on actions taken on an entity instance. So if the goal of a process is to create a record, then update it, then assign it, there are three separate steps. Each step is defined by the capabilities of the entity – not necessarily your business process.

Where to use Actions 


Actions provide the ability to define a single verb (or message) that matches an operation you need to perform for your business. These new messages are driven by a process or behavior rather than what can be done with an entity. These messages can correspond to verbs like Escalate, Convert, Schedule, Route, or Approve – whatever you need. The addition of these verbs helps provide a richer vocabulary for you to fluently define your business processes. You can apply this richer vocabulary from clients or integrations rather than having to write the action within clients. This also makes it easier because you can manage and log the success or failure of the entire action as a single unit.

An example of a custom action could be “Approve”. Often times we have to design an approval process for Dynamics CRM. Once the item is approved, certain actions need to be performed. In previous versions it would either be implemented as a Workflow that is manually executed from the Workflows Dialog or it involved added of a custom attribute that when checked would imply the item is approved and then the workflow would capture the update of this field to process any automated actions defined.

Copied and Shared from : Microsoft Dynamics CRM blog

Wednesday, November 20, 2013

Tuesday, October 29, 2013