KUMAVISION base
See also the following ChangeLogs
29.1.7452.0 - 2026-11-16
Hotfix
- Lost Permission Modify Sales Shipment Header (#19988, KBA-3284)
Indirect permissions have been added.
29.1.7433.0 - 2026-11-13
Hotfix
- Sales condition lines remain unchanged on changed sales lines "not billable" (#19859, KBA-3269)
If the Not Billable is entered, the corresponding condition lines are deleted based on the discount or price change. - Sales Condition based on the sales price are calculated using the item's price (#19971, KBA-3279)
If prices are calculated using a “Sales Condition for Sales Prices,” the item's price is no longer used to calculate the initial price. This corresponds to the old FCY functionality.
29.1.7408.0 - 2026-11-09
Hotfix
- Measures are not archived (#19266, KBA-3197)
When a complaint was archived, the action associated with it was not archived as well. This issue has been resolved. Through the Warranty Claims & Complaints Setup, you can run an action that restores old mappings in the archive once. - Validation of the Price G/L Account in a Purchasing Invoice When Linked to a Project (#19431, KBA-3213)
A change in the standard purchase price codeunit has been implemented. - BANF: Levels are not displayed (#19502, KBA-3242)
To provide a clearer overview of the purchase request, a drill-down page for the current level is now available. - Pricing using a sales condition based on the sales price does not work (#19533, KBA-3238)
Previously, the initial price for the sales condition was determined solely based on the asset in the price line found. Now, the asset from the original line is used for this purpose. This represents a gap in requirements that was previously addressed by the FCY but was not taken into account in the new implementation. - BEO - Testfields in Setup OAuth 2.0 (#19665, KBA-3254)
Fixed an issue that could prevent the activation of BEO OAuth 2.0 due to an incorrectly set TestField. - UDI: Incorrect export of Medical Product Substances in the XML (#19743, KBA-3259)
The export of the substances was checked and corrected. - Update Cancellation: Upgrade to Finished Sales Contract (#19816, KBA-3268)
The sales setup is updated in the upgrade routine after the number series has been created.
Change
- Transfer of Warenhouse Shipment No. to Sales Shipment Header (#18690, KBA-3123)
Warehouse Shipment No. and Posted Warehouse Shipment No. fields are now stored on the Sales Shipment Header, automatically populated during warehouse shipment posting, and displayed on Posted Sales Shipment pages for improved traceability and visibility. - Usability improvement: Print Line, “Change Print Line” action at Posted Documents (#18849, KBA-3140)
This change explains why the print flag is not changed for some lines. - Subscription Enhancement: Next Billing Date (#19384, KBA-3023)
You can now use a date formula (set up in the system) to calculate the next billing date, and this date will be taken into account when generating invoices. - Performance improvements (#19444, KBA-3168)
Enhanced performance when processing Item Tracking data. - Set Default Values for Not Billable at resources (#19460, KBA-3232)
As described in the item, the not billable code can now also be preset on the resource. - Resetting the Quantities in the Sales Line Upon Cancellation (#19583, KBA-3020)
In the sales setup, you can now specify whether quantities in open documents should be reset when invoices are canceled (a standard feature). - E-Document: Optionally Include Additional Texts (KUMAVISION Base) in the E-Document (#19636, KBA-3215)
The KUMAVISION base's beginning and ending texts can now be transferred to e-documents as an option. Export can be enabled in the sales setup. The text is transferred to nodes BT-22 and BT-127 as plain text. KUMAVISION base also offers functions for retrieving the text for third-party apps. However, this feature is currently implemented only for standard E-document formats. KUMAVISION base provides only the Peppol integration directly, for ZUGFeRD and XRechnung, the corresponding bridge app must be installed.
29.0.7363.0 - 2026-11-03
Hotfix
- Update Cancellation: Upgrade to Finished Sales Contract (#19816, KBA-3268)
The sales setup is updated in the upgrade routine after the number series has been created.
29.0.7297.0 - 2026-10-21
Hotfix
- Validation of the Price G/L Account in a Purchasing Invoice When Linked to a Project (#19431, KBA-3213)
A change in the standard purchase price codeunit has been implemented. - Pricing using a sales condition based on the sales price does not work (#19533, KBA-3238)
Previously, the initial price for the sales condition was determined solely based on the asset in the price line found. Now, the asset from the original line is used for this purpose. This represents a gap in requirements that was previously addressed by the FCY but was not taken into account in the new implementation.
29.0.7248.0 - 2026-10-12
Hotfix
- Measures are not archived (#19266, KBA-3197)
When a complaint was archived, the action associated with it was not archived as well. This issue has been resolved. Through the Warranty Claims & Complaints Setup, you can run an action that restores old mappings in the archive once.
29.0.7220.0 - 2026-10-06
Hotfix
- “Use in Dispatch Order” does not apply to all selected entries (#18965, KBA-3166)
The multiple selection of lines is carried over to the dispatch order. - Issue with partial shipments when invoiced in installments (Type <> Item) (#19261, KBA-3194)
For orders with partial deliveries that are also invoiced in parts, incorrect shipment are printed (Line Type <> Item). The problem was analyzed, and it was determined that only shipment with Line Type = Item should be printed. With the Event OnFindPostedShipmentDateOtherTypeUseLegacyShipmentDate the leagcy shipment date printing can be activated. - Renaming a user does not update KBA tables that have the user in a composite primary key (#19290, KBA-3201)
When a user is renamed, the records in tables KVSKBAProductionUserSetup and KVSKBACLLCallUserAuthorizGroup are also renamed.
Change
- Subscription Billing Process Document ID (#18158, KBA-2996)
The Document Process ID can now also be used in the Subscription module. - Inclusion of Bank Account from Invoice (#19072, KBA-3173)
The bank account listed on the document is now taken into account when generating a payment QR code. - Dispatch Order: Expansion of the existing “Insert Load Carrier” function (#19223, KBA-2951)
Dispatch carrier assignment has been enhanced. Standard carriers can now be defined, and items are automatically assigned to the appropriate carrier when the line is marked. - Preparation for BC29 (#19247, KBA-3160)
Scheduled features are enabled, the code is adapted to changes in the base app, and obsolete events, procedures, and objects are removed. - Optional Item Tracking in Inventory Summary (#19267, KBA-3109)
Optional Item Tracking Entries are now consolidated and displayed correctly in the Inventory Summary, aligned with standard Business Central behavior. - BC29: New Peppol App (#19325, KBA-3189)
The KBA-specific requirements have been implemented.