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.

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

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.

When you run Data Observability multiple times on a data set, profiling metric values are not deleted when anomalies are introduced and detected during later runs.

If you import a rule specification that contains an invalid expression in the rule logic, Data Quality fails to display a validation error.

A rule specification returns different output data at run time when rule specification name contains spaces than when the name contains no spaces. The issue arises when you use a mapplet in the rule specification.

An exception task that writes to local storage loses its target connection details after you import the task.

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.

Data Quality throws an error when you create a Microsoft Fabric rule specification through an API, run the asset in the user interface, and save the asset.

Data Quality throws an error when you test a rule specification in the following scenario:

The rule specification contains a mapplet with a Java transformation that uses several external libraries.
You test the rule specification in advanced mode.

The following issues arise when you create tags, assign tags to an asset, or remove tags from an asset:

When you add a tag to an asset, a current tag is removed from the asset.
When you add tags to an asset and delete the tags on the
Explorer
page, you can still see the tags in the asset.
When you add a tag to an asset and close the asset without saving, you can still see the new tag in the
Explorer
page and within the asset.

When you test a basic rule specification, Data Quality can append two to three redundant zeros to the end of a float or date value. The issue can arise when the float value ends in a zero following the decimal point or the date value includes milliseconds that end in a zero.

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.

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.

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.

When you configure an exception task to write to local storage and run the task, the exception

Job details

page does not identify the data storage type.

If an exception task name includes a character space and you configure the task to write to your local storage, the task execution fails.

The exception data generates with the name REPLACE_WITH_LOCAL_TARGET_NAME.csv in the following scenario:

You create an exception task that writes to local storage.
You add a custom email address in the
Email notification
options of the exception task.
You run the task.

An exception data appends

_out

to the field names in a local storage file in the following scenario:

You create a profiling task with a source mapplet.
You create an exception task that writes to local storage from the profiling task, and you run the exception task.

An exception task fails in the following scenario:

You create the exception task from a profiling task that reads an Oracle source.
You configure the exception task to write to local storage.

If you rename an exception task and run the task, the updated name doesn't appear in the exception job or exception file.

When you run an exception task that writes to local storage, the

Job details

page displays the number of exception issues as the source rows value.

When you run an exception task that writes to local storage, the

Rule Names

and

Rule Input

columns are absent from the exception data file.

A rule specification test fails in the following scenario:

You configure an advanced rule specification with an input and output of data type float. - You set the precision to 50 and the scale to 28.
You configure a simple expression and test the rule specification.

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.

A rule specification in advanced mode uses the rule specification properties to define a scale value for an output and not the output properties.

Data Quality can return

<NULL>

in place of an empty cell in an advanced rule test. The issue is observed when you use the following functions:

MOVINGAVG
MOVINGSUM
RATE

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.

When you test any data quality asset other than a rule specification, the test does not return data for the final row of input data.

If you add special characters to a rule specification name with special characters, Data Quality does not invalidate the name change. The issue arises when you filter on the

Explore

page for assets that use tags.

Data Quality can display a validation error for a valid rule specification when you perform the following steps:

You configure the asset in basic mode.
You configure the custom expression
IIF
in a rule statement in a child rule set.
You convert the rule specification to advanced mode.
You validate the asset.

Data Quality does not invalidate a rule specification in the following scenario:

You configure the rule logic to read a rule specification that includes a control character in its input field.
You validate the rule.

The test results in an advanced rule specification display output as duplicate double quotes instead of blank values in the following scenario:

You create an advanced rule specification with simple configurations and run the test data.
You create a simple basic rule specification, convert the rule to advanced and run the test data.

You configure the asset in basic mode.
You configure the custom expression IIF in a rule statement in a child rule set.
You validate the asset.

The rule specification contains a rule statement that reads 17 or more dictionaries.

An exception task job fails to run and the service becomes unresponsive when the Secure Agent that you selected in the associated profiling task is inactive in the runtime environment.

A scheduled exception task job fails to run when the Secure Agent that you selected in the associated profiling task is inactive in the runtime environment.

A mapping or profiling task that reads a rule specification asset generates a warning when the rule epecification inclues a TO_DECIMAL('NOT A NUMBER') function. Following multiple runs, the mapping or profiling task accumulates multiple such errors and fails.

You set the data locale to Arabic in the deduplicate asset.
Your source data contains Arabic script characters.
You run the mapping in advanced mode in an advanced serverless runtime environment.

The rule statement in the primary rule set reads a mapplet that contains the result of a child rule set.

If you have Read permission for assets and no other permission, the

Save

option appears and the

Convert to Advanced

option remains enabled when you open a rule specification asset.

If you enter test data in a cleanse asset and then add one or more input fields, you cannot enter test data for the newly added input fields.

An exception task fails when the Exception description field in the associated rule specification contains double quotation marks.

When you run a mapping with a Verifier transformation, the Secure Agent applies the default value of 5 for the

ParallelExecutionInstances

property and ignores any non-default value that you define on the property.

Data Quality does not display a validation error when you use control characters in a primary rule set name.

You use an input of integer or float data type in the rule logic.
You use the
is within
or
is not within
operator in the rule logic.
You specify a data type in the
List of Values
function that is different to the input data type.

You use the Date/Time data type for the parameter value that you define in the
List of Values
function.
You use the
is within
or
is not within
operator in the rule logic.

You cannot create an exception task from a profiling task when the runtime environment that you selected to create the profiling task contains an inactive Secure Agent.

The rule logic reads a dictionary from a bundle.

You configure the custom expression FV, NPer, Pmt, PV, or Rate in a rule statement.
You save and convert the rule specification to advanced mode.

You cannot save a dimension value to a Cleanse asset.

Data Quality does not enable the

Select

button in the

Select Mapplet

dialog box when you specify a mapplet in a rule specification action.

The

Job details

page incorrectly updates the duration time of an exception task job when you resume a failed job.

When you import or export multiple assets in Data Quality, the service does not display the number of assets that you import or export.

A Verifier transformation adds incorrect version data for the Informatica address verification engine to an AMAS (Australia) certification report. The transformation identifies the engine version number as 5.16.2.

A rule specification asset in advanced mode erases the test data from an input field in the following scenario:

You use an IS_SPACES function in the rule logic.
The test data input field contains character spaces only.