Release 10.0.47.72 (March 2026)

New or changed features in Release 10.0.47.72 (March 2026) – Connectivity Studio.

1. Word Document Tables Fit Within Page Boundaries

Tables generated by the Create Microsoft Word Document deployment feature now automatically fit within page boundaries. Previously, tables in generated Word documents could extend beyond the visible page area, requiring manual resizing to ensure readability.

This enhancement ensures all tables are properly constrained to the page width at the time of generation, eliminating the need for post-generation adjustments.

This feature was added as a result of change request CS00235811.

See also: Create Microsoft Word Document from project.

2. Field Deletion Validation Includes Source Query Ranges

When you delete a field from a source document query, the system now checks whether the field is used in a Range configuration and displays a validation prompt before proceeding. Previously, the system only warned about fields used in Relations or Sorting configurations. Fields used in ranges were silently deleted, causing the range setup to break without any notification.

The validation prompt now covers all field usages:

• Relations

• Sorting

• Ranges

If a field is used in one or more of these configurations, you must confirm the deletion. The system then removes the field and its associated configuration.

This feature was added as a result of a customer request.

See also:

• Add document record field - Internal documents

• Add document records fields - ODBC documents

3. Dead Letter Queue Properties Support

When processing messages from a Service Bus Dead Letter Queue (DLQ), Connectivity Studio now reads and exposes two additional message properties:

• DeadLetterReason – contains the reason the message was moved to the Dead Letter Queue

• DeadLetterErrorDescription – contains the detailed error description associated with the dead-lettered message

These properties are available for mapping in the source document, enabling you to capture diagnostic information about failed messages and use it in downstream error handling processes within D365 F&SCM.

Previously, these properties were not accessible through Connectivity Studio, making it difficult to understand and act on the cause of message failures without external tooling.

This feature was added as a result of change request CS00238534.

See also:

• Data import from Azure service Bus dead letter queue

• Monitor and troubleshoot Service Bus dead letter data

4. Performance Index on Service Bus Received Data Table

A non-clustered index has been added to the BisConSbReceivedData table. This resolves deadlock issues that occurred when multiple batch threads processed Service Bus messages across different legal entities simultaneously.

In high-throughput multi-company environments where Service Bus messages are processed in parallel, concurrent writes and reads to the BisConSbReceivedData table could cause deadlocks, resulting in failed message processing. The new index reduces contention and improves processing stability and throughput.

This feature was added as a result of change request CS00238981.

See also: Monitor data received from Azure Service Bus queue or topic subscription

5. ODBC Large Dataset Processing Improvements

Several improvements have been made to Connectivity Studio's ODBC integration to support reliable processing of large datasets, including databases with millions of records.

5.1 Background

When connecting to on-premises databases with very large tables through ODBC, users encountered timeout errors during both data retrieval and parallel processing. The root causes included slow record-count queries, inefficient paging strategies for large datasets, and missing database index hints that caused full table scans.

5.2 What changed

• Query info timeout handling
  Timeout handling has been added to the query info function, which determines the total record count and calculates the number of processing threads. Previously, this function could run indefinitely on large datasets, blocking the processing start. The function now respects the configured timeout threshold.

• Modulo paging option
  A new paging method, Modulo, is now available for ODBC documents. The modulo option assigns records to pages based on the record ID divided by a set number, rather than using offset-based paging. This approach results in more consistent query performance for large datasets because it avoids the performance degradation that occurs with high-offset queries in traditional paging.

• Partition and Data Area ID in ODBC queries
  ODBC connector queries now automatically include the Partition and Data Area ID fields. In database systems such as AX 2012, primary indexes include these fields. Without them, queries could not use the primary index and resulted in full table scans. Including these fields ensures the database uses the correct index, significantly improving query performance.

  The connector uses the current legal entity's Data Area ID automatically, reducing the need for manual changes when running the same document for different companies.

• SQL query execution plan viewer
  A new diagnostic tool is available on ODBC documents. You can use it to retrieve and display the SQL Server execution plan for the configured query. This allows message and document designers to verify which indexes are being used and to identify missing indexes that may affect performance.

• Data range support for incremental ODBC imports
  ODBC imports now support data ranges, allowing you to migrate or synchronize only new or changed records instead of the full dataset. This is useful for large initial data migrations and for ongoing delta synchronizations where re-importing unchanged records is unnecessary.

• Rerun failed pages
  When processing data in parallel across multiple threads, individual pages (thread batches) may fail. You can now rerun only the failed pages instead of restarting the entire data load. This reduces processing time and resource usage when recovering from partial failures.

• Consistent delta run date handling across parallel threads
  In delta run scenarios using parallel processing, all threads now use the same start and end date. Previously, threads could use slightly different time boundaries, resulting in missed or duplicated records. This change ensures complete and consistent data synchronization across all threads.

6. EDI Telemetry for Message Consumption

The telemetry infrastructure has been updated to capture and report on EDI message consumption data. This enables better operational visibility into EDI throughput and usage patterns for monitoring and reporting purposes.

Bug fixes in Release 10.0.47.72 (March 2026) - Connectivity Studio.

The following issues have been identified in Release 10.0.47.72 (March 2026) - Connectivity Studio.

1. Licensing

This release includes TCL Common model version 1.0.0.63, which contains a new license certificate. After deploying this release, you must reinstall all STAEDEAN licenses as described in KB0018522 (https://staedean.service-now.com/support?id=kb_article_view&sysparm_article=KB0018522).

Note

If you have already installed TCL Common model version 1.0.0.63 and reinstalled all STAEDEAN licenses, you can skip this step.

2. Libraries

Libraries in Release 10.0.47.72 (March 2026) – Business Integration Solutions, including Connectivity Studio.