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 … Continue reading Workflow must be in Published state

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 … Continue reading Status Change using WebApi

“Not In” \ “Does Not Have” Query in Dynamics CRM – By Cobalt

In Dynamics CRM Advanced Find, Querries can be built for various conditions \ for various filter criteria. But, "Not In" type queries cannot be built and it doesn't work with OOTB querying. Cobalt has a cool feature which allows users to make "Not In" \ "Does Not Have" types of queries in Advanced Find and … Continue reading “Not In” \ “Does Not Have” Query in Dynamics CRM – By Cobalt

Updating Resolved Cases in Dynamics 365

Some Dynamics 365/CRM record updates need specific workarounds. Due to various reasons such as adding new fields to case entity, option set changes, migrating data to some other environments etc... developers need to modify the case records including resolved cases. This post is to explain a workaround for updating and migrating Resolved Case records. Get resolved cases using views or … Continue reading Updating Resolved Cases in Dynamics 365

ISSUE: The plug-in type could not be found in the plug-in assembly

I registered one plugin assembly with two plugins written targeted to contact entity and registered in one of Dynamics CRM 2015 Online instances. It worked properly after adding steps into it. Here I am discussing the issue raised, an observation was done and the solution to the issue. But this only on a scenario for … Continue reading ISSUE: The plug-in type could not be found in the plug-in assembly