Clinton Dmello Blogs

Introduction: In this blog we will discuss about the error(“Verify the state of the solution in CRM”) i faced while using the Package Deployer tool for Dynamics 365 Customer Engagement.    Solution: Step 1: In the ImportConfig.xml file we name we give the name of the solutionpackagefilename Then we build the project and copy the folder containing the solution and the Package.dll file created. Then we run the Package Deployer application and connect to the  organization the below screen shows the suction is successfully unpacked  But when the solution is imported the error shown is as follows In the Log file we can see that the import was not successful due to the missing dependencies Once the missing dependencies are added the solution is successfully imported using the package deployer. The depending components can also been seen if the solution is imported manually. Hope this small tip Helped!

Introduction: In this blog we will demonstrate how to call a workflow directly from a button without any custom JavaScript code. Implementation: Step 1:  Create the required workflow. In this example i have created a  simple workflow on the opportunity and remember to select the  “As an on-demand process” option. Step 2:  After the workflow is created store the GUID of the workflow. To get the GUID select the workflow and copy down the ID from the URL as shown in the below image. Step 3:  Now create the custom button on Opportunity entity using Ribbon Workbench. Step 4:  Create a new Command and click on “Add Action>JavaScript Action” as shown in the image. Step 5:  In the library option write the following “ /_static/_forms/form.js ” and in the Function Name field “ Mscrm.FormAction.launchOnDemandWorkflowForm “. Then as shown in the above image add two Parameters as follows: Crm Parameter = PrimaryEntityTyp...

Introduction:  In this blog lets look at how to call an unbound action using Xrm.WebApi which provides properties and methods to use Web API to create and manage records and execute Web API actions and functions in Customer Engagement Implementation The syntax for execute method is as follows: Step 1:  Create an unbound action. Here we created an action “new_ActionTest” and activated it. In the action steps we have written a step to create a new contact with the name “Jessy David”. Here in our action we an Integer parameter. Any steps can be added as required. Step 2:  Below shown code is function used to call the unbound action. Here “boundParameter” parameter is an optional String parameter, we have specified it as null as our action is not bound to any entity. “operationName” is an optional String parameter which is the name of the action.“operationType” is an optional Number parameter which indicates the type of operation we are execut...

Introduction In this blog we will demonstrate how to create and associate records using Xrm.WebApi which provides methods to use Web Api to create and manage records. Implementation Step 1: The syntax to create a new entity record is as follows: Here entityLogicalName(string) and data(object) parameters are required where,  "data" is the JSON object defining the attributes and values for the new record. Step 2: In this example we will create a sample account record along with a primary contact for that account, associate an opportunity to the account and create task and notes for the opportunity all in a single operation. This type of process if called deep insert. The code for the same is as shown below: Screenshots: 1. A New Account is created with the name “CRAYONS LTD” and in the primary contact file the primary contact is set with the name Clinton Dmello as set in the code. 2. Also an opportunity is associated to the account as shown below in the associate...

Introduction In this blog we will be discussing about the Business Rule validation issue in  Editable grids caused when the fields are not present in the views. Scenario In our demonstration we will take the example of a contact form and design a business rule to lock the email field if the Job Title field is blank.  Implementation Step 1 : First we enable editable gird for the contact entity as shown in the image below Step 2 :  Then we create a business rule for the contact form  to lock the Email field if the Job Title field is blank. The Business Rule is shown below Step 3:  Now in the editable grid we can see that the Email field is locked as the Job Title is blank. The field is unlocked once the job title is entered Step 4: Now we edit the criteria of the Business Rule and add a new condition to also check if the Description field contains data  as shown in the image below. ...

Introduction: In this blog we will see how audit logs in D365 can be fetched that can be used for reporting purposes. Auditing helps to track changes made to the data in D365. The System Auditing entity cannot be accessed. Actionable Audit is a App by Microsoft Labs in which the required audit logs can be stored in the actionable audit entity which can be used later on by fetching the records of that entity. This audit log can be helpful to create Dashboards in Power BI, create reports etc to get meaningful information from the data. Implementation: Step 1: First we enable the auditing for the organization(globally) in Settings > Auditing Step 2: We then enable auditing for the required entities and fields. Step 3: Download the Actionable audit app from the AppSource  Step 4: After accepting the terms and condition is done, it will take some time to install the solution as shown in the notification below.  Step 5: In the plug-in registration tool we can see the assembl...

Introduction: After switching to Dynamics 365 Customer Engagement V 9.0 many of us are getting an error while trying to connect with the system using code.  Here we will see how to connect to Dynamics 365 using a Console app in v8.2 and when the same code is used to connect to version 9 we get an error. We will also discuss about how to resolve the issue. Implementation: Step 1: The code shown below is used to connect to Dynamics 365 version 8.2 using Console App Below is the ConnectToCRM function Step 2: When we run the above code, we get the following output Step 3: Now we change the credentials and try connecting to Dynamics 365 V9 with the same code we get the following error Step 4: To solve this issue there are two ways in the first method, set the Target framework to “.NET Framework 4.6.2 or above”. Step 5: After changing the target version build the solution again and run the app and the connection to Dynamics 365 ...