Microsoft Dynamics 365 - Soluciones de Negocio

Compatibilidad con las versiones de .NET Framework A continuación se describen las consideraciones sobre compatibilidad del código personalizado escrito con Microsoft .NET Framework 4.5.2. Cualquier cliente de servicio web creado con Microsoft .NET Framework 4.5.2 o posterior que llama a los servicios web de Dynamics 365 es completamente compatible en Dynamics 365. .NET Framework SDK Client Dynamics CRM versions Description .net 4.0 CRM 2013 (6.x) Download here v6.x, v7.x, & v8.x Supported with new Microsoft.Xrm.Sdk.dll assembly included in: Dynamics CRM 2013 SDK Version 6.1.2, January 2017 NuGet Package: Microsoft.CrmSdk.CoreAssemblies Version 6.1.2 .net 4.5.2 CRM 2015 (7.x) Download here v6.x, v7.x, v8.0 & v8.1.0 Supported* *v8.1.1+ is not supported, Move to SDK version 8.x for support for CRM version 8.1.1+ .net 4.5.2 CRM 2016 (8.x) Download here v6.x, v7.x, & v8.x Supported Fuente: https://blogs.msdn.microsoft.com/crm/...

A Custom Workflow Activity Plugin is very similar to a Plugin exempt that it is executed from within a CRM Workflow, Whereas Plugins Are executed on Events that Occur on the Entity. Workflow Activities -Custom workflows are triggered by standard workflows available in CRM. Triggers limited(Create, Update, StatusChange, Delete and On assign). -Workflows are better when you need the operation needs to be configured periodically by non programmer administrator, where you can implement the configuration part as standard workflow (Workflow1), and static part of the functionality as custom workflow which will be executed by the standard workflow (workflow1). -An workflow won't work in offline mode because it requires to have access to the crm live server to trigger the workflow, whilst in offline mode changes are not made to the live crm server...they are made locally on the client app and synced later. -Workflows can be manually executed, or automatically triggered by selec...