Release Notes for IDMC
- Release Notes for IDMC
- All Products
Issue
| Description
|
|---|---|
DQC-34908
| Data Quality can display a validation error for a valid rule specification when you perform the following steps:
|
DQC-34884
| Data Quality invalidates a valid rule specification in the following scenario:
|
DQC-34506
| 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.
|
DQC-34505
| 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.
|
DQC-34473
| 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.
|
DQC-34337
| A mapping that contains a Deduplicate transformation fails in the following scenario:
|
DQC-34039
| A rule specification asset does not return the expected results in the following scenario:
|
DQC-33934
| 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.
|
Issue
| Description
|
|---|---|
DQC-34010
| 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.
|
DQC-33628
| An exception task fails when the Exception description field in the associated rule specification contains double quotation marks.
|
DQC-24049
| 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.
|
Issue
| Description
|
|---|---|
DQC-33450
| Data Quality does not display a validation error when you use control characters in a primary rule set name.
|
DQC-33441
| A rule specification asset does not display a validation error in the following scenario:
|
DQC-33440
| When you configure a rule specification, you can enter a script with HTML tags as a parameter value in the
List of Values function in the following scenario:
|
DQC-33352
| 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.
|
DQC-33289
| Data Quality fails to convert a rule specification asset from basic mode to advanced mode in the following scenario:
|
DQC-33039
| When you click a link to a dictionary in the
Depends on section on the
Asset References panel of a cleanse asset, the dictionary appears empty when it opens.
The issue is observed when you log in with a support engineer role.
|
DQC-32247
| The test results on a rule specification asset can display varying numbers of decimal digits. The issue is observed in the following scenario:
|
DQC-31768
| You cannot save a dimension value to a Cleanse asset.
|
DQC-31073
| Data Quality does not enable the
Select button in the
Select Mapplet dialog box when you specify a mapplet in a rule specification action.
|
DQC-31039
| The job details page incorrectly updates the duration time of an exception task job when you resume a failed job.
|
DQC-30770
| When you import or export multiple assets in Data Quality, the service does not display the number of assets that you import or export.
|
DQC-30553
| 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.
|
DQC-24689
| A rule specification asset in advanced mode erases the test data from an input field in the following scenario:
|
Issue
| Description
|
|---|---|
DQC-33175
| Data Quality does not enable the Delete button on the test panel of a rule specification asset in advanced mode in the following scenario:
|
DQC-33129
| Data Quality fails to send email notifications for exception task job. The issue is observed when you log in to Informatica Intelligent Cloud Services on a pod that runs on Amazon Web Services.
|
DQC-33107
| The Unparsed Data column in the test output of a parse asset that you configure in pre-built parse mode disappears when you run a test in the asset.
The issue is observed when you select one of the following pre-built parsing locales:
|
DQC-33101
| When you click the link to a mapplet on the Asset References panel or in the rule logic of a rule specification asset that reads a mapplet, the mapplet fails to open.
|
DQC-33044
| When you click the
Convert to Advanced option on the
Definition tab of a rule specification asset, Data Quality opens the asset in advanced mode on the
Definition tab instead of the
Configuration tab.
|
DQC-32800
| A rule specification incorrectly invalidates a condition or action in the following scenario:
|
DQC-32704
| If you add a tag to a data quality asset but you do not save the asset, the tag that you add appears on the Explore page for the asset.
|
DQC-31667
| The built-in regular expression Email Alternate in a parse asset does not return the expected result.
|
Issue
| Description
|
|---|---|
DQC-32844
| If a column name in the source object contains a space and you create an exception task for the source data, the task fails. The issue is observed when the associated profiling task reads an SQL-based source object.
|
DQC-32419
| Data Integration generates an error when you run a mapping with JDBCV2 connection and SAP source type, although the mapping runs successfully. The issue is observed when you enable the Data Quality service for the runtime environment.
|
DQC-32154
| When the results of an exception task job include HTML characters and you download the results, the downloads operation ends at the first row that contains the HTML characters.
|
DQC-32037
| If you import data from a file to a dictionary, the operation fails to complete successfully in the following scenario:
The issue is observed when a dictionary contains a single column and the file that you import contains more than one column.
|
DQC-32029
| If you create an exception task from a profiling task that applies an SQL sub-query filter on an SQL-based source, the exception task fails.
|
DQC-31874
| If you import a large quantity of data to a dictionary, the dictionary asset and the data may display with errors until you save and reopen the dictionary.
|
DQC-31226
| A rule specification asset test fails in advanced mode in the following scenario:
|
DQC-31032
| A rule specification asset does not validate that the data type of a mapplet output in a rule statement matches the data types of other rule statements in the same rule set.
|
DQC-30912
| A rule specification asset displays a validation error if you do not define two single parameters in an LTRIM function.
|
DQC-24952
| You cannot define an input on a Cleanse transformation in the following scenario:
|
DQC-22863
| If you run a test in a rule specification asset, Data Quality displays an error message in the following scenario:
|
DQC-22615
| You can run multiple instances of the same exception tasks concurrently.
|
DQC-22605
| When you use the List of Values option in a condition function and run a test, the rule specification asset applies the Case sensitive option to the test data and does not return the expected results. The issue is observed when you configure the condition without selecting the Case sensitive option for the test data.
|
Issue
| Description
|
|---|---|
DQC-31904
| Data Quality fails to save a rule specification asset in advanced mode in the following scenario:
|
DQC-31707
| Data Quality displays a blank page when you open the
Explore page and click
Pull from Git in a version-controlled environment.
|
DQC-31702
| The test results on a rule specification asset can display date values in different formats. The issue is observed in the following scenario:
|
DQC-31581
| A rule specification asset in advanced mode does not return the expected results if you use the NOT IN operator in the rule logic.
|
DQC-31465
| When you select a rule specification in a rule statement function, the input from the rule specification can disappear from the rule statement. The issue is observed when you close and reopen the rule specification.
|