Release Version 2.37.1

The content on this site may have changed or moved since you last viewed it. As a result, some of your bookmarks may become obsolete. Therefore, we recommend accessing the latest content via the Hevo Docs website.

In this Release

• Fixes and Improvements

Fixes and Improvements

Destinations

• Handling Data Loading Issue in Google BigQuery

  • Fixed an issue where Pipelines failed to load data into BigQuery due to incorrect handling of nested field names. This issue occurred because Hevo did not quote each part of the nested field path. As a result, BigQuery converted unquoted field names to uppercase, causing mismatches with the actual field names in the Destination table and leading to data load failures. With this fix, Hevo now correctly quotes every part of a nested field name. This keeps the correct case, ensuring accurate field mapping and error-free data loading.

Sources

• Handling Data Mismatch Issue in Twilio

  • Fixed an issue where the API call to fetch the Usage Records object for a specific date returned incorrect data. This issue occurred because the API call returned the sum of the field values for the selected date and the following day. As a result, the records in the Destination contained inflated values.

    With this fix, the API now correctly retrieves only the data for the specified date. To enable the fix for your existing and new Pipelines, contact Hevo Support. If you observe a data mismatch for the Usage Records object in your existing Pipelines, you must enable the fix and then restart the historical load for the object.

• Handling Pipeline Save Failure in SQL Server

  • Fixed an issue for all variants of SQL Server where configuration changes, such as renaming or updating connection settings, could not be saved for any Pipeline configured in Table Mode with Full Load. The configuration tests failed with the error, Unable to include ‘condition’. Please ensure Change Tracking is enabled for the database. This issue occurred because Hevo incorrectly triggered Change Tracking validations, even though it was not enabled for the Pipeline.

    With this fix, Hevo no longer performs unnecessary Change Tracking checks for Pipelines that do not use this feature, allowing configuration changes to be saved successfully.