Action prefix does not honour Solution Publisher prefix

Today, while working with Dynamics 365 v.8.2 online, I found a strange issue while creating an Action from a process template: the solution prefix is not honored by the copy process and the new action gets the default "new_" prefix. In order to solve this issue, there are two workarounds: Create a solution using the … Continue reading Action prefix does not honour Solution Publisher prefix

Advertisements

Lead Qualification error – Access Is Denied

Hello everybody, An issue related to lead qualification arose today, which made me crazy for a day or so...kind of feeling like   So, to give you a little backgroud about the customer implementation: Dynamis CRM 2016 8.2.1 on-prem migrated from MS Dynamics CRM 2013 Several business units, with records owned by teams. Not many … Continue reading Lead Qualification error – Access Is Denied

Invalid object name ‘dbo.MatchCodec287f61db88f4921a560cfc8971ae2e1’.

Hi there, Today, while working with duplicate detection jobs in a Dynamics CRM 2016 8.2 on-premise deployment, I faced the issue that gives name to this post: Invalid object name 'dbo.MatchCodec287f61db88f4921a560cfc8971ae2e1'. Prior to this error, I have unpublished a duplicate detection rule and then created a new duplicate detection job, which after a while failed. … Continue reading Invalid object name ‘dbo.MatchCodec287f61db88f4921a560cfc8971ae2e1’.

Dynamics 365 CE – Setting available entities in lookup fields

Hi there, Today, I learn that in the next major update of Dynamics 365 CE (v. 9.0), we finally have the hability to set the available list of entities in a lookup control. So, lets say we want to limit the Potential Customer field on the opportunity's form to only show contacts and not accounts, we … Continue reading Dynamics 365 CE – Setting available entities in lookup fields

Useful links

Hi, This post is just a list of useful links that I found to be helpful. Documentation / Product Information Microsoft Dynamics 365 Roadmap Developer Guide for Dynamics 365 Customer Engagement Client API Reference for Customer Engagement What's new for developers in Dynamics 365 (online), version 9 Dynamics 365 Customer Engagement General Availability Readme (Known … Continue reading Useful links

Error al importar la solución de integración entre Dynamics NAV 2017 y Dynamics 365

Hola a tod@s, Hoy me encontrado con el siguiente error durante la instalación de la solución administrada para la integración entre Dynamics 365 y Dynamics NAV 2017 The import has failed because component {92853f5b-24cc-e611-80fa-c4346bac3fa4} of type 20 is not declared in the solution file as a root component. To fix this, import again using the … Continue reading Error al importar la solución de integración entre Dynamics NAV 2017 y Dynamics 365

Microsoft Dynamics CRM 2015 update 1: bug en campos enteros con formato duración

Hola, Trabajando con un CRM 2015 update 1 (online), me he encontrado con un comportamiento inesperado en los campos de tipo número entero con formato duración. Como saben, estos campos si bien son numéricos, cuando se visualizan en un formulario, permiten seleccionar o introducir cantidades de duración en días, horas y minutos. Los valores se … Continue reading Microsoft Dynamics CRM 2015 update 1: bug en campos enteros con formato duración

Error al intentar conectar a CRM 2015 desde un reporte de SSRS FetchXML mediante Visual Studio 2012

Si al intentar actualizar un DataSet de un reporte de SQL Server Reporting Services para Microsoft Dynamics CRM basado en FetchXML se obtiene el siguiente mensaje de error:"The selected data extension MSCRMFETCH is not installed or cannot be loaded. Verify that the selected data extension is installed on the client for local reports and on … Continue reading Error al intentar conectar a CRM 2015 desde un reporte de SSRS FetchXML mediante Visual Studio 2012

Are your CRM plugins creating technical debt?

I couldn’t agree more with you Ben!

Hosk's Dynamic CRM Blog

The image above is from the article DEALING WITH TECHNICAL DEBT, which I recommend you read, right after reading this one 🙂

The common method of creating plugins in the CRM projects I have worked on, is putting all/most of the code directly in the plugin class, this creates code which is

  • Complex code
  • Hard to read
  • No code reuse
  • Difficult to debug
  • Writing unit tests is hard so most CRM developers don’t bother

This method of developing plugins creates technical debt to the CRM project instantly and pushes the code towards legacy status and creates spaghetti code

The motivation for writing this blog post is a most CRM projects don’t have enough classesabstractions in them and the code written is not adhering to good object orientated design principles.

The lack of design and structure in CRM plugins I believe is one of major reasons there is little code reuse…

View original post 1,754 more words