Release: SSIS Integration Toolkit v3.1 for Salesforce.com

08 August 2013
KingswaySoft Announcement

Today we are very excited to announce the release of SSIS Integration Toolkit v3.1 for Salesforce.com, which includes some important new enhancements and bug fixes.


Migrating Business Units using SSIS Integration Toolkit for Microsoft Dynamics CRM

25 June 2013
Daniel Cai

In this blog post, we will try to discuss the scenario when you need to replicate or migrate business units from one CRM organization to another one. While walking you through the development process, we also try to illustrate some implementation patterns that you might find useful.


Writing Script Component or Script Task using CRM Connection Manager

24 June 2013
Daniel Cai

In this blog post, we will walk you through how to write SSIS script component or script task by utilizing CRM connection manager in your SSIS package which provides full SDK capability that allows talking to CRM server.


Limitations with CRM FetchXML

18 June 2013
Daniel Cai

This blog post discusses some limitations with CRM FetchXML query.


Release: SSIS Integration Toolkit v3.1 for Microsoft Dynamics CRM

12 June 2013
Daniel Cai

Today we are pleased to announce the release of SSIS Integration Toolkit v3.1 for Microsoft Dynamics CRM. The new release includes some important enhancements and bug fixes.


Release: SSIS Integration Toolkit v3.0 for Salesforce

12 June 2013
KingswaySoft Announcement

Today we are very excited to announce the release of SSIS Integration Toolkit v3.0 for Salesforce, which includes some important new features.


SSIS 2012 Error - 'Salt' attribute for PassWord is missing in the project manifest

31 May 2013
Daniel Cai

We have received a couple of reporting of the error mentioned in the title for SSIS Integration Toolkit for Dynamics CRM. We have done some preliminary investigation and we believe this is a SQL Server bug. Read for more information about the error and workaround solution.


CRM Connection Error: Value cannot be null. Parameter name: authenticationCredentials.SupportingCredentials

16 May 2013
Daniel Cai

We recently received a couple of reporting of "Value cannot be null. Parameter name: authenticationCredentials.SupportingCredentials" error. Read more for solution to the problem.

comments powered by Disqus