As per Microsoft Docs “The core SSDT functionality to create database projects has remained integral to Visual Studio. The extensions for Analysis Services, Integration Services, and Reporting Services projects are not available for Visual Studio 2022 at this time.”
Changes in SSDT for Visual Studio 2022
Continue reading “Extensions for SSAS, SSIS and SSRS are not available for VS 2022 at this time! (Feb2022)”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.
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 provides a basic idea about XperiDo as this is the start for Smart Flows. Also, most of the concepts are still same and most parts of the architecture is similar in the Smart Flows.
XperiDo is a document generation solution available as an online service and as an on-premise solution. It’s a fully compatible document generation platform for Dynamics CRM giving various of functions to generate different types of documents using Dynamics CRM data. XperiDo supports building complex document generation activities, accessing dynamics CRM schema in a user friendly environment.
Continue reading “Road to Smart Flows (Part 1) : Document Generation with XperiDo”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:
Visual Studio 2019 is now available for developers and dynamics 365 CE version 9.x Software Development Kit (SDK) too. However Dynamics 365 Developer Toolkit only supports for Visual Studio 2012, 2013, 2015 and it uses Dynamics 365 CE SDK 8.x assemblies and tools.
This article to make Dynamics 365 Developer Toolkit workable for VS 2019 and to prevent some common issues when setting up Plugin Library project to work with Dynamics 365 CE version 9.x core assemblies.
Special thanks to Sucheet Chavan for sharing useful information to the article.
Setting up Developer Toolkit for VS2019
Although Dynamics 365 Developer Toolkit doesn’t support after Visual Studio 2015, developers perform few workarounds to use the extension with VS2017. Following article is still valid for VS2019 with one change to the extension.
Continue reading “Setting up Developer Toolkit for VS2019 with Core Assemblies(9.0)”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.
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 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.
Continue reading “SMS Integration with Dynamics 365 + Microsoft Flow + Nexmo”
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.
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);
});
};
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 in Dynamics CRM – By Cobalt) explains the problem and it describes a solution for the problem for previous versions.
The solution in 9.0 :
The scenario is to query all the accounts which have no cases under in each account. Following query returns the expected results using advanced find without installing any third party components.
“Does Not Contain Data” Clause
The above advanced find query doesn’t allow users to select any more attributes from the cases as it looks for accounts which have no cases. It’s very logical to restrict the user to filter values from the cases when “Does Not Contain Data” option is selected. Continue reading “Advanced Find – “NOT IN” Query is Supported in v9.0″
Promote to Admin feature allows any user in Dynamics 365 to make himself an Administrator in the system if the user is authorized from the Admin Center.
Usually when you create an online instance of Sales/Customer Service by yourself but you won’t be able to see most of the admin settings.
If any user has been granted the admin priveledges from the admin center, but that user has no system admin roles assigned (under manage roles) in Dynamics 365, then this feature is useful for getting the System Administrator user role back.
Promote to admin is one of the options that you can use in order to gain the admin priveledges. It will add “System Administrator” user role to the user.
C R M F o r t r e s s | Indika's Dynamics 365 CE Blog 