Release Version 2.38

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.

This release note also includes the fixes provided in all the minor releases since 2.37.

To know the complete list of features available for early adoption before these are made generally available to all customers, read our Early Access page.

In this Release

• New and Changed Features
• Fixes and Improvements
• Documentation Updates

---

New and Changed Features

Sources

• Support for Scheduled Execution of Data Refresher Tasks for Google Analytics 4 (Added in Release 2.37.2)

  • Introduced the ability to run data refresher tasks at a fixed time each day for Pipelines created with Google Analytics 4 as a Source. Previously, refresher tasks were triggered only if 24 hours had passed since the last successful run. As a result, the execution time of refresher tasks became inconsistent.

    With this enhancement, Hevo can now schedule refresher tasks to run at a fixed time daily, regardless of the Pipeline ingestion schedule. This ensures consistent data refreshes and improved data availability. To enable this enhancement for your new and existing Pipelines, contact Hevo Support.

Fixes and Improvements

Destinations

• Handling Data Loading Issue in Google BigQuery (Fixed in Release 2.37.1)

  • 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.

• Support for Including File Creation Date and Time in Amazon S3 File Names

  • Introduced the option to include the file creation date and time in the file names for data loaded to Amazon S3 Destinations. Previously, the date and time could be included in the directory path as part of the Destination configuration. With this enhancement, Hevo now supports including the date and time as part of the file name in the YYYYMMDD_HHMMSS format. This enhancement is useful when you want to easily identify when each file was created. To enable this feature for your new and existing Pipelines, contact Hevo Support.

Sources

• Handling Data Ingestion Issues in HubSpot (Fixed in Release 2.37.3)

  • Fixed an issue where data ingestion was delayed for objects with a large volume of data. This issue occurred because HubSpot sets a limit on the number of API requests allowed for an object within a time frame. If this limit was exceeded during a poll, Hevo would skip fetching data for that object until the next polling cycle, causing a delay in data ingestion.

    With this fix, when the API rate limit is exceeded for an object during a poll, Hevo now waits for 10 seconds and then retries fetching data from that object, up to 5 times. This ensures data from all objects is ingested with minimal delay. If all retries fail, Hevo attempts to fetch data in the next polling cycle. To enable the fix for your new and existing Pipelines, contact Hevo Support.

• Handling Data Mismatch Issue in QuickBooks Online (Fixed in Release 2.37.3)

  • Fixed an issue where the timestamp fields for the Invoice object were incorrectly detected as LONG data type, resulting in incorrect values being populated in the Destination. This issue occurred because Hevo converted date fields such as due_date and txn_date, into Unix timestamps during ingestion. A Unix timestamp represents a date and time as the number of milliseconds since January 1, 1970. These large numeric values did not match the expected DATE format in the Destination, leading to data type mismatches.

    With this fix, Hevo now correctly parses date fields such as due_date and txn_date in the expected DATE format, ensuring accurate data mapping in the Destination. To enable the fix for your existing and new Pipelines, contact Hevo Support. If you observe a data mismatch for the Invoice object in your existing Pipelines, you must enable the fix and then restart the historical load for the object.

• Handling Data Mismatch Issue in Twilio (Fixed in Release 2.37.1)

  • 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 in Release 2.37.1)

  • 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.

User Experience

• Handling Missing UI Elements in Pipeline Overview Page (Fixed in Release 2.37.2)

  • Fixed an issue in Hevo user interface (UI) where the gear icon and Pipeline status label were not visible on the Pipeline Overview page for some Facebook Ads Pipelines. This issue occurred because the display-details API call, which retrieves configuration details for the Pipeline, timed out when multiple ad accounts were linked to a single Pipeline. As a result, the page failed to render key UI elements, preventing users from reconfiguring the Source or adding new ad accounts. With this fix, the missing UI elements are now consistently visible, regardless of the number of linked ad accounts with the Pipeline.

Documentation Updates

The following pages have been created, enhanced, or removed in Release 2.38:

Account Management

• Inviting and Moderating Team Members

Data Ingestion

• Query Modes

Destinations

• Google BigQuery

• Snowflake

Introduction

• Events

• Hevo Pipeline Framework

Pipelines

• Auto Mapping Event Types

• Database Objects and Actions

• Prioritizing a Pipeline

• Why is there a delay in my Pipeline?

Sources

• Amazon Aurora MySQL

• Amazon Aurora PostgreSQL

• Amazon RDS MySQL

• Amazon RDS PostgreSQL

• Amazon S3

• Azure Blob Storage

• Azure MySQL

• Azure PostgreSQL

• CleverTap

• Generic MySQL

• Generic Oracle

• Generic PostgreSQL

• Google Analytics 4

• Google Cloud MySQL

• Google Cloud PostgreSQL

• Google Cloud Storage (GCS)

• Google Drive

• HubSpot

• LinkedIn Ads

• MariaDB MySQL

• Mixpanel

• NetSuite ERP

• PostgreSQL

• PostgreSQL FAQs

  • How can I prevent data loss when migrating or upgrading my PostgreSQL database? (New)

  • Why do FLOAT4 and FLOAT8 values in PostgreSQL show additional decimal places when loaded to BigQuery? (New)

• REST API

Transform

• Model Reset

• Working with SQL Models