TMT Fleet Maintenance V.2023.3.2 Release Notes

This document contains information on the latest version, including:

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

PDF version

General information

All information in this section applies to all 2023 releases except where noted.

Warnings

PLEASE READ BEFORE UPGRADING

Starting with V.2022.2, the AMSLIC (license) database has been merged with the TMWAMS (TMT) database. The installer now works with the new merged database alone.

Existing customers must:

  • Run the provided installer migration script to copy all the data from their AMSLIC database to the TMT database.

  • Perform the upgrade using this merged TMT database. The AMSLIC database will become an invalid input in the SQL setup page of the installer.

After doing an upgrade, the web.config file should only have a TMT database, so that the application will launch without issues. The web.config file will still have two database connect entries, as they exist today, but both will refer to the same database.

New customers with a fresh database do not need to run the installer migration script. They can install the program using the TMT database alone.

If you are currently using an older Client-Server version, you must upgrade to at least V.2019.4 before running the merger script to upgrade to V.2022.2.

Important information, please read

  • SQL Server Cardinality

    Changes to SQL Server cardinality are affecting the performance of TMT Web. The issue happens when SQL Server compatibility mode is set to 120 or greater. This has been identified through Trimble benchmarking and customer feedback.

    At this time, Trimble recommends that you set the SQL Server option for Legacy Cardinality Estimation to ON. This will lessen the effects of the new SQL Server cardinality behavior, which still needs further assessment/improvements in TMT Web.

  • Trimble Technician Portal (TTP) single sign-on (SSO)

    • If you will be using TTP SSO, you must allow pop-up windows. You cannot block them. This applies to Apple and Android phones and tablets. If you block pop-up windows, SSO will not work correctly.

    Follow the directions for your tablet and browser to allow pop-up windows.

    • If you have issues with TTP after upgrading, you may need to clear your browser cache. Close the TTP application and follow the directions for your browser to clear the cache.

    • If you have bookmarked a TTP URL that has a version number, such as 21-3, you should delete that bookmark. Use and bookmark this URL instead: https://tmt-ttp.trimble-transportation.com/

  • TMT Client-Server (Delphi) 2019.4.1 or any earlier version cannot be used with TMT Fleet Maintenance 2022.1 or later. Do not upgrade unless you are ready to go to TMT Web only.

  • Customers using both Integration Options and Windows Authentication should set up their systems so that User dropdown lists use the WINUSER value, instead of the USERNAME value.

  • This version requires .Net Framework 4.8. See the hardware requirements for more information.

  • Customers who are on versions of TMT Web before 2021.3 may be exposed to a vulnerability documented by one of our third-party software vendors (Telerik). Guidance varies depending on the installed TMT Web version (see below). For information directly from Telerik, please use this link: https://docs.telerik.com/devtools/aspnet-ajax/knowledge-base/common-allows-javascriptserializer-deserialization

    • 2021.3, 2021.3.2, 2021.3.3, 2022.1, and later

      These versions use an upgraded Telerik version that has patched the vulnerability. No changes are needed.

    • 2019.4

      A future service pack will include patched Telerik DLLs. In the meanwhile, remediation is possible via web.config changes.

    • 2019.2

      • Remediation possible with web.config changes in this version and higher (2019.2-2021.2.X).

    • Before 2019.2:

      • Remediation is not possible with web.config changes. You must upgrade.

      • For Delphi/Web hybrid customers, see 2019.4 section above. For all others, we would suggest you upgrade to the latest version of TMT Web.

        Telerik Vulnerability Remediation

      Please refer to this link for detailed steps on patching this vulnerability:
      https://docs.telerik.com/devtools/aspnet-ajax/controls/asyncupload/security

    This involves web.config changes, and it can be done without taking an upgrade. However, we strongly encourage you to upgrade to a later version of TMT Web for the greatest level of mitigation.

Before upgrading your production environment, Trimble recommends that you read the hardware requirements and install the latest version in a test environment. If you have questions, please contact your Trimble customer representative.

Changes to hardware requirements

You must be using SQL Server 2016 or later to use TMT Web V.2022.1 or later.

For SQL Server 2016, the minimum compatibility mode is 130. TMT Web will also support modes 140 and 150.

Two files from Microsoft are required for this version:

  • SQL Server 2016 CLR Types

  • SQL Server 2016 Shared Management Objects

You must download and run both files using these links before upgrading to TMT Web V.2022.1:

You must not delete the 2008R2 CLR/SMO SQL Server components from any TMT Web environment when installing or upgrading. The installer is still using these components at this time.

Windows Server and SQL Server upgrades are included in TMT Web software as a service (TMT Web SaaS). For information about upgrading to TMT Web SaaS or other technical questions, contact Dawn Siegel at [email protected].

If you have technical questions, contact TMT Support:

Windows Server and SQL Server Support

  • Windows Server 2012, 2016, and 2019 support SQL Server 2016.

  • Windows Server 2022 does not support SQL Server 2016.

  • Windows Server 2012, 2016, 2019, and 2022 support SQL Server 2017.

  • Windows Server 2016, 2019, and 2022 support SQL Server 2019.

  • Windows 2012 does not support SQL Server 2019.

Trimble Technician Portal (TTP) Update

Trimble upgraded TTP to V.2023. 3 on Sunday, December 10, 2023. Users should clear their cache when logging back in following the update, please refer to the Security Considerations guide for instructions. The production URL will stay the same: https://tmt-ttp.trimble-transportation.com/.

If you are using TTP on premise, and you do not want to upgrade to V.2022.2 or higher, you can still use the same TTP URL as above.

Interactive Workstation replaced by TTP

Effective with V.2022.3, Trimble has replaced Interactive Workstation (IWS) with Trimble Technician Portal (TTP). Mechanics Workstation (MWS) has also been replaced by TTP.

For more information, see V.2022.3 Release Notes.

Enhancements

Login

  • TMT-322575

    TMT users can now log in and perform transactions in the TMT Application without Admin-level SQL access connecting them via the Web Config connection strings to the SQL user. Admin-level access to the SQL-user is still needed at the time of application installation or upgrade. If you desire to remove admin-level access, you may update the Web Config connection strings following the installation or upgrade of the application to a non-admin SQL user.

Orders > Repair Order

  • TMT-322764

    Added the ability to add lines to pending orders.

Resolutions

Activities > Accounting > Accounting

  • TMT-319960

    Fixed an issue where orders would go directly to the Error Trap. If you selected Redisburse they would disburse to the correct accounts, even if no changes were made.

Activities > Accounting > Accounting > Dynamics GP

  • TMT-321130

    Fixed an issue where all order types were being selected even though only one order type was being exported. This change has improved performance.

Activities > Accounting > Accounting > QuickBooks

  • TMT-322565

    Fixed an issue where some transactions were being exported multiple times.

  • TMT-322592

    Fixed an issue where when exporting you would get a message saying that the order already exists in Quickbooks, even though it was a brand new transaction.

Activities > Fuel Data Import

  • TMT-321857

    Fixed an issue where the FuelDataImport.exe does not check the on-hand quantity while creating fuel tickets. This causes a fuel ticket to get created even if there is not enough on-hand to complete the ticket.

    Now if the quantity on-hand is less than the required amount for the fuel ticket it should throw an exception for insufficient quantity for that ticket and all subsequent tickets in the import.

Inventory > Parts Transfer

  • TMT-322616

    Fixed an issue where when using the "In-Transit" for a part transfer that the inventory is not updating properly. The Source shop is showing an update in the Cost History (but it does not update the On Hand QTY). The Destination shop is not showing any update in Cost History or On Hand.

Inventory > Physical Inventory

  • TMT-322524

    Fixed an issue where parts set up as Fluids with a decimal quantity are not updating quantity properly when completing a physical inventory adjustment.

Masters > Shop Inventory

  • TMT-322524

    See TMT-322524 under Inventory > Physical Inventory.

Orders > Indirect Charges Listing

  • TMT-322904

    Fixed an issue where when adding supplies to indirect charges and creating a credit PO with a supply part no data is generated for accounting.

Orders > Purchase Order

  • TMT-322904

    See TMT-322904 under Orders > Indirect Charges Listing.

Orders > Repair Order

  • TMT-322794

    Fixed an issue where Order Work Card was not showing Labor and Parts

  • TMT-322776

    Fixed an issue where under certain conditions when returning a Trailer tire to inventory the system would credit the Tractor and use the tractor tire original price.

Reports > Reports - SSRS > SSRS Report Viewer > Standard Reports > AMS SSRS Report Library

Accounting > Current Book Value by Inventory

  • TMT-322978

Fixed an issue where the Current Book Value by Inventory Account Pending Usage wasn’t including parts on orders that are not closed

  • TMT-323044

Fixed an issue where the Current Book Value by Inventory Account report was not returning the correct book value If multiple shops are selected in the input parameters that have the same account ID.

  • TMT-323065

Fixed an issue where the Current Book Value by Inventory Account Pending Usage was not including all parts on Open In Transit Orders.

  • TMT-323097

Fixed an issue where the Current Book Value by Inventory Account Pending Usage should include all parts on Credit Issue orders that are not closed.

Trimble Technician Portal

  • TMT-322794

    See TMT-322794 under Orders > Repair Order.