New or changes EDI Studio features in Release 10.0.45.71 (January 2026) - Business Integration Solutions.

1. Bundle Outbound Queue by EDI Partner

EDI administrators can now bundle outbound EDI messages by EDI Partner instead of by individual EDI Party. This allows consolidated document delivery to corporate headquarters or central processing centers.

A new "Bundle by" field has been added to EDI Document Flows with the following options:

Option Description
EDI Party Bundle by individual EDI Party. All documents for the same EDI Party are grouped into one file. This is the default behavior.
EDI Partner Bundle by EDI Partner. All documents for EDI Parties sharing the same EDI Partner are grouped into one file. Falls back to EDI Party bundling if no EDI Partner is assigned.

Details:

  • Reduced file volume: Send a single consolidated file per EDI Partner instead of multiple files per EDI Party
  • Trading partner compliance: Meet partner requirements for centralized document processing
  • Extensibility: The "Bundle by" field is an extensible enum, allowing partners and customers to add additional bundling options

For existing configurations, the upgrade automatically sets "Bundle by" to "EDI Party" when "Bundle outbound queue by message" is enabled, preserving current behavior.

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

2. Configurable File Extension for Web Service Outbound Files

You can now configure the file extension for outbound files sent through web services. Previously, files sent via web services were always assigned an .xml extension, regardless of the actual content type (such as X12 or other EDI formats).

The system now uses the file extension based on the target document type defined in the message configuration. This ensures that files arrive at the destination with the correct extension matching their content format.

3. Original Quantity and Unit of Measure in Purchase Arrival Journal

Two new fields, Original Qty and Original Unit, are now available on the EDI Purchase Arrival page. These fields allow validation of incoming DESADV documents when vendors send quantities in different units of measure than what is defined on the purchase order.

Details:

  • Unit conversion support: When the Original Unit differs from the Purchase Order unit, the system automatically checks for and applies unit of measure conversions
  • Display methods: New display methods (purchUnit and convertedPurchQty) enable quantity conversion calculations
  • Validation rules: Two new validation rules are available:
    • BisEdiCheckPurchArrivalUnitConversion: Checks if the Original Unit can be converted to the Purchase Order unit
    • BisEdiCheckPurchArrivalOriginalUnit: Validates that the Original Unit exists in the system

The fields can be added to the page using the personalization feature. Existing users who do not use these fields are not affected.

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

4. Original Quantity and Unit of Measure in Sales Order Journal

Similar to the Purchase Arrival Journal enhancement, the EDI Sales Order Journal now includes Original Qty and Original Unit fields. When the Original Unit differs from the Sales Order unit, the system converts the quantity using the configured unit of measure conversion.

New display methods enable the conversion calculation:

  • purchUnit: Displays the unit from the source sales order
  • convertedPurchQty: Displays the converted quantity based on unit of measure conversion

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

5. EDI Transportation Tender

A new EDI Transportation Tender module enables electronic exchange of transportation tender requests with carriers. This feature integrates with the standard D365 Transportation Tender functionality.

Key capabilities:

  • Carrier setup in EDI Party: Transport carriers can be configured in EDI Party Setup, enabling EDI communication with carriers
  • Transport Carrier account code: EDI Document Flows now support Transport Carrier as an account code option
  • EDI Transportation Tender page: A new form is available under EDI > Common > EDI Transportation Tender for managing transportation tender documents
  • Validation rules: Dedicated validation rules for EDI Transportation Tender Journal ensure data integrity
  • Outbound message queue support: Transportation tender documents are processed through the standard EDI outbound message queue

This feature enables automated tender requests and responses with transportation carriers through EDI.


Provide feedback