If you enable the

Auto Sync Catalog

option for a data store, the

Connection String

and

Schema Option

property values get deleted.

If you run a scan on a Salesforce source, the scan fails at the Collect Row Count step.

When you create a Microsoft SQL Server data store, if you enter the instance, the Test Connection option fails.

When you import details to create a new data store, the values you add in the

Schema/Path

column of the import file do not appear on the UI.

When you scan an SAP data store, the following issues occur:

The data scan does not identify sensitive fields.
After a metadata or data scan, the risk score is set to zero.

For Amazon S3 data stores, when you run a metadata with data scan, the

Evaluate Classification Job

fails.

For Salesforce data stores, when you run a scan, the risk score and policy impressions values are set to zero.

For French and German instances, when a field or file name contains extended ASCII codes such as

ÚÜáàâãçéêíóôúü_All_Customers.csv

, Secure@Source is unable to determine if the field or file is sensitive.

Users with the View Task, Edit Task, and Export privilege cannot download and view DSAR reports unless they also have the View Subject Registry privilege.

Although the user has the required DSAR privileges, the

Task Details

tab freezes and displays an error.

There is no Online Help for the Manage Risk Simulation feature.

For Secure@Source 5.0 and the Protection 5.0 product, if you configure a Catalog metadata CSV file to add or delete some of the metadata, import the CSV file, and later import a CSV file that contains only the Catalog metadata you did not add or delete in Secure@Source, Enterprise Data Catalog retains only the metadata included in the latest imported CSV file.

On the

Subject Registry Details

page, a user can view data stores that the user does not have permission to view.

Persistent Data Masking job logs are not available on the Secure@Source UI. The job displays the following error message:

Job with ID <ID number> failed in TDM

.

Persistent Data Masking jobs fail when the name of the Data Integration Service is not

DIS

or

Data_Integration_Service

.