{"id":12649,"date":"2025-09-17T15:04:01","date_gmt":"2025-09-17T13:04:01","guid":{"rendered":"https:\/\/www.capcargo.com\/?page_id=12649"},"modified":"2025-09-17T15:04:01","modified_gmt":"2025-09-17T13:04:01","slug":"10-0-cap49-0-17-09-2025","status":"publish","type":"page","link":"https:\/\/www.capcargo.com\/en\/10-0-cap49-0-17-09-2025\/","title":{"rendered":"10.0-CAP49.0 (17.09.2025)"},"content":{"rendered":"
\n\n\n\n\t\n\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t
Topic<\/th>Title & Details<\/th>Release Month<\/th>Task type<\/th>ADO ID<\/th>\n<\/tr>\n<\/thead>\n
Dispatching and confirmation<\/td>
CO2 calculation (PTV, ISO 14083) - Official V1 (without Shipment builder)<\/summary>

PTV Routing API is used to calculate emissions according to the international recommended guidelines described in the GLEC framework. The globally uniform standard ISO 14083 (factor-based) has gained acceptance in the industry and replaces the European standard EN16258.
\nCAPcargo uses the above norm to calculate several emissions KPIs per tour, based on differentiated input values on several accuracy levels (actual, plan, average\u2026). From the tour the KPIs are split to transport orders and trade orders for BI, reporting and analysis reasons.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>114795<\/td>\n<\/tr>\n
Optimizer<\/td>
Adjust and enhance field validation for certain Optimizer Regulation parameters<\/summary>

Previously, when Optimizer Regulation parameters 'Driving time regulation' or 'Working time directive' were set to a value <> None, the fields 'Maximum tour duration (hr)' and 'Maximum driving time per tour (hr)' were disabled.
\nThis was possibly confusing to user, since leaving both of these fields parameterized with \"\u00d8\" zero value could result in impossibility to plan any Transport Legs via Optimizer.
\n
\nBoth fields 'Maximum tour duration (hr)' and 'Maximum driving time per tour (hr)' are now always editable. Furthermore, the Optimizer request builder was enhanced so that, in case any\/both of these fields are parameterized with zero value \"\u00d8\", then Optimizer would simply disregard them and apply the most limiting of the set Regulations parameters.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>116558<\/td>\n<\/tr>\n
Geo-services<\/td>
Introduce new 'Absolute maximum speed' field to speed profiles<\/summary>

A new field ('Absolute maximum speed') has been added to speed profiles. The value in this field acts as an absolute limiter for all speed values entered in the other speed profile fields. It also plays a role in the generation of HPRN's.
\nThe default field value is zero '\u00d8'. If zero '\u00d8', field is ignored and the values of the different speed profile fields are considered as defined.
\nThe maximum value possible in the field is 255.
\nWhenever this value is adjusted (even from the initial zero value '\u00d8'), it is highly recommended to re-generate all HPRN's defined for vehicle types using the related speed profiles, to ensure that the new maximum speed is taken into consideration.
\n
\nIt is also highly recommended to re-generate all HPRN's used on vehicle profiles at the time of the release, even if the value of this field is left at the default zero '\u00d8' (old HPRN's may have been created with a default maximum speed value of 80).<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>116102<\/td>\n<\/tr>\n
Integrations<\/td>
Unify and simplify TAL\/Optimizer xServer parameterization<\/summary>

Previously, separate fields for parameterization of the xServer url\/alive ports were dedicated both in Transport Parameters and in Optimizer parameters, even though they were all populated with the same data.
\nThe parameterization is now simplified, and all the separate fields were unified into one xServer url field under Transport Parameters > Geo services > xServer parameter. Alive port fields have been eliminated.
\n
\nThe Optimizer parameters related to xServer endpoint fields have also been removed, and when enabled, Optimizer is now using the xServer setup from main Transport Parameters.
\n
\nThe functions 'Clear xServer cloud token' and 'Check xServer health status', previously available only in the Optimizer parameters form, have been moved and are now available directly in the Transport parameters xServer settings.
\n
\nA data migration job has also been provided (see ADO 115332) to re-populate the new url field with the previously existing values.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>112919<\/td>\n<\/tr>\n
Customer Portal<\/td>
Introducing a possibility to refresh\/update portal button configuration (in D365), to include also newly adding buttons into previously existing portal button configuration templates<\/summary>

Each portal button configuration template (in D365) now can be manually synchronized, via \"Settings create \/ synchronize\" button. During synchronization, newly added buttons are added to portal button configuration template (and obsolete buttons are also removed).
\nDuring creation of new template, the synchronization happens automatically.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>115953<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Several enhancements and corrections of subcontracting request process<\/summary>

Following improvements were done to subcontracting request process:
\n - during subcontracting request creation in D365, it is now possible to set \"Carrier price requested\" for some or all new requests
\n - \"OK & Release\" button has been added to subcontracting request creation dialog, to allow direct releasing of subcontracting requests to carriers. Button is especially useful when \"Carrier price requested\" requests are being created.
\n - for \"Carrier price requested\" cases, the spot price calculation (for received price) is now performed automatically in D365 during transformation of subcontracting request into subcontracting order. Hence the manual step (with spot price calculation) is not needed anymore in D365 and can be skipped.
\n - new dispatching conflict was added (conflict ID 425 \"Process - Tour has open subcontracting requests\") - to help dispatchers better identify tours with active subcontracting requests
\n - to avoid subcontracting request discrepancies (eg. tour content is changed AFTER the subcontracting requests were released\/confirmed etc.), a new blocking mechanism was introduced - many processes are now blocked on the tour if tour contains subcontracting requests (that are in status Released\/Confirmed\/Rejected). Both in D365 'Dispatch light Tours' and also in GPB gantt screens.
\n
\nTogether with improvements, following issues were corrected:
\n - Subcontracting requests without price (ie. with flag \"Invoice=false\") could not be previously released to carriers
\n - Subcontracting order could be previously created directly even when vendor account was set as \u201eSubcontracting request = Mandatory\u201c<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>115596<\/td>\n<\/tr>\n
Customer Portal<\/td>
Rework of the order line section (for editing of existing order lines, for creation new order lines)<\/summary>

Order line editing (and creation of new lines) is now done via new dedicated dialog. Previously, the \"in grid line\" editing and creation was used (together with order line collapsible section), which was not user friendly, was buggy and hard to maintain.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>115055<\/td>\n<\/tr>\n
Customer Portal<\/td>Transport address id is now shown in address dropdowns also for public addresses<\/td>2025-09<\/td>New feature<\/td>115046<\/td>\n<\/tr>\n
Carrier Portal<\/td>On carrier portal, also the buttons on tour screen can now be managed via portal button configuration templates<\/td>2025-09<\/td>New feature<\/td>114823<\/td>\n<\/tr>\n
Customer Portal<\/td>
Better informing of the portal user, in case some errors are encountered on the portal<\/summary>

When following issues are encountered, portal users is now informed via new infologs:
\n - D365 is not accessible during portal launch (eg. D365 is offline, or D365 authentication cannot be done)
\n - D365 is accessible but portal user configuration is not finished in D365 (eg. customer assignments are missing, portal user is not existing)
\n - when no records can be displayed in the grid (because no records are fitting to active filters)
\n
\nAlso carrier portal was enhanced accordingly (eg. when no resource could be shown etc.)<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>114569<\/td>\n<\/tr>\n
Customer Portal<\/td>When price calculation fails on customer portal (because of some error in D365), the portal user is now informed via error infolog<\/td>2025-09<\/td>New feature<\/td>114344<\/td>\n<\/tr>\n
Customer Portal<\/td>
Declare certain contact details as mandatory, for new contact creation on the portal<\/summary>

Following new parameters were added to portal parameters:
\n - Customer contact first name mandatory
\n - Customer contact last name mandatory
\n - Customer contact phone mandatory
\n - Customer contact email mandatory
\n - Carrier contact first name mandatory
\n - Carrier contact last name mandatory
\n - Carrier contact phone mandatory
\n - Carrier contact email mandatory
\n
\nVia these parameters it can be specified which contact details must be filled as mandatory, when creating new contacts on the portals.
\n
\nPlease note: even when no contact details are declared as mandatory, at least one of \"First\/Middle\/Last\" names have to specified anyway.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>114072<\/td>\n<\/tr>\n
Carrier Portal<\/td>
Introducing the dangerous goods coverage also to carrier portal<\/summary>

Previously, the dangerous goods coverage was existing only in customer portal. With this task the dangerous goods are covered also in carrier portal.
\n
\nKey points:
\n - dangerous goods icons are now shown on tour & tour stop & tour order level
\n - dangerous goods overview is accessible on tour order level
\n - dangerous goods details are accessible on tour order level (the \"eye\" icon)
\n - dangerous goods report can be printed on tour order level
\n
\nUnlike to customer portal (where dangerous goods can be registered), on the carrier portal it is only possible to see existing dangerous goods - the registration of new dangerous goods in carrier portal is not supported.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>113128<\/td>\n<\/tr>\n
Depot App<\/td>
Announcing General availability (GA) of Depot app<\/summary>

After a preview period the Depot app for Android is now generally available (GA). It will replace Truck loading app which will be deprecated in the future.
\n
\nDepot app contains most of the existing Truck loading app functionality and many more features. In addition to loading and unloading the app can be used for cross-docking. The app is aware of depot locations - users can specify a depot location when unloading, and then the loaders of next tour can see where the goods are. Users can choose between available vehicles and compartments when loading (carrying resource assignment). Goods can be moved between depot locations with Pick&Put process, which can also be used for loading and unloading.
\n
\nDepot app is an online app with real time integrations to D365 data.
\n
\nDepot app is currently only distributed as an APK package, not in Google Play Store.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>117036<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Company switch feature within GPB deprecated<\/summary>

The feature to switch the current user company from the GPB start screen did not reliably work and was not supported by Microsoft anymore. The consequence was, that within GPB wrong data happened to be visualized, mainly filters would not reliably read from the proper company. Therefore the feature was removed. There is a simple work-around, to change the company within D365 per user\/worker.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>115487<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
GS: Various improvements for Level 1 icon used for subcontracting request\/order<\/summary>

Various improvements were made in the display of the level 1 icon dedicated to subcontracting requests\/orders, depending on the different process stages (request confirmation deadline active or passed, all requests answered already, some requests still open etc.).<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>114761<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Storing the quick access toolbar setup<\/summary>

The quick access toolbar setup in GPB (GST\/GSR\/OS) is now stored in a D365 table. This means that any end user customization of the quick access toolbar will be 'remembered' for future sessions and\/or future GPB versions.
\nThe 'Show quick access toolbar below the ribbon' and 'Minimize the ribbon' functions are still limited only to the currently open GPB session.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>113882<\/td>\n<\/tr>\n
Optimizer<\/td>
GS: Add context menu button 'Show optimizer tourplan' for tours generated by Optimizer<\/summary>

A new button ('Show optimizer tourplan') appears now in the right-click context menu on tours (GS). The button is enabled only when selected TMS tour was generated by Optimizer processes. Pressing it opens a browser window showing the exact tourplan which generated the tour in focus.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>111348<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Additional improvements in the display of tours originating from Optimizer processes<\/summary>

For TMS tours originating in Optimizer processes, these additional improvements were implemented:
\n - GPB tooltip shows the Optimizer tourplan ID from which selected tour originated
\n - in Dispatch Light Tour, the tour header now displays an additional Optimizer grouping, with a Tour plan ID field hyperlinked for easy access of the original Optimizer tourplan.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>111344<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GPB technical update (for newer Telerik dlls)<\/summary>

To follow the supported lifecycle and to ensure being up to par with current version of Telerik dll libraries (which are fundamentally responsible for GPB visualization), the WPF libraries were updated to version 2025.2.521, which also required updating the .NET Framework to 4.6.2 (as stated in the GPB requirements document).<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>93494<\/td>\n<\/tr>\n
Other \/ General<\/td>
Microsoft License enforcement - Adjustments CAPcargo roles<\/summary>

Microsoft is changing their license policy for Dynamics 365 Finance and Operations customers. Starting September 1st 2025 users who are not (correctly) allocated a D365 license will receive awarning, from November 1st 2025 access to D365 will be revoked. See for more information:
\n\u2192 https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/it-professional\/2025\/03\/28\/simplifying-license-management-dynamics-365\/
\n
\nWith the new features 'User security governance' and 'user security governance license usage summary report' new Microsoft tools are available to verify proper licensing. Find a report under 'System Administration\\Security\\Security governance\\Licenses usage summary' to show per security role which D365 license (SKU name) is covering the content\/access provided by this role (if the number in the column 'not entitled' is zero, it means, this license covers the role).
\nMicrosoft has changed the license requirements of some functionalities. You can find the entire Microsoft license guide here: Dynamics 365 Licensing Guide
\n
\nCAPcargo keeps providing 2 types of security roles:
\n - Roles made for pure CAPcargo processes. \u2192 Requires Microsoft \u201cTeam Member\u201d license \u2192 Concerns the majority of the CAPcargo users, example: T&L Dispatcher
\n - Roles made for CAPcargo processes interfaced with D365 standard processes. \u2192 Requires higher Microsoft license e.g. \u201cFinance\u201d, example: T&L Accounts Receivable Clerk D365
\n
\nBased on the availability of the new Microsoft security governance report, CAPcargo needed to review its security roles against the new Microsoft license requirements, and has adjusted several security roles to maintain the status quo as best as possible. With this CAP49 release, updated CAPcargo T&L security roles are shipped in order to pass the new Microsoft license enforcement. More information can be found in the CAPcargo whitepaper 'Security Roles & Licensing'.
\n
\nNote1: Between Sep 1 (warning starts) and Nov 1, your system will continue to run normally also without our fixes applied. However, after November 1 Microsoft has announced to block users without correct licensing. Hence latest until October 31st you have to install our latest release or the hotfixes we will provide shortly. Then also the warnings should disappear, and if not, you do need to check your licenses. Be aware: it can take up to 24 hours before changes made to the security roles appear in the license usage summary report. It is therefore recommended to start early with applying the CAPcargo CAP49 release resp. hotfixes for older versions allowing time for validation to ensure smooth continuance of operations on November 1st.
\n
\nNote2: If you are using customized security roles these may need to be adopted too to reflect the new license policy.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>117042<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Tour confirmation form: change the labels and help texts of empties Inflow&Outflow<\/summary>

Field \"Inflow (at address\") has been renamed to \"Unload\". The old name is now used as the help text of the field.
\nField \"Outflow (at address\") has been renamed to \"Load\". The old name is now used as the help text of the field.
\n
\nSame terminology change will be applied to Driver app in the next Driver app version (CAP50).<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>116818<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
TRO line: \"Initialize quantities from packages\" should not initialize \u00d8 zero transport quantity if packages exist<\/summary>

Previously, due to missing conversion, the transport quantity of unplanned return orders could be \u00d8 zeor, even though packages existed. This was fixed, so that number of packages and transport quantity would be the same when an unplanned return order is created.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>116707<\/td>\n<\/tr>\n
Integrations<\/td>
New data entity: TAL Item material code ship text translation<\/summary>

New data entity 'TAL Item material code ship text translation' was added to the system, it is now possible to import or export hazardous material item ship text translations.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>116377<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Small adjustment of the \"ADR\/SDR document\" report (for dangerous goods)<\/summary>

Following adjustments were done:
\n - Instead of \"Kilogram\", the \"Kg\" is printed. Instead of \"Liter\", the \"L\" is printed
\n - ADR calculated score & NEM amount is newly aligned to the left
\n - Instead of BK0\/BK1\/BK2\/BK3\/BK4, the 0\/1\/2\/3\/4 is printed
\n - contact information in report header are expanded to two lines<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>115608<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Align Dangerous goods terminology\/synchronization between TMS and D365<\/summary>

These properties were better labeled, also with help labels to understand their purpose:
\n - Environmentally hazardous
\n - Combustible goods
\n - Marine pollutant (D365) = Hazardous to water (CAPcargo)<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>115575<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Change default sorting of Packages on Transport order line<\/summary>

Previously, the Packages list on Transport order line was sorted by default from Z-A (Descending).
\nThis was now changed to A-Z (Ascending) default sorting.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>115427<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Add validation to minimum planning quantity for volume-related planning quantity<\/summary>

When transport type parameter 'Register weight information' was set to 'Yes', a validation already existed for the weight-related planning quantity, so that the value of the field would be editable, but not lower than the gross weight per transport unit * transport quantity (else a validation error was triggered).
\nSimilarly, when transport type parameter 'Register measurement information' is set to 'Yes', a validation for the volume-related planning quantity is introduced, so that the value of the field would be editable, but not lower than the volume determined by the transport unit's pre-defined measurements (else a validation error is triggered).
\nThis validation is introduced on the 'Create new transport order' form, on the existing Transport order line, and on the default order.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>115361<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Unexpected initialization of Measurements on automatically created packages on Transport order<\/summary>

Previously, even though Transport Type parameter 'Register measurement information' was set to 'No', if 'Automatic package creation' was set to 'Yes', then packages which were automatically created still had the measurements (length\/width\/height initialized from the transport unit).
\nIn this particular scenario, the measurements are now initialized with 0.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>115287<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Enhance form 'Update physical dimensions' on Packages<\/summary>

The form opened by menuitem 'Update physical dimensions' on Packages was enhanced, so that:
\n - 'Tare weight' and 'Tare volume' fields were added (previously they were missing, could not be updated on packages from this form)
\n - volume recalculation is now triggered as soon as measurement values are changed
\n - all fields related to Weights\/Measurements\/Volume were re-arranged to be consistent with the layout of corresponding fields in the Package form.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>115185<\/td>\n<\/tr>\n
Integrations<\/td>
New info message when validating imported orders (in EDI process)<\/summary>

When validating imported orders for errors, user is now informed via new infolog about result (eg. how many orders were processed). Previously, the validation process just silently finished and users have no clue what was done (and if something was done at all).<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>114919<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
'Create new tour' button in 'Dispatch directly' form was disabled even when no tours available for selection<\/summary>

Previously, in the 'Dispatch directly' form which opened from Transport order grid, the 'Create new tour' button was disabled when no tours were available for selection, while the 'Plan into tour' button was still enabled, even though no selection was available\/possible.
\nThis was fixed, so that the 'Create new tour' button is now always enabled in this form, and the 'Plan into tour' button is enabled only when at least one tour is available for selection in the 'Dispatch directly' form.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>114554<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Weight handling on Transport order line to include update to packages for weight<\/summary>

Previously, when weight-related fields (net\/tare\/gross\/unit) were updated on the transport order line (given that transport type parameter 'Register weight information' was set to Yes and packages were already created for the transport order line), the system made no attempt to update the same fields on the packages.
\nNow, when performing such an update, user automaticaly receives a dialog, asking for confirmation whether to update the data at package level as well, and doing so if confirmed. This is in line with the already-existing behavior when measurement-related fields were similarly updated.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>113177<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Validation of qualification criteria fields<\/summary>

Previously, there was no validation in the filling of qualification criteria fields, so that user could mistakenly fill multiple criteria on same line by skipping some of them (for example, select a value in Criterion 1 and 3).<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>113034<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Adjust text of UI labels from 'Depth' to 'Length'<\/summary>

Various places in TMS were labeled either 'Length' or 'Depth', even though both terms referred to the same physical dimension.
\nEven though 'Depth' is the standard text used by Microsoft for this dimension, 'Length' is now used in TAL as the generic term in Transportation&Logistics in all UI labels for this dimension. No table field labels have been touched.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>110975<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Improve handling of subcontracting orders when partial delivery is done on predecessor transport legs<\/summary>

This is a followup on predecessor ADO 108729. When partial delivery happens on a leg\/tour preceeding another successor leg\/tour already subcontracted, the subcontracting order tariff and planning quantities (from successor tour) are not affected by the quantity split.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>109697<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Company switch feature within GPB deprecated<\/summary>

The feature to switch the current user company from the GPB start screen did not reliably work and was not supported by Microsoft anymore. The consequence was, that within GPB wrong data happened to be visualized, mainly filters would not reliably read from the proper company. Therefore the feature was removed. There is a simple work-around, to change the company within D365 per user\/worker.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Deprecation<\/td>115634<\/td>\n<\/tr>\n
Optimizer<\/td>
Initialize new Process type field on TALoptJob table<\/summary>

In the 'Optimizer jobs' form, the Job process type was incorrectly set as 'Undefined' for historical records. This data migration adjusts them to proper values ('Distance matrix creation' or 'Optimization').<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Data conversion<\/td>116778<\/td>\n<\/tr>\n
Other \/ General<\/td>
Reduce xServer setup for Transport Parameters\/Optimizer processes to only one URL<\/summary>

Data migration job needed to populate the new xServer field with previous value, after changes implemented to TAL Geo services \/ Optimizer Integration setup (see ADO 112919 for more details).<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Data conversion<\/td>115332<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Two correction of address \"Geocoding by map\" process<\/summary>

Following corrections were done, in the area of address \"Geocoding by map\":
\n - improving the \"Geocoding by map\" error infolog, to better explain to user why geocoding by map cannot be done (eg. address geocoordinates are locked for editing and needs to be unlocked first).
\n - when geocoding by map was done for one time address (ie. during order creation), then the geocoordinates were previously not applied\/refreshed<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>116536<\/td>\n<\/tr>\n
Customer Portal<\/td>During order creation, new address creation was previously possible only when some address was already selected<\/td>2025-09<\/td>Bug<\/td>116806<\/td>\n<\/tr>\n
Customer Portal<\/td>
\"Empties exchange\" flag was missing in address creation dialogs<\/summary>

When creating a new address, it was previously not possible to directly activate the address for \"Empties exchange\", as the flag was not showed in address creation dialog even when activated in portal parameters.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>116516<\/td>\n<\/tr>\n
Carrier Portal<\/td>
Several issues were corrected which were happening when carrier portal was accessed via direct \"deep links\"<\/summary>

Following issues were corrected when opening a carrier portal via \"deep links\":
\n - The portal button configuration is now applied
\n - Related screen name is now highlighted in side main menu
\n - Accessibility of several buttons were corrected (eg. some buttons were not accessible even when they should)
\n - German translation of several buttons was improved<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>116346<\/td>\n<\/tr>\n
Customer Portal<\/td>
\"1900-01-01\" value in SLA \"Assigned at\" field, when editing the existing order line<\/summary>

\"Date not specified\" is now shown instead of \"1900-01-01\" date, when editing order line (for which the SLA was not assigned manually).<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115561<\/td>\n<\/tr>\n
Customer Portal<\/td>Stackability specification was previously not translated on order lines grids<\/td>2025-09<\/td>Bug<\/td>115558<\/td>\n<\/tr>\n
Carrier Portal<\/td>
Accessibility of \"Confirm\" & \"Reject\" buttons on freight offer in carrier portal was previously wrong<\/summary>

Buttons were accessible when they should not be, duplicate rejection was possible etc. The issue was corrected.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115378<\/td>\n<\/tr>\n
Customer Portal<\/td>\"Delete\" button on Claim Management \"Line\" in edit mode was not working<\/td>2025-09<\/td>Bug<\/td>115101<\/td>\n<\/tr>\n
Customer Portal<\/td>
New work instructions can be now added only \"one by one\"<\/summary>

Previously, it was accidentally possible to add several work instructions without saving, which lead to loss of work instruction (as only one could be saved, the rest went gone). The issue was corrected and new work instruction can be created only when previous is saved.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115043<\/td>\n<\/tr>\n
Customer Portal<\/td>
Order filtering via customer account was previously not reliable in customer portal (ie. some customer orders were not shown)<\/summary>

The issue was happening because together with customer account filter (which was expected) portal screen also applied a transport type filter (which was not expected). The issue was corrected and portal order screen now applies only customer account filter (if set).<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>114825<\/td>\n<\/tr>\n
Customer Portal<\/td>
Unrealiable behavior of address creation dialog, when session language was changed (via flags) during address creation<\/summary>

Several issues could have been encountered:
\n - wrong duplicate results (geocoding vs reverse geocoding)
\n - country name was sometimes translated, sometimes not<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>114821<\/td>\n<\/tr>\n
Carrier Portal<\/td>
Several buttons were accessible even when underlying feature was not activated via license configuration key<\/summary>

Following buttons were affected:
\n
\nIn the carrier portal (on tour screen):
\n - Register driver
\n - Print driving order
\n
\nIn the customer portal (on order screen):
\n - Print driving order<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>114516<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Icons for dangerous goods in GPB OS improved<\/summary>

In specific constellations the DG icons were not properly displayed. This was fixed.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>117087<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Incorrect date (1.1.0001) was previously displayed on GPB Map pin popups, after pulling the transport legs into the map via \"From OS\" button<\/td>2025-09<\/td>Bug<\/td>117085<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>SQL error \"A column has been specified more than once in the order list\" was sometimes encountered in GPB 'Transport order \/-legs\" screen<\/td>2025-09<\/td>Bug<\/td>117054<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
[GS] Level 2 tour stop black\/white line not properly updated<\/summary>

Previously, when selecting or refreshing a tour in the Gantt Screen, the tour stop black\/white line in the already open level 2 was not updated immediately to reflect the color changes from the similar line in level 1.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>116068<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
[GPB] Size of tour activity dialog not properly adapted to the size of the dynamic field (Address)<\/summary>

Previously, when the Address field in the tour activity dialog was very long due to content, the action buttons were not visible anymore. This was fixed, so that the dialog size is manually adjustable, and scroll bar also available, depending on size.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115863<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
[GPB] 'Release to depot' confirmation dialog doesn't correctly identify number of loading depots on tour<\/summary>

Previously, when pressing 'Release to depot' or 'in GPB, the popup confirmation dialog mentioned multiple loading depots, even when there was only one loading depot on tour. The proper count was fixed both in this instance, and when using 'Undo 'Release to depot'.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115512<\/td>\n<\/tr>\n
Driver App<\/td>
Collect additional orders - not working in multi company environments<\/summary>

Fixed a bug that caused errors in the process if Driver app tour was dispatched in another legal entity than the Driver app service account's default legal entity.
\nThis fix is inside D365 system, no app update needed.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115857<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Fix for creating CAPcargo shipment for deleted purchase order line<\/summary>

Previously when the an order line of an already confirmed purchase order was deleted, the system still tried to create a CAPcargo Shipment if the Disable WHS handling of purchase order lines parameter was active. This is fixed now.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115908<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Help label fix for ADRCodesSyncNeeded on CAPcargo Shipment line<\/summary>

The help label is fixed and translations are added.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115589<\/td>\n<\/tr>\n
Shipment Builder<\/td>
ADR score update after splitting off package<\/summary>

When splitting off a package from a shipment based transport order, a new transport order line is created with the split-off quantity. Previously, the ADR score was not updated on the initial and on the new transport order lines. This is fixed.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115118<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Changing dates on the transfer order line<\/summary>

Dates of the transfer order line were always updated based on the SLA setup right after changing any of the date fields manually. Ultimately, making it impossible to have manually defined dates on the transfer order line. This update issue is fixed.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115008<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Shipment builder related buttons in GPB gantt screens<\/summary>

The GPB gantt screen buttons of the new shipment builder (v3) did not work due to a technical issue. This is fixed, hence the same functionality is available in GPB gantt screens for shipment builder version 3 as we have for the previous shipment builder version.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>114828<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Transport orders with no finance impact were previously considered for standard balance calculation and credit limit check<\/summary>

Transport orders that are not planned to be invoiced from CAPcargo Transport (Invoice flag set 'false') are not anymore considered by standard credit limit calculations.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>114636<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Dispatching conflict 1243 (Qualification - missing driver qualification for trailer) was malfunctioning (conflict was not detected even when it should)<\/td>2025-09<\/td>Bug<\/td>116738<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Changing requested dates\/times doesn't work<\/summary>

Changing requested dates\/times was no longer possible in \"Change rough plan date\" dialog. This bug has now been fixed and requested dates and times can be changed in addition to changing the rough plan date.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>116553<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Transport Leg\/order directly subcontracted is still found and planned in tour by batch 'Generate\/update tour out of route\/zone'<\/summary>

Previously, Transport orders directly subcontracted or Transport legs directly subcontracted could still be found and planned on tour by the periodical function ''Generate\/update tour out of route\/zone'.
\nThis was fixed, so that all legs directly subcontracting would not be considered by this batch anymore.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>116097<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Instruction activity rules were not evaluated when using 'Generate\/Update tour out of route\/zone' (direct or batch function).<\/summary>

The manual function 'Regenerate instruction activities' was also fixed.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>116050<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Tour release could previously fail, in certain (very specific) constellation<\/summary>

The issue was happening only when releasing a tour in the following constellation:
\n - tour has subcontracted resource
\n - when track & trace status message was activated (for Status230 \"Tour released\")
\n - and Recipient was set to \"Customer and vendor\"
\n - and when status code was used in the status message setup (where the Recipient was set to \"Customer\" or \"Customer contact\")
\n
\nIf all above met then release of tour was failing with \"Object reference not set to an instance of an object\" error.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>116023<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Transport order created from default order does not initialize weights as defined in default order<\/summary>

In the context of TT parameters 'Register Measurements information' and 'Register Weight information' being set to 'Yes',
\nif specific measurements\/weights were defined on a default order, when creating a transport order from that particular default order, the measurements were correctly initialized from default order measurement values, but the weight values were not. Instead, they were initialized from the default weight values on the transport unit itself.
\nThis was fixed, so that weight is always initialized on new transport order line from the underlying default order values.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>116014<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Volume-related plan quantity initialized with wrong values while editing dimensions on Default transport order<\/summary>

Previously, on the Default transport order, during initial line creation, the volume-related planning quantity was correctly calculated based on Measurements (assuming that TT parameters 'Register Measurements information' and 'Register weight information' were set to 'Yes'). But when editing any of the weight-related dimension fields, the volume-related planning quantity would be wrongly re-initialized with value from transport unit conversion, instead of measurements.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>116012<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
'Create new packages for all order lines' does not initialize volume and weight correctly on packages<\/summary>

When Transport type parameter 'Automatic package creation' was set to 'No', then regardless of setup of TT parameters 'Register measurement information' and 'Register weight information', the volume and weight was not correctly initialized on packages created while using Transport order grid function 'Create new packages for all order lines'.
\nThis was fixed so that, if these parameters are set to 'No', then volume and weight fields on newly created packages are initialized with 0 values. If these parameters are set to 'Yes', then volume and weight fields on newly created packages are initialized from Transport order line volume and weight values.
\nThis is now in line with the behavior of those fields in case of automatic package creation.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115975<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Changing transport unit on transport order line does not change the transport unit of already-created packages<\/summary>

Previously, on a transport order line with packages already created based on an initial transport unit, if user changed the transport unit on the order line, the transport unit on the existing packages was not re-initialized.
\nThis functionality will stay the same. However, a warning infolog was added to inform the user of the discrepancy between new transport unit on the order line and existing transport unit on packages.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115973<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Transport order grid menuitem 'Package identification code' shows ALL packages, instead of the ones from order<\/summary>

Previously, when user pressed TRO grid menuitem 'Package identification code' while a particular order was selected, a list of all packages with identification codes in the system was displayed. This was now fixed, so that only the packages with identification codes from the order in focus will be displayed.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115951<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Dialog to take dimension change back to order line planning quantity is removed<\/summary>

With the introduction of measurement dimensions to TAL (ADO 94646), if packages existed on the Transport order line and user changed one of the dimension from the Transport order line, user had to answer two dialogs:
\n'Do you want to take over dimension change to packages?'
\n'Do you like to take over the qty change m3 to the order line?'
\nBy design, the second dialog was not supposed to be displayed and there is no clear logic why the user would answer 'No' to that question, regardless of how he answered the first one, when the change was initiated from the Transport order line. Therefore, the second dialog in this scenario has been suppressed, and the system behaves as if the user always answers 'Yes'.
\nThis means that any change in dimension triggered from the transport order line side will update the volume-related planning quantity only insofar as package dimensions were actually changed.
\nThere is no system impact in this scenario when Transport Type parameter 'Register measurement information' = No, or when dimensions are changed from the package side.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115868<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Fields related to subcontracting request added to subcontracting order header, but not to subcontracting request header<\/summary>

Previously, the Subcontracting request grouping of fields was added only to the subcontracting order header, with all fields open to editing.
\nThe following improvements have now been implemented:
\n - on the subcontracting order header, the subcontracting request grouping is now displayed only when the subcontracting order was generated from a subcontracting request; when shown, all fields are not editable
\n - the subcontracting request grouping of fields is now displayed on the subcontracting request header; fields are editable only when request status = Registered.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115610<\/td>\n<\/tr>\n
Subcontracting\/IC invoicing<\/td>
Vendor type validation in invoice pools could be previously manually workarounded<\/summary>

Via manual grid filter adjustment, the self-billing cases could be previously selected (and posted) in vendor invoice journal pools and vice versa. Such constellation is not supported and is now actively blocked - by disabling the removal of \"Invoice type\" filter.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115510<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Conflicts for 'Missing transport address\/address area for motor vehicle\/trailer' are displayed even when properly provided<\/summary>

Previously, conflicts with ID's 1234, 1235, 1244, 1245 ('Missing transport address\/address area for motor vehicle\/trailer') were improperly displayed during tour conflict analysis even when the requested qualifications were correctly provided.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115499<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
No qualifications-related conflict triggered when none of the resources setup with OR criteria on the qualifications framework provide that qualification (part 2)<\/summary>

In a previous release, this bug was fixed specifically for 'OR' qualification conditions setup for 'Missing qualification for Transport address' (conflict ID 121x) (see release letter notes for ADO 110340).
\n
\nThis task fixes the same scenario for the rest of the setups:
\n - illegal qualification for transport address (conflict ID 120x)
\n - missing qualification for transport order (conflict ID 122x)
\n - missing qualification for motor vehicle (conflict ID 123x)
\n - missing qualification for trailer (conflict ID 124x)
\n - missing qualification for Transport unit (conflict ID 125x)
\n - missing qualification for commodity (conflict ID 126x)
\n - illegal qualification for address area (conflict ID 127x)
\n - missing qualification for address area (conflict ID 128x)<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115492<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
'Load\/Unload scheduling date options' suggests different unload date than the actual Predispatching<\/summary>

In certain data setup constellations, it was previously possible that the actual unload date defined on the Transport leg during Predispatching was slightly different than the unload date suggested by the 'Load\/Unload scheduling date options' engine.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>115434<\/td>\n<\/tr>\n
Integrations<\/td>TAL Contract-conditioned unit conversion' data entity previously could be used only for exporting the data;, the import\/update\/delete was failing<\/td>2025-09<\/td>Bug<\/td>115053<\/td>\n<\/tr>\n
Customer Portal<\/td>Certain CUS buttons were previously available in the portal button configuration template (in D365) even though the underlying license configuration key was not activated<\/td>2025-09<\/td>Bug<\/td>115003<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>Tariff surcharge (with transport unit criteria) was previously not applied to subcontracting order during price calculation<\/td>2025-09<\/td>Bug<\/td>114723<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Weight of automatically created package during order creation initialized incorrectly<\/summary>

Previously in certain edge case scenarios, the weight of an automatically created package was wrongly initialized during order creation from another default transport unit. This meant that it was sometimes possible that even when Transport type parameter 'Register weight information' was set to false, the automatically created package weight could still be >0.
\nThis was now fixed and aligned with the manual process of package creation.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>Bug<\/td>113888<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Performance improvements in dispatching processes (GPB)<\/summary>

Many optimizations and improvements have been made in various dispatching processes. The improvements impact mainly GPB but also Dispatch light.
\n
\nImproved processes include:
\n - Loading tour data when selecting another tour in GPB Gantt screen (10-70% improvement*)<\/b>
\n - Create tour by drag&drop legs from GPB Order screen to Gantt Screen (20-50% improvement*)<\/b>
\n - Add order(s) to tour by drag&drop leg(s) from GPB Order screen to Gantt screen (20-50% improvement*)<\/b>
\n - Move tour stop to another position in the same tour by drag&drop it in GPB Gantt screen (20-40% improvement*)<\/b>
\n - Move tour stop from one tour to another tour by drag&drop it in GPB Gantt screen (20-40% improvement*)<\/b>
\n - Delete tour stop from a tour by selecting it and deleting it in GPB Gantt screen
\n - Add resource(s) to tour by drag&drop from GPB Resource screen to Gantt screen
\n - Remove resource(s) from tour by selecting them in GPB Gantt screen and deleting them
\n
\n*<\/b>=the percentages are based on tests in CAPcargo test system. Automatic distance and time calculation was disabled in the tests. Shipment builder was not used. Results in customer systems can vary based on environment sizing, data constellation, system load etc.. The percentages should be interpreted as rough indications of the relative improvement.
\nNote examples:
\n - 50% improvement means \"twice as fast\", e.g. originally 6 sec, new 3 sec.
\n - 75% improvement means \"4 times as fast\", e.g. originally 6 sec, new 1.5 sec.
\n - 16% improvement means \" 1.2 times faster\", e.g. originally 6 sec, new 5 sec.
\n
\nMore improvements will be introduced in upcoming releases.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>117040<\/td>\n<\/tr>\n
Subcontracting\/IC invoicing<\/td>
Vendor invoicing adjusted due to new MS license enforcement<\/summary>

The existing process 'receive and prepare vendor invoice' has been slightly adjusted due to the new MS license enforcement (see also 117042). - Self-billing process is not affected.
\n
\nThe clerk receiving and preparing a vendor invoice (only needing MS Team Member license) can now do so by using a new button 'CAPcargo Transport - New vendor invoice' which directly opens the CAPcargo invoice pool feature, instead of manually creating an empty journal and then fill it by means of the invoice pool. The remaining processes stays the same, the clerk who posts the journal to the ledger still needs a MS Finance license.<\/p><\/details><\/div><\/code><\/td>

2025-09<\/td>New feature<\/td>116759<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Grid cell values could not be previously copied in the GPB 'Transport orders \/-legs' screen<\/summary>

Copy-pasting cell values from the grid in the GPB 'Transport orders \/-legs' screen didn't work. It was broken by an update in \"Telerik\" component in CAP49 GPB version.<\/p><\/details><\/div><\/code><\/td>

2025-10 (CAP49.1)<\/td>Bug<\/td>117459<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Tour stop address name\/details no longer shown if there are no Dangerous goods transactions in the system<\/summary>

If the legal entity had no dangerous goods transactions (=at least one transport order that has dangerous goods in it) then the tour stop address name and other address information were not shown in the Graphical Planning Board Gantt Screens<\/p><\/details><\/div><\/code><\/td>

2025-10 (CAP49.1)<\/td>Bug<\/td>117453<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Cost\/revenue is sometimes calculated in real time even though the feature is switched off<\/summary>

A bug in caching caused cost\/revenue to be sometimes calculated in real time when loading data in Graphical Planning Board Gantt Screens, despite the real time calculation being disabled in GPB parameters.<\/p><\/details><\/div><\/code><\/td>

2025-10 (CAP49.2)<\/td>Bug<\/td>117675<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
\"Generate\/Update tour out of route\/zone\" batch doesn't find any legs and therefore doesn't create tours<\/summary>

A bugfix in CAP49 release caused a regression that prevents \"Generate\/Update tour out of route\/zone\" batch to find any transport legs. Therefore it doesn't create any tours.
\n
\nThe problematic bugfix was for 116097 Transport Leg\/order directly subcontracted is still found and planned in tour by batch \"Generate\/update tour out of route\/zone\".<\/p><\/details><\/div><\/code><\/td>

2025-10 (CAP49.2)<\/td>Bug<\/td>117658<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
\"Generate\/Update tour out of route\/zone\" doesn't create load\/unload activities<\/summary>

A regression caused by performance optimizations caused tours to lack load\/unload activities. This prevented confirming the tours via Driver app.<\/p><\/details><\/div><\/code><\/td>

2025-10 (CAP49.2)<\/td>Bug<\/td>117650<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Web browser (D365 form) launched from GPB does not work - \"An unexpected client error has occurred\"<\/summary>

When launching a web browser (D365 form) from GPB the browser displayed \"An unexpected client error has occured\", instead of navigating to the expected form.
\nThis issue started happening in all CAPcargo versions after Microsoft changed something in the standard D365 solution. Therefore this fix is published for all still supported CAPcargo versions.<\/p><\/details><\/div><\/code><\/td>

2026-02 (CAP49.3)<\/td>Bug<\/td>120279<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"","protected":false},"author":4,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"100-width.php","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"class_list":["post-12649","page","type-page","status-publish","hentry"],"yoast_head":"\n10.0-CAP49.0 (17.09.2025) - CAPcargo AG<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.capcargo.com\/en\/10-0-cap49-0-17-09-2025\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"10.0-CAP49.0 (17.09.2025) - CAPcargo AG\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.capcargo.com\/en\/10-0-cap49-0-17-09-2025\/\" \/>\n<meta property=\"og:site_name\" content=\"CAPcargo AG\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"250\" \/>\n\t<meta property=\"og:image:height\" content=\"57\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap49-0-17-09-2025\/\",\"url\":\"https:\/\/www.capcargo.com\/10-0-cap49-0-17-09-2025\/\",\"name\":\"10.0-CAP49.0 (17.09.2025) - CAPcargo AG\",\"isPartOf\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#website\"},\"datePublished\":\"2025-09-17T13:04:01+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap49-0-17-09-2025\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.capcargo.com\/10-0-cap49-0-17-09-2025\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap49-0-17-09-2025\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\/\/www.capcargo.com\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"10.0-CAP49.0 (17.09.2025)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.capcargo.com\/en\/#website\",\"url\":\"https:\/\/www.capcargo.com\/en\/\",\"name\":\"CAPcargo AG\",\"description\":\"Consulting and Software Applications for cargo industry\",\"publisher\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.capcargo.com\/en\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.capcargo.com\/en\/#organization\",\"name\":\"CAPcargo AG\",\"url\":\"https:\/\/www.capcargo.com\/en\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\/\/www.capcargo.com\/en\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg\",\"contentUrl\":\"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg\",\"width\":250,\"height\":57,\"caption\":\"CAPcargo AG\"},\"image\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/\",\"https:\/\/www.linkedin.com\/company\/capcargo-ag\/?viewAsMember=true\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"10.0-CAP49.0 (17.09.2025) - CAPcargo AG","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.capcargo.com\/en\/10-0-cap49-0-17-09-2025\/","og_locale":"en_GB","og_type":"article","og_title":"10.0-CAP49.0 (17.09.2025) - CAPcargo AG","og_url":"https:\/\/www.capcargo.com\/en\/10-0-cap49-0-17-09-2025\/","og_site_name":"CAPcargo AG","article_publisher":"https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/","og_image":[{"width":250,"height":57,"url":"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_misc":{"Estimated reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.capcargo.com\/10-0-cap49-0-17-09-2025\/","url":"https:\/\/www.capcargo.com\/10-0-cap49-0-17-09-2025\/","name":"10.0-CAP49.0 (17.09.2025) - CAPcargo AG","isPartOf":{"@id":"https:\/\/www.capcargo.com\/en\/#website"},"datePublished":"2025-09-17T13:04:01+00:00","breadcrumb":{"@id":"https:\/\/www.capcargo.com\/10-0-cap49-0-17-09-2025\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.capcargo.com\/10-0-cap49-0-17-09-2025\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.capcargo.com\/10-0-cap49-0-17-09-2025\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.capcargo.com\/en\/"},{"@type":"ListItem","position":2,"name":"10.0-CAP49.0 (17.09.2025)"}]},{"@type":"WebSite","@id":"https:\/\/www.capcargo.com\/en\/#website","url":"https:\/\/www.capcargo.com\/en\/","name":"CAPcargo AG","description":"Consulting and Software Applications for cargo industry","publisher":{"@id":"https:\/\/www.capcargo.com\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.capcargo.com\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":"Organization","@id":"https:\/\/www.capcargo.com\/en\/#organization","name":"CAPcargo AG","url":"https:\/\/www.capcargo.com\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/www.capcargo.com\/en\/#\/schema\/logo\/image\/","url":"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg","contentUrl":"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg","width":250,"height":57,"caption":"CAPcargo AG"},"image":{"@id":"https:\/\/www.capcargo.com\/en\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/","https:\/\/www.linkedin.com\/company\/capcargo-ag\/?viewAsMember=true"]}]}},"_links":{"self":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12649","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/comments?post=12649"}],"version-history":[{"count":1,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12649\/revisions"}],"predecessor-version":[{"id":12650,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12649\/revisions\/12650"}],"wp:attachment":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/media?parent=12649"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}