TopicTitle & DetailsRelease MonthTypeID
Customer order management & pricing
Enhancements of the transport order cancellation process


The transport order cancellation logic was enhanced in order to handle the direct delivery (ie. orders with no transport leg split) correctly. The 'Failed delivery' delivery process was also adjusted accordingly (as it can trigger the transport order cancellation).

Following points were enhanced/introduced:
- Previously, the transport leg was removed from the tour regardless whether the loading has already been confirmed or not. Newly, in case the loading has already been confirmed, the system will not delete the transport leg from the tour anymore.
- The unload address of the transport leg is newly updated with the return address (as defined in the cancellation dialogue). Furthermore, the related tour stops are updated by this address too.

2021-03New feature73744
Customer order management & pricing
Extension of the 'Invoicing and delivery on hold' customer parameter


With the new ‘Allow processing/invoicing of existing transport orders’ customer parameter there is more flexibility for handling blocked customers. A new setting extends the standard customer parameter 'Invoicing and delivery on hold' and allows the user to block creation of transport orders for a certain customer, yet still allow any existing transport order to be dispatched and invoiced. The data migration entity for customers has been updated to reflect this change.

2021-03New feature73997
Customer order management & pricing
Empty invoice account on the part-invoice order


Previously, it was possible to have a part-invoice order without an invoice account. As the invoice account is mandatory for the invoicing process, it becomes newly a mandatory field already in the part-invoice order.

2021-03New feature79171
Customer order management & pricing
Feature of transport order 'header' package was deprecated


The feature of transport order 'header' package was deprecated, as the feature implementation was lacking and the feature was not used in the productive installations.
What remains (and is in main focus) is the functionality of packages linked to the transport order lines.

2021-03New feature80201
Customer order management & pricing
New feature: Pro-forma invoice for transport order, before order is invoiceable


Previously, it was possible to create (eg. print) pro-forma invoice only when transport order was invoiceable (as the pro-forma printing was existing only in the TMS customer invoice pool). Enhancement in this task introduces an option to create/print pro-forma invoice directly from the transport order form (and even for transport orders that are not yet invoiceable).

Please note:
- Pro-forma invoice can be generated/printed from the transport order form only when order is calculated.

2021-03New feature80352
Dispatching & confirmation
Deprecated functionality: 'Dispatching information' on the TMS address


Previously, the Dispatching information was defined on the TMS address, copied to the transport order header and visualized in the dispatching (both in GPB gantt screens, as well in 'Dispatch light - Tours' form). With the enhanced framework for the work instructions, the 'Dispatching information' feature is not anymore needed, as was just duplicating the work instructions, hence was deprecated.

The existing 'Dispatching information' on TMS addresses are transformed via data migration task into work instruction templates on TMS addresses.

2021-03New feature78562
Dispatching & confirmation
'Asynchronous filtering (ie. the 'Filter' menuitem) was deprecated on the GPB 'Transport orders /-legs' screen


''Filter' menuitem for asynchronous filtering in the GPB 'Transport orders /-legs' screen was removed as deprecated. The 'Filter' menuitem was originally introduced to achieve a better filtering performance of the transport leg screen, as it allowed to specify several filtering criteria and execute the filter just once (instead of executing the whole filter after setting of every criteria). It was reported by various projects that the 'Filter' menuitem had certain unforeseen side effect (ie. was conflicting with the automatic individual grid column filters), that ultimately led to user confusion. As the performance of the GPB 'Transport orders /-legs' screen was in the meanwhile enhanced by so called 'paging' feature (which ensure that only relevant fragment of resulting records is visualized on the screen), the asynchronous filtering via 'Filter' menuitem is not anymore needed and was deprecated.

2021-03New feature78579
Dispatching & confirmation
Revival of feature 'Route/cost optimization'


Previously existing feature of 'Route/cost optimization' was not working properly and was repaired by this task. Via this feature it is possible to pre-define various tour toll cost optimization models and test the tour against these models, for better tour cost comparison.

Key points:
- Route/cost models can be applied to the tour in both GPB gantt screens (in header section Dispatching, in menuitem group Geo services). There it is possible either to create a new individual set of route/cost models, or generate route/cost models from template.
- Route/cost models template creation & parameterization is done in the 'Variation template route/cost optimization' form (that is available in main menu under 'CAPcargo Transport -> Setup -> Dispatching -> Variation template route/cost optimization).
- Toll costs for each route/cost optimization model can be then calculated and compared. Selected toll cost optimization model can be then applied to the tour (where it overrules the default toll cost calculation from the map provider).
- It is also possible to visualize each optimization model in the GPB Map screen

2021-03New feature78986
Dispatching & confirmation
The implementation of the 'Unloading list' report was redesigned, to cover also the failed pickup process


Following enhancements were done for the 'Unloading list' report:
- The 'Unloading list' printing dialog now ignores/doesn't show tour stops where ALL its tour order lines are with "Failed pickup" = 'Fully failed'.
- The report itself now also doesn't print tour order lines that have "Failed pickup" = 'fully failed'.

In result, the 'Unloading list' report doesn't anymore print "dummy/zero-quantity/pre-confirmed" unload transport leg point from the failed pickup leg.

2021-03New feature79143
Dispatching & confirmation
Grid field sequence can be newly personalized in the GPB 'Transport orders /-legs' screen


Previously, the change of the grid field sequence in the GPB 'Transport orders /-legs' screen was not saved between user sessions, the screen always reset to the default grid field sequence upon next screen opening. The behavior was improved and the screen now 'remembers' the user personalized grid field sequence.

2021-03New feature79814
Dispatching & confirmation
Distorted tour stop overview in the resource swap dialog (when opened from GPB gantt screens)


Previously, when the resource swap dialog was opened from GPB gantt screens, both top grids (ie. with tour stops) were graphically distorted (ie. were occupying only a small fragment of the screen, users have to extensively scroll to see some tour stop details etc.). The resource swap dialog was enhanced, to have the similar GUI experience according to D365 dialog version.

2021-03New feature79920
Dispatching & confirmation
Implement a priority-based throttling of the GPB client, as a mandatory requirement from the D365FO hosting platform


As per April, 2021, Microsoft will start applying the priority-based throttling for the D365FO installations. Priority-based throttling prevents the over-utilization of resources to preserve the system's responsiveness and ensure consistent availability and performance for environments running Dynamics 365 Finance and Operations apps.

The purpose of priority-based throttling is to make sure that enough computing resources are left for the actual D365FO users. This is done at the expense of calls from third parties.

When throttling is applied by D365 hosting, the GPB (as a third-party element) might be also affected. In that case the GPB user is informed in the following way:
- On the main GPB screen - via red text "The [Azure] server is overloaded, please wait." in the top right corner
- On the GPB individual screens - via red bar above the GPB screens and with the message "The [Azure] server is overloaded (Code 429, Microsoft priority-based throttling). Please wait for it to get accessible again; we will try shortly again." in the red bar.

Once the throttling restriction is removed by the D365 hosting, the GPB processes are automatically continued/finished.

The encountered priority-throttling events are also listed in the Lifecycle Services Monitoring page.

2021-03New feature80113
Dispatching & confirmation
New features: Cleaning framework & Truck loading history


A new framework is introduced, that is responsible for warning the user when, where and which carrying resource needs to be cleaned. Furthermore, based on the mode of the cleaning, additional costs can be added to the tour.

Prerequisites of using the cleaning determination logic are:
- the setup of the cleaning type, that defines the way of cleaning and the efficiency of it
- the setup of the cleaning matrix, that contains the rules which determine what type of cleaning is necessary if a certain commodity was carried by the vehicle/compartment prior the current load

The aim of the logic is to determine what type of cleaning has to be done before loading goods into vehicle or compartment. This cleaning type is returned on the one hand to the conflict management – which raises a conflict by it –, on the other hand to a new form, that gives information for the user about the necessity of cleaning and provides a semi-automatic way of inserting cleaning activity/activities.

Regardless which tool is used, the goal is to insert cleaning activity/activities with the right cleaning type into existing or new cleaning specific tour stops. Such activities are not only indicators for the driver, that cleaning has to be done at pre-defined locations, but they are also used for the creation of tour additional costs automatically at the confirmation of the cleaning activity.

As an overview for the user also a new form is introduced, the Truck loading history. Via this form, the system grants always up-to-date information for the user, what activities happened with which vehicle. It depends on a new parameter of the activity master data, whether the activity is shown in the Truck loading history.

2021-03New feature80163
Dispatching & confirmation
Performance improvement of the GPB 'Transport orders /-legs' screen (introducing an individual transport leg refresh on the system level)


Previously, when some grid refresh was needed in the GPB 'Transport orders /-legs' screen, the system could only do the full refresh of the grid (ie. including the paging). By this task the refresh mechanism was improved, newly the system is capable of refreshing the individual transport legs.
The enhancement is activated immediately (and automatically) and is used by various processes of the GPB 'Transport orders /-legs' screen (ie. it cannot be called manually by user but is used internally by the GPB client).
On the frontend users should get better experience and general responsiveness when working with the GPB 'Transport orders /-legs' screen.

2021-03New feature80275
Dispatching & confirmation
Several GUI enhancements of GPB 'Transport orders /-legs' screen, in area of order 'blocking'


Following GUI enhancements were done on the GPB 'Transport orders /-legs' screen:
- New 'Blocking' checkbox filter was added to the screen, to simplify the filtering. By setting the 'Blocking' filter checkbox, the grid contains only the transport leg that are blocked
- Blocked transport leg are newly shown in red font color

2021-03New feature80316
Dispatching & confirmation
Enhance 'Simple' tour confirmation form view by new menuitems 'Confirm' & 'Undo confirmation'


Previously released new menuitems 'Confirm' & 'Undo confirmation' were only appearing in the 'Advanced' view of the tour confirmation form. This enhancement introduces both menuitems also to the 'Simple' tour confirmation form view.

2021-03New feature80322
Dispatching & confirmation
GUI rework of the 'OK' column in the tour confirmation form


In the tour confirmation form, the previously existing 'OK' column was renamed to 'Orders confirmed', to better explain the column purpose. Also the icon visualization logic was enhanced:
- when at least one tour order is not yet confirmed at the tour stop, the 'Orders confirmed' newly show no sign/icon. (Previously such state was visualized with a warning yellow 'triangle', which led to impression that there is something wrong with the tour stop. Which is not entirely correct as the tour stop confirmation might just not happened yet.)
- when all underlying tour orders are confirmed at the tour stop, the 'Orders confirmed' show the 'checked' sign/icon. (This case didn't need any enhancement as it is working according to expectation.)

2021-03New feature80331
Dispatching & confirmation
Performance driven optimization of the GPB 'Resource Dispatching' screen


Following improvements were done in the GPB 'Resource Dispatching' screen, to achieve better performance when launching the screen:
- Determination of icons (for quantity change conflict & number of drivers, in level 1 gantt bars) were moved to the web service
- Several other code adjustments

2021-03New feature80534
Dispatching & confirmation
Address area icon was sometimes not displayed in the tour stop details in both GPB gantt screens


An address area icon (that is shown on the tour stop level 3 details in both GPB gantt screen) was sometimes not visible, as it could get covered up by too long address name. The visualization of tour stop level 3 was enhanced and long address name is newly cut, to ensure that the address area icon is always visible.

2021-03New feature80564
Dispatching & confirmation
The 'i" information icon is newly displayed under tour stop (in level 3, in both GPB gantt screens) only when some work instruction exist for the tour stop


With the deprecation of the 'Dispatching information' feature, the 'i" information icon that is displayed under the tour stop (in level 3, in both GPB gantt screens) was adjusted, to appear only when there exist some work instruction for the tour stop.

2021-03New feature81261
Driver App
Display the package identification code directly in the mobile app activity


New parameter 'Show package identification' was added to the mobile app parameters, with following logic:
- When parameter 'Show package identification' is set to 'Package ID', then the mobile app activity shows only the package id (ie. previously existing functionality)
- When parameter 'Show package identification' is set to 'Package identification code', then the mobile app activity shows the package identification type (that is specified in the main TMS parameters, in Package management)

Also new information section was added to the mobile app activity details (that is shown in the mobile app when drivers click/open the activity) that shows all package identification types.
(The same information section is available in the D365, in 'Driver app tour' form, in activity details, field 'Additional information')

2021-03New feature64566
Driver App
Modification of tour stop confirmation logic, to reflect the 'non-mandatory' mobile app activities


Previously, a tour stop was considered as 'confirmed' when all underlying elements (ie. activities, orders, flags 'Arrived' and 'Time & distance confirmed') had been fully confirmed. With the introduction of 'mandatory' & 'non-mandatory' mobile app activities, the logic of when tour stop (and thus also the whole tour) is considered as 'confirmed' had to be modified.

Newly, even if there are some unconfirmed activities that are not mandatory for driver, the tour stop is to be considered as confirmed. This means that the previously existing logic (that updates tour stop to confirmed, when all activities are confirmed) was modified, to ignore activities that are not mandatory for mobile app.

The modification of the tour stop confirmation logic happens only when the license configuration key 'CAPcargo Mobile Apps - Driver App' is enabled.

2021-03New feature78802
Driver App
Logic of 'Driver app tour' export was enhanced, to cover also the cases when export fails with 'Processed with error'


As the D365 composite entities don't support change tracking, a dedicated 'change tracking' system had to be developed for mobile app tour export. Solution relies on the 'Export pending' flag, which is used as a filter in tour export, and is set to 'No' upon export.

Previously, the flag might have been set to 'No' even if there was an error in the export. This could result in missing data in the mobile app because D365 would consider the data as exported, even though the export actually failed.

Newly, the update logic is moved to another place, and the flag is updated only if the recurring data job status goes to 'Finished (successfully)'.
Additional benefit of this change is that now the status is updated only when the specific "Driver app tour" data project - specified in mobile app parameters - is executed.

Please note:
- If some project is exporting the 'Driver app tour' data via their own project (or via OData (Excel)), this will not update the status of the tours, which would also lead to missing data in the mobile app.

2021-03New feature79728
Driver App
Introduce a timestamp to the 'Review Driver app issues' form


To improve the information base for the tour confirmation process, a new field 'Timestamp' was added to the 'Review Driver app issues' form (that is available in the tour confirmation form, in 'Inquiries', only for the tours that ware submitted to the mobile app).

2021-03New feature80302
Driver App
New feature in the mobile app: Loading later


Previously, the driver could not depart from a location before all orders (and potential other activities) were fully confirmed/scanned. This sometimes does not reflect the reality (as some order might not be ready for the loading etc.). Therefore a new process was introduced to the mobile app, so that driver newly has an option to depart from the location even though not all loads are scanned. New process is activated when driver would like to depart from location (ie. driver is 'swiping off' the 'Depart' activity) and system detects that not all loads are successfully scanned. In such case the mobile app first asks the driver (whether he/she would really like to depart, as there are still some remaining activities not yet done) and in the second step asks for additional details (driver should select the 'Load later' reason code and provide some description and/or attach a photo). Afterwards the driver can depart (and continue with his trip).
During the synchronization with D365 the remaining loads are 'moved' from the current tour stop (and are assigned to the end of the current tour).

Please note:
- 'Load later' is possible only on the tour stops that are defined as TMS depots. Loading later on the customer locations is not supported.
- Certain driver attention is needed as it is supported to load later (aka. skip) only the package sets that are representing the whole transport order line. In other words, to 'load later' only one package (whereas transport order line has 4 other packages) is not supported.

2021-03New feature80490
Driver App
Respect the work instruction load code and show work instructions in the mobile app only in order related tour stops


The work instruction load code is newly respected when showing the work instructions in the mobile app. The logic is following:
- If work instruction load code is 'Load', then the work instruction is shown in the mobile app only on the tour stop(s) where loading of the transport order happens
- If work instruction load code is 'Unload', then the work instruction is shown in the mobile app only on the tour stop(s) where unloading of the transport order happens
- If work instruction load code is 'None', then the work instruction is shown in the mobile app on the tour stop(s) where loading of the transport order happens and on the tour stop(s) where unloading of the transport order happens

2021-03New feature80813
Driver App
Driver App: new app features with CAP.Transport&Logistics 10.0-CAP16.0


Terminology in D365 user interface has been updated: many forms and menu items now mention "Mobile app(s)" instead of "Driver app".

New app features:
- Load later: New reason codes in "Skip remaining activities" dialog, now supporting "Load later" feature in D365 when all the goods don't fit in the truck.
- Fix layout issue in barcode scanning dialog with small resolutions when using German language.
- After "Skip activity" or "Confirm without barcode scan" the app goes automatically back to activity list, instead of staying in activity details screen.
- Enhancements in the barcode scanning functionality will be published in the upcoming weeks in a separate app version.

2021-03New feature81063
Integrations
New data entity: TAL Distance Table


New data entity 'TAL Distance Table' was added to the system, it is now possible to import or export TMS Distance table entries.

2021-03New feature79763
Integrations
''Number of retries' in the 'Imported attachments' form was renamed to 'Import attempts', to avoid user confusion


In the 'Imported attachments' form the previously existing field 'Number of retries' was renamed to 'Import attempts", as it previously had the same label as the general parameter 'Number of retries' in the main TMS parameters, which (despite being in the same process area) serves a slightly different purpose. Main TMS parameter 'Number of retries' is a general parameter, while the 'Import attempts' is the current counter of the import attachment attempt.

2021-03New feature80029
Integrations
New data entities: TAL Default order & TAL Default order lines


New data entities 'TAL Default order' & 'TAL Default order lines' were added to the system, it is now possible to export & import TMS Default orders.

2021-03New feature80124
Integrations
New data entity: TAL Rule order collection


New data entity 'TAL Rule order collection' was added to the system, it is now possible to import or export TMS order collection rules.

2021-03New feature80125
Integrations
New data entity: TAL Rule collective invoice


New data entity 'TAL Rule collective invoice' was added to the system, it is now possible to import or export TMS invoice collection rules.

2021-03New feature80126
Integrations
New data entity: TAL Variation template lines


New data entity 'TAL Variation template lines' was added to the system, it is now possible to import or export TAL variation template route/cost optimization details.

2021-03New feature80127
Integrations
Two package related data entities were added to the system


Following package related data entities were added to the system:
- TAL Package identification codes
- TAL Package content

It is now possible to export package identification codes and package content; both data entities are allowed only for exporting.

2021-03New feature80625
Master data
Import of ASTAG distance table was previously not possible in main TMS parameters


Previously it was not possible to import ASTAG Distance table into TMS, the 'Import ASTAG Distance table' menuitem (in the main TMS parameters) was failing with some system error. The menuitem functionality was restored and can be used again.

2021-03New feature49477
Master data
New feature of address geo-coding via map


Previously, geo coding of addresses could be done ether manually (by entering geo coordinates on address level) or by using the function 'Geo-code selected address' that uses the PTV xServer interface to get the geo coordinates of the selected address. This task introduces a third option - geo-coding via map. Newly it is possible to determine the address geo-coordinates by placing a pin symbol directly inside the map component (either street or satellite view is possible). Resulting geo-coordinates are then saved to the 'Global address book' address details, with flag "Preserved". The menuitem 'Geo-coding via map' is also available directly on the TMS Address form.

Please note: the feature of geo-coding via map requires certain parameterization (in the main TMS parameters, section 'Geo services', field group 'Integrated map'), as different map provider is used.

2021-03New feature79645
Other / General
Rework of the 'Package management' license configuration key (to cover only GUI elements)


Previously, the 'Package management' license configuration key covered many various elements:
- GUI elements (eg. menuitems, forms/-form elements)
- Data elements (eg. tables, enums, extended data types etc.).

This was reworked in this task, newly only the GUI elements (ie. menuitems, forms/-form elements) are linked to the 'Package management' license configuration key; not anymore the data elements. The data elements are newly linked to the main TMS license configuration key instead.

Main reason for the rework was to still provide the option to activate/deactivate the Package management process but keep internal CAPcargo testing & maintenance efforts reasonable (and regression risks small), when Package management process is deactivated.

2021-03New feature65643
Other / General
GUI main menu change: 'Process imported attachments' periodic function was moved to new main menu path


As the periodic function for the document attachment import was recently enhanced (to cover not only the transport order documents but also the tour documents), it is newly also positioned in different place in the main menu.

Previous path:
CAPcargo Transport -> Periodic -> Transport order import -> Process imported attachments

New path:
CAPcargo Transport -> Periodic -> Document handling -> Process imported attachments

2021-03New feature80087
Other / General
Mobile app related parameters were moved from main TMS parameters into Mobile app parameters


Mobile app related parameters that were previously in main TMS parameter form were moved to the Mobile app parameters form.
Data migration job needs to be run to copy the values from Transport parameters.

2021-03New feature80712
Shipment Builder
Performance driven enhancement of the TMS specific unit conversion


The implementation of TMS specific unit conversion was altered, to improve the performance of the shipment builder related processes. The enhancement is activated immediately, has no parameterization, and (beside the improved performance of the shipment builder) has no impact on the front end.

2021-03New feature24365
Shipment Builder
Several enhancements of the 'CAPcargo Shipment lot' form


Following enhancements were done in the 'CAPcargo shipment lot' form, to provide more information to the user:
- Inventory unit was added to the left record overview pane and also to the right section (to top line)
- Fields from the left record overview pane were added also to the right section, with proper field labels

2021-03New feature56765
Shipment Builder
New feature: Direct delivery


Via introducing the new – Direct delivery chain – shipment building area, the user is enabled to generate transport orders out of linked order lines. Since mostly these linked order lines don’t have load lines or have too many load lines, the base entity of this new way of shipment building is the order line chain itself.

The main characteristics of chain based shipment building: the chain is handled as 1 entity, therefore, the transport order is linked to the whole chain; load line WHS entity is not mandatory for transport order creation; loading related information is taken from the beginning of the chain; unloading information is taken from the end of the chain.

Except the order line chain detection and the transport order creation processes are unique for the new shipment building area, essentially the chain based transport order behaves the same way in transportation as any other shipment based transport order.

Order line chains, that are handled as a direct delivery chain in CAP.Transport:
- purchase order line → sales order line (linked via delivery type Direct delivery)
- purchase order line → intercompany sales order line (linked via delivery type Direct delivery) → intercompany purchase order line (linked via intercompany trading)
- intercompany sales order line → intercompany purchase order line (linked via intercompany trading) → sales order line (linked via delivery type Direct delivery)
- intercompany sales order line → intercompany purchase order line (linked via intercompany trading)
- purchase order line → intercompany sales order line (linked via delivery type Direct delivery) → intercompany purchase order line (linked via intercompany trading) →sales order line (linked via delivery type Direct delivery)

2021-03New feature79772
Subcontracting/IC order management & pricing
New feature: Sub-contracting tour order against the vendor from the route


The enhancement allows to trigger the creation of sub-contracting tour order against a vendor defined on the route/zone. This is a typical use case for rail or other intermodal providers where costs occur for using their service (eg. train service) and where the pricing is charged by the number of resources put on the train service. The parameterization on the route allows to activate the sub-contracting tour order creation either for one individual truck (or trailer), or for the vehicle group, or for all trucks/trailers based on the route/zone configuration.
Further enhancement made in this task is that on a route/zone it is newly possible to specify the service lead time (via parameters 'Duration (days)' or 'Duration (hours)'). This improves the accuracy of the planning as a better ETA of the tour can be captured in the master data.

2021-03New feature79974
Subcontracting/IC order management & pricing
Vendor reference on the sub-contracting tour and sub-contracting transport leg (LTL) order forms


Sub-contracting tour and sub-contracting transport leg (LTL) order forms were enhanced, to store a vendor reference. The reference can be used as a primary reference throughout the transportation and vendor invoicing process.

2021-03New feature80329
Master data
Missing control menuitems for the addition (and the removal) of delivery terms, in the 'Delivery term group' form.


Previously, the addition (and also the removal) of the delivery terms was a bit troublesome in 'Delivery term group' form, as the delivery term grid didn't have dedicated control menuitems. The issue was corrected and the delivery term section contains the 'New' and 'Remove' control menuitems.


2021-03New feature80737
Integrations
Document type was added to the 'Imported attachment' form.


To improve the user understanding about which document attachments are being imported into the system, a new field 'Type' was added to the 'Imported attachments' form. Field shows the document type of the attachment.



2021-03New feature80089
Customer order management & pricing
Under certain parameterization the tariff quantity on the transport order could get removed by the system


The issue was especially happening when 'Use confirmed quantity' feature was used on the transport order, but the contract/version/relation parameterization (to use the confirmed quantity) was not set up, or when not all required order elements were confirmed. Then, instead of preserving the existing tariff quantity, the system reset the tariff quantity to zero. The issue was corrected, the tariff quantity is now updated by confirmation values only when it really should & can.

2021-03Bug78483
Customer order management & pricing
Posting profile of the surcharge invoice detail lines was sometimes updated by the order line posting profile update mechanism


Change of the posting profile on the transport order line could sometimes override also the posting profile on surcharge related invoice detail lines, even though some specific posting profile was pre-defined on the surcharge type. The issue was corrected and the change of the posting profile on the order line only updates the freight related invoice detail lines. The issue was affecting all TMS order type entities.

2021-03Bug79567
Customer order management & pricing
Wrong amount of decimal places in the unit price on the transport order line


Previously, the unit price on transport order line showed only two decimal places, despite the unit price was defined in more decimal places.
The issue was only on the GUI form level, in the price calculation the system then worked with correct amount of decimal places. The issue was corrected and the correct amount of decimal places is shown in the transport order line.

2021-03Bug79669
Customer order management & pricing
''Invoice type' was not specified on transport order when order was generated from pre-order


Previously, the 'Invoice type' was not initialized properly on the transport order when order was generated from pre-order. The issue was corrected and invoice type is not initialized correctly in pre-order process.

2021-03Bug80208
Customer order management & pricing
Update of the package identification via transport order EDI process was sometimes failing


Update of the package identification via transport order EDI process could sometimes fail, system reported an error 'Field Package unit must be filled in.' during transport order firming. The issue was corrected.

2021-03Bug80239
Customer order management & pricing
Missing control menuitems for the creation (and removal) of cause, in the TMS claim management


Previously, the adding (and also the removal) of the claim cause was a bit troublesome in the claim management form, as the cause grid didn't have dedicated control menuitems. The issue was corrected and the cause grid now contains the 'New' and 'Remove' control menuitems.

2021-03Bug80573
Customer order management & pricing
Wrong package structure after removal of last transport order line from the transport leg


Previously, when Goods management forms launched from the transport legs screens, it was possible to remove (via menuitem 'Remove') the last transport order line from the transport leg. This resulted into improper structure of packages in transport legs. The issue was corrected and the system now informs the user that it is "Not allowed to fully split last position ('1/'1)! Only partial split possible. No qty split split allowed at leg TRO1-XXXXXX '1/'1'!" and the package structure is not altered.

2021-03Bug80744
Customer order management & pricing
'Duplicate generation of 'Print labels' report


''Print labels' report was sometimes generated multiple times in the transport order form. This was especially happening when transport orders war transported via several transport legs (eg. depot split was applied). The issue was corrected and 'Print labels' report generates one report per transport order, with individual package labels on separate pages.

2021-03Bug80937
Customer order management & pricing
From/Till-times fields on transport leg points were sometimes not initialized from the transport order data


Under certain parameterization the 'From/Till'-times fields on transport leg points were sometimes not initialized for unload leg point. This was especially happening when parameter "Transport order controls/impacts rough planning" was activated on the transport type. The issue was corrected and 'From/Till'-times fields are initialized on transport leg points (that are related to load or unload addresses of the transport order).

2021-03Bug81057
Dispatching & confirmation
In both GPB gantt screens, the behavior of 'Not allowed' sign/icon (that is informing the user that it is not possible to drop tour stop to this position) was not reliable


When reordering the tour stop sequence (via drag & drop in the tour stop level 3, in both GPB gantt screens), the system dynamically validates whether the selected (ie. 'dragged') tour stop can be 'dropped' in the current mouse pointer position. If the dynamic validation is activated (eg. when dispatcher selects the unload tour stop and hovers over the position that is before the loading tour stop) the system informs him via 'Not allowed' sign/icon. Previously the behavior of 'Not allowed' sign/icon was unreliable (ie. sometimes it worked but sometimes it was not dynamically updated as the dispatcher hovered over different tour stop sequence positions). The issue was corrected.

2021-03Bug72476
Dispatching & confirmation
Order package structure could get inconsistent after certain dispatcher actions


The order package structure could get inconsistent after certain dispatcher actions. This was especially happening when a whole order line split has been performed (via 'Keep' or 'Remove' menuitems in goods management forms) on transport leg that belong to the transport order which was already geographically split (ie. had some depot splits). The behavior was corrected, now the package structure is consistent after quantity & geographical split actions.

2021-03Bug73625
Dispatching & confirmation
''Get address type' visualization tool in the GPB Map screen was sometimes not working


Under certain circumstances the visualization of address type layer on the map was working only when used for first time, the further visualization attempt showed no address types. This was especially happening when some address type element (eg. gas station) was in the meanwhile added to the tour (via drag & drop from the map screen). The issue was corrected.

2021-03Bug78985
Dispatching & confirmation
In conflict management, the vehicle (and compartment) related information was sometimes not shown properly in the Resource section


The error "Error executing code: TALWrkCtrTableTable_Extension object does not have method 'TALdsplVehicleMark'." was sometimes encountered in the conflict management (in Related information side panel, in Resource section). The issue was corrected and resource related information is now shown correctly.

2021-03Bug79153
Dispatching & confirmation
Incorrect customer wished delivery date & time in the 'hover the mouse over' tooltip window of the tour stop level 3


In both GPB gantt screens, in the 'hover the mouse over' tooltip window of the tour stop level 3, the display of the customer wished delivery date & time was sometimes not exactly corresponding to the customer wished delivery date & time (as visualized on the tour stop level 3 itself). The behavior of the 'hover the mouse over' tooltip window was corrected.

2021-03Bug79632
Dispatching & confirmation
Some sub-processes were not launched in 'Process' menuitems in both GPB gantt screens


Previously, in both GPB gantt screens, some menuitems in the 'Process' menuitem group didn't launch all sub-processes (as activated in the TMS main parameters). This was for example happening for Release tour(s). The issue was corrected and the process menuitems in both GPB gantt screens now include also all activated sub-processes.

2021-03Bug79643
Dispatching & confirmation
''Parking' addresses were sometimes not shown on the map


Some address types were not properly visualized on the GPB map screen. Addresses were either shown at all or were shown when some other address type was activated. The issue was especially happening when user switch on the visualization for Parking and was corrected.

2021-03Bug79659
Dispatching & confirmation
Assignment of the carrying resource to the tour was sometimes automatically triggered even though there was no resource specified on the tour


It was especially happening when a tour was sub-contracted with 'Transport leg sub-contracting order (LTL)'. In such cases the carrying resource assignment was failing and user was informed via warning infolog. The issue was corrected and the carrying resource assignment is triggered only when some resource is already assigned to the tour.

2021-03Bug80119
Dispatching & confirmation
Confirmed quantity (in the tour confirmation) was sometimes not initialized properly to the successor transport legs


This was especially happening when the depot split was performed after the different quantity was confirmed on the predecessor transport leg (that was already participating on some quantity split). The issue was corrected and the confirmed quantity is initialized correctly to the successor transport legs even after the depot split was performed.

2021-03Bug80133
Dispatching & confirmation
Package weight & volume was sometimes not updated from the confirmed data on the predecessor transport leg (point)


During package confirmation process, confirmed package load weight & volume amounts sometimes didn't update the weigh & volume amounts on the counterpart (ie. package unload) transport leg point, even though the parameter 'Promote confirmed quantity to successor planning leg' was activated on the transport type. This also caused that package weight & volume on any successor transport leg was not updated. The issue was corrected and the confirmed package weight & volume is now updating the further successor elements (ie. counterpart transport leg points or successor transport legs) correctly.

2021-03Bug80187
Dispatching & confirmation
Wrong planning quantity on the transport legs in certain complex business cases


Via certain dispatching actions, it was previously possible to achieve an inconsistent planning quantity structure on the transport legs. This was especially happening when certain sequence of quantity split, depot split, remove partial delivery and another depot split was performed on one transport order. The issue was corrected and is not happening anymore.

2021-03Bug80232
Dispatching & confirmation
Paging counter of total filtered records in the GPB 'Transport orders /-legs' screen was sometimes not actualized automatically


The paging counter of total filtered records in the GPB 'Transport orders /-legs' screen was sometimes not actualized automatically. So for example when dispatchers had 20 records in the grid (ie. transport legs) on one page (out of total 25 records), then when one transport leg was planned into tour, the resulting paging counter previously was showing 19 records out of 25 records. Which was not correct, as the paging counter should show 19 records out of 24 records. The issue was corrected.

2021-03Bug80314
Dispatching & confirmation
Undo tour confirmation was possible even on the already closed tours (ie. when tour was in status 'Done')


Previously introduced menuitems 'Confirm' & 'Undo confirmation' (in the tour confirmation form) didn't respect the tour status 'Done'. So it was possible to undo the tour confirmation (via menuitem) even on the tour that was already closed (ie. in tour status 'Done'). The issue was corrected and 'Confirm' & 'Undo confirmation' menuitems are now not available in the tour confirmation form, until the tour is re-opened (ie. 'Undo tour closing' is used).

2021-03Bug80318
Dispatching & confirmation
Conflict management form was sometimes not opening when conflict analysis was launched from GPB 'Transport orders /-legs' screen


In certain constellation it could happen that the conflict management form was not opened from the GPB 'Transport orders /-legs' screen, even though there were some conflicts identified. In such cases the dispatcher was only informed by infolog 'No conflicts detected.'. The issue was corrected and conflict analysis menuitem performs now correctly in the GPB 'Transport orders /-legs' screen.

2021-03Bug80453
Dispatching & confirmation
Missing screen refresh of level 3 of GPB 'Resource Dispatching' screen


After certain dispatching actions, the GPB 'Resource Dispatching' screen level 3 was not automatically refreshed (and had to be refreshed manually).
This was especially happing after following actions:
- when transport order was planned via 'drag & drop' to the GPB 'Resource Dispatching' screen
- when tour stop was manually removed

2021-03Bug80526
Dispatching & confirmation
Tour stop details were sometimes not loaded after changing the tour start (by 'drag and drop' of the whole tour) in 'Resource Dispatching' screen


When changing the tour start (by 'drag and drop' of the whole tour) in 'Resource Dispatching' screen, the tour stop details (aka. level 3) were sometimes not loaded and users just saw the 'Loading data' spinning icon. This was especially happening when only trucks were filtered in the 'Resource Dispatching' screen. The issue was corrected, the tour stop details are now loaded properly after the 'drag and drop' of the tour, even when only trucks are filtered in the 'Resource Dispatching' screen.

2021-03Bug80528
Dispatching & confirmation
''No conflict detected.' infolog was sometimes triggered on the tour even though the conflict analysis sub-process was disabled


Under certain parameterization the "No conflict detected." infolog was triggered on the tour, even though the conflict analysis sub-process was deactivated for the conflict analysis process menuitem (in the main TMS parameters). Which was a bit misleading as the conflict detection was actually not performed. The issue was corrected and the 'No conflict detected.' is populated only when conflict analysis sub-process is activated (and no conflicts are detected).

2021-03Bug80623
Dispatching & confirmation
Tours in GPB 'Resource Dispatching' screen were sometimes displayed only when the gantt view point was changed


In certain parameterization it could happen that the tours in GPB 'Resource Dispatching' screen were not immediately displayed in the gantt, but appeared only when the gantt view point was changed (eg. by scrolling the gantt to 1hr into the future or into the past). This was especially happening when '1-day' view point of gantt was used and when load date range was set to 'from 0, to 0' in GPB parameters. The issue was corrected and tours are displayed in the gantt without needing to change the gantt view point.

2021-03Bug80627
Dispatching & confirmation
Resource assignment start was sometimes wrong in the tour tooltip in GPB 'Resource Dispatching' screen


For tours that were created from default tours, the resource assignment start was sometimes wrong in the tour tooltip in GPB 'Resource Dispatching' screen (ie. the resource assignment start was shown as 01.01.01 00:00). The issue was especially happening when 'Initialize confirmed values from planned values' parameter was deactivated in the main TMS parameters. The issue was corrected and the resource assignment start is calculated correctly, regardless of the 'Initialize confirmed values from planned values' main parameter.

2021-03Bug80637
Dispatching & confirmation
In certain parameterization some dispatching processes were failing, as system could not create carrying resource assignments


Assignment of the carrying resource was sometimes failing and system reported the error 'Cannot create a record in Uld transactions (TALuldTransactionTable). Order: TO-XYZ. The record already exists.' The issue was especially happening when there were already some (but not all) tour orders assigned to the carrying resource. As the carrying resource assignment could be activated as a sub-process (of some main process, eg. tour release etc.), the whole main process was failing. The issue was corrected and the error is not anymore encountered.

2021-03Bug80654
Dispatching & confirmation
Not all elements were removed on the map when 'Clear all layers from map' was used


On the map screen, the menuitem 'Clear all layers from map' sometimes didn't remove all elements on the map. Especially the available resources (ie. which could be planned into tours) were sometimes not cleared. This issue was corrected.

2021-03Bug80681
Dispatching & confirmation
Loss of tour activities after removal of some resource from the tour


When unplanning a resource (ie. truck/trailer/driver/passenger) from the tour, in certain constellations all tour activities were also removed. This was especially happening when some cleaning related activity was used. The issue was corrected and the system removes now only the activities that are related to individual resources.

2021-03Bug81117
Dispatching & confirmation
Duplicate opening of the dialog (for the creation of the new tour) when transport leg was planned into new tour in the GPB


Previously, it could happen that when transport leg was planned in to new tour (via 'drag & drop' from the GPB 'Transport orders /-legs' screen to the 'Resource Dispatching' screen, the dialog (for the creation of the new tour) was opened twice. The issue was corrected and the dialog 'for the creation of the new tour) is not duplicated anymore.

2021-03Bug81119
Dispatching & confirmation
GPB gantt screens were sometimes not automatically refreshed after certain dispatching actions


After certain dispatching actions, the GPB gantt screens were sometimes not automatically refreshed (and had to be refreshed manually).
This was especially happing after following actions:
- when new tour stop was manually insert into tour
- when sequence of tour stops was changed via drag & drop
- when carrying resource was assigned
- when tour stop split was performed
- when tour additional costs were created
- when new sub-contracting order was created (either tour sub-contracting, or transport leg sub-contracting, or intercompany order)

2021-03Bug81263
Dispatching & confirmation
Correction of the 'Owner' filter in the GPB 'Resource Dispatching' screen


Previously, in the GPB 'Resource Dispatching' screen, the 'Owner' filter was applied against the owner of the tour. This was not correct and was adjusted. Newly, the 'Owner' filter is applied against the owner of the resource.

2021-03Bug81283
Driver App
Several issues in the area of tour stop sequence synchronization between D365 TMS and mobile app


Following issues were fixed in the area of tour stop sequence synchronization between D365 TMS and mobile app:
- Change of the tour stop sequence in the D365 was not sometimes reflected correctly in the mobile app
- In mobile app, the changed tour stops are highlighted/marked, so that driver can easily recognize where the change happened. The issue was that the highlight/marking mechanism was not reliable, especially when tour stops were changed because of the tour stop sequence change in D365

Both issues were corrected.

2021-03Bug80271
Driver App
Filtering option was not usable in the 'Review Driver app issues' form


For the tours that are submitted to Driver app, it is possible to open 'Review Driver app issues' form in the tour confirmation. The issue was that the default filtering was not working on the 'Review Driver app issues' form. The issue was corrected.

2021-03Bug80299
Driver App
Activity feedback was sometimes failing when the driver decided to skip a mobile app activity of type 'Take a picture'


In mobile app, skipping the activity for taking a picture (and providing a reason description for skipping) could get wrongly interpreted when synchronizing the activity feedback back to D365 TMS. As the system was previously trying the process the provided reason description as the taken picture itself. The issue was corrected and the provided reason description (for skipping the activity 'Take a picture') is handled correctly now.

2021-03Bug80583
Driver App
Sequence and handling of activities was sometimes not correct in the mobile app


Issues was especially happening when activities per address area were used (eg "Scan barcode: Address area"). Then following (faulty) behavior could be encountered in the mobile app:
- Activities with duplicate sequence
- Load/unload without parent activity id even if they belong to address area

Both issues were corrected.

2021-03Bug81079
Driver App
Several 'Reason code' related issues were solved in the mobile app interface


Following 'Reason code' related issues were solved in the mobile app interface. Issues were mostly happening when the asynchronous change tracking mode was activated in the general mobile app parameters:
- Newly created 'Transport order cancellation reason codes' & 'Claim codes' were sometimes not automatically synchronized to the mobile app
- Manual re-generation of the newly released mobile app reason codes (ie. via 'Settings create/synchronize' on the 'Driver app reason code' form) was sometimes failing

Both issues were corrected.

2021-03Bug81272
Driver App
Full failed pickup (performed in mobile app) sometimes failed to synchronize to D365


When the full failed pickup was performed in the mobile app then sometimes the synchronization to D365 failed and activity feedback in D365 remained unprocessed. This was especially happening when transport type parameter 'Retry after failed pick-up' was set to 'None'. The issue was corrected and the full failed pickup is process regardless of the 'Retry after failed pick-up' parametrization.

2021-03Bug81303
Integrations
EDI process tried to update transport order address (ie. via EDI update message) even though the address update was not allowed


Previously, the EDI import process sometimes tried to update a transport order address even though the address update mechanism was not activated in the EDI Import process. Such update was failing during the firming of transport order (due to certain error in the address handling), but should not happen at all. The issue was corrected and EDI update of transport order address happens only when it is activated.

2021-03Bug80237
Integrations
Transport order EDI import process sometimes failed when import file contained TMS address id (or TMS address id was mapped via external codes)


Under certain parameterization (and data constellation) the transport order import process was failing and transport orders could get imported only with manual intervention of user. This was especially happening when a general zip code validation was activated in the D365 address setup and the import EDI file contained either exact TMS address id (or the TMS address id was achieved via external code mapping). The issue was corrected.

2021-03Bug80587
Master data
Tariff zone lines with certain characters could not be imported into 'Simple' tariff zones


In certain data constellation it was not possible to import tariff zone lines into TMS even when the target tariff zone was set to "Simple" setup type. This was especially happening when some address element (eg. city) contained some special character (eg. St. Gallen). System then wrongly classified such zone definition as "Advanced" and didn't allow the import into "Simple" tariff zones. The validation mechanism was re-worked and system now validates for 'Advanced' tariff zones only following special characters:
, (comma)
* (asterisk)
.. (double dot)
< (less than)
> (greater than)
? (question mark)
: (colon)
! (exclamation mark)

2021-03Bug80050
Master data
Missing validation of transport unit (and planning/tariff units) in several forms


When defining a transport unit (in the transport type form) the system correctly validated the transport unit selection (via lookup). But when typing the transport unit manually it was still possible to save a record (even though the "typed in" transport unit didn't exist in the transport unit master table). Similar issue was happening with different fields (eg. unit ID in the transport type form, planning units in the transport type form, tariff units in the contract/version/relation forms etc.). The issue was corrected, the transport unit (and other units) are now validated even when being typed in manually.

2021-03Bug80295
Master data
Barcode scanning activities could not be created


Creation of new activities of action types 'Barcode scan (address area)' or 'Barcode scan (address)' was previously not possible, system failed with an error. The issue was corrected and new barcode scanning activities can be created.

2021-03Bug80440
Other / General
Several qualification related menuitems were missing a security parameterization


Following qualification related menuitems were missing a security parameterization, so the menuitems could be used only by users with 'System administrator' role:
- Menuitem 'Vehicle qualifications' on the TMS Vehicle form
- Control menuitems 'New', 'Edit', 'Save' on the 'Qualification transport unit' form

2021-03Bug79334
Other / General
Mobile app global parameters (TALdraGlobalParameters) table was set global (SaveDataPerCompany: No)


Mobile app parameters form shows data from this table.

This table was intended to be global, but was accidentally left as company specific. One D365 system is always using one Driver app middleware even if Driver app is used in multiple legal entities. This table contains technical settings related to the integrations with the middleware, therefore it makes sense to store the data globally, not having to set it up for each company separately.

(For storing the information that should be controlled per legal entity, there exists already a non-global table, also shown in Mobile app parameters form.)

2021-03Bug80376
Subcontracting/IC invoicing
Wrong posting profile on the 'Tour sub-contracting order (FTL)'


The posting profile finder (that is responsible for finding a posting profile for order lines) was previously not respecting the owner of the 'Tour sub-contracting order (FTL)'. So it could happen that 'Tour sub-contracting order (FTL)' was allocated with the posting profile that was defined for some other owner company. The issue was corrected and the owner criteria is respected in the posting profile finder also in the 'Tour sub-contracting order (FTL).

2021-03Bug80149
Other / General
Data migration task - to fill the empty invoice account on part-invoice orders


Data migration job for 79171.
Data migration task fills the invoice account on part-invoice orders (and on collective part-invoice orders), if no invoice account was specified.

2021-03Data conversion80407
Other / General
Data migration task - to set a new flag 'Driver app' on all existing driver app users


Data migration task for the upcoming feature of truck loading app. Data migration task populates the flag 'Driver app' on all existing driver app users.

2021-03Data conversion80509
Other / General
Data migration task - to update the WHS reference type of the shipment log quantity buffer


Data migration task for 77606 (Connect container structure to shipment builder), which was released already in TMS 10.0-CAP15.0 release.
Shipment builder related data migration task sets the picking reference on shipment lot quantity to license plate id.

2021-03Data conversion80524
Other / General
Data migration task - to remove duplicate Mobile app global parameters (TALdraGlobalParameter) entries


Data migration task for 80376.
Data migration task finds & removes the duplicate entries in the TALdraGlobalParameter table, after the table was set global.

2021-03Data conversion80707
Other / General
Data migration task - to move the mobile app related parameters from main TMS parameters into mobile app parameters


Data migration task for 80712.
Data migration task moves the mobile app related parameters from main TMS parameters into mobile app parameters.

2021-03Data conversion80720
Other / General
Data migration task - to migrate existing 'Dispatching information' on TMS addresses to work instruction templates on TMS addresses


Data migration task for 78562.
Data migration task migrates existing 'Dispatching information' on TMS addresses to work instruction templates on TMS addresses.

2021-03Data conversion80751
Other / General
Data migration task - to recreate the tour activities after the resource was removed from the tour


Data migration task for 81117.
Data migration task recreates the tour activities that were lost due the to bug in the resource unplanning mechanism.

2021-03Data conversion81126