Known issues - trillium_quality - trillium_discovery - Latest

-restoredatakey fails with Windows Authentication:

The -restoredatakey command does not work when Windows Authentication is enabled. Although the -backupdatakey command works with any security type, -restoredatakey depends on the security configuration and fails to update the .registry file correctly when using Windows Authentication. This problem also affects all Active Directory-based security types, such as WinAuth, LDAP, LDAPS, and SSO.

In Trillium version 18.0, the drilldown feature on a rule fails when using repositories set to the Spanish (Spain) locale with delimited data sources. This issue occurs after migrating from version 15.7.4, but does not happen when migrating from later versions. Re-running the rule in version 18 temporarily resolves the problem.

When you run the out-of-the-box (OOTB) project through TSI, the SOAP response may not include the expected values. This issue is often caused by problems in the stub generated from the selections made in the cleanser and matcher tabs. As a result, downstream integrations or validations that rely on these values can be affected.

The current filter functionality in Data Connections does not support table names enclosed in double quotes, which is the required format for defining case-sensitive table names in DB2 and ODBC databases.

• DB2 table names are uppercased by default. For example, a table named TABLE2 can be found using filters like tab, TAB, or any variation.
• However, a table explicitly named "tAbLE2" (with quotes) will not be recognised by the filter, as quoted names are treated as case-sensitive and the system does not currently support this format.

Workaround:

Avoid using double-quoted, case-sensitive table names in filters until support is added.

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.

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 v18.0.0. Your Business Rules will need to be modified to use the correct date format.