Release Version 2.36.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

Sources

• Handling Data Ingestion Issue in Salesforce Bulk API V2

  • Fixed an issue where data from certain Full Load objects, such as EntityDefinition, was being ingested in each Pipeline run instead of once every seven days. This behavior led to excessive consumption of Events. With this fix, Hevo now ensures that data from all Full Load objects is ingested every seven days. This fix applies to new and existing Pipelines.

• Handling Data Mismatch Issue for Item Types in NetSuite ERP

  • Fixed an issue where updates to inventory data were not captured for the following real-time inventory item types, leading to mismatches between the Source and Destination data:

    • Inventory Item
    • Assembly Item
    • Lot Numbered Inventory Item
    • Serialized Inventory Item

    This issue occurred because NetSuite does not update the lastModifiedDate field when a transaction affecting inventory takes place for these item types. As a result, Hevo could not detect changes based solely on this field, causing data discrepancies. With this fix, Hevo now uses the lastQuantityAvailableChange and lastModifiedDate fields to identify inventory-related updates. This ensures that inventory changes are captured even if no updates are made to the item type itself. If you notice a data mismatch in any of your existing Pipelines, contact Hevo Support to enable the fix for that Pipeline.

• Handling Historical Data Ingestion Issue in ActiveCampaign

  • Fixed an issue in the ActiveCampaign connector where historical data was incorrectly marked as completed. This problem occurred because Hevo did not retry the ingestion task after receiving an internal server error in the API response.

    With this fix, Hevo now retries ingesting the historical data from the same offset that was recorded before the error occurred. The fix applies to new and existing Pipelines.

• Handling Ingestion Lag Issues in Snapchat Ads

  • Fixed an issue where data ingestion for Snapchat Ads was delayed due to incorrect time zone handling during the data fetching process. This issue occurred because Hevo miscalculated the data range needed to retrieve data. Specifically, the start date used for fetching data was inadvertently set earlier when converting from UTC to the Source’s local time zone. As a result, Hevo did not retrieve data for recent dates, even though the Snapchat Ads API had data available for them.

    With this fix, Hevo has corrected the logic for calculating the date range, ensuring that data is fetched accurately for the intended days, regardless of time zone differences. The Pipeline now consistently ingests the most recent data available, eliminating the delay.

• Improved Refresher Data Availability for Ad_Hourly_Report Report in TikTok Ads

  • Enhanced the data refresher task for the Ad_Hourly_Report report to align with the Pipeline frequency if it is set to less than six hours. As a result, data for the report is refreshed more frequently, improving data availability and timeliness. Earlier, by default, the task ran once every six hours.

    With this change, the task will run only once every six hours if your Pipeline frequency is set to more than six hours. To enable this functionality for your new and existing Pipelines, contact Hevo Support.