Repository navigation
Releases: Reimaginate/DataHub.Agent.Dataverse
Releases · Reimaginate/DataHub.Agent.Dataverse
Release list
DataHub Agent for Dataverse 1.4.8
DataHub Agent for Dataverse 1.4.8
- Refreshes referenced entities after Dataverse reconciliation so newly introduced
Owner references resolve before outbound business updates are mapped. - Preserves existing User and Team identities, explicit Owner clearing, external
references, and unchanged-record behavior. Reference failures affect only the
relevant record; cancellation stops processing. - Updates DataHub dependencies to 1.4.12, Dataverse Client to 1.2.27, and the
Microsoft, Azure, cryptography, and test-support maintenance dependencies. - Uses ProcessingLock 4.0 with its separate Redis provider and releases acquired
locks even when the processing request is cancelled. - Adds 23 reconciliation regression cases and five ProcessingLock compatibility
cases. All 86 Dataverse unit tests and the S1001 live integration test passed
during validation.
Consumers that configure ProcessingLock directly must use the 4.0-compatible
packages and Redis registration API. Full DataHub runtime consumers must use
DataHub 1.4.12 or a later compatible release.
DataHub Agent for Dataverse 1.4.7
DataHub Agent for Dataverse 1.4.7
- Preserves every detected Dataverse field difference when preparing outbound
updates, preventing partial updates from omitting changed fields. - Removes unsafe concurrent writes from synchronous in-memory entity comparison
while retaining cancellation checks between compared fields. - Adds regression coverage for replacing, clearing, adding and retaining mapped
values, repeated multi-field comparisons, and comparison cancellation.
DataHub Agent for Dataverse 1.4.6
DataHub Agent for Dataverse 1.4.6
- Adds chainable Dataverse test-agent helpers for asserting that a DataHub
record sync returns no result, using either a supplied record or a stashed
record. - Reports sync failures directly while distinguishing unexpected successful
results from the expected empty response. - Adds unit coverage for dispatch, scenario-state preservation, empty responses,
unexpected successful responses and sync failures.
DataHub Agent for Dataverse 1.4.5
DataHub Agent for Dataverse 1.4.5
- Resolves DataHub alternate keys using the configured Dataverse data-source
prefix instead of assuming thedataverseprefix. - Preserves compatibility with existing
d365alternate keys as a fallback
when a custom data-source name is configured. - Adds unit coverage for configured, case-insensitive, logical-name and legacy
alternate-key resolution and for the missing-key failure path. - Updates DataHub and Core Agent dependencies to 1.4.1, Microsoft.Extensions
dependencies to 10.0.11, Microsoft.Azure.Cosmos to 3.62.1 and Testcontainers
dependencies to 4.14.0.
DataHub Agent for Dataverse 1.4.4
DataHub Agent for Dataverse 1.4.4
- Prevents transient or partial Data Hub alternate-key registration failures
from causing duplicate Dataverse records on a later synchronization. - Correctly correlates each alternate-key registration response with its
corresponding Data Hub entity and withholds source tracking for registrations
that remain unsuccessful. - Retries only failed or missing alternate-key registrations using a bounded
Polly resilience pipeline with configurable exponential backoff and jitter. - Adds regression coverage for partial registration recovery and verifies that
a subsequent synchronization reuses the original Dataverse record. - Remains compatible with DataHub 1.4.0, Core Agent 1.4.0, and .NET 10.
DataHub Agent for Dataverse 1.4.3
DataHub Agent for Dataverse 1.4.3
- Prevents repeated merge-failure results for the same Dataverse source entity
from causing a null-reference failure while processing updated entities. - Preserves the failed sync outcome and latest merge-failure reason when a
repeated result is reported. - Publishes the cumulative release-note history in the generated public source
repository. - Remains compatible with DataHub 1.4.0, Core Agent 1.4.0, and .NET 10.
DataHub Agent for Dataverse 1.4.2
DataHub Agent for Dataverse 1.4.2
- Fixes merge-failure reporting so DataHub receives the required failure type
and reason while retaining the description used by notifications. - Reports
SourceEntityNotFoundonly for records that Dataverse identifies as
missing and includes a descriptive reason for each missing record. - Remains compatible with DataHub 1.4.0, Core Agent 1.4.0, and .NET 10.
DataHub Agent for Dataverse 1.4.1
DataHub Agent for Dataverse 1.4.1
- Fixes Dataverse synchronization to consistently use the configured
DataSourcefor alternate keys, tracking updates, sync allow/block lists,
deletion handling, referenced entities, and resolution promises instead of
assuming the source is namedDataverse. - Supports configured aliases such as
D365while remaining compatible with
DataHub 1.4.0, Core Agent 1.4.0, and .NET 10. - Corrects the Dataverse test-framework package so its shared test-support
assembly is included directly instead of appearing as an unpublished NuGet
dependency.
DataHub Agent for Dataverse 1.4.0
DataHub Agent for Dataverse 1.4.0
- Aligns the Dataverse agent packages with DataHub 1.4.0 and .NET 10.
- Introduces
Reimaginate.DataHub.Agent.Dataverseas the replacement for
Reimaginate.DataHub.D365Agent. - Introduces
Reimaginate.DataHub.Agent.TestFramework.Dataverseas the
replacement forReimaginate.DataHub.TestFramework.Agents.D365CE. - Publishes buildable MIT-licensed source and safe unit tests in the dedicated
Dataverse release mirror.
DataHub Agent for Dataverse 1.4.0-rc4
DataHub Agent for Dataverse 1.4.0-rc4
- Clarifies that the Dataverse Agent source and official package content are
licensed under MIT while DataHub dependencies retain their separate BUSL
licence. - Adds generated third-party dependency notices to the public source snapshot
and NuGet packages. - Restricts full DataHub hosting dependencies and namespaces to Dataverse
integration-test support. - Aligns with DataHub 1.4.0, the Core Agent 1.4.0-rc4 packages, and .NET 10.