For Freshers, starting to learn TCI might not know how to create NAV connector. NAV is On-premise and since its On-premise its Agent is need to be installed. So, in this blog you will get to know how to create NAV connector as well how to install the agent on its server. Firstly we will see how to install the Agent on NAV server. For that you need to ON the Virtual Machine from the Azure Portal, here our Virtual Machine’s name is NAV2018 or you can contact IT Admin to do the same for you. After your VM is ON you now need to connect to the RDP. Download the RDP file. Run the downloaded file and Click on Connect. Enter Username and Password and click OK. Now you are connected to NAV 2018 server Now login to https://app.scribesoft.com and from More select Agents. Click on the + button to add agent on NAV server. Click on Install On-Premise Agent Copy the Agent Key for further use. Click on Run Tick the check box and click Next Click Next. Paste the Agent Key which you earlier copied and Click on Next Check the location and click on next. Now click on Install Agent Now your Agent is Installed and you can now create the connector. Click on the + button and add new connector. Now you can fill up the necessary data such as OData URL, User and Password, Company Name which you will get from NAV ( you can check this by searching USERS). Also choose the agent as NAV Agent. Test the Connector and Save the Connector.

In this Blog a Request/Reply Map is created to verify the Event based map which can send and receive data. This can be done a number of ways but Postman is more commonly used utility that can be used for this purpose. Login to app.scribesoft.com and select the Organization as CloudFronts Technologies LLP. To Create a new Solution click on the + Button and Select Integration Event Now Rename the Solution and in the Maps section, click on the three ellipsis and select Create Request/Reply Map to create a new Map. Now Rename the Map and Add Connector. You can Create a new Connector or select any connector which is already created. Create a Map as shown below. In Wait for Request Block, click on Request and add field names as desired and Click on Validate and then OK. In Create Block, in General Tab and add the entity name in which you want to integrate. In Fields Tab, map the important fields and click on OK. In Build Reply Block, in the Fields tab drag and drop the fields from Results section to the Target Connection side and the click OK. Once the Map is created then Click on Apply and OK. Again open the map and copy the Endpoint URL. Now in Postman click on + icon and Add a request. Select POST and paste the Endpoint URL, then in Authentication tab select No Auth. In the Headers tab, enter the Key and the value as shown In the Body tab, select raw and select JSON, then type the JSON Format and enter the field and value as desired. Click on Send. You will get this as result in the Body section. In Tibco, in the execution history you can see the process is completed successfully. In CRM, you can now see the Record is created.

Sometimes we may feel the need to copy our data from one Microsoft Dynamics 365 CRM environment into another for scenarios such as moving data from UAT environment to production, copying data from Parent organization to Child, etc. This can be easily achieved by leveraging Tibco Cloud Integration’s simple and no code approach. Following is the method in which we can integrate our data Go to app.scribesoft.com and from the dashboard create a new integration app. Inside the app dashboard click on the Hamburger style button and then click on Create integration Map option In the page that opens up we can name our map as desired. Since I am going to integrate account entity in this tutorial I have named it as account integration. Now we have to add a source connection from which data will be extracted, here we can use existing connectors or create a new connector. After clicking the Ok button the metadata for source connector will load, in the meanwhile we can add Destination connector as well. We have to wait a while until the metadata of both source as well as destination gets loaded. After the connectors get loaded we have to drag the Query block from the source connector to the map designer as we want to Query and get the required entities first. Double click on the Query block and from the entity drop down you can select any entity you want to copy from source to destination, for this tutorial I am selecting Account entity. From the filter tab you can choose to filter records from the entity based on the fields. After adding filters, in order to check if correct data is being pulled from source along with the filters applied click on the Preview Tab and verify the values of the fields of the entity. Validate and click on Ok button. Now since there may be multiple records, for each record in source we have to create a record in the destination for doing this we use For Each loop from the Controls section. Since for each record we found in source we have to create a record in destination we will insert the Create block from destination connector in between the For loop. Now we will double click and open the Create block and select Account in the Destination Connector’s Entity. In the fields tab we will map all the necessary fields required to create an Account in CRM and then click on the OK button. If some important field isn’t mapped correctly it will throw an error during validation. Our map is now ready without any errors we will click on the Apply button and save the map and proceed for debugging. Debugging is important as it helps us to understand the flow of Data and if in case of any errors they can be tracked easily, In the Debug mode click on Start. Click on Next to see step by step execution of the map, and continue to finish running the map. After execution is complete the following window will be shown If you check the destination CRM now you will find the new record has been reflected from source. This was it, in few steps we copied Data from one CRM system to another. Thank you for reading my blog, hope it helped !!

Introduction: Use the Update Block to update existing records in the source or target datastore. While integrating with Microsoft Dynamics NAV as a destination use the Update Merge Block to perform the Update Operation in Microsoft Dynamics NAV. The Update Merge block can configured as follows. General Tab Following Options are available under the General Tab. Change the Block Label Add Description Set Batch Processing Options Select the entity to use for this Operation. Matching Criteria Tab Following Options are available under the Matching Tab. Specify one or more fields in your source and target data to select records for this operation. Fields Tab Following Options are available under the Fields Tab. Map the required fields from your source to destination directly or based on some formulae. Note: The following fields must Hardcoded Error Handling Tab Following Options are available under the Error Handling Tab. When an operation fails — If the record cannot be updated, an error is logged. If no matches are found — If the record being processed does not match the criteria in the Matching Criteria Tab, it is not updated, and an error is logged. Errors and Warnings Tab Following Options are available under the Errors And Warnings Tab. Various Errors available are displayed. Once you have corrected the errors click on Validate button to update the Errors and Warnings Tab.

Introduction: Establishing a connection is an important step before developing a solution for Integration. While integrating with Microsoft Dynamics NAV as a source/destination a Connection is needed which can be established as follows. Step 1: Click on “More” tab and choose Connections. Step 2: Click on “Addition” Symbol to add a Connection. Step 3: Install On-Prem Agent on Nav server. Refer to the link below. https://help.scribesoft.com/scribe/en/index.htm#sol/agent/agentinstall.htm?Highlight=On%20prem%20agent Step 4: Add the details as follows. Connector Type: Microsoft Dynamics 365 Business Central/NAV. Name: Give a name for your connection. OData Service URL: Get the required Odata URL from NAV. Note: The URL should end with “Odata” at end. No additional forward slash must be added at the end of the URL which might result in errors. http://ftl-nav-dev:7048/FTL-DEVInstance/OData User: Find it after the date as follows. Password: Password for NAV Company Name: Find it before the date as follows. Agent: Select the On-Prem Agent which you had installed.

Consider migrating the data from Microsoft dynamics CRM online to Microsoft dynamics GP. Our goal is after the data migration is completed successfully, we want the result of the data migration (successful/failure) to go back to the source system. Steps: Scenario: 1st block: We query the source account entity 2nd block: We try to update/insert the target customer entity 3rd block: We update the source account entity, based on the result of the 2nd block (success/ failure) 4th block: We also update the target customer block based on the result of the 2nd block (success/ failure) In the target block (Update/Insert Customer), uncheck the error handling checkbox [Note: Error handling checkbox, is used to check if there are any fatal errors in the executions] After the data is inserted, we can have an update block for the source entity(Update account) that will write back the result (whether the data is successfully migrated or not) to the source system. In this example, GP2015_CustomerUpdateInsert is for inserting the data in the target system. As we can see in field’s column, we can capture information about the previous block by the highlighted fields, which can then be stored in the source system for tracking if the data went through.