Find information on Release 10.0.48.73 (June 2026) of the Connectivity Studio for Microsoft Dynamics 365 for Finance and Supply Chain Management.
Version information:
Product | Version | Minimum version | Latest validated version | Planned next |
|---|---|---|---|---|
Connectivity Studio | 10.0.48.73 | D365 F&SCM 10.0.45 | D365 F&SCM 10.0.48 | September 2026 |
Note
Connectivity Studio updates are released as part of the Business integration Solutions (BIS) release.
What’s new
New or changed features in Release 10.0.48.73 (June 2026) of the Connectivity Studio.
1. Error History Per Message Tab
A new Error history per message tab has been added to the Integration Operations workspace. This tab aggregates error occurrences per message, providing a consolidated view of which messages are failing and how frequently.
Previously, the History errors tab created one row per message run, making it difficult to identify patterns or recurring failures across messages. The new tab groups errors by message, enabling faster identification of problematic integrations that require attention.
This feature was added as part of sustained engineering improvements.
2. On-Demand Error Message Retrieval
You can now retrieve detailed error information on demand from the Error history per message tab. This allows you to access the full error details for a specific message without navigating through individual run history entries.
This complements the Error history per message tab by providing drill-down capability into the specific error messages associated with each failing integration.
This feature was added as part of sustained engineering improvements.
3. Document Field Length Validation on Message Import
A new validation option is available on source document fields that checks whether incoming field values exceed the configured field length during message import. You can configure the validation behavior per field using the Validate field length dropdown:
Error – Rejects the message if the field value exceeds the configured length
Warning – Logs a warning but continues processing
None – No validation (default, preserves existing behavior)
This validation applies to read operations only and supports XML, JSON, and Text document types. It helps catch data quality issues at the point of ingestion rather than encountering failures downstream in D365 F&SCM processing.
This feature was added as a result of product backlog item.
4. Post Packing Slip (SO) - Standalone Posting Handler
A new document handler BisDocumentPackingSlipPost, Post Packing slip (SO), is now available for D365 F&SCM document types. This handler posts the packing slip on a sales order using the standard D365 F&SCM packing slip posting logic without attempting to modify the picking list.
Previously, packing slip posting was only available through the existing handlers that combine picking list registration with packing slip posting. The new standalone handler supports scenarios where the picking list is already registered (for example, by a warehouse management system or 3PL) and only the packing slip posting needs to be triggered through an inbound message.
The handler validates that the sales order exists and is in a state that allows packing slip posting. If the order is not in a valid state, the handler logs an error and the message is moved to the dead letter queue.
This feature was added as a result of product backlog item.
5. SharePoint Connector Environment-Specific Properties
SharePoint connector properties are now correctly saved and resolved per environment type. Previously, when configuring different Client ID, Secret, and Drive ID values for Development and Production environments on the same connector, the properties were not correctly isolated per environment type.
The connector now respects the environment type configured in the Connectivity Studio parameters when resolving file paths and connection settings. Each environment type maintains its own set of connector properties independently.
This feature was added as a result of change request 234029.
Bug fixes
Bug fixes in Release 10.0.48.73 (June 2026) of the Connectivity Studio.
Bug ID | Title | Description |
|---|---|---|
240943 (CS00239700) | BlobNotFound error when running messages with an Azure Blob Storage source connector | Resolved an issue where running a message with an Azure Blob Storage source connector returned a BlobNotFound error, even though the test connection succeeded and the file existed in storage. |
243798 (CS00240226) | Blob-related execution error in messages that use Azure Blob Storage connectors | Resolved an issue where messages using Azure Blob Storage connectors failed with a blob-related error during execution. This is related to the same root cause as bug 240943. |
241645 (CS00240065) | Single-file test fails for the Azure Blob Storage connector | Fixed an issue where performing a single file test using the Azure Blob Storage connector produced an error. Testing now correctly retrieves and processes the selected file. |
224154 (CS00239641) | CompanyInfo tracer lines are empty during message processing | Fixed an issue where tracer lines for CompanyInfo were empty, preventing proper diagnostic output during message processing. |
239201 (CS00239790) | Files without extensions cannot be processed | Resolved an issue where Connectivity Studio failed to process files that had no file extension. Files without extensions are now handled correctly during file move processing. |
239343 | Document fields can be deleted even when dependent relations exist | Resolved an issue where copying a project failed with the error "target project is blocked by version management." Project copy now works correctly regardless of the version management state of the target project. |
245829 | Copying a message to another project fails during validation | Resolved an issue where copying a message to a different project could fail during copy dialog validation. Message copy across projects now completes successfully. |
244387 (CS00240268) | File indexing errors cause message processing failures | Fixed an issue where file indexing produced errors during processing, causing message failures. |
240944 | License configuration shows ambiguous Connectivity Studio entries | Fixed an issue in license configuration where Connectivity Studio labels were shown ambiguously, causing duplicate-looking entries. Labels now clearly distinguish the base BIS configuration and Connectivity Studio configuration. |
238169 | EDIFACT output contains duplicated release characters | Resolved an issue where the release character appeared multiple times in the middle of EDIFACT output instead of being correctly removed. The release character now properly escapes the following special character and is not included in the final output. |
242766 | Project copy fails when version management is active | Resolved an issue where copying a project failed with the error "target project is blocked by version management." Project copy now works correctly regardless of the version management state of the target project. |
Known Issues
Known issues in Release 10.0.48.73 (June 2026) of the Connectivity Studio.
Issue | Description |
|---|---|
Context-sensitive help button | Connectivity Studio forms have a context-sensitive help button. Example: At this moment, the connection between the context-sensitive help button and the new documentation portal is not yet fully established. When clicking the help button, you will be redirected to the main page of Connectivity Studio in the new documentation portal. From there, you can navigate or search to find the information you need. |
Form Mapping Recorder Error | Starting the form mapping recorder can cause a fatal error. This occurs when opening the message from the BIS workspace. If you open the message from the BIS menu, the error does not occur. |
Feature Management Limitations | Microsoft regularly introduces new features via Feature Management or directly in the application. Some features are in public preview and will become generally available in future releases. Others are already generally available and can be activated. Compatibility with all new features or combinations is not tested. If issues arise after enabling a feature, contact STAEDEAN support. |
SQL Trigger Creation Error | Version 10.0.39 enables the "SQL row version change tracking" feature by default, adding the SysRowVersion field to all tables. Exclude this field from synchronization triggers in Connectivity Studio messages or web services. Do not use version 10.0.39 with a Connectivity Studio version older than 10.0.39.59. |
Inconsistent Test Results for Azure Blob Storage | In version 10.0.43.66, the Test functionality produces inconsistent results when the file action type is Azure blob storage. |
Empty File Creation on Export | When an export message fails, an empty file is created on the target storage. |
Missing File Action Detail for SFTP Import | In version 10.0.43.66, file action details are missing from file history after import when using the SFTP flow action type with the Azure file storage connector. |
Started On Date Not Updated in Project and Task History | The Started on date is not being updated in project history and task history, leading to inconsistencies in tracking. |
Open File Option Not Displaying Records in File Storage Explorer | The Open file option does not display records in the File Storage Explorer, impacting file visibility. |
Processed Tile Count Not Displayed for Four-Digit Values | In the Connectivity Studio workspace, the Today processed and 7 days processed tile counts are not displayed correctly when the count reaches four digits. |
Service Bus Dead Letter - Entering 0 Does Not Retrieve All Messages | When receiving dead letter messages from a Service Bus queue, entering 0 in the Number of messages field does not retrieve any messages. Entering a specific number works as expected. |
Incorrect Label Displayed for Certificate Upload | When uploading a certificate in the Secret reference setup, the label incorrectly shows Select private key file instead of the correct label for certificate upload. |
Accept All Warnings Not Working in Inventory and Transfer Journals | The Accept all warnings functionality does not work for inventory and transfer journals. Users may need to manually address warnings in these scenarios. |
EDI Sales Order Created with Empty EAN/GLN Code for Invoice Address | When a message is executed with an empty EAN/GLN code for the invoice address, the system allows the EDI sales order to be created without validation. This known limitation will be addressed in a future release. |
Item ID Validation Not Triggered When EDI DELFOR Journal Is Created | When an EDI DELFOR journal is created with an item ID that does not exist in D365, item ID validation rules are not triggered. The journal is created with Approved status instead of the expected Rejected status. |
Appendix
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.
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.48.73 (June 2026) – Business Integration Solutions, including Connectivity Studio.
Library | Publisher | Usage |
|---|---|---|
AS2EncryptDecryptHandler.dll | STAEDEAN | Used to encrypt and decrypt for AS2 however it is deprecated but still part of the model |
Azure.Storage.Files.Shares.dll | Microsoft | Standard .net library, the same as what D365 FSCM uses but added because D365 FSCM is not adding it to the default bin directory |
BIS.Security.OAuth2.dll | STAEDEAN | Own library used to connect to third party web api and azure blob storage |
BIS.System.Collections.dll | STAEDEAN | Own library used to connect to third party web api and azure blob storage |
BisDotNetTools.dll | STAEDEAN | Some internal .net functions used by Connectivity Studio |
BisEmail.dll | STAEDEAN | Own library wrapper for sending and receiving email |
BisEmailWrapperMailKit.dll | STAEDEAN | Own library wrapper for sending and receiving email |
BisFileCursor.dll | STAEDEAN | Own library to handle XML documents |
BisInitFromXSDSchema.dll | STAEDEAN | Own library to handle XML documents |
BisJsonReader.dll | STAEDEAN | Own library to handle JSON documents |
BisMsGraphHelper.dll | STAEDEAN | Own Library to handle connection the Share point via MSGraph |
BisNetworkShare.dll | STAEDEAN | Own library to make connection to a file storage to support direct read and write |
BisOAuth.dll | STAEDEAN | Own library used to connect to third party web API and azure blob storage |
BISODBCServiceBusClient.dll | STAEDEAN | Own library to handle the access to an on-premises database |
BisRunCustomCode.dll | STAEDEAN | Own Library to handle expression in the mapping |
BisSecureBlackBox.dll | STAEDEAN | Own Library to handle the access to use Secure Blackbox libraries |
BisServiceBusQueueHelper.dll | STAEDEAN | Own Library to handle the access to service buses / Queue |
BisStorageExtension.dll | STAEDEAN | Own library to handle the access to blobs storage use bearer tokens |
BouncyCastle.Crypto.dll | Third party | Used for AS2 and email and encryption |
BouncyCastle.Crypto.xml | Third party | Used for AS2 and email and encryption |
BytesRoad.Net.Ftp.dll | Third party | Used for sending FTP |
BytesRoad.Net.Sockets.dll | Third party | Used for sending FTP |
ClosedXML.dll | Third party | Used for excel documents |
DocX.dll | Third party | Used for Word document exports |
ICSharpCode.SharpZipLib.DLL | Third party | Used in the Zip flow action |
Microsoft.ServiceBus.dll | Microsoft | Standard .net dll used for service bus Queue |
Microsoft.WindowsAzure.Configuration.dll | Microsoft | Used for Azure blob storage is deprecated and replaced by standard azure.storage.Blobs dll |
MimeKit.dll | Third party | Use for encryption As2 and for sending email |
SecureBlackbox.Cloud.dll | Third party | All Secure blackbox dll |
SecureBlackbox.dll | Third party | All Secure blackbox dll |
SecureBlackbox.FTPS.dll | Third party | All Secure blackbox dll |
SecureBlackbox.HTTP.dll | Third party | All Secure blackbox dll |
SecureBlackbox.HTTPCommon.dll | Third party | All Secure blackbox dll |
SecureBlackbox.SFTP.dll | Third party | All Secure blackbox dll |
SecureBlackbox.SFTPCommon.dll | Third party | All Secure blackbox dll |
SecureBlackbox.SSHClient.dll | Third party | All Secure blackbox dll |
SecureBlackbox.SSHCommon.dll | Third party | All Secure blackbox dll |
SecureBlackbox.SSLClient.dll | Third party | All Secure blackbox dll |
SecureBlackbox.SSLCommon.dll | Third party | All Secure blackbox dll |
SecureBlackbox.XML.dll | Third party | All Secure blackbox dll |
System.Memory.Data.dll | Microsoft | Standard .net |
Tl.OpenXmlClr.dll | Third party | Library used for excel |
UtfUnknown.dll | Third party | Library used to detect file encoding in case dynamic encoding is used |