Release Version 2.36
On This Page
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.35.
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
Sources
-
Support for Spatial Data Types in SQL Server Sources (Added in Release 2.35.2)
-
Added support to parse geometry and geography data types from all variants of SQL Server Source. With this enhancement, Source fields containing spatial data are now accurately parsed using the Well-Known Text (WKT) standard format, instead of being converted into unreadable raw binary strings as before.
To enable the enhancement for your new and existing Pipelines, contact Hevo Support. For existing Pipelines, to re-ingest data from objects containing spatial data, restart the historical load for those objects.
-
Fixes and Improvements
Hevo API
-
Handling Status for Model Reset in the API Response (Fixed in Release 2.35.2)
-
Fixed an issue where, in some cases, retrieving the Model details using the Get Model endpoint resulted in an internal server error. This issue occurred because Hevo did not handle the status of the Model when it was being reset.
After the fix, when the Model details are fetched during a reset, Hevo now correctly displays the Model’s status as RESETTING in the API response.
-
Sources
-
Handling Connection Issues in NetSuite SuiteAnalytics (Fixed in Release 2.35.2)
-
Fixed an issue in the NetSuite SuiteAnalytics integration where the SuiteAnalytics Connect Service rejected duplicate connection requests. This issue occurred because the OAuth header contained a previously used nonce (number used once). NetSuite requires a unique nonce in the OAuth header of each connection request.
After the fix, Hevo includes a unique randomized nonce in the OAuth header of each request to ensure successful authentication. The fix applies to all new and existing Pipelines.
-
-
Handling Data Mismatch Issue in Amazon S3 (Fixed in Release 2.35.1)
-
Fixed an issue where bytes data from the Source was stored in an unreadable format in the Destination due to improper data parsing. This issue occurred because Hevo parsed bytes data from the Source and stored it directly as a string in the Destination, causing a data mismatch. With this fix, Hevo now converts the bytes data to its hexadecimal representation before storing it as a string in the Destination, ensuring that data is stored in a readable format.
Contact Hevo Support to enable the fix for your new and existing Pipelines. For existing Pipelines, if you observe a data mismatch in your Destination tables, restart the historical load for that Source object.
-
-
Handling Data Mismatch Issue in Pipedrive (Fixed in Release 2.35.2)
-
Fixed an issue where, in some cases, data ingested from the Pipedrive Source was not synced correctly with the Destination, causing data mismatches. This issue occurred because Hevo fetched updated records based on the since_timestamp parameter. This parameter includes only those records with a strictly later updated_at timestamp, excluding those records with an exact timestamp as the one passed in the request.
With this fix, Hevo now uses the start parameter along with since_timestamp to fetch records that have the same updated_at timestamp, where the start parameter is used to paginate the API results received within the same time window. Hevo fetches all records with the same timestamp by increasing the start value across consecutive API calls until the API response returns fewer records than the page limit or is empty. This ensures that all data within the same time window is retrieved before moving to the next timestamp.
The fix applies to all new and existing Pipelines. If you observe a data mismatch in your existing Pipelines, you must restart the historical load for the affected objects.
-
-
Handling Missing TOASTed Data for PostgreSQL Source (Fixed in Release 2.35.3)
-
Fixed an issue affecting all variants of PostgreSQL Source, where TOASTed records were lost during batch processing if Hevo’s internal data processing system encountered downtime or failure. The issue occurred when Hevo attempted to retrieve data from PostgreSQL using a batch query, but could not process it because the system was unavailable. Since there was no fallback mechanism, any unprocessed data was lost.
With this fix, if the internal system is down during such scenarios, the retrieved record will now be temporarily stored in Hevo’s temporary memory cache. When the system is back online, the data from the cache is processed, ensuring no data is lost. To enable this fix for your existing or new Pipelines, contact Hevo Support.
-
-
Handling Token Refresh Issue in Pinterest Ads (Fixed in Release 2.35.3)
-
Fixed an issue where, in some cases, Pinterest Ads Pipelines failed to refresh tokens automatically and needed a manual account reauthorization. This issue occurred because Hevo did not call the refresh token API when the access token expired. As a result, Hevo could not generate a new access token using the existing refresh token, leading to authentication errors.
With this fix, Hevo now triggers the refresh token API before the access token expires. This enables automatic generation of new access tokens prior to expiration.
-
-
Improved Refresher Task for Ad_Hourly_Report Report in TikTok Ads (Fixed in Release 2.35.2)
-
Enhanced the refresher task for the Ad_Hourly_Report report. Previously, Hevo refreshed data for this report once every six hours.
With this enhancement, Hevo now runs the refresher task as per the Pipeline frequency if your Pipeline is configured to run more often than every six hours. As a result, Hevo refreshes the data for the report more frequently. However, if your Pipeline runs less frequently, the refresher task will continue to run every six hours. To enable this functionality for your new and existing Pipelines, contact Hevo Support.
-
-
Improved Tracking of Deal Stages in HubSpot (Fixed in Release 2.35.2)
-
Enhanced the data ingestion process for the deals object to capture all stage changes of a deal. Previously, when a deal moved through multiple stages, at the time of incremental ingestion, Hevo captured only the latest stage of the deal in the dealstage field. This limited visibility into the movement of a deal across stages.
With this improvement, Hevo now captures each stage of the deal, providing a comprehensive view of the deal’s progress. To enable this improvement for your new and existing Pipelines, contact Hevo Support. For existing Pipelines, if you want to capture all the stage changes, restart the historical load for the deals object. However, doing so may lead to higher Events quota consumption.
-
User Experience
-
Displaying Cluster Keys for Snowflake Destination Tables (Fixed in Release 2.35.1)
-
Fixed an issue in the Hevo user interface (UI) that caused the cluster key icon to be missing in the Schema Mapper and the Destination Workbench for columns that are part of the cluster key in Snowflake tables.
With this fix, the icon now appears correctly in the Hevo UI, making it easier for you to identify the columns that form the cluster key in your Destination tables.
The fix will be deployed to teams across all regions in a phased manner and does not require any action from you. However, to make this fix available for your team immediately, you may contact Hevo Support
-
Documentation Updates
The following pages have been created, enhanced, or removed in Release 2.35: