Tag: CRM Online

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

This is one of two 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:

This post explains the main steps when moving to Smart Flows from XperiDo. Also, this discusses some practical issues, important information to understand during the migration.

Step 1: Get access to an Smart Flow environment/server

Continue reading “Road to Smart Flows (Part 2) : XperiDo to Smart Flows Migration”

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:

  1. Open the CRM solution and navigate to Entities->Process->Fields.
  2. Find the fields, stageid and traversepath under the fields.
  3. Delete both the fields.
Continue reading “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”

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 challenge and now Microsoft Flow can be used to create workflows between different apps.

Nexmo https://www.nexmo.com

Nexmo provides various cloud-based APIs such as SMS, Voice, User Authentication, User Identity APIs. Nexmo says SMS API allows you to send and receive text messages to users around the globe through simple RESTful APIs and having following features.

  • Programmatically send and receive a high volume of SMS anywhere in the world.
  • Build apps that scale with the web technologies that you are already using.
  • Send SMS with low latency and high delivery rates.
  • Receive SMS for free using SMS-enabled local numbers in countries around the world.
  • Only pay for the usage.

Continue reading “SMS Integration with Dynamics 365 + Microsoft Flow + Nexmo”

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 records and reactivate them back will resolve the issue.

 

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 and statuscode
var data = {
“statecode”: statecode,
“statuscode”: statuscode
};
// WebApi call
Xrm.WebApi.updateRecord(entityLogicalName, id, data).then(function  success(result) {
executionContext.getFormContext().data.refresh(true);
}, function (error) {
executionContext.getFormContext().data.refresh(true);
});
};

“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 for Views.

The Problem:

One Account can have many Cases. Dynamics CRM can display all the “Accounts which has Cases” in Advanced Find\Views. But, Dynamics CRM cannot display all the “Accounts which has no Cases” using Advanced Find\Views.

query1

Solution:

Use “Does Not Contain Data” clause for filtering 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 advanced find.

1

Export all the resolved case records using Excel Online. 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 this issue to be raised and there can be many other scenarios to see this same issue.

Issue: After some time I wanted to add few more plug-ins to the same assembly, targeting some custom entity events and I updated the same registered plugin assembly with the newly build assembly. However, after adding steps to the relevant plugins and after triggering relevant events I got some errors from all the plugins I newly added. I checked the very first plugin events I registered in the same assembly and those functioned perfectly.

Error Message: All the errors showed the same error message “The plug-in type could not be found in the plug-in assembly:” in them.

Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: System.ArgumentNullException: Value cannot be null.
 Parameter name: TrackingId: 87e5f936-7499-4bc1-b649-f78fd4739016, Depth: 1, Message: SandboxAppDomainHelper.Execute: The plug-in type could not be found in the plug-in assembly:  Continue reading "ISSUE: The plug-in type could not be found in the plug-in assembly"