Find information on Release 10.0.44.68 (July 2025) of EDI Studio for Microsoft Dynamics 365 for Finance and Supply Chain Management.
Note
EDI Studio updates are released as part of the Business integration Solutions (BIS) release.
What’s new
New or changed features in Release 10.0.44.68 (July 2025) – Business Integration Solutions.
1. Customer Receipt Calendar Validation on Requested Receipt Date
A new EDI staging rule checks that the requested receipt date on the sales header is a working day per the customer’s receipt calendar. If a calendar is assigned, the system verifies that the requested date is valid. This prevents orders from being scheduled on closed days.
2. STAEDEAN Accelerator – Published New EDI Messages
The STAEDEAN Accelerator library now includes new EDI messages, accessible via the BisProject_TutorialEDI resource. Key additions:
Sales – Confirmation to XML
Sales – Delivery to XML
Sales – EDI Order to Order
Sales – Invoice to XML
Sales – XML Order to Order
Sales – XML to EDI Order
These are part of a broader update to Order-to-Cash EDI flows.
Additional updates include:
Standard messages (810, 850, 855, 865) are now included in the tutorial resource
See internal path: EDI Internal Workshops – Templates for updated message definitions
Use the “Import standard EDI tutorials from resource” action to load the latest messages
This ensures all standard order, shipment, and invoice messages are ready for both internal and customer use
Bug fixes
Bug fixes in Release 10.0.44.68 (July 2025) – Business Integration Solutions, including EDI Studio.
Bug ID | Title |
|---|---|
216725 (CS00235689) | Incorrect SQL generation for GUID fields in document queries caused partial message processing |
221513 (CS00235815) | SQL trigger recreation did not validate existing state, causing incorrect or missing trigger updates |
217119 (CS0023815) | Recreating SQL triggers across multiple projects caused deadlocks and message failures |
220070 (CS00236786) | Records with 'ValidTo = Never' date excluded from SQL export using Direct SQL connector |
221796 / 221554 (CS00237389) | Azure Blob Storage connector failed in batch mode due to unsupported SDK constructor |
221971 | Clicking 'No' on SQL trigger confirmation dialog incorrectly completed the operation |
222057 (CS00237015 / CS00236979) | 10.0.43 issue with BIS project versions gives error and no descriptions |
220270 | NoExistsJoin causes SQL syntax error in ODBC document testing |
223928 | Azure Blob connector throws SAS credential conflict error during file upload |
211179 | BisEdiCheckAddressEanCode validation ignored customer account context |
215904 | Handler BisDocumentEdifactCounterTradaComm had incorrect naming and misleading description |
217349 | File Action history with records should not display when an export message is failing |
217396 | Cross-company filter in CustomQuery does not restrict child records based on root record range |
217982 | SQL trigger creation fails on BatchJob table due to reserved keyword |
Known issues
Known issues in Release 10.0.44.68 (July 2025) – Business Integration Solutions, including EDI Studio.
Issue | Description |
|---|---|
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 |
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”. |
Appendix
Libraries
Libraries in Release 10.0.44.68 (July 2025) – 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 |