Changelog – Data Exchange SDK 7.2.0-beta
Release Date: March 6, 2026
This release includes new features, API improvements, and behavioral changes from v7.1.x to v7.2.0.
What’s New
- New class:
FeatureCapabilities— Declare which UI features your connector supports. - New capability:
EnableSelectElements(enabled by default) — Let users select/highlight exchange elements in the host application. - New event:
IInteropBridge.ExchangeOperationCompleted— Get notified when exchange operations complete. - New types:
ExchangeOperationTypeenum,ExchangeOperationCompletedEventArgsclass.
Breaking changes:
GetGeometriesAsyncsignature changed — see Changed section.SkippedElementType.Miscellaneousremoved — see Removed section.
Behavioral change: Geometry translation methods return partial results instead of throwing exceptions — see Behavioral Changes section.
Deprecations: See Deprecated section.
Added
FeatureCapabilities Class
The FeatureCapabilities class controls which UI features are available to users.
| Property | Type | Default | Description |
|---|---|---|---|
EnableTaskCancellation |
bool |
false |
Show cancel button during operations |
EnableHideUnhideExchange |
bool |
false |
Allow hiding/showing exchanges |
EnableSelectElements |
bool |
true |
Add "Select Elements" to context menu |
ExchangeOperationCompleted Event
When users create, load, or update exchanges through the Connector UI, your host application may need to respond — for example, refreshing a project tree, logging metrics, or closing the UI after an operation completes.
The ExchangeOperationCompleted event notifies your application when these operations complete.
Event: IInteropBridge.ExchangeOperationCompleted
When it fires:
- After SDK has finished processing the operation.
- After cleanup operations (StopSession, SkippedElements logging).
- After response has been delivered to Connector UI.
Event data:
| Property | Type | Description |
|---|---|---|
OperationType |
ExchangeOperationType |
Type of operation completed |
Succeeded |
bool |
Whether operation completed successfully |
Operation types:
| Value | Description |
|---|---|
Create |
A new exchange was created |
Load |
An existing exchange was loaded |
Update |
An existing exchange was updated |
Delete |
One or more exchanges were deleted |
LoadLatest |
Latest version of an exchange was loaded |
Example:
bridge.ExchangeOperationCompleted += (sender, e) =>
{
Console.WriteLine(
$"Exchange operation {e.OperationType} " +
$"{(e.Succeeded ? "succeeded" : "failed")}"
);
};
Details: Initializing the Connector UI — Working with Exchange Operation Events
Changed
GetGeometriesAsync Method Signature
⚠️ Breaking Change: Existing code using
GeometryFilterswill not compile. See migration table below.
The GetGeometriesAsync method now accepts GeometryOutputOptions instead of GeometryFilters, aligning it with GetElementGeometriesAsync.
| Old Code (v7.1.x) | New Code (v7.2.0) |
|---|---|
GetGeometriesAsync(GeometryFilters.All) |
GetGeometriesAsync() |
GetGeometriesAsync(GeometryFilters.BrepOnly) |
GetGeometriesAsync(new GeometryOutputOptions { GeometryFilters = GeometryFilters.BrepOnly }) |
GetGeometriesAsync(filters, token) |
GetGeometriesAsync(new GeometryOutputOptions { GeometryFilters = filters }, token) |
Default behavior unchanged: Passing null or no parameters returns all geometry types.
Why this change: The GeometryOutputOptions object enables future expansion (output format, streaming options) without adding more parameters.
Details: Migration Guide
Removed
SkippedElementType.Miscellaneous
⚠️ Breaking Change: Code using
SkippedElementType.Miscellaneouswill not compile.
The Miscellaneous value has been removed from the SkippedElementType enum.
| Old Code | New Code |
|---|---|
SkippedElementType.Miscellaneous |
SkippedElementType.Unsupported |
Remaining values: Failed and Unsupported
Why this change: To enforce explicit classification of skipped elements. Use Unsupported for element types the connector doesn’t handle, and Failed for elements that encountered processing errors.
Migration:
// Before
skippedElement.Type = SkippedElementType.Miscellaneous;
// After — Use Unsupported for elements the connector doesn't handle
skippedElement.Type = SkippedElementType.Unsupported;
// Or use Failed for elements that encountered errors
skippedElement.Type = SkippedElementType.Failed;
Behavioral Changes
Geometry Translation Error Handling
⚠️ Behavioral Change: Code that assumes complete results may now silently process incomplete data. Review and add count validation where needed.
Geometry translation methods now log failures and return partial results instead of throwing exceptions.
Affected methods:
GetElementGeometriesAsyncInternalToGeometriesGeometriesToInternal
| Aspect | Before (v7.1.x) | After (v7.2.0) |
|---|---|---|
| Error signaling | Exception thrown | Logged only |
| Result guarantee | All or nothing | Partial results allowed |
| Count equality | Input = Output (or exception) | Input ≥ Output |
Why: One problematic element previously failed an entire batch. The new approach processes what it can and logs failures.
Impact: Code that assumes complete results must now validate the count:
var elementList = elements.ToList();
var geometries = await data.GetElementGeometriesAsync(elementList);
var geometryList = geometries.ToList();
if (geometryList.Count != elementList.Count)
{
var missing = elementList.Count - geometryList.Count;
logger.Warning($"Incomplete: {missing} of {elementList.Count} failed");
}
Details: Migration Guide
Deprecated
| Deprecated Property | Replacement |
|---|---|
InteropBridgeOptions.EnableTaskCancellation |
FeatureCapabilities.EnableTaskCancellation |
InteropBridgeOptions.EnableHideUnhideExchange |
FeatureCapabilities.EnableHideUnhideExchange |