Update to Data Exchange SDK .NET (7.1.0)

The Autodesk Platform Services (APS) Data Exchange SDK has been updated to Beta v7.1.0, bringing refinements that improve consistency, expand patterns for modern workflows, and smooth the developer experience for building robust data exchange solutions.

This release builds on the SDK’s continued evolution, with a focus on clearer API conventions and easier-to-maintain integrations, in line with the direction set by previous updates.

In this post, we walk through what’s new in v7.1.0, highlight the most notable breaking changes, and share guidance to help you migrate existing connectors and integrations with confidence.

While this update is particularly relevant for those maintaining connectors or working closely with Data Exchange geometry and metadata, many of the enhancements will also be valuable for developers consuming exchanges downstream.

What’s New in Data Exchange SDK Beta 7.1.0

Exchange Descriptions

The SDK now supports exchange descriptions, allowing developers to attach human-readable context to exchanges, similar to Git commit messages.

You can: - Add descriptions when creating or updating exchanges - View descriptions in the Connector UI exchange history - Retrieve descriptions programmatically via the SDK

This feature improves traceability and makes it easier to understand why an exchange was created or modified.

Automatic SDK Metadata for Exchanges

Version 7.1.0 introduces automatic metadata attributes that are added to every exchange by the SDK:

Connector name and version
Host application name and version

This information is captured automatically and displayed clearly in the Connector UI under Authoring Connector and Authoring App. Custom attributes remain separate under Filters applied.

For most developers, no code changes are required—the SDK handles this automatically.

Cleaner Attribute Naming

Attribute keys no longer include the platformAttribute- prefix. Existing exchanges created with older SDK versions continue to load correctly, as the SDK normalizes attribute names when reading.

Only code that explicitly parses attribute names will require updates.

Major API and Architecture Changes

Geometry API Refactoring

The geometry type system has been redesigned to use a unified, stream-based model.

Removed: - GeometryProperties - Geometry format–specific stream types (IFC, OBJ, STEP)

New approach: - FileGeometry and StreamGeometry - Explicit conversion methods between file and stream representations

This change results in clearer ownership of geometry resources and more predictable access patterns.

Client and ElementDataModel Changes

Several APIs have been removed or simplified: - SetGeometryConfiguration() is no longer required and has been removed - UpdateElement() has been removed; element properties are now set directly - GetElementGeometryByElementAsync() has been replaced with GetGeometriesAsync()

These changes reduce redundant abstractions and align the SDK more closely with modern .NET design practices.

Hosting Provider Interface Update

The hosting provider interface has been updated to return richer status information: - GetExchangeMetaDataAsync() has been replaced with GetExchangeMetadataDescriptorAsync()

This new API provides explicit status codes and messages, improving error handling and diagnostics.

UI Package Changes

A large portion of the UI package has been internalized to reduce accidental coupling with internal implementation details. Public usage should rely on the remaining supported namespaces such as:

Autodesk.DataExchange.UI.Core
Autodesk.DataExchange.UI.CustomForm
Autodesk.DataExchange.UI.Helper

Connectors referencing internalized UI APIs will need to update their implementations.

New Capabilities in 7.1.0

Element Attributes for attaching metadata directly to elements
ElementGeometry Parameters for schema-driven geometry metadata
ValidationStatus infrastructure for consistent exchange validation
IFC download support via DownloadCompleteExchangeAsIFC()
Disposable pattern for FileGeometry to ensure proper resource cleanup

These additions provide more flexibility and robustness when building advanced workflows.

Migration Guidance

What Requires Immediate Attention

Replace GeometryProperties with FileGeometry / StreamGeometry
Remove calls to SetGeometryConfiguration()
Update hosting providers to use GetExchangeMetadataDescriptorAsync()
Update code that depends on the platformAttribute- prefix

What Continues to Work

Existing exchanges created with SDK 6.x load correctly
Custom attributes are preserved
Older connectors can read exchanges created by v7.1.0

Recommended Migration Approach

Update package references to v7.1.0
Address critical API removals first (geometry and hosting provider changes)
Review UI dependencies for internalized APIs
Validate exchange creation, loading, and UI display
Incrementally adopt new features such as element attributes and validation status

Why Upgrade

While v7.1.0 introduces breaking changes, it provides: - Cleaner and more consistent APIs - Better alignment with modern .NET patterns - Improved developer clarity and diagnostics - Stronger foundations for long-term SDK evolution

These improvements reduce integration risk and make connector code easier to maintain over time.

Conclusion

We encourage all developers to migrate to version 7.1.0 to take advantage of these improvements and as with previous beta releases, we recommend testing migrations incrementally and validating workflows early. The migration process is straightforward when following the steps outlined in this guide.

Additional Resources:

If you have not yet enrolled in the beta program, you may access it here.

Feedback from real-world usage continues to shape the SDK, and we encourage developers to share their experiences as they adopt v7.1.0.

Tags:

Data Exchange API

Back to Community Blog