Road to Smart Flows (Part 2) : XperiDo to Smart Flows Migration

This is a series of connected posts to introduce document generation features with Xpertdoc Smart Flows, explaining the important steps and issues faced during XperiDo to Smart Flows migration. Connected Posts: Road to Smart Flows (Part 1) : Document Generation with XperiDoRoad to Smart Flows (Part 2) : XperiDo to Smart Flows Migration Road to …

Road to Smart Flows (Part 1) : Document Generation with XperiDo

This is a series of connected posts to introduce document generation features with Xpertdoc Smart Flows, explaining the important steps and issues faced during XperiDo to Smart Flows migration. Connected Posts: Road to Smart Flows (Part 1) : Document Generation with XperiDoRoad to Smart Flows (Part 2) : XperiDo to Smart Flows Migration Road to …

Dynamics 365 CE Issue-Fixed: The entity relationship role of the referencing entity is required when creating a new one-to-many entity relationship vr_processstage_workflow

The post is about fixing the import issue, "The entity relationship role of the referencing entity is required when creating a new one-to-many entity relationship vr_processstage_workflow". The problem is mainly with two deprecated fields in Process entity in this scenario. However there are few similar incidents/scenarios reported and seeking solutions in the forums. The Fix: …

SMS Integration with Dynamics 365 + Microsoft Flow + Nexmo

Microsoft Power Platform brings a great set of tools to customize, extend capabilities of most of the favorite apps and create new apps online. Power BI, Power Apps, and Flow are the three pillars of Power Platform. Microsoft Flow https://flow.microsoft.com In the modern world, so many applications from different technologies exist and integrating them was a …

Workflow must be in Published state

The above error message is displayed in Dynamics 365 and most of the developers\users will look around workflows as the error says "Workflow must be in Published state." E.g. Creating a case throws the above error with the following details. [Microsoft.Crm.Service.GlobalSlaPlugin: Microsoft.Crm.Service.GlobalSlaPlugin.SlaPostCreatePlugin] [ebd908b4-2c74-e811-a95d-000d3ae0bc37: ObjectModel Implementation] The issue is with SLA records associated with Case. Deactivating SLA …

Status Change using WebApi

In Dynamics 365, OOTB status field value can be changed in many different ways. Following WebApi can be used to update the Status (statecode + statuscode) as follows. changeStatus = function (executionContext, entityLogicalName, recordId, statecode, statuscode) { // Remove brackets from the GUID if there's any var id = recordId.replace("{", "").replace("}", ""); // Set statecode …

Advanced Find – “NOT IN” Query is Supported in v9.0

Dynamics 365 9.0 supports "Not In" \ "Does Not Have" type of queries as an OOTB feature in Advanced Find. In previous versions of Dynamics 365 had no this feature but there were some custom solutions to facilitate this problem. The problem in previous versions :  This post (“Not In” \ “Does Not Have” Query …

Dynamics 365 – Developer Toolkit & Extensions for VS2017

Microsoft Dynamics 365 Developer Toolkit and Dynamics CRM & 365 Developer Extensions are great Dynamics 365 development accelerators available in the Visual Studio Marketplace. Still, these tools are not compatible with Visual Studio 2017, which is the latest release of VS. This is a workaround that you can make use of these tools with Visual …