The most common use case to export Dynamics 365 or Common Data Service data to an external database/datastore is to have more control over the data (without going through API route) with the ability to run analytics such as Power BI Reporting, Machine Learning, Data Warehousing, Integration, etc. For analytics, we can also use our … Continue reading “Replicate / Export Dynamics 365 (CDS) data – different options”
KingswaySoft provides 3 components specific to Azure Blog Storage Azure Blob Connection Manager Azure Blob Storage Source Azure Blob Storage Destination Check other blog posts on SSIS https://nishantrana.me/2020/10/16/ssis-kingswaysoft-and-dynamics-365/ Let us take a simple example where we are extracting \ reading contact data from Dynamics 365 \ CDS and saving it as a text file in … Continue reading “Using KingswaySoft Azure Blob Storage component with Dynamics 365”
For complex data migration requirements, usually we’d be using 3rd party tools like KingswaySoft or Scribe, or Informatica as they already have components (connection, transformation, source, destination etc.) built for Dynamics 365 instead of building our own. Check other posts on data migration https://nishantrana.me/2020/10/16/ssis-kingswaysoft-and-dynamics-365/ https://nishantrana.me/2020/05/19/data-migration-in-dynamics-365-key-considerations/ For some simple / basic requirements instead of using 3rd … Continue reading “Connect to Dynamics 365 through Script Component – SSIS”
In our previous post, we created the SSIS Catalog (SSISDB) in Azure and deployed the SSIS package using SSDT. Supported version for SSDT – SQL Server Data Tools to deploy SSIS package to Azure. For Visual Studio 2017, version 15.3 or later. For Visual Studio 2015, version 17.2 or later. In this post, we’d use … Continue reading “Using SQL Server Management Studio to deploy and run SSIS package in Azure Data Factory”
In the previous post, we saw how to deploy and run SSIS packages on the cloud. Here we take it one step further and will deploy and run the SSIS packages that use KingswaySoft’ s SSIS Integration Toolkit components. Here we will need an Azure Subscription, where we will host the SSISDB, followed by provisioning … Continue reading “Deploy and run SSIS Integration Toolkit for Dynamics 365 on Azure Data Lake (KingswaySoft)”
Before the SSIS package can be deployed to Azure Data Factory we need to provision Azure-SQL Server Integration Service (SSIS) runtime (IR) in Azure Data Factory. In the previous posts, we had created an Azure data factory instance had used Azure SQL Database as the source. Within Azure Data Factory in the Let’s get started … Continue reading “Deploy and run SSIS package in Azure Data Factory”
At times we need to generate sample data for our entities in Dynamics 365 for various reasons, performance testing is one of them. Data Spawner component which is part of KingswaySoft’s SSIS Productivity Pack provides us the most efficient way of doing so. Download the component here – https://www.kingswaysoft.com/solutions/ssis-data-generation-anonymization-components/data-spawner-component Let us generate the sample data … Continue reading “Using Data Spawner component (SSIS) to generate sample data in Dynamics 365”
Let us take a very simple example to understand how to migrate the multi-select option set in Dynamics 365. Few points to consider before we use Multi-select option set https://nishantrana.me/2018/04/27/limitations-of-multi-select-option-sets-in-dynamics-365-ce/ Here we will take excel as our source. Create a new SSIS package, add the Excel Source component and Dynamics CRM Destination component in the … Continue reading “Migration of multi-select option sets in Dynamics 365 – SSIS (KingswaySoft)”
Error: The “Derived Column” failed because truncation occurred, and the truncation row disposition on “Derived Column.Outputs[Derived Column Output].Columns[FilePath]” specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
We might get the error while using Derived Column in our SSIS Package To fix it right click the Derived Column component and select Show Advanced Editor .. Go to Input and Output Properties tab, expand Derived Column Output and select the field and update the length in the properties window. Hope this helps..
Something went wrong. Please refresh the page and/or try again.
Author: Nishant Rana
I love working in and sharing everything about Microsoft.NET technology ! View all posts by Nishant Rana