As an ETL Developer, you may have use cases where you would need to process tabular data in order to produce an XML/JSON file to be saved in a cloud location. Usually, this is done by first merging and creating an XML file in a local or network path and then, on a regular basis, moving it to the cloud storage. However, for users who are running their SSIS packages on the cloud via ADF and who do not wish to use local storage, this could be a roadblock. In this blog post, we will discuss a technique that facilitates direct file writing using KingswaySoft SSIS Productivity Pack components.

Custom access tokens are commonly used to obtain authorization tokens. Sometimes, they process requires using one of the parsing and extraction strategies. In this blog post we will illustrate some advanced use cases for this feature when using the HTTP connection manager offered in our SSIS Productivity Pack product.

The components we developed at KingswaySoft generally discover metadata automatically whenever possible - That is, our software retrieves metadata information made available by the API itself in order to properly populate our ETL components. In most cases, the metadata in our components is generally accurate, provided the target system has a reliable metadata API. This includes services like Dataverse/Dynamics 365 CE, Salesforce, SharePoint, etc. Accurate metadata is vital for data integrity in ETL processes. However, there are occasional cases where some ETL metadata fine-tuning may be necessary due to unique situations. For instance, you might encounter cases where a text field contains more data than what is indicated by its metadata, potentially causing the source extraction to fail. In such instances, manual editing of the metadata will be required in order for the ETL process to work. In this blog post, we will show you how such changes can be made properly for your ETL components.

Discover how to handle unique client cases that require both authentication and payload data sent in the body using the x-www-form-urlencoded format. Set up authentication in Postman, configure the SSIS data flow, and utilize the XML Source component for parsing out data efficiently. In this blog post, we'll show you step-by-step how to achieve this seamlessly using KingswaySoft's SSIS Productivity Pack.

KingswaySoft’s Premium Excel Destination component not only allows you to write values to an Excel file but also supports formulas. By using formulas in your Excel file, it can open up your data flows to many more possibilities. In this blog post, we will demonstrate one example of using formulas to create hyperlinks in an Excel file.

OAuth offers clear advantages over basic authentication, establishing it as the superior choice for data integration projects that involve processing or consuming your Dynamics 365 Business Central data. In this blog post, we will explore the secure and flexible nature of OAuth, its advantages over basic authentication, and its role in data integration projects. By following the steps outlined in this concise guideline, you will be able to create a connection manager using OAuth authentication for integration with Dynamics 365 Business Central online.

When loading data into Dynamics 365 using any API-based tools, any of your Power Automate flows you have defined will be triggered as the load occurs. This can result in unnecessary overhead for the data load. In this blog post, we will show you how to bypass Power Automate flows during data loading by leveraging the new features introduced in our latest v23.1 release.

Applications and processes often rely on external resources, which can be expensive to retrieve or obtain. Therefore, modern applications often employ cache strategies to save these external resources in the local file system and achieve improved performance. In some other cases, you might have an application that keeps creating random temporary files to facilitate certain system requirements which cannot be achieved otherwise. However, as every coin has two sides, these caches or temporary files, in the long run, can build up in the system and occupy large disk space, which could have adverse effects and result in volume deficiency in the system. Implementing a scheduled cleanup of the cache folder by removing those files that are older than a certain age can become necessary in your ETL process.