10.0-CAP49.0 (17.09.2025)

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.
CAPcargo uses the above norm to calculate several emissions KPIs per tour, based on differentiated input values on several accuracy levels (actual, plan, average…). From the tour the KPIs are split to transport orders and trade orders for BI, reporting and analysis reasons.

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.
The default field value is '0'. If '0', field is ignored and the values of the different speed profile fields are considered as defined.
The maximum value possible in the field is 255.
Whenever this value is adjusted (even from the initial value '0'), 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.

It 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 '0' (old HPRN's may have been created with a default maximum speed value of 80).

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).
During creation of new template, the synchronization happens automatically.

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.

Previously, the dangerous goods coverage was existing only in customer portal. With this task the dangerous goods are covered also in carrier portal.

Key points:
- dangerous goods icons are now shown on tour & tour stop & tour order level
- dangerous goods overview is accessible on tour order level
- dangerous goods details are accessible on tour order level (the "eye" icon)
- dangerous goods report can be printed on tour order level

Unlike 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.

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.

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.
The 'Show quick access toolbar below the ribbon' and 'Minimize the ribbon' functions are still limited only to the currently open GPB session.

For TMS tours originating in Optimizer processes, these additional improvements were implemented:
- GPB tooltip shows the Optimizer tourplan ID from which selected tour originated
- 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.

Microsoft is changing their license policy forDynamics 365 Finance and Operations customers. Starting September 1st2025 users who are not (correctly) allocated a D365 license will receive awarning, from November 1st 2025 access to D365 will be revoked. Seefor more information:
→ https://www.microsoft.com/en-us/dynamics-365/blog/it-professional/2025/03/28/simplifying-license-management-dynamics-365/

With 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 coveringthe content/access provided by this role (if the number in the column 'notentitled' is zero, it means, this license covers the role).
Microsoft has changed the license requirements of somefunctionalities. You can find the entire Microsoft license guide here: Dynamics365 Licensing Guide

CAPcargo keeps providing 2types of security roles:
- Roles made for pure CAPcargo processes. → Requires Microsoft “Team Member” license → Concerns the majority of the CAPcargo users, example: T&L Dispatcher
- Roles made for CAPcargo processes interfaced with D365 standard processes. → Requires higher Microsoft license e.g. “Finance”, example: T&L Accounts Receivable Clerk D365

Based on the availability of the new Microsoft security governance report,CAPcargo needed to review its security roles against the newMicrosoft license requirements, and has adjusted several security roles tomaintain the status quo as best as possible. With this CAP49 release, updated CAPcargo T&L security roles are shipped in order to passthe new Microsoft license enforcement. More information can be found in the CAPcargo whitepaper 'Security Roles & Licensing'.

Note1: Between Sep 1 (warning starts) and Nov 1, your system will continue to runnormally also without our fixes applied. However, after November 1 Microsofthas announced to block users without correct licensing. Hence latest untilOctober 31st you have to install our latest release or thehotfixes we will provide shortly. Then also the warnings should disappear, andif not, you do need to check your licenses. Be aware: it can take up to 24hours before changes made to the security roles appear in the license usagesummary report. It is therefore recommended to start early with applying theCAPcargo CAP49 release resp. hotfixes for older versions allowing time forvalidation to ensure smooth continuance of operations on November 1st.

Note2: If you areusing customized security roles these may need to be adopted too to reflect thenew license policy.

Field "Inflow (at address") has been renamed to "Unload". The old name is now used as the help text of the field.
Field "Outflow (at address") has been renamed to "Load". The old name is now used as the help text of the field.

Same terminology change will be applied to Driver app in the next Driver app version (CAP50).

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.

These properties were better labeled, also with help labels to understand their purpose:
- Environmentally hazardous
- Combustible goods
- Marine pollutant (D365) = Hazardous to water (CAPcargo)

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).
Similarly, 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).
This validation is introduced on the 'Create new transport order' form, on the existing Transport order line, and on the default order.

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

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.
This 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.

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).

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.

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').

Following corrections were done, in the area of address "Geocoding by map":
- 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).
- when geocoding by map was done for one time address (ie. during order creation), then the geocoordinates were previously not applied/refreshed

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.

"Date not specified" is now shown instead of "1900-01-01" date, when editing order line (for which the SLA was not assigned manually).

Buttons were accessible when they should not be, duplicate rejection was possible etc. The issue was corrected.

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.

Several issues could have been encountered:
- wrong duplicate results (geocoding vs reverse geocoding)
- country name was sometimes translated, sometimes not

In specific constellations the DG icons were not properly displayed. This was fixed.

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.

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.
This fix is inside D365 system, no app update needed.

The help label is fixed and translations are added.

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.

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.

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.

The manual function 'Regenerate instruction activities' was also fixed.

In the context of TT parameters 'Register Measurements information' and 'Register Weight information' being set to 'Yes',
if 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.
This was fixed, so that weight is always initialized on new transport order line from the underlying default order values.

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'.
This 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.
This is now in line with the behavior of those fields in case of automatic package creation.

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.

Previously, the Subcontracting request grouping of fields was added only to the subcontracting order header, with all fields open to editing.
The following improvements have now been implemented:
- 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
- the subcontracting request grouping of fields is now displayed on the subcontracting request header; fields are editable only when request status = Registered.

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.

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.

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.
This was now fixed and aligned with the manual process of package creation.