Data Quality enables the

Save

button and throws a validation error in the following scenario:

You search for an input or an output that you haven't selected in a verifier asset.
You search for an input or an output that doesn't exist in the verifier asset.

When you search for a user-defined pattern or sort pattern entries in a Parse asset in pre-built parsing mode and you switch to full-screen mode, your search and sort settings are lost. You don't see your settings when you exit full-screen mode.

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.

The verifier asset inputs and outputs you select are unchecked when you search any of your selected inputs or outputs.

When you create a mapping and run the mapping with an asset transformation, the input fields in the target file are automatically sorted.

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.

Data Quality throws a validation error in the following scenario:

You create a rule specification in basic mode with a condition that searches for single quotation marks.
You convert the rule specification to advanced mode and validate the rule specification.

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.

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.

When you configure a rule specification with STANDARDIZE and IFF expressions in basic mode and you convert the rule specification to advanced mode, the expressions that you configured don't appear.

Data Quality fails to throw a validation error in the following scenario:

You configure a rule specification in basic mode with a ROUND(Numeric) custom expression.
You convert the rule specification to advanced mode and you delete the ROUND(Numeric) custom expression.
You validate the rule specification.

When you run an exception task, open the

Job Details

page while the job is in progress, and refresh the page multiple times, the exception data download becomes inactive. During this time, you can't access the exception data.

Data Quality throws a validation error in the following scenario:

You create a basic rule specification.
You configure the rule logic with a
STANDARDIZE
function and
IFF
statements.
You validate the rule specification.

When you run an exception task, open the

Job Details

page while the job is in progress, and refresh the page multiple times, the exception data download becomes inactive. During this time, you can't access the exception data.

If a basic rule specification is configured with a mapplet that has multiple inputs, but only one input is mapped in the rule logic, an error appears when you convert the rule specification to advanced mode.

For users with the Support Engineer role, Data Quality fails to load and throws a

503 Service Unavailable

.

In a labeler asset, you see a space is selected by default and appears in the output field delimiter, instead of the previously selected value after performing the following steps:

Select a value for the output field in the labeler asset property and save the asset.
Re-open the
Labeler Properties
dialog box and create a new custom delimiter for the output field delimiter.
Delete the newly created delimiter.

If you create a Microsoft Fabric rule through API, run the rule and save it, Data Quality throws an error.

When you open a dictionary asset from a hyperlink in Data Profiling, an error appears.

When you add a new field-based consolidation in a deduplicate asset, the new field doesn't appear in the

Test Data

panel of the

Consolidation

tab.

The rule specification in basic mode fails to generate correct outputs when you perform the following actions:

Select
Date/Time
as the data type in the input.
Configure rule logic as
IF <input> is not null value THEN <input>
, add some input, and run the rule specification.

When you configure the rule logic of a rule specification in basic mode to the

TO DATE

function and pass the format as

yyyy-MM-dd hh:mm:ss.ms

, Data Quality throws an error.

If you create a rule specification in basic mode but the input data type doesn't match with the rule logic conditions you specify, Data Quality fails to display a validation error.

If you run a rule specification asset that contains nested rules, Data Quality fails to run the rule specification.

The email notification doesn't show the percentage of exceptions in the following scenario:

When you configure multiple exception tasks to write the results of the exception task jobs to Informatica's cloud storage.
There is no exception data.
The generated exception data is less than 1 and more than 0.

Verifier mappings fail to run because the Secure Agent could not download the Address Verification IPU license files and ignored the customer agent proxy configuration setup.

The verifier mapping fails to run if there is no Address Verification license file folder in the CDQAV.LicenseFileDirectoryPath.

When you test a parse or labeler asset, Data Quality creates a duplicate of the last row of input data in the second row of the test pane.