PII scan on the derived tables from a JSON file show incorrect Table and column names

Products

• CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

When registering a Swagger JSON file as an object, and running a Data model scan against the gtrep database table created for the registered object, the column name is not correct for the PII data model. The PII audit report shows the wrong values for the column names.

For example:

"offsetAccountArrangement": {
           "type": "object",
           "properties": {
                     "transitNumber": {
                               "type": "string"
                       },
                     "accountNumber": {
                               "type": "string"
                      },
                     "accountClassificationType": {
                               "type": "string"
                      },
                     "accountCountry": {
                               "type": "string"
                      },
                     "denominationCurrency": {
                                "type": "string"
                      }
            }

For the above snippet, we need to see the output as follows:

table	column	datatype
offsetAccountArrangement	transitNumber	String
offsetAccountArrangement	accountNumber	String
offsetAccountArrangement	accountClassificationType	String
offsetAccountArrangement	accountCountry	String
offsetAccountArrangement	denominationCurrency	String

 

However, what is seen in the PII audit report below, contains the wrong table name and column names:

 

schema	table	column	datatype
SampleSwagger_869258	SWAG_ABSIndicator	type	nvarchar
SampleSwagger_869258	SWAG_accountBalance	type	nvarchar
SampleSwagger_869258	SWAG_accountClassificationType	type	nvarchar
SampleSwagger_869258	SWAG_accountCountry	type	nvarchar
SampleSwagger_869258	SWAG_accountNumber	type	nvarchar
SampleSwagger_869258	SWAG_additionalData	type	nvarchar
SampleSwagger_869258	SWAG_additionalDebugText	type	nvarchar
SampleSwagger_869258	SWAG_additionalField	type	nvarchar
SampleSwagger_869258	SWAG_additionalInfo	$ref	nvarchar
SampleSwagger_869258	SWAG_additionalPostingInfo	$ref	nvarchar

Environment

TDM Portal 4.10+

Cause

The results seen are a direct correlation to the JSON file content being registered.

Resolution

To get the output as described, the JSON content should be as follows:

"offsetAccountArrangement": {
     "transitNumber": "1234",
     "accountNumber": "23456789",
     "accountClassificationType": "type",
     "accountCountry": "country",
     "denominationCurrency": "currency"
}