Skip to main content

Solutions

Products

Recommended products

Questions? We are here to help.
Contact us

Purchase

Questions? We are here to help.

Resources

Determination Anywhere

Determination Anywhere 2025.06 hot fix release notes

Release highlights

This patch resolves few critical issues identified in the Determination Enterprise Cloud and Determination Anywhere applications.

New features

The following topics outline the new features introduced in this release.
DA Cloud Full Config Update using SDI – Performance Improvements (4608354)
This enhancement addresses performance bottlenecks in the SDI-based process used to move a tenant company’s full configuration data from Enterprise Cloud Determination to the DA deployed side. Large volumes of data – particularly exemption-related Customer and Certificate records – previously caused significant delays in the SDI process, sometimes even resulting in timeouts.
To improve efficiency, database ID generation for bulk record entities will now be handled differently during sync. For example, a tenant syncing approximately 1 million certificate records, which previously required close to 24 hours, is now expected to complete in about 4 hours.
To enable this capability, new settings in Overlay should be configured for feature table entities having high record counts. The following parameters can be set to optimize performance in the case of exemption certificate performance:
  • -DTB_EXEMPT_CERTS.id.generator.max_lo
  • -DTB_MERCHANT_XML_ELEMENTS.id.generator.max_lo
  • -DTB_EXEMPT_CERT_ZONES.id.generator.max_lo
  • -DTB_CUSTOMERS.id.generator.max_lo
Additional improvements to the SDI full sync process include:
  • Timeout configuration:
     The default 24-hour limit can now be increased by adjusting the
    sdi.transaction.timeout
     setting in Overlay.
  • Batch size configuration:
     The default batch size of 100 records can now be modified using the
    sdi.batch.size
     setting in Overlay.
DA Sync API Token Generation – Enable Proxy to TR Mothership (4611367)
With the release of DA version 2025.05, support was introduced for DA Clients to connect to the TR Mothership through corporate proxy servers (see release note 1649181 for additional details).
Previously, proxy support was missing for the Apigee call used in token generation requests during the webservice data sync. This functionality has now been added as part of this release.
Please note that proxy support currently applies only to content and configuration data synced from the DA Mothership to the DA client side. It is not yet available for transaction or telemetry data syncing in the opposite direction. That capability will be included in the upcoming DA release.

Fixes

The following topics highlight high‑risk issues uncovered during UAT that necessitated a patch in this release.
DA Cloud – Transactions Not Syncing to Audit (4619596)
An issue was identified in older versions of DA where transaction data failed to sync back to audit if the TR side already contained the latest version. This occurred due to a change introduced on the Enterprise Cloud data set side that did not support backward compatibility, resulting in all synced transactions being moved to the failed queue.
With this fix, failed queue transactions will be automatically reprocessed and moved successfully into reporting/NGRA.
Please note that this issue has only been observed in the UAT environment and does not affect production transactions synced through DA.
DA Cloud – International Content update failure (4603022)
In this DA release, the international tax content update was failing when the CaaS form of content processing was enabled (see 1744175). The issue was traced to the way tax content files were being created.
To resolve this, content delivery was temporarily re-enabled using the historical method of retrieving tax content from BCC. With this correction in place, content will now begin utilizing CaaS for delivery as intended.
DA Cloud – Incorrect Cache Configuration (4627963)
In this release, the Helm Chart setting required to manage cache updates within DA – specifically tied to TransEditor changes – was inadvertently overwritten. This has now been corrected so that the appropriate value of 0 is set for both
lifespan
 and
max-idle
 in
Determination.FilterGroup
.

This article applies to:

  • PRODUCT: ONESOURCE Determination

Related Content