Release Version 2.33.3

In this release, we have addressed the following issues to improve the usage and functionality of our product features. 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

• New and Changed Features
• Fixes and Improvements

---

New and Changed Features

Sources

• Support for Discount Applications Object in Shopify

  • Added support for replicating data from the discount_applications object as a child of the Order object in Shopify. This object is an ordered list that captures all discounts applied to an order, reflecting the sequence in which they were added.

    To enable this for any new or existing Pipelines, reach out to Hevo Support. For existing Pipelines, restart the historical load for the Order object to retrieve historical data for the discount_applications object.

• Support for Simple and Kanban Board Types for Jira Cloud Source

  • Hevo now supports data ingestion from Simple and Kanban board types for the Sprint object. This enhancement allows for more comprehensive data replication from a wider range of Jira boards.

    Board Type	Description
    Kanban	Organizes tasks into different stages to facilitate continuous tracking and workflow management.
    Simple	Manages tasks without predefined stages, offering flexibility in task handling.

    To enable data ingestion for the above board types in your new and existing Pipelines, contact Hevo Support. As Sprint is a Full Load object, enabling data ingestion for these board types will lead to higher Events quota consumption.

Fixes and Improvements

Sources

• Handling API Authentication Issue for Charge Object in Stripe

  • Fixed an issue where Hevo was unable to retrieve the refundIds field from the Charge object due to a missing API key in the API call. The API key is required to authenticate the request for retrieving data from this field. Without the API key, the authentication failed, preventing historical data ingestion for the object.

    With this fix, Hevo now includes the API key in the API call, ensuring successful authentication and historical data ingestion for the Charge object. This fix applies to all new and existing Pipelines.

• Handling Data Mismatch Issue in Salesforce Marketing Cloud

  • Fixed an issue where Hevo was unable to fetch data for the itemID field in the campaign_asset object due to a case mismatch. This issue occurred because the API attempted to access the itemId field instead of the correctly named itemID. As a result, Hevo loaded zero as the default value for this field into the Destination.

    With this fix, Hevo can now retrieve the data for the itemID field, ensuring accurate data is loaded into the Destination.