This release significantly expands HubSpot Lists and related object support, improves synchronization efficiency and rate-limit handling, strengthens Salesforce Refresh Token Rotation, extends Shopify GraphQL write capabilities, and delivers important reliability improvements for REST and legacy OData integrations.
Upgrade Note: If you require any of the new features or improvements introduced in this release, please contact our Support team to schedule the upgrade to the latest version. Our team will assist you with the upgrade process and ensure a smooth transition.
HubSpot Lists can now be read, created, and deleted directly through integrations.Newly created List IDs can also be returned using StoreNewId, making it easier to use the new list in subsequent integration steps.
List creation supports the list types available through the HubSpot API. Updates to existing lists are not currently supported.
Added support for List Memberships, allowing records to be added to or removed from supported HubSpot lists. Each transfer works with a specific list using its listId, providing controlled management of list membership.
HubSpot Goals are now available for integration through the goal_targets object, expanding access to performance and target-related data.
Added read-only support for Feedback Submissions, allowing HubSpot survey responses to be retrieved through integrations.
Improved Update and Delete operations when HubSpot records are identified using a unique property rather than the internal HubSpot record ID.This provides more reliable synchronization when external identifiers, such as ERP customer numbers, are used to match existing HubSpot records.
HubSpot transfers now skip records when no data has changed instead of sending an unnecessary Update on every run. This reduces API usage, prevents unnecessary changes to hs_lastmodifieddate, and avoids triggering HubSpot workflows when the underlying record has not actually changed.
Enhanced LinkStorage behavior when creating or updating HubSpot records.Newly generated HubSpot identifiers are now captured more reliably, improving subsequent record matching and synchronization.
Improved validation and error reporting for operations that are unavailable or unsupported through the HubSpot API.This makes configuration issues easier to identify without masking the underlying API response.
HubSpot now uses dedicated rate-limit handling that better reflects HubSpot's API limits. This reduces unnecessary waiting after a 429 Too Many Requests response and can significantly improve processing times for larger HubSpot environments.
Further strengthened Salesforce Refresh Token Rotation handling. If a connection is interrupted while processing a token refresh, the integration now avoids reusing a refresh token that may already have been rotated. This helps protect the authentication chain and reduces the risk of subsequent authorization problems. Clearer messages are also provided when re-authorization is required.
Shopify LinkStorage now correctly stores the identifier returned by Shopify when a new product is created. This ensures subsequent transfers can reliably reference the newly created Shopify record using the same identifier format returned during normal reads.
Updated the Shopify integration to use a current API version, maintaining compatibility with Shopify's evolving API platform.
Expanded Shopify GraphQL support to allow product variants to be created for products created within the same transfer process. Unsupported variant operations are now clearly identified rather than being sent as invalid requests.
Shopify write operations are now built based on the operations available in the Shopify GraphQL schema. This improves compatibility with Shopify API changes and provides clearer feedback when a requested operation is not supported.
Enhanced connection handling for REST and SOAP integrations using OAuth2 or NTLM authentication. The integration now handles server-closed connections more reliably between requests, reducing intermittent SSL-related transfer interruptions.
Improved REST handling of 429 Too Many Requests responses so configured wait periods are applied more precisely. This avoids unnecessary additional waiting while respecting API rate limits.
Resolved an issue affecting data retrieval from older OData V3 services, including legacy Microsoft Dynamics NAV OData endpoints. Records are now returned correctly without unnecessary metadata reloads.
Improved paging for OData V3 services so transfers can reliably retrieve records beyond the server's first page. Paging links are also handled more robustly, helping prevent incomplete data retrieval when services return variations in their paging URLs.
Enhanced LinkStorage handling when creating OData records. Values returned by the destination system can now be captured more reliably after record creation, including cases where Business Central normalizes the submitted value.
Comment Editor X