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.

There are many reasons you might need to send retries on failed HTTP-based service requests, particularly when you are working with API integration in an ETL process. Now, a simple retry can easily be done in the HTTP Connection Manager using its built-in Retry on Intermittent Errors option. In addition, there might be cases in which you would want to implement a more customized retry on additional HTTP errors to facilitate a more resilient integration process. In this blog post, we will see how KingswaySoft can help in both scenarios.

It is not unusual to run into a business requirement that you need to extract Dynamics 365 metadata during your ETL process. We used to believe that this is not a general requirement until we have recently announced our DES deprecation replacement solution, in which it is important to have a way to retrieve the list of Option Set values along with their label values in the system since Dynamics Entity Changes feature only returns integer values for those option set/picklist options. In this blog post, we will discuss this scenario and how to work with our DES deprecation replacement solution.

When working with Dynamics 365 online, your integration performance is subject to what is allowed by the server infrastructure managed by Microsoft. In particular, Microsoft has a throttling strategy in place to prevent exhaustive resource usage on the server-side from each individual tenant. This is for the good reason of making sure that the servers operate in a healthy environment, so that it does not degrade the overall performance of all other tenants in the same server group, while one tenant is performing a high-paced data load. However, this can create challenges when your data load has to be completed in a particular time window, in which case you might have exhausted all of your options to speed up the data load performance. In this blog post, we will discuss a new feature that can be used to overcome this limitation and boost data load speed.

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.