Enumeration fields or optionsets need to be handled well in a migration scenario. And it is easy to not have an option in a target system, which was a legacy option in your Source data set. One such example would be currency options. Currency abbreviations can easily be missed, incomplete, or need to be changed to better reflect the destination system. In this business case, we are working with an old database system and have now been tasked to create the contact information in HubSpot.

While migrating from CRM to CRM, or any other Source system to CRM, in an ETL, records will need to be associated with users. And since the Source and Target Systems are different, there may not be a guarantee that some users may still exist in the organization. And in such cases, such users become either unlicensed, or stub users. These type of users have restrictions when it comes to being set as an owner of records, and in this blog post, we will see how this can be handled efficiently.

In SSIS, the sensitive credentials have to be handled in a special way to ensure that they get preserved and decrypted while the packages run in an unattended way. There are a few means to do this, and in this blog post, we will discuss some popular ways this can be done.

With the recent news of SOAP basic authentication deprecation, it becomes imperative to start using the OAuth authentication for your SharePoint integration process. In response to this deprecation, we have recently added support for OAuth in the latest (v22.1) of our SharePoint toolkit, which offers a paralleled feature set as the SOAP service endpoint. It also includes some enhanced capabilities that were not possible using the SOAP service endpoint. This blog post will demonstrate the process involved in order to start using the OAuth authentication type in your integration.

Having a JSON response that needs to be properly parsed is a very common use case. This can be an advanced JSON structure like arrays, key-value pairs, etc. Our KingswaySoft JSON components can easily parse through them using the various settings and options available. However, there could be cases in which a JSON design is such that it could have records that need to be handled separately. In this blog post, we will discuss such a case.

If you have a large number of records, you need to read and the process is taking longer than anticipated you may benefit from using Salesforce’s Bulk API. Salesforce Bulk API benefits you when you have many records (Salesforce states data operations with 2000+ records make a good candidate) in the Salesforce system and these records are being read synchronously. Today we will look at the features in Salesforce Bulk API and how KingswaySoft components make Bulk jobs easier.

Audit logs take up a lot of space in your CRM/CE instance, and there are cases where you would want to have a way to archive the audit logs and have them removed from the system after archiving, to reclaim the space in an automatic manner. Using KingswaySoft, this can be easily achieved.

Sometimes we need to attach files with specific conditions to one email and send it. In this blog post, we will show how you can quickly do it by using our components.