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.

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.

In this blog, we are trying to get the metadata information from Dynamics 365 CRM API and save the entities and attributes in different tables. This is useful in many use cases where you wish to get a list of all the present entities and their corresponding metadata as a part of your integration - especially for further parameterization plans.