Steps to implement Data cleanse transform.

[Former Member]

Hi All,

I want to break Multiline input field to discrete output field and I am using data cleanse transform.

I could not find any document on steps to implement this transform so I tried it myself.

However I am getting errors like 'option group error: At least 1 'Report and analysis option  must be present in this group'

I have changed following in options tab of transform gave input column 'Broker name ' to Multiline1

What are the corrections I should make or could you please tell me the steps from beginning or any document on this?

Thanks,

Shweta

[Former Member · Accepted solution]

Hello All,

Anything on this, any document stating steps to implement data cleanse and address cleanse transorm would be useful.

Thanks,

Shweta

[former_member187605 · Accepted solution]

There's plenty of material available in Data Quality - Enterprise Information Management - SCN Wiki and in

[former_member106536 · Accepted solution]

There is an information steward pdf that has roughly 200 pages of data cleanse information, which is in my opinion a critical reference if you are to understand how this transform really works.

[virginia_hagen · Accepted solution]

You don't say what kind of data you have in your multilines.  The mapping of your data into the Data Cleanse input fields to tell the engine what type of data is on those fields, is important.    If its a multiline with any kind of data, you can set the parsers to look in the best order for your data. 

The location that Dirk refers you to contains blueprints for the Data Quality transforms which gives you jobs that are configured to work. So that you can see what the engine can do and demonstrates the basic functionality.

The Information steward doc is going to have in it how to configure and customize the dictionary to work as the Data Cleanse transform can be configured to use Custom Cleansing packages (which your screen shot is the default package) and it shows you how you can edit and publish the default package.   Both places are very different in terms of what its going to give you.  Both hold valuable information. 

Reading what you are saying your errors are make me question where the .atl file that you are using started. it sounds like an error that we see when an older version .atl file is imported into a newer version and the job doesn't go through the "force upgrade" of a command line switch or the repository upgrade utility.  If you using the blueprints, you have to make sure you are using the package for the version of Data Services you are using.