Using custom classification, I've created a list in Excel (.csv) and listed all possible values for classification. For example: I have these 2 columns listed As I scan my Azure Data Lake Storage Gen2, this is the classification: Why is it so that one column has been properly classified and the other has been missed?

Purview: Custom Classification with .csv file not correctly classifying all columns

Bryan 0

Using custom classification, I've created a list in Excel (.csv) and listed all possible values for classification. For example: I have these 2 columns listed User's image

As I scan my Azure Data Lake Storage Gen2, this is the classification: User's image

Why is it so that one column has been properly classified and the other has been missed?

PRADEEPCHEEKATLA 90,446 Reputation points

2024-05-14T04:44:27.1266667+00:00

@Bryan - It's possible that the custom classification rule you created for Contract_end_date is more specific than the one you created for Contract_start_date. When you create a custom classification rule, you can specify the conditions that must be met for a column to be classified with that rule.

For example, if you created a custom classification rule for Contract_end_date that specifies that any column with "end_date" in the name should be classified as Contract_end_date, but you did not create a similar rule for Contract_start_date, then only the Contract_end_date column would be classified.

To ensure that both Contract_start_date and Contract_end_date are classified correctly, you should review the custom classification rules you created and make sure they are specific enough to capture all relevant columns. You may need to create additional rules or modify existing ones to achieve the desired classification.

If you have already reviewed your custom classification rules and are still experiencing issues, it's possible that there is an issue with the scanning process. In this case, you may want to re-run the scan and review the scanning logs to see if there are any errors, please share for further assistance.

Looking forward for your response.
Bryan 0 Reputation points

2024-05-14T19:42:37.4433333+00:00
@PRADEEPCHEEKATLA Hi, the classification rule that I used was through a customized .csv file:

I've double checked that there aren't any trailing spaces or spaces forward of the column names. The column names I have are exactly as they are for contract_start_date and contract_end_date. I have also looked at the scanning process and reviewed the logs and there are no errors.
Bryan 0 Reputation points

2024-05-14T19:48:19.4766667+00:00

@PRADEEPCHEEKATLA Hi, for the custom classification rule - I created a .csv file to detect all possible values for a classification.

I made sure that there weren't any trailing or forward spaces for each column name. I have reviewed that they were properly spelled out and matched the case as well. I have also re-scanned the source and reviewed the scanning logs to find no errrors.
PRADEEPCHEEKATLA 90,446 Reputation points

2024-05-15T03:56:04.33+00:00

@Bryan - I agree that this issue looks strange and I wasn't able to reproduce this issue. If you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us?
Bryan 0 Reputation points

2024-05-16T15:39:46.1666667+00:00

@PRADEEPCHEEKATLA I do not have a support plan
PRADEEPCHEEKATLA 90,446 Reputation points

2024-05-17T03:18:07.64+00:00

@Bryan - Working offline to resolve the issue.
PRADEEPCHEEKATLA 90,446 Reputation points

2024-05-23T08:51:04.95+00:00

@Bryan - We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Share via

Purview: Custom Classification with .csv file not correctly classifying all columns

Your answer