User Guide > Designing and Executing Data Profile
Was this helpful?
Designing and Executing Data Profile
Data Profiler allows you to create data quality rules using Data Profile Wizard or Data Profile Editor, that are specific to an individual use case or project. You can configure Profiler rules to identify specific data patterns, formats, and values. You can also configure rules to identify null, blank, or duplicate values in fields. This helps you to quickly determine quality levels of the source data, identify the types of problems, and reduce issues resulting from propagating bad data to down-stream systems and applications.
In Data Profiling, the data is profiled (identified) based on its conformance to configured rules (conformance to identified data quality characteristics of accuracy, completeness, consistency, timeliness, validity, uniqueness, etc.). Once data has been profiled, data quality can be quantified (calculated), and an insight into specific data quality issues (what types, how many) can be determined. Then the records that adhere to the profiling rules are written to a “pass” output file and the records that do not adhere to the profiling rules are written to a “fail” output file. Since the data is written into two separate files, the “passing” data can be processed and the “failing” data can be rectified of its data quality problems.
In addition to the Data Profile Editor, there is a Data Profiler Invoker which enables you to execute profiles from within the Process Designer workflows and also from the command line interface. For more information, see Data Profiler Invoker.
Note:  For running profiles directly from the command line interface, see Using Data Profiler Engine. For working with previously created Data Profile artifacts using the import feature, see Importing Artifacts from Folder.
Last modified date: 10/22/2024