Find information on Release 10.0.47.72 (March 2026) 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 EDI Studio features in Release 10.0.47.72 (March 2026) - Business Integration Solutions.
1. Document Flow Validation for Delivery Forecast Journal
A validation rule has been added to the BisEdiDelforJour table to check whether a document flow exists before processing. This aligns the Delivery Forecast journal with the validation behavior available on all other EDI journal tables and enables proper EDI party validation for Delivery Forecast messages.
Previously, the absence of this check meant that Delivery Forecast journals could be processed without a configured document flow, potentially bypassing EDI party validation.
This feature was added as a result of a customer request.
2. Sales Line Name Field Initialization with Variant Items
When importing sales orders that contain items with a variant identifier (ConfigId or VariantId), the sales line Name (Text) field is now initialized with the variant-specific description. Previously, the system used the default item description rather than the description corresponding to the specific variant provided in the import file.
This ensures that the sales line accurately reflects the variant description as intended in the source EDI message.
This feature was added as a result of change request CS00238525.
3. Simplified EDI Document Flow Labels on Customer Address Page
The EDI-related labels and section heading on the customer Address page have been updated for clarity and consistency with EDI naming conventions.
The following changes were made:
Previous label → Updated label
EDI Document Flows (section heading) → Disable EDI Document Flows
Field labels for individual flows → Descriptive labels indicating the purpose, for example: "Turn on to exclude this address from the EDI confirmation document flow"
These changes make it clearer to users that toggling these fields disables the respective document flow for the address, reducing the risk of misconfiguration.
This feature was added as a result of change request CS00238961.
Bug fixes
Bug fixes in Release 10.0.47.72 (March 2026) - EDI Studio.
Bug Number | Title | Description |
|---|---|---|
238773 (CS00239683) | Address EAN code validation behavior changed after upgrade | Fixed a regression where the BisEdiCheckAddressEanCode validation rule caused errors after upgrading. The validation now correctly handles scenarios where a customer uses multiple invoice accounts and the invoice address exists under a different invoice account. |
237406 | Sales order not linked to EDI sales order | Resolved an issue where the EDI sales order button on the D365 Sales Order page did not navigate to the related EDI sales order after the journal was processed. |
235180 (CS00238697) | EDI sales journal validations skipped when customer field is empty | Fixed an issue where EDI sales journal validations did not execute when the customer account field was empty. The validation rule BisEdiCheckCustomerExist now correctly evaluates journals regardless of whether a customer account value is populated. |
Known issues
Known issues in Release 10.0.47.72 (March 2026) – EDI Studio.
Issue | Description |
|---|---|
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. |
239841 – 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. |
Release Character Appears Multiple Times in EDIFACT Output | When a release character is used in EDIFACT messages, the release character appears multiple times in the middle of the output instead of being removed. The expected behavior is that the release character escapes the following special character and is not included in the output. |
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
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.
Libraries
Libraries in Release 10.0.47.72 (March 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 |