Issue | Description |
|---|---|
DQC-40768 | When you test a rule specification that you configured in advanced mode, the rule logic incorrectly applies case sensitivity to the word 'invalid'. |
DQC-40385 | For the Verifier transformation, Data Integration did not consider the Tracing Level option that you selected and always used the Normal option. |
DQC-40250 | When you perform duplicate analysis on the Product Name index key for the Product objective, the Deduplicate transformation doesn't create clusters for similar product names in Japanese. |
DQC-39484 | In a mapping, when you place a Rule Specification transformation immediately after a SQL transformation, the Preview panel of the Rule Specification transformation fails to load the data for the transformation. |
DQC-39367 | When you switch from your account to a sub-organization user that has both session ID and JWT token enabled, you can't select data quality assets in a mapping and you see an error. |
DQC-39342 | If you run multiple Verifier mappings in Data Integration, you can download corrupted reference data files and see an error in the session logs for the mapping task. |
DQC-39340 | If you set NoPreLoadCountries and run a Verifier mapping on a Kubernetes cluster in Data Integration, the reference data files do not automatically download in the ReferenceDataDirectoryPath location. |
Issue | Description |
|---|---|
DQC-38732 | Data Quality enables the Save button and throws a validation error in the following scenario:
|
DQC-38386 | The verifier asset inputs and outputs you select are unchecked when you search any of your selected inputs or outputs. |
DQC-38488 | If you run a mapping that includes a Verifier transformation and consumes IPUs, the Secure Agent does not create a directory for the address verification license file and the mapping fails. |
DQC-38472 | When you choose At Sign, Dash, or Comma as a custom token delimiter in a Parse asset in pre-built parsing mode, you see some parts of the test result outputs in lowercase. |
DQC-38181 | When you create a mapping and run the mapping with an asset transformation, the input fields in the target file are not automatically sorted. |
DQC-38143 | Data Quality fails to throw a validation error if you create a rule specification, configure the default rule statement on the rule specification with no action, and validate the asset. |
DQC-37851 | Data Quality throws a validation error when you configure a rule specification in advanced mode with a large number of nested rule specifications. The issue is observed when you configure 34 nested rules. |
DQC-37835 | When you include one or more character spaces in the name of a rule specification and in the name of the primary rule set, Data Quality changes the spaces in the primary rule set name to underscore characters. |
DQC-37731 | Data Quality fails to throw a validation error in the following scenario:
|
DQC-37109 | When you pass a child rule set as an argument in a Least or Greatest function in the rule logic of a rule specification, Data Quality fails to save the rule specification. |
DQC-36853 | When you run a Verifier transformation advanced mapping in Interactive mode, the mapping fails. |
DQC-35700 | When you enable the override option in the properties of a rule specification in advanced mode and you update the string precision value, you can create an input or output with a string precision that is greater than the override value. |