Skip to content

KUMAVISION trade#

See also the following ChangeLogs#

27.3.3720.0 - 2026-01-23#

Hotfix

  • Error when printing a sales invoice (#16689, TRD-1026)
    Fixed a permission error when trying to send/print a posted Sales Invoice document.

27.3.3711.0 - 2026-01-20#

Hotfix

  • Unit Cost Price List Reference is cleared when no Discount Price List is found for Purchase Line (#16584, TRD-1015)
    This change fixes an issue in the price list assignment logic where the reference to the unit cost price list was incorrectly cleared if no matching price list was found for the discount. With this fix, the unit cost price list remains intact and is no longer affected by the absence of a discount price list, ensuring correct and independent handling of both price list types.
  • Error opening the Service Item Worksheet (#16609, TRD-1010)
    If “Disable Cust. Check on Serv. Item Input” is activated in the service setup, an error occurs in the following scenario. A service order is created for a customer with a “Ship-To Code” A service item is selected that has a different customer and a different “Ship-To Code” than the service order. An error then occurs when attempting to open the Service Item Worksheet.

Change

  • Document Dispatch (#12653, TRD-652)
    This change introduces the integration of automatic document dispatch via the standard document sending profile functionality into the periodic invoicing process. In addition, five new fields have been added to posted sales invoices to provide transparency on how a document was delivered, indicating whether it was sent by email or through an electronic document exchange service, and whether it was downloaded or printed. When these indicators are set, the corresponding timestamp is automatically recorded in the “Document Sent At” field.
  • Calculation Base for Freight Cost and Minimum Order Value (#16352, TRD-987)
    The calculation base for freight costs and minimum order value have differed up to now. Freight costs based on the “Line Amount” field in the sales line, while the minimum order value was based on the “Amount” field. To standardize this, two new fields for the calculation base were created in the "Sales & Receivables Setup". One for the calculation base for freight costs and one for the calculation base for the minimum order value. “Amount” and “Line Amount” can be set in each case. The default value is the value corresponding to the previous logic: Freight costs: "Line Amount" and Minimum order value: "Amount".
  • Extensibility Request: Make "SetDocumentType" in "KVSTRDVendorPurchHistory" and "KVSTRDCustomerSales (#16448, TRD-996)
    To support the integration of the FactBoxes "Vendor History - Purchases by Vendor No." and "Customer History - Sales by Customer No." on the Vendor and Customer list pages, the previously internal procedure SetDocumentType in the pages KVSTRDVendorPurchHistory and KVSTRDCustomerSalesHistory has been made externally accessible. This change enhances extensibility and enables proper initialization of the FactBoxes when used in additional page contexts.
  • Check copy documents attachment when posting purchase order (#16461, TRD-1000)
    A change in Microsoft standard functionality introduced in BC 27.3 caused an error in some cases when a purchase order was posted that had file attachments assigned to it and the trade function “Copy Attachments to Posted Documents” was activated in the purchasing setup. The error prevented the document from being posted. This adjustment fixes the error so that these purchase documents can be posted and the attachments copied accordingly. Furthermore, the copying of attachments for correction credit memos has been adjusted.
  • Disable Validation of Field "Description" for Rental Transfer Order Line Creation (#16469, TRD-1002)
    When creating rental transfer orders, the description of the generated transfer line is now assigned directly instead of being validated. This change removes the standard logic that checks for existing items with the same description and prompts the user to confirm the use of an alternative item number. As a result, transfer lines are created without user interaction and with the originally intended description and item number of the corresponding Rental Item BoM. To allow customer-specific behavior, the event "KVSTRDOnBeforeSetDescriptionInInsertTransferLine(TransferLine, RentalItemSalesBOM, IsHandled)" has been added. By subscribing to this event, customers can decide whether the description should be set using the previous validation-based logic or handled differently according to their requirements.
  • Extensibility Request: Add events in "KVSTRDRentalManagement", "KVSTRDRentalPostingMgt", "KVSTRDRentalRedesignPostingMgt", "KVSTRDMultiRentalMgt" (#16513, TRD-1006)
    Added several events in Rental Objects.
  • Missing Value in Rental Transfer Orders (#16518, TRD-1008)
    In the Rental Tranfer Order List the value "Outbound" was not shown in the "Rental Transfer Direction" field.
  • Change Telemetry Filter (#16592, TRD-1017)
    The date filter has been removed from some telemetry signals that belong to the master data.

27.2.3634.0 - 2025-12-11#

Hotfix

  • Service Item cannot be inserted into Item Service Line by using the Lookup (#16369, TRD-984)
    When inserting a service item into a service order, the service item could be selected via the lookup, but the service item number was not transferred to the field in the service item line.

Change

  • Telemetry Signals KUMAVISION trade (#15353, TRD-898)
    Telemetry signals are sent to find out which features are used and how intensively they are used.
  • French Translation for KUMAVISION trade (#16278, TRD-978)
    The french language file (fr-FR) has been added. It is provided in accordance with the guidelines.

27.1.3598.0 - 2025-12-05#

Change

  • Improve Update Performance (#16339, TRD-986)
    The update performance has been improved in case the "trade365 Catatolg Items" feature is used and the database contains a huge number of records in the extended text table for the trade catalog items.

27.1.3591.0 - 2025-12-04#

Hotfix

  • Rental Setup: Color Configuration Controls for Rental Planner Not Rendering Correctly (On-Prem) (#16221, TRD-970)
    This update resolves an issue in the Rental Setup where the controls for configuring Rental Planner colors were displayed incorrectly in On-Premises environments. With this fix we removed the color-picker. All controls now render properly, and color configuration works as intended.
  • Transport time is not considered in a transfer line for a container transfer (#16289, TRD-981)
    This ticket fixed an error that occurred when creating a transfer order from the container page. The receipt date was calculated correctly in the header, but not in the lines.

Change

  • Enhancements to Item Sales Restrictions Pages and Variant Selection (#16247, TRD-974)
    Added the fields "Description", "Description 2", "Variant Description", and "Variant Description 2" to the pages "Prohibited Sales Countries", "Customer Specific Sales Items" and "Item Sales Restrictions". Also added "Description 2" to the "Variant Code" drop-down to provide clearer context for users. Additionally, introduced the "Customer Name" field on the "Customer Specific Sales Items" and "Item Sales Restrictions" pages.
  • Rename "Periodic Billing" to "Periodic Invoicing" (#16283, TRD-979)
    The terminology for "Periodic Invoicing" has been updated across the application. All occurrences of "Periodic Billing" have been renamed to "Periodic Invoicing" to more accurately reflect that the feature solely handles invoice generation rather than the full billing and payment process.
  • Extensibility Request: Events to Exclude Sales Lines from Automatic Shipping in Rental Periodic Invoicing (#16294, TRD-983)
    Added two new events to codeunit "KVSTRDRentalPostingMgt" procedure "SetQuantitiesToShipInSalesOrderLines" to allow selective exclusion of non-rental sales lines from automatic shipping during periodic rental invoicing: KVSTRDOnAfterSetSalesLineFiltersInSetQuantitiesToShipInSalesOrderLines(SalesLine) KVSTRDOnBeforeSetSalesLineQuantityToShipInSetQuantitiesToShipInSalesOrderLines(SalesLine, IsHandled)

27.1.3552.0 - 2025-11-27#

Hotfix

  • Alloy Surcharge cannot be inserted in purchase quote (#16241, TRD-973)
    Under certain circumstances, the error message "There is not enough space to insert all surcharge lines." appears when creating quote requests from a Planning Worksheet and the items have alloy surcharges set up.

Change

  • Set ToolTips (#15394, TRD-903)
    With the implementation of this ticket, tooltips will be provided for all fields and actions.
  • Various optimizations of Catalog-Item Functionality (#15678, TRD-926)
    We have made various optimizations and fixed some small bugs in the trade catalog item functionality.
  • Document Type in Vendor Purchase History does not match to current Document (#16195, TRD-967)
    When a tile in the Factbox "Vendor History - Buy-from" is clicked in purchase documents, the page "Vendor Purchase History" opens with the corresponding filter on the document type. If the document type filter in the header fields of this page is changed, this change is saved. As a result, when clicking a tile in a purchase document again, the page no longer opens with the expected document type but with the previously saved one. With the implementation of this ticket, the logic has been adjusted accordingly.

27.1.3528.0 - 2025-11-14#

Change

  • Price and Discount Origin in Sales and Purchase Line (#15757, TRD-908)
    In order to provide more transparency regarding the origin of prices and discounts, the solution has been extended to include references to the price lists used in both sales and purchase lines. For each line, additional information is now stored to indicate from which price list and price list line the sales or purchase price, as well as the discount, has been derived. This enhancement ensures that users can clearly trace whether a value originates from a price list and, if so, from which one. If no price list is involved in the calculation, the new fields remain empty and are cleared by code to avoid misleading information. The implementation covers all relevant tables and pages in sales and purchasing processes, including order, blanket order, invoice, credit memo and archive lines. It is important to note that this functionality is only supported for price calculation methods provided by Microsoft and KUMAVISION Base; when using third-party solutions, compatibility must be ensured with the respective provider.
  • Deprecation and Replacement of "Production Blocked" Boolean Field with New Enum Field (According to Microsoft Standard) (#15777, TRD-939)
    With the release of this ticket, the Boolean fields for "Production Blocked" has been deprecated and replaced by the corresponding standard Enum field. All existing references to the deprecated field have been updated accordingly, affecting areas such as catalog imports, catalog items and the item lifecycle. A data upgrade has also been provided to ensure compatibility and seamless migration.
  • Line split check (#15889, TRD-951)
    A new Boolean field "Line Splitted" is was inserted in the sales and purchasing line to identify lines that has been split or are created by "Split line". When the function is executed, the value is set to true. The field is not visible by default but it can be displayed by the user via personalization. The price origin and line discount origin are only temporarily set to "Manual" to prevent a new price calculation. At the end of the function, the original value is set in both lines.
  • New Events and internal removements for codeunit "KVSTRD Item Replacement Mgt." and codeunit "KVSTRD (#15931, TRD-957)
    In code of the “ Item Replacement” area, several events have been added and the “internal” flag has been removed from some functions and/or objects to make them usable from outside the KUMAVISION trade solution.
  • "Show Shipment Dates in Calendar Weeks" will not be correctly transferred from the Sales Header to new Sales Lines created by business logic (#16035, TRD-950)
    With this release, the field "Show Shipment Dates in Calendar Weeks" will now be correctly inherited from the Sales Header to all newly created Sales Lines, even when these lines are generated automatically through business logic rather than direct user input. This ensures consistent data transfer for functionalities such as freight cost calculation, minimum order value adjustments or similar automated processes. Previously, the field remained empty in such scenarios, potentially leading to inconsistent behavior unless each project implemented custom handling. The enhancement improves reliability and reduces the need for individual adjustments in these cases.
  • Manual Insert Sales Minimum Order Value for Prepayment (#16036, TRD-958)
    In the context of sales orders with activated minimum order value logic, a new action named "Add Minimum Order Value Line" has been implemented. This adjustment ensures that users can manually add a minimum order value line before releasing the sales order, enabling the correct calculation and inclusion of the minimum order amount in the prepayment invoice. The functionality is only available when the minimum order value feature is activated in the Sales & Receivables setup.
  • Event Request: Add Event After Filtering Record “Rental Item” in LookupRentalItemFromSalesLine (#16065, TRD-964)
    An event has been added to the LookupRentalItemFromSalesLine function in codeunit KVSTRDRentalRedesignManagement (5157200) to allow filtering of the "Rental Item" record before the lookup is opened. This enhancement enables external subscribers to apply custom filters to the data set shown in the lookup, ensuring more flexible and context-specific behavior based on the calling logic.
  • Wrong reservation quantity in blanket sales order (#16108, TRD-965)
    If an item has the setting “Reserve” = “Always” and is entered in a blanket sales order, the reservation entry of the blanket order line contains an incorrect quantity after an order is created for a partial quantity. This requires that "Can Reserve on Blanket Sales Orders" in the "Sales & Receivables Setup" is set to True.

27.0.3457.0 - 2025-10-13#

Hotfix

  • "Qty. to Handle"-Error when creating a Pick (#15750, TRD-930)
    This modification fixes an error that occurred when creating a pick if the "Synchronize Qty. to Handle in Whse. Activities" switch was enabled in the "Inventory Setup" and the user selected the "Do not fill quantity to handle" option on the request page.

Change

  • Add "Consumption Counter" Fields in Rental Item Card (#15531, TRD-911)
    The "Consumption Counter" fields are now shown in the rental item card. Which of the fields are displayed depends on the setting of the invoicing type field.
  • Removed logic due to removed KBA feature (KBA-1973) (#15567, TRD-918)
    Due to the removal of certain KBA fields (see KBA-1973), related application logic has been cleaned up accordingly. This includes the removal of filters and conditions referencing the now-removed field KVSKBAQtyCancelled in both transfer and rental shipment processes. The affected logic was used to distinguish between canceled and posted shipment lines. With the deprecation of the underlying KBA feature, all associated application code has been adjusted or removed to align with the updated data structure.
  • Invoice Discount and Payment Term Code in Price Information (#15721, TRD-928)
    This ticket introduces enhancements to the Customer Price Information page by adding two new fields: the "Invoice Discounts Exist" and the "Payment Terms Code" from the corresponding customer. The "Invoice Discounts Exist" field is displayed as a read-only lookup based on the customers data. Additionally, the customer's payment terms are now shown to provide further context. These fields are purely informational and do not influence any pricing or transactional logic.
  • Exclusion of Individual Customers from Minimum Profit Check (#15731, TRD-907)
    This change introduces the possibility to exclude specific customers from the Minimum Profit check. For these customers, the check will not be performed either at document level or at line level. To support this, a new flag is added to the customer card that indicates "Minimum Profit Check Disabled". During sales document release, the system evaluates this flag and skips the check accordingly. In addition, it becomes configurable whether the Minimum Profit Check and the associated order release archive should be used at all. If deactivated, no checks are executed and no release archive is generated, which helps avoid unnecessary processing and improves system performance, especially in wholesale scenarios with a high volume of daily sales orders.