Customers are crucial to the success of any business. When you build your business focusing primarily on giving the best experience to your customer, your business is going to bloom. Your profits are going to multiply each year. Dynamics 365 for customer service is one of the best ERP solutions that you can find in the world.  It will help in streamlining the processes in all the departments to make your business customer-friendly and customer biased. When customers know that you value their association, they are going to stay with you for a long time becoming your loyal customers.  People who never used this ERP solution may not know how to find what they want. Here is a topic that you should learn as it will be quite helpful to you in the long run. Data Integration project support two types of executions Manual and auto-refresh i.e. schedule-based refresh. For a manual refresh, we have to select the project and click on run. In this blog, we will learn how to create a schedule to run an Integration project at a specific date and/or time. First, go to Admin Center Go to the Data Integration -> Projects and click on the ellipses of the project to be scheduled and click on Schedule We will get two options a. Run Manually b. Run on specific day and/or time  Now let’s schedule the project, in this example we going to schedule the project every hour starting at 17-Aug-2019 to 30-Aug-2019, and it should run form 12 AM to 2 AM. After scheduling click on save We can schedule the project in another way also, to do this  go to the scheduling after selecting on the Integration project After clicking on the project following window will open and then click on the Scheduling and same scheduling window will appear. In this way we can create schedule-based refresh for the Integration project

Error handling is very important part of any integration project, it is also very important to fix the issue when it is recognized, so it is very important to take action to resolve it earliest. In the Integration project of CDS we can setup email alert option in following way. First go to Admin Center Go to Data Integration -> Select the project -> Go to Scheduling Following window will appear Tick the checkbox and specify the email address on which we wanted to receive the alerts and click on save. In this way we can set up the email alert notification for Integration progress in CDS.

Introduction This log error will help us to understand and fix an issue as quickly. There are three main phases in an SSIS ETL execution life-cycle to catch errors: When data is being extracted from source systems When data is being transformed When data is loaded to the target systems Customized Error Handling also avoids the failure of Package during Runtime. It allows the package to be executed successfully and the Errors can be checked later from the Customized Error Log Table which you create to know what problem exactly occurred. Our Scenario For demonstration purpose, we will consider a Units Integration Map for Integration of Units from SQL to Dynamics CRM. In this Blog, we will Create a Customized Error Log Table in SQL and Catch the Errors from SQL (Source Block) and Dynamics CRM (Destination block). The Map for Unit Integration is as follows: Customized Error Handling in SSIS Execute the following query and create a customized Error Log Table in SSIS: CREATE TABLE [dbo].[ErrorLog]( [ErrorID][uniqueidentifier] NOT NULL default newid() primary key, [Entity] [varchar](250) NULL, [Record_Id] [int] NULL, [RecordName] [varchar](250) NULL, [ErrorDescription] [varchar](500) NULL, [DateTime] [datetime] NULL ) ON [PRIMARY] The structure of Table is as follows: ErrorID Entity Record_Id Record Name ErrorDescription DateTime Primary Key of Error Log Table. (System Generated) Unit UnitId Unit Name  Error Message  Error Log Date Error Handling at OLEDB Source Block: Step 1: Add a Script Component to catch the Error Description, Error Log Date and Entity. Select Transformation and click on Ok. Step 2: Connect the Error Output (Red Arrow) from OLDEB Source to the Script Component. Select “Redirect row” for all columns in the Error and Truncation Columns to redirect Error Output to Script Component. Step 3: Configure the Script Component as following: In Input Columns section Select Error Code and Error Column. In Inputs and Outputs section Add following Columns Column Name Data Type Length ErrorDescription Unicode string [DT_WSTR] 500 ErrorLogDate database timestamp [DT_DBTIMESTAMP] —- Entity string [DT_STR] 50 In the Connection Managers Section add a new connection and select your SQL connection In the Script Section click on Edit Script. After a minute a New Editor Window will Open. Here you have to copy and paste the following Script inside the “public override void Input0_ProcessInputRow(Input0Buffer Row)” section. Code Snippet: try { Row.Entity = “Unit”; Row.ErrorDescription = this.ComponentMetaData.GetErrorDescription(Row.ErrorCode); Row.ErrorLogDate = DateTime.Now; //If an error occurred due to Check Constraint, the ErrorColumn would be 0, and that error affects the entire row. Hence there is no specific column for that error   if (Row.ErrorColumn == 0) { Row.ErrorDescription = “An error that affects the entire row”; }   //If an error occurred due to Data type, then errorcolumn name would be updated.   else { var componentMetaData130 = this.ComponentMetaData as IDTSComponentMetaData130; if (componentMetaData130 != null) { Row.ErrorDescription = componentMetaData130.GetIdentificationStringByID(Row.ErrorColumn).Replace (“Customer Target.Inputs[OLE DB Destination Input].Columns[“, “”).Replace(“]”, “”); } } }   catch (Exception ex) { Row.ErrorDescription = “Unable to get Error Column Name”; } Click on Save and then Close the Window. Step 4: Add a Data Conversion Block to avoid any Truncation Errors because of Data Type Conversion between NVarchar and Varchar Data Types of the Error Description Column. Select ErrorDecription Column and select Data Type as String. Click on OK. Step 5: Add an OLEDB destination block. Configure your OLEDB Connection Manager and Select the Error Log Table which you had created in SQL Server. In the Mapping section do the following Mappings and click on Ok. Error Handling at Dynamics Destination Block: Step 1: Perform the Steps 1 and 2 as specified above in Error Handling at OLEDB Source Block. Step 2: Configure the Script Component as following: In Input Columns section Select Error Code, Error Column and CrmErrorMessage. In Inputs and Outputs section Add following Columns Column Name Data Type Length ErrorLogDate database timestamp [DT_DBTIMESTAMP] —- Entity string [DT_STR] 50 In the Connection Managers Section add a new connection and select your CRM connection: In the Script Section click on Edit Script. You have to copy and paste the following Script inside the “public override void Input0_ProcessInputRow(Input0Buffer Row)” section. Code Snippet: Row.Entity = “Unit”; Row.ErrorLogDate = DateTime.Now;\ Click on Save and then Close the Window. Step 3: Add a Data Conversion Block to avoid any Truncation Errors because of Data Type Conversion between NVarchar and Varchar Data Types of the Error Description Column. Select CrmErrorMessage Column and select Data Type as String and length as 500 i.e. according to the length of columns SQL. Click on OK. Step 4: Add an OLEDB destination block. Configure your OLEDB Connection Manager and Select the Error Log Table which you had created in SQL Server. In the Mapping section do the following Mappings and click on Ok. Checking the Error Occurred during Integration You can see the Error rows passing through the Error Output and being logged in our Error Log Table. Open the Error Log Table to check the Errors Occurred. Now you can easily identify the errors occurred during Integration process from your Custom Error Log Table and solve them to have successful Integration results.  

Introduction This blog explains how to use “startswith” filter query in MS Flow. Use Case Using MS Flows to retrieve the bunch of students who’s mobile numbers begin with +91 and send them a text (using Twilio connector) regarding the Top Indian Universities. The “starts with” filter query in MS Flows allows to easily achieve this functionality. Steps to be Followed: We will use “Dynamics 365 – List records” Actions. Enter the Organization Name and select the entity. Filter Query: startswith(new_phonenumber,’+91′) “new_phonenumber” is the logical name of the field which stores the phone number of students. ‘+91’ is the value of phone number by which we want to filter the retrieved student list. Enter the above query in Filter Query: Run the flow to test.It will return all the students whose phone number starts with “+91”

Introduction This blog explains how to use “contains” filter query in MS Flow. Use Case Retrieve all the Accounts whose name contains ‘cloud’. Steps to be Followed: We will use “Dynamics 365 – List records” Actions. Enter the Organization Name and entity.Filter Query: contains(name,’cloud’) name is the logical name of the field which stores the account name. ‘cloud’ is the value of account name by which we want to filter the retrieved account list. Enter the above query in Filter Query: Run the flow to test.It will return all the account whose name contains “cloud’.

Microsoft has mandated TLS1.2 for Dynamics 364 v9.0, which is why we may face issue while connecting to the CRM online instance from visual studio for creating new report via fetch XML. This post will help developer to solve the connectivity issue for connecting with latest Dynamics 365 v9.0 using SQL Server Data Tools and FetchXml Authoring Extension. Issues: Not able to login Plugin registration tool (keeps popping up for Credentials)                     Not able to see custom entities in Plugin Registration tool Connection to CRM from Custom Web Application and Console fails Able to retrieve data in dataset in Report RDL but unable to preview           Root Cause: This issue occurs because of the latest update in the Microsoft TSL(Transport Layer Security) Protocol in SDK assemblies. Microsoft has allowed TSL connection 1.0 and 1.1 for the browsers or client to connect to the CRM org. The Microsoft TLS 1.0 implementation has no known security issues but because of the potential security vulnerabilities for future downgrade attacks and TSL vulnerabilities, Microsoft has discontinued the support for TLS 1.0 and 1.1 in Microsoft Office 365. Now Microsoft supports only TSL 1.2 or above. If you are connecting your org with the old version of plugin registration tool , then you may face this issue.   What is TSL ? Transport Layer Security (TLS) is a cryptographic protocol used to establish a secure communications channel between two systems. It is used to authenticate one or both systems, and protect the confidentiality and integrity of information that passes between systems.   HOW TO IDENTIFY: Use fiddler to check the your server request TSL Version. Install fiddler https://www.telerik.com/download/fiddler Go to Fiddler Setup -> Tools -> Options           Click on highlighted text after “Protocols” label and add ;tls1.2 text at the end and click “OK”:                               Run the report again. It should work as expected. This is how we can fix the connectivity issues between SSDT, Report Authoring Extension and Dynamics 365.

Today, I will show you the Environment Setup for PSA to F&O integration with CDS. Step 1: Create the environment Open the link https://admin.powerapps.com and click to create new environment Following pop-up window will appear and enter the details and click on Create Environment, so new environment will gets created   The environment will get created   Step 2: Create the connections To create the connection, open the link https://web.powerapps.com and go to the connection in newly created environment (In this case: DemoEnvironment) In the data section click on connections section and click on the “Create a connection” to create new connection Following screen will be visible, select the “Dynamics 365” connection. When clicked on the Dynamics 365 popup window will appear asking whether to create connection or not. Click on create and enter the credentials     And finally source connection gets created Now create the Destination connection In the connections search for “Dynamics 365 for Fin & Ops”, when clicked it will ask whether to create connection or not click on create and then enter the credentials and finally connection will be created     Once we created the Environment and connections now create Connection sets and create project   Go to https://admin.powerapps.com and open the Data Integration tab.   2. Click on the connection set section and click on the “New Connection Set” following popup window will appear and click on Create   Step3: Once Connection set gets created now let’s create the Project   Go to project section and click new project and following form will be visible and enter the Integration project name and select the ready made template available or create custom integration project. In this case we are selecting ready made template for account and click on next.   Select the connection set from the drop down select the connection set which we have created earlier: DemoConnectionSet and click on next Select organization and click next and finally click on create   So now we have created accounts integration project Hope the above helps!

Introduction: This blog explain the steps to lock the columns of Editable Grid in D365 CE UCI. Scenario: Lock the View columns of Editable Grid in D365 CE. Steps: Below are steps to be performed for locking fields of Editable Grid in View Create Business Rule to lock the field. 2. Mark the Scope of Business rule at Entity level 3. Editable Grid with locked columns in View   Note: Fields are locked for all Views and subgrid.  Conclusion: This blogs helps developers to lock columns of View and Subgrid in Editable Grid of D365 CE.

Key Technologies: Microsoft Dynamics CRM Online, Exchange Online, Outlook 2013 Introduction 1. Server Side Synchronization(SSS) is setup for Email processing between Microsoft CRM Online and Exchange Online within Office 365. 2. Appointments, Contacts and Tasks in CRM can also be synchronized using SSS. Pre-Requisites An Office 365 user must have the following licenses to setup SSS in CRM: 1. Microsoft Dynamics CRM Online. 2. Office 365 Enterprise E1 / E3 / E4 license. 3. Setup OWA once an Office 365 Enterprise license is assigned. Enable Server Side Sync for a Mailbox 1. Before we enable SSS for a Mailbox. We need to turn SSS on at Organization level as shown below: 2. Then, select the Mailbox you want to enable Server Side Sync for under Mailbox option in Email Configuration area. 2.1. To do so, you need to select the Mailbox and “Approve Email” (shown below) for the same if Process emails only for approved users was check marked as in the System Settings as shown above. 2.2. Then choose, Approve Email. 2.3. Once the mailbox is Approved, choose to Test & Enable Mailbox for the approved Mailbox. 2.4. Once, all the tests are successful, you should see the same as shown below: You should also receive an Email in your Outlook that your Mailbox was successfully able to send out an Email. Setting Personal Options for Tracking Email in CRM for Outlook 1. We can set Personal Options for tracking email in our CRM. Click the gear icon on the top right corner of your CRM interface. 2. Navigate to the Email tab. Where there will be an option Select the email messages to track in Microsoft Dynamics CRM Under the dropdown menu labelled Track, there are 4 options to select the tracking method used in CRM. They are:   1. All email messages – Tracks all email messages. 2. Email messages in response to CRM mail – Track email messages only if the person has a record in Microsoft Dynamics CRM. 3. Email messages from CRM Leads, Contacts and Accounts – Track email messages only if they originate from someone with a Microsoft Dynamics CRM Lead, contact or Account record. 4. Email messages from Microsoft Dynamics CRM records that are email enabled – Tracks email messages from all record types (including custom record types) that contain an email address field. Now, you are configured for using Server Side Sync for Dynamics CRM with Outlook. Hope this post was helpful !

Key Technologies: CRM Online, Scribe Insight Note: This article assumes understanding of CRM Online entities and relationships. Knowledge of Scribe insight tool for data integration. For more information on Scribe Insight refer https://www.cloudfronts.com/scribe-integrationsmigrations/ Connections can be used to define the relation between the two entities. You can have an account related to any contacts. With the help of connection you can define that one of the contact is actually the employee in the company and another an employer. 1. Before connections, you should have connection roles and association between the roles defined. 2. Connection Roles A role should have a role category. Consider, a role ‘Client’ which is part of ‘Business’ category, ‘Sibling’ which is under ‘Family’ category. 3. Connection Role Association After defining a role, we should associate different roles. This entity stores guid of the main role and the associated role. Role ‘Client’ can have other roles associated with it. See below example. 4. Select record type ‘All’ to avoid restriction on any entity. 5. Connections Map the following fields for connections between records of different entities. • Record1id • Record2id • Record1objectTypecode (ex: account) • Record2objectTypecode (ex: contact) • Record1roleid (ex: Client) • Record2roleid (ex: Employee) • Description • Status • Ownerid Below is a sample of a contact with role ‘Client’ connected to another with role ‘Attorney’.