Field | Required? | Description |
|---|---|---|
testCaseName | Yes | Name of the test case. |
description | No | Description of the test case. |
leftObjectType | Yes | Type of the data source. Specify one of the following values:
|
leftConnId | Yes | Connection ID of the first connection. When you open the connection in Administrator, the numeric value that you see in the URL is the connection ID. For example, if the URL is <Informatica Intelligent Cloud Services URL>/cloudUI/products/administer/main/ConnectionDetailsWS/014N8B0B000000000898/read, the connection ID is 014N8B0B000000000898. |
leftSavedSqlQuery | No | ID of the saved SQL query of the first connection. Use the following format: "leftSavedSqlQuery" : { "id" : <value> } |
leftTableName | No | Table name of the first connection. |
leftTablePk | Yes | Primary key of the table in the first connection. You can also enter multiple keys. |
rightObjectType | Yes | Type of the data source. Specify one of the following values:
|
rightConnId | Yes | Connection ID of the second connection. When you open the connection in Administrator, the numeric value that you see in the URL is the connection ID. For example, if the URL is <Informatica Intelligent Cloud Services URL>/cloudUI/products/administer/main/ConnectionDetailsWS/014N8B0B000000000898/read, the connection ID is 014N8B0B000000000898. |
rightSavedSqlQuery | No | ID of the saved SQL query of the second connection. Use the following format: "rightSavedSqlQuery" : { "id" : <value> } |
rightTableName | No | Table name of the second connection. |
rightTablePk | Yes | Primary key of the table in the second connection. You can also enter multiple keys. |
runtimeEnvId | Yes | Runtime environment where the test case runs. |
stagingConnectionId | Yes | Connection ID of the flat file connection that Data Validation uses to stores reports. When you open the flat file connection in Administrator, the numeric value that you see in the URL is the connection ID. For example, if the URL is <Informatica Intelligent Cloud Services URL>/cloudUI/products/administer/main/ConnectionDetailsWS/014N8B0B000000000ATW/read, the connection ID is 014N8B0B000000000ATW. |
frsDocLocation | Yes | The location to save the test case. To save the test case in a project, use the following syntax: "{\"type\":\"Project\",\"id\":\"<project_ID>\",\"path\":\"<project_name>\"}", To save the test case in a folder, use the following syntax: "{\"type\":\"Folder\",\"id\":\"<folder_ID>\",\"path\":\"<folder_name>\"}", When you open a project, the numeric value that you see in the URL is the project ID. Similarly, when you open a folder, the numeric value that you see in the URL is the folder ID. By default, the test case is saved under the Default project. |
emailNotificationStrategy | Yes | Specify one of the following values:
|
successEmails | Required if emailNotificationStrategy is set to CUSTOM | Specify the email addresses that Data Validation must use for the success email notifications. Separate multiple email addresses with a comma. |
errorEmails | Required if emailNotificationStrategy is set to CUSTOM | Specify the email addresses that Data Validation must use for the failure email notifications. Separate multiple email addresses with a comma. |
leftConnPath | Required for Amazon Redshift v2 and Amazon S3 v2 connections | If you use an Amazon Redshift v2 or an Amazon S3 v2 connection, enter a valid path for the first connection. |
leftConnAdvancedParams | No | If you use an Amazon Redshift v2, Amazon S3 v2, or flat file connection, specify the advanced parameters to be used for the first connection.
{ "S3BucketName": "<value>" } {"formatId":"Parquet","@type":"dataFormat","dataFormatAttributes": {}} For flat file connections, specify the advanced parameters to determine how the flat file must be parsed.For example, enter: { "srcFFAttrs" :{ "delimiter" : "<value>" , "textQualifier" : "<value>" , "escapeChar" : "<value>" , "headerLineNo" : <value> , "firstDataRow" : <value> }} |
rightConnPath | Required for Amazon Redshift v2 and Amazon S3 v2 connections | If you use an Amazon Redshift v2 or an Amazon S3 v2 connection, enter a valid path for the second connection. |
rightConnAdvancedParams | No | If you use an Amazon Redshift v2, Amazon S3 v2, or flat file connection, specify the advanced parameters to be used for the second connection.
{ "S3BucketName": "<value>" } {"formatId":"Parquet","@type":"dataFormat","dataFormatAttributes": {}} For flat file connections, specify the advanced parameters to determine how the flat file must be parsed.For example, enter: { "srcFFAttrs" :{ "delimiter" : "<value>" , "textQualifier" : "<value>" , "escapeChar" : "<value>" , "headerLineNo" : <value> , "firstDataRow" : <value> }} |
leftConnWhereClause | No | WHERE clause to be used for the first connection. If you use a WHERE clause, Data Validation selects those rows for sampling that meet the condition specified in the WHERE clause. |
rightConnWhereClause | No | WHERE clause to be used for the second connection. If you use a WHERE clause, Data Validation selects those rows for sampling that meet the condition specified in the WHERE clause. |
verboseMode | No | Defines the logging level. Enter true to use the verbose mode. The log includes messages of all logging levels. This option is useful for debugging. Enter false to use the standard mode. The log includes only error messages. |
keepDIAssets | No | Defines whether you want to save the Data Integration mappings and tasks that Data Validation creates when it runs the test case. Enter true to save the Data Integration assets after the test case run. Enter false if you do not want to save the Data Integration assets after the test case run. |
ignoreCase | No | Defines whether you want to ignore casing differences in the data. Enter true to ignore casing differences in the data. Enter false to consider the casing differences in the data as a mismatch. |
trimString | No | Defines whether you want to trim leading and trailing white spaces in string values. Enter true to trim leading and trailing white spaces in string values. Enter false to retain leading and trailing white spaces in string values. Default is false. |
badRecordLimit | No | Defines the maximum number of unmatched, extra, and missing records to show in the detailed test results. Enter the value as 100, 500, or 1000. Default is 100. |
colMappings | Yes | Defines the name, type, precision, and scale for each column mapping. Use the following syntax to map columns in the first connection and second connection: "colMappings": [ { "aggrFunc": "<function1,function2,functionn>", "leftColName": "<value>", "leftColType": "<value>", "rightColName": "<value>", "rightColType": "<value>", "rightColPrecision": <value>, "rightColScale": <value>, "leftColPrecision": <value>, "leftColScale": <value>, }, { "leftColName": "<value>", "leftColType": "<value>", "rightColName": "<value>", "rightColType": "<value>", "rightColPrecision": <value>, "rightColScale": <value>, "leftColPrecision": <value>, "leftColScale": <value>, "aggrFunc": "min" } ], Use the aggrFunc field to define the aggregation functions that Data Validation must use to compare the table. Separate multiple aggregation functions with a comma. The aggregation function names must be in uppercase. An aggregation functions test retrieves summarized information about the data contained in the data sources. Use aggregation to verify whether all records were moved or to identify incorrect logic in WHERE clauses. Based on the data type of the columns, you can use one or more of the following aggregation functions:
|
sampling | Yes | Configure data sampling for Data Validation to compare between sample source data and sample target data. The less data that Data Validation samples, the faster the test runs. Use the following syntax to specify the sampling type and value: "sampling": { "type": "<value>", "val": <value> } } Use one of the following options:
"sampling": { "type": "percentage", "val": 25 } } "sampling": { "type": "first", "val": 100 } } "sampling": { "type": "last", "val": 1000 } } |
Field | Type | Description |
|---|---|---|
testCaseId | String | ID of the test case. |
frsDocId | String | ID of the test case in the Informatica repository. |
testCaseName | String | Name of the test case. |
Field | Type | Description |
|---|---|---|
code | String | Code of the error message. |
message | String | Error message. |
debugMessage | String | Message that can be used for debugging the issue. |
details | String | Detailed information about the error message. |