Microsoft Dynamics CRM 2013 Application New Features - Security Models
Monitor cases in one place on the Dynamics CRM interactive service hub dashboard
Solve customer issues faster with interactive service hub dashboards. Watch this video to see the two main dashboards in action. The Tier 1 dashboard helps you find your cases and the things you need to do fast. Use visual filters, snapshots, and tiles to decide what you want to see and work on. The Tier 2 dashboard gives team leads and managers a single place to monitor more complex or escalated cases. Interactive service hub dashboards give you everything you need to support many customers and issues from one central location.
MS CRM Many-to-Many Relationships of the "Native" Kind : CRM 4
Taking Advantage of Web Resources Dynamics CRM 2011
Collaborative selling capabilities with Sales by Microsoft Dynamics
With Microsoft Dynamic CRM, discover and share ideas with the entire organization with enterprise social networking tool Yammer. Collaborate on sales proposals and presentations with document management and real-time document co-authoring from Office 365 and SharePoint. Reach experts with contextual presence, IM, voice, video, and online meetings via Skype for Business.
Error Handling in Plug-ins
For synchronous plug-ins, the Microsoft Dynamics CRM platform handles exceptions passed back to the platform by displaying an error message in a dialog of the web application user interface.
For asynchronous plug-ins, the exception message is written to a System Job (AsyncOperation) record.
For plug-ins not registered in the sandbox, the exception message (System.Exception.Message) is also written to the Application event log on the server that runs the plug-in.
Sandboxed plug-ins should use tracing.
Tracing is to provide isolated (sandboxed) plug-ins and custom workflow activities with a way to output runtime information when an exception is thrown because isolated plug-ins and custom workflow activities cannot write information to the system event log or the file system.
The tracing service was implemented to provide sandboxed plug-ins and custom workflow activities with a means to output run-time information when an exception is thrown. In addition, tracing is also supported in plug-ins that is not sandboxed.
Activity Feeds Auto Post Workflow (5 of 5): Dynamics CRM 2011
This snack explains how activity feeds allows users to stay up to date on the CRM records that are most important to them. After you complete this snack you will be able to:
This video will take you through tracking and converting an email into a lead record. Then convert that lead record into a new opportunity record and demonstrate how to associate products, quotes, orders, and invoices when working with an opportunity record in CRM 2011.
Generate early bound entity classes with the code generation tool (CrmSvcUtil.exe)
CrmSvcUtil.exe is a command line tool which can generate early bound classes for Microsoft Dynamics CRM. Output file can be C# or VB.Net file.
Generated file contains
All entities, one partial class for each entity
These strongly typed classes provide early binding and Intellisense support in Microsoft Visual Studio.
Generated file can be referenced by projects that use Microsoft Dynamics CRM. Following assemblies must also be referenced in that project
These assemblies can be found in SDK\bin folder of the SDK.
Running code generation tool
Make sure Microsoft.Xrm.Sdk.dll assembly is in same folder.
To list the supported command-line parameters, use the following command.
The following table lists the code generation tool parameters and a gives a brief description of their use.
Device ID used when you connect to the Online server for authentication. Only required if the device ID has not been stored on disk in the %USERPROFILE%\LiveDeviceID folder. Only used with the Microsoft account identity provider.
Device password that is used when you connect to the Online server for authentication. Only required if the device password has not been stored on disk in the %USERPROFILE%\LiveDeviceID folder. Only used with the Microsoft account identity provider.
The domain to authenticate against when you connect to the server.
The URL for the Organization service.
The file name for the generated code.
The language to generate the code in. This can be either “CS” or “VB”. The default value is “CS”.
The namespace for the generated code. The default is the global namespace.
The user name to use when you connect to the server for authentication.
The password to use when you connect to the server for authentication.
The name of the generated organization service context class. If no value is supplied, no service context is created.
Show usage information.
Suppress the banner at runtime.
Generate request and response classes for actions.
When set to true, a dialog to log into the CRM service is displayed. All other connection related parameters specified on the command line are ignored.