Known issues - trillium_quality - trillium_discovery - Latest

Trillium DQ Release Notes

Product type
Software
Portfolio
Verify
Product family
Trillium™ software
Product
Trillium™ software > Trillium™ Quality
Trillium™ software > Trillium™ Discovery
Version
Latest
ft:locale
en-US
Product name
Trillium Quality and Discovery
ft:title
Trillium DQ Release Notes
Copyright
2024
First publish date
2008
ft:lastEdition
2026-01-30
ft:lastPublication
2026-01-30T16:16:09.403000
L1_Product_Gateway
Verify
L2_Product_Segment
Data Quality
L3_Product_Brand
Precisely Trillium
L4_Investment_Segment
Legacy DQ
Core Data Quality
L5_Product_Group
Legacy DQ - Application
Data Quality - Application
L6_Product_Name
Trillium Quality
Trillium Discovery

  • If you are using the Date/Time functions in your Business Rules (e.g., DT_ROUND_UP, DT_ADD, etc.), you may encounter some rule failures or discrepancies compared to previous versions. This is due to an upgrade in the third-party libraries used for processing dates. These libraries are now stricter when comparing input data against the date format defined in your Business Rule.

    For example, the following may have previously worked:
    DT_ADD("03/12/2013 09:12:45", "MM/dd/yyyy HH:mm:ss:SSS", "Month", "3")

    However, the date format defined in the rule does not match the format of the date in the input data (it is missing milliseconds), which will cause it to fail in v17.3.0. Your Business Rules will need to be modified to use the correct date format.

  • The Director service may fail to start on a Windows machine during the first attempt due to a timing issue.
  • Dynamics: Selecting "Save and Close" prevents the duplicate popup + matchlink tables from properly functioning.
  • Adding TSI Web Server link to Web Service does not work.
  • Data Source Load fails when "Change Data Source Options" feature uses an alternative data source that does not match the original settings.
  • Humanize Name are displayed for Data Source Attributes when Data Source record added through Discovery Center and Control Center with keep_source_names=1 for some data connection types.
  • Repository migration from 17.x to 17.3 on Windows must be done by following the process for cross-platform migration. Running this migration via the installer process is not supported in this configuration.
  • The 64-bit ODBC Reporting Adapter is not available as part of the initial v17.3 software release, and will be released at a later date. Please contact Customer Support for additional information.