10.0-CAP46.0 (26.03.2025)

The following improvements were done in form "No unique address match found at geo-coding":
- 'Evaluated results' label and filter were removed
- Add display fields for Min. score parameters (as set in Transport parameters>Geo services)
- When form is first opened, the first (top) record in the list is now selected and actively displayed on map
- When record is selected in grid, result is also highlighted on the map (red pin)
- When pin is selected on map, related record is also highlighted in grid

Due to the implementation of "Google API (new)" version, the previously existing API parameter "radius" has been replaced with "region" (ie. country of customer address) to provide better address autocomplete results, as the radius was previously limited to 50km.

Additional validation has been added to the attachment dialog, to allow new attachment upload only when the file is ready (ie. when fully processed by browser, after file selection), while disabling the upload button until then. Additionally, extra validations have been implemented in the request to ensure the file is uploaded correctly.

The order line creation process has been adjusted to auto-populate values from the fields if the order line grid is empty. Hence, it is not required anymore to create 1st order line via dedicated line grid, but order can be created directly. The line grid can still be used when more order lines are to be created in one order creation action.
Validations have also been added to the "Add New Line" button.

This concept improves order data quality and utilizes information from empties data on order line to initialize and validate input from user in regards to plan units for mass (weights) so that it equals or is higher than the combined weight of empties units combined tare weight.

When a resource leg covered a tour only partially (for example, from Tour start to some intermediate tourstop), and user extended in GS lvl 2 that resource leg to reach tour end (or tour start, as the case may be), there was no re-initialization of that tour start/end, even if parameterization would have warranted such re-init based on that resource leg. This would have been done if, for example, the same resource would have been dragged&dropped on that tour start/end from the beginning).
So, for consistency, this additional re-init was implemented even when resource legs are extended manually in lvl 2, if parameterization indicates that it should be possible to do so.

When selecting an activity in lvl2 it will now be highlighted similar to the tour stop. Additionally the corresponding tour stop will also be selected. So that the user can now easily see which tour stops and activities are associated with each other.

This update improves multi-select functionality in GPB buttons by ensuring buttons are disabled where multiselect is not supported. This ensures a clearer user experience and prevents unintended partial execution when multiple records are selected.

Reverse synchronization feature for shipment builder shouldn't be applied in Shipment builder (Unified global model). Hence, code was enhanced that this logic ignores the latest version.

License plate consolidation is a standard D365 WHS feature that merges the items on 2 license plates that are placed on a staging location. CAPcargo now supports this feature in the Shipment builder (Unified global model).
The license plate consolidation can be only used in combination with the CAPcargo custom work line. It is not supported if containers are defined on the work header or work line. Furthermore, only those license plates can be consolidated that are in the same load.

A new feature called "Block release to CAPcargo Transportation" is extended from sales orders to both transfer and purchase order headers and lines, ensuring consistent blocking behavior across order types in Shipment builder (Unified global model).

Two new parameters are introduced in Trade and Distribution parameters for transportation blocking: one for credit limit check and one for order blocking. These parameters define what is the blocking level: None, Shipment line or Transport leg. The main logic determines how shipment lines or transport legs are affected and recalculates trade line flags when the block release flag or credit management status changes, influencing shipment creation and transport leg processing, including special handling for direct deliveries where blocking cascades from the first element in the chain.

Invalid validation was added to the Block release to CAPcargo Transportation feature (see ADO Id 111401) in the Shipment builder (Unified global model).
New parameter Blocking level invalid address is introduced in Trade and Distribution parameters. It defines the level of blocking in case the trade order has an invalid address. This is the minimum configurable address validation. Additional validations can be switched on to validate whether the address is geocoded, or all the required fields of the address format are filled. A non-configurable address validation is whether the transport address is inactive. This validation is always done and not parameterizable.

A new subcontracting mode is now implemented, labeled 'Tour subcontracting'.
Resources (vehicles/drivers) cannot be setup with this new subcontracting mode.

A tour can be subcontracted in this new mode by using a new menuitem 'Create subcontracting order (Tour)', located in the existing Subcontracting group.
IF a tour is already subcontracted by using TrLeg or Resource subcontracting, it cannot be subcontracted by tour subcontracting any longer.
IF a tour is subcontractted by using tour subcontracting, no vehicles (truck/trailer/additional trailer) can be added to such a tour, only drivers (even ones which further trigger TrLeg/Resource subcontracting).

In this new subcontracting mode, the whole tour is being subcontracted to one selected vendor. From a functionality perspective (Line details, etc.) the Tour subcontracting order is very closely aligned with that of a Resource subcontracting order. In this new case, however, all tariff quantities are taken from the Tour, instead of Resource leg.

A new grouping 'Tour subcontracting' was also added to Transport Parameters>Dimensions. When setting up such dimensions, the enum value 'Tour' is also available, so that on a tour subcontracting order, the financial dimensions could also be initialized directly from the tour.

In Transport Parameters>Invoice>Invoice Transport>Accruals, a new lookup field was added 'Accruals posting (tour subcontracting)'. Default value for this field is set to 'None'.

The price calculation of subcontracting orders was also enhanced with the implementation of the 'spot price' feature (already in place for Transport orders for a long time). The functionality itself is very similar on subcontracting order as on transport order, except it uses a contract which is setup for vendor and has to be defined in a separate lookup in Transport Parameters>Pricing - Contract finding>Spot price

As a signal of the existence of a tour subcontracting order on a Tour, a new flag 'Tour subcontracting' was added to the Tour Header>Additional information>Resources group.

The mechanism for confirming this new type of subcontracting order is the same as that of Resource subcontracting order.

The 2 batches 'Statistics cost/revenue split transport order' and '-tour', depending on an advanced and inter-dependent up-to-date logic, have now a simplified filter option "Also run already calculated orders" which interprets the different flags on the relevant entities. (Before, this needed to be handled with individual filters on the relevant checkboxes).

Previously, the flag 'Release tour for departure' in 'Dispatch directly to new tour' was always set to Yes (True) by default.
A new parameter 'Release tour for departure' was now introduced in Transport Parameters>Dispatching>Tour>Tour release, by which the default value of the same flag on 'Dispatch directly to new tour' form can be controlled.
Initial value of this new general parameter will be set to Yes (True), via corresponding data migration job (see 111529)

In the current version of customer portal, the process of "adding new order line to previously existing transport order" is weaker than adding new order line during new order creation. Several issues were identified that will be addressed in R47 only, as code & GUI refactor is needed:
- When adding new order line in side detail pane, the change of transport qty seems not updating the empties qty
- The measure unit (and height/width/length) seems never initialized when collapsible section (with order line details) is expanded
- Several order line values are not initialized when collapsible section (with order line details) is collapsed

Workaround:
If automated initialize & update mechanisms fail when adding new order line to existing order, please specify the values manually.

Data migration task for 110580.

The data job should create a single record by copying the existing setup from the map profile field. This new record will be set as active.

If the default profile field is empty, the data job should insert a record with "CAPcargo" (predefined as the default) as the default map profile.

Data migration job for 112162.

When shipment lines were created via the Create/Update transport order dialog, the Direct delivery chain ID wasn't filled in case of direct delivery chain. Therefore, data migration job was created to fill in the Chain ID in case it is empty in direct delivery based shipment lines.

Data migration task for 111197.

In main transport order grid, when switching between transport orders (while having side details pane open), the attachments were previously not refreshed.

A bug has been fixed where newly uploaded (and also previously existing) work instruction attachments became invisible after uploading a new attachment to work instruction.

The issue was happening only on attachment of work instruction and was caused by not respecting work instruction attachment 'storage' specifics (ie. work instruction is a shared global table, that requires attachments to be stored in 'dat' company).

The address creation dialog was reworked/expanded, to be usable also on screens with lower resolution (eg. mobiles/tablets).

After a customer account change, the default load/unload addresses are re-initialized. If the new customer account has default load/unload addresses, they will be initialized in the dialog. If not, the load/unload fields will be emptied only if the new customer account does not have access to the previously specified addresses.

Previously when starting GSR or RS Screens, if the default Company filter value was not the exact same casing as the Company Id parameter then it would fail to initialize the Company filter and show a message saying the value does not exist.

In Order Screen, the feature Generate tour out of route/zone with applied Dispatch sector filter was not creating a tour. The feature worked without the dispatch sector filter, but failed when the filter for dispatch sector was applied.
This fix ensures the Generate tour out of route/zone button operates as expected, even when using a dispatch sector filter.

The GSR filter now correctly respects the ‘Driver’ flag even when individual drivers are selected in the lookup. Drivers are no longer shown on the Y-axis if the flag is set to false.

In GSR, when a tour had multiple assigned resources with some of them assigned partially (meaning not starting /ending at tour start/end), level 2 activities were incorrectly displayed as if the resource leg started at the tour start (resource leg ended at tour end). As a result, related tour stop highlights on level 3 were also misaligned.
With this fix, level 2 activities now correctly reflect the actual starting and ending points of the resource leg and tour stop highlight on level 3 correspond accurately to selected activity.

The dialog for 'Init tour start address' and 'Init tour end address' would always appear regardless of whether or not the 'Do not show this dialog again' checkbox was checked. This has been fixed, so it will now respect the checkbox value.

In CAP45 a bug prevented drivers from selecting a reason code for claims (Goods damaged, Vehicle damaged, General incident). No matter what was selected from the dropdown, the first value in the list ended up in the claim dialog. This has been fixed and it's again possible to specify any reason code.

The issue was caused by combination of specific events and timing of the change tracking batch.

This issue sometimes happened when all following conditions were met:
- Tour has been already sent to Driver app
- Quantity of a transport order in that tour is changed
- The transport order is removed from the tour

In CAPcargo version 44, the commodities feature has been enhanced. Part of this change was to replace the commodity name with the commodity id as the primary key. However, the shipment building criteria (string that controls which shipment lots are grouped into the same shipment / transport order, and controls which shipment lot quantities are grouped into the same transport order line) was not updated. This should have been done via a data migration job that was not delivered as part of CAPcargo version 44.

This means that if the CAPcargo shipment and/or the transport order was created before the installation of CAPcargo version 44, then after the installation of CAPcargo version 44 the transport order synchronization will fail. Such synchronization can be necessary when a transportation relevant information is changes on the trade order (sales, purchase, transfer) and when you receive feedback (contain type) from the warehouse.

Part 1: prevent creation of orphan records

Part 2: clean-up orphan records will follow in a next release with #113114

As a regression of subcontracting harmonization in some cases when subcontracting orders were deleted, their order lines were not properly removed as a cascade. This produced orphan data, which though does not do any harm. - With this task this bug was fixed, the clean-up data job will follow in any next release.

In the following scenario:
- Parameter ' Register measurements information' on Transport Type is set to 'Yes' (true)
- Transport unit to be used is setup with measurements
- both when using the 'Create new transport order' form and when adding new line to existing TRO

the Volume-related planning quantity was correctly initialized from measurements, but whenever user would afterwards alter any values related to weight (net, tare, gross, unit) or empties (quantities or units), the volume-related planning quantity would wrongly get re-initialized based on transport unit conversion.

This was now fixed, so that the volume-related planqty does not revert to conversion rates whenever measurements are enabled and defined on transport units/TT, regardless of what other non-measurement related changes are done on TRO line.

After updating D365 to Release: 10.0.42/Platform update 66, error "Object reference not set to an instance of an object" started appearing when opening various forms within Import projects in Data management. Microsoft confirmed it is an issue that they are working on, and solution status can be tracked here:
https://shorturl.at/9kfvQ

Available workarounds:
-- re-create the import data project
-- remove and add again the entities to the existing data project
-- ignore the error and continue (to be tested first if data import is not affected in some way).