Find information on Release 10.0.46.71 (January 2026) of the Connectivity Studio for Microsoft Dynamics 365 for Finance and Supply Chain Management.
The release notes provide information on these solutions:
Connectivity Studio
Connectivity Monitor PowerApp
Note
Connectivity Studio updates are released as part of the Business integration Solutions (BIS) release.
What’s new
New or changes Connectivity Studio features in Release 10.0.45.71 (January 2026) - Connectivity Studio.
1. Extended Character Limit for Mapping Condition Values
The SelectorValue field in the BisConMappingTable has been extended to support larger values. Previously, the field was limited to 50 characters, which restricted users when they needed to filter mappings using multiple values (such as a comma-separated list of vendor IDs). The field now uses a memo data type, removing this character limitation.
This enhancement allows users to configure mapping conditions with longer filter values without encountering field length restrictions.
This feature was added as a result of change request CS00238179.
2. File Action Support for Inbound Definitions with Connectors
Inbound definitions configured with a connector now correctly execute the source file action. Previously, when an inbound definition was set up to use a connector, the file action configured on the connector (such as Move, SFTP, or SMTP) was not triggered during processing.
The system now follows the correct file handling sequence:
Execute the file action from the origin (connector) to the inbound definition connector's working path
Move the file from the inbound definition connector's working path to the message source connector's working path
This ensures that file actions like Move, Copy, SFTP, and SMTP configured on connectors are properly executed when processing inbound definitions.
3. 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.
Bug fixes
Bug fixes in Release 10.0.45.71 (January 2026) - Connectivity Studio.
Bug ID | Title | Description |
|---|---|---|
233160 | Change company does not work correctly when target document is Ledger Journal | Resolved an issue where the ledger journal header was created in the wrong legal entity when using the Change company setup, causing a mismatch between the journal header and lines. |
229426 (CS00238104) | Incoming message using company folders causes error | Fixed an issue where the company name was appended twice to the file path when using company folders, causing a file not found error during message processing. |
231340 (CS00238402) | Importing a selected file in combination with company folders fails | Resolved the issue where importing a selected file with company folders enabled caused the file path to be incorrectly constructed. |
227322 | Web service action skips empty fields | Fixed an issue where using the V1 (non-V3) handler caused empty fields to be skipped in X12 document output. |
231339 (CS00237374) | Running BIS message manually fails when using company folders and selecting file | Resolved the file path construction issue when manually running a BIS message with company folders enabled and selecting a specific file. |
225214 | Message in Document flows cleared out after performing Get latest | Fixed an issue where messages created using the Copy function were cleared from document flows, batch job parameters, and dynamic action setup after performing Get latest in version management. |
224019 (CS00237168) | BIS message running on selection of file corrupts file name | Resolved an issue where running messages interactively and selecting a specific file from a company folder caused the system to corrupt the file name by appending the legal entity ID. |
Known issues
Known issues in Release 10.0.45.71 (January 2026) - Business Integration Solutions, including Connectivity Studio.
Issue | Description |
|---|---|
Custom Query Performance | Complex custom queries with multiple join operations may experience slower performance in high-volume scenarios. |
Cross-Company Filtering | Some filtering operations may require additional validation when working across multiple legal entities. |
File Processing Timeout | Very large file processing operations may occasionally timeout in environments with limited resources. |
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. |
Appendix
Libraries
Libraries in Release 10.0.46.71 (January 2026) – Business Integration Solutions, including EDI 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 |