Complete Guide to Creating a Profiling Definition
Use this guide to learn how to create enhanced profiling definitions in Cuneiform® for Salesforce® using object field selection, profiling insights configuration, field utilization thresholds, and creating condition-based scenarios.
APPLIES TO | CUNEIFORM FOR CRM CUNEIFORM FOR DATA CLOUD
The process for creating your first profiling definition is generally consistent across all of our applications, so you can follow this guide to create your first profiling definition in Field and Data Management, Business Data Reliability, or Cuneiform for Data Cloud.
Creating your first profiling definition?
Consider working through the Profiling Definition Quick Start Guide before the Complete Guide to get foundational knowledge and results to help inform your profiling strategy.
Table of Contents
- 1 What to Profile?
- 2 Profiling Definition Filters, Insights, and Conditions
- 3 Creating a Profiling Definition
- 3.1 Step 1: Launch the Profiling Definition Wizard
- 3.2 Step 2: Select the Fields to Profile
- 3.3 Step 3: Select the Profiling Insights
- 3.4 Step 4: Set the Field Utilization Thresholds
- 3.5 Step 5: Configure the Primary Scenario
- 3.6 Step 6: Configure the Secondary Scenario
- 3.7 Step 7: Name and Categorize Your Profiling Definition
- 3.8 Step 8: Save and Profile
What to Profile?
When creating profiling definitions, it’s helpful to start with a clear goal in mind—specifically, an object you’d like to learn more about. Consider asking yourself these questions:
Which objects are most critical to my organization’s success?
For example: Does your organization focus heavily on Leads or Contacts?Are there objects where I know issues exist?
Think about objects like Contacts or Opportunities that may need attention.Have previous profiling results pointed to an issue with a specific set of fields, or in a specific time period?
If you have already started profiling, consider reviewing those results to identify problem areas.
If you’re unsure where to begin, consider starting with one of these commonly used objects:
Opportunity
Account
Contact
Lead
Contract
Campaign
Case
Profiling Definition Filters, Insights, and Conditions
Cuneiform enables precise profiling of object records and their fields with features like:
Individual field selection
Profiling insights
Field utilization thresholds
Condition-based scenarios
Our Profiling Definition Quick Start Guide encourages users not to use these features for their first profiling definition because excessive filtering and changing default configurations could obscure impactful trends or issues. In the Complete Guide to Creating a Profiling Definition, we build on that knowledge and explain how to enhance your profiling definitions by selecting individual object fields, configuring profiling insights, adjusting field utilization thresholds, and creating condition-based scenarios.
Creating a Profiling Definition
Step 1: Launch the Profiling Definition Wizard
Launch the Profiling Definition Wizard from either the Open Profiling Definition Wizard button or the Profiling Definition Wizard button in the utility bar.
Search for and select the object you’d like to profile.
Cuneiform for CRM supports standard and custom objects, and Cuneiform for Data Cloud supports data lake objects.
If the object you want to profile doesn’t appear, check with your admin to ensure it’s supported or not filtered. For more information, refer tohttps://jira-peernova.atlassian.net/wiki/spaces/CFCPD/pages/3181248585.
Once selected, the wizard displays the object’s label, API name, total record count, and available fields.
Step 2: Select the Fields to Profile
From the Available Fields search bar, search for the fields you’d like to include in the profiling definition and use the directional buttons to add them to the Selected Fields section. Then, click Next to continue the wizard's profiling insights selection.
Step 3: Select the Profiling Insights
Profiling offers granular controls to select specific data insights, all enabled by default. Keeping these insights enabled allows Cuneiform to collect detailed metadata. To remove an insight, simply toggle it off.
Profiling insights include:
Metadata Profiling: Audits Salesforce object and field metadata, including custom field dependencies (flows, layouts, and report dependencies).
Record Count Profiling: Captures record counts, field utilization rates, and profiling statistics. It also calculates data reliability KPIs, provided that one or more KPIs have been assigned to the profiling definition.
Retrieve Common Profiling Values: Records field value frequencies, highlighting the most and least frequent values.
Cuneiform for CRM supports Metadata Profiling, Record Count Profiling, and Retrieve Common Profiling Values. Cuneiform for Data Cloud supports Record Count Profiling and Retrieve Common Profiling Values.
Step 4: Set the Field Utilization Thresholds
Field Utilization Thresholds identify the utilization rates that result in fields being identified as Low Population, Highly Distinct, or Dominant.
Low Population %: This slider defines the highest population rate your organization considers 'low.' Fields with population rates at or below this threshold will be categorized as Low Population.
Distinct Density %: This slider sets the maximum rate of unique values considered notably distinct by your organization’s standards. Fields with unique value rates exceeding this threshold will be categorized as Highly Distinct.
Dominant Value %: This slider determines the population rate at which your organization’s standards consider a single value dominant. Fields where a single value meets or exceeds this threshold will be categorized as Dominant.
If available, use the rate sliders to adjust the field utilization thresholds as shown below:
Field and Data Management users cannot change the default rate sliders for field utilization. Business Data Management and Cuneiform for Data Cloud users can adjust the rate sliders for their respective profiling insights.
Availability of some thresholds varies based on the profiling insights you have toggled on, as shown below:
Click Next to continue to begin configuring the definition’s primary scenario.
Step 5: Configure the Primary Scenario
Once you’ve selected the object, fields, and profiling insights gathered by a profiling definition, you can set filters for at least one profiling scenario.
Field and Data Management users can define only one scenario per profiling definition: the Primary Scenario.
Business Data Management and Cuneiform for Data Cloud users can define a Primary and Secondary Scenario that allows you to compare criteria on the same object records without creating a second definition. Using two profiling scenarios within a single definition allows you to compare different criteria on the same object records without creating a second profiling definition. For example, to identify the differences between winning and losing opportunities, you can configure the scenarios to filter for each criterion accordingly.
By default, all selected object records are included in the profiling definition. Scenario filters let you focus on a subset of records by setting condition requirements.
Choose a condition type from the Condition Requirements drop-down:
None - Profile All Records: Profiles all records without conditions, preventing the assignment of data quality or business impact KPIs.
All Conditions Are Met (AND): Includes records only if all specified conditions are met.
Any Condition Is Met (OR): Includes records if any of the specified conditions are met.
Custom Condition Logic Is Met (CUSTOM): Uses a SOQL query with a custom WHERE clause to filter records.
Selecting one of the condition requirements will display a new set of fields where you can select the field to base the filter on, the operator, and the value to filter for.
Search for and select the object field by which you want to filter records from the Field field.
The available operators in the Operator drop-down depend on the data type of the selected field. Similarly, the Value field options will vary based on the field’s data type. For example, selecting a picklist field like Opportunity Stage will populate the Value field with the available picklist options. In the example below, these conditions will filter for records where the Opportunity Stage field Equals Closed Won.
Refer to https://jira-peernova.atlassian.net/l/cp/qyvFeHRdfor details on how selected data types influence available operators.
Select + Add Condition and define the additional filter to add more to the condition requirements.
Step 6: Configure the Secondary Scenario
A Secondary Scenario is only available to Business Data Reliability and Cuneiform for Data Cloud users.
Follow the steps described for the primary scenario when configuring the secondary scenario. In the example below, the Secondary Scenario will filter for records where the Opportunity Stage field Equals Closed Lost. Click Next to complete the condition requirements and finalize the new profiling definition.
Step 7: Name and Categorize Your Profiling Definition
Name your profiling definition (e.g., Case Object Profiling Definition) and add a description (e.g., First profiling definition for the Case object). Use the category fields to start organization your profiling definitions by a base category, time category, and segment category. These values can be helpful when creating reports and filtering profiling definition results.
Definition Category: A base category useful for categories like Baseline, Comparative, or Field Analysis.
Time Category: A time-based category useful for years, Lifetime, or Last Quarter.
Segment Category: A segment-based category useful for segments like Closed/Won, Person Accounts, or Open Cases.
If you’re creating profiling definitions to understand the shape of your CRM data, we recommend using the Definition Category Baseline. By default, our free reporting package Cuneiform for CRM: Data Health Reports uses data from profiling definitions assigned to the Baseline category.
Click Next to review and finalize your new profiling definition.
Step 8: Save and Profile
Review your profiling definition’s details and choose one of the following options:
Save Definition to save your work without running the profiling operation.
Save & Profile to save and start the analysis immediately.
Selecting Save & Profile will direct you to your new profiling definition’s record detail page, where you can monitor progress and profiling status.
Cuneiform uses a silent queuing system to manage profiling requests and limit the number of requests processed simultaneously in your org. For example, if you run multiple profiling definitions simultaneously, the system will automatically stagger the requests to ensure smooth processing. For more information on customizing your org’s experience with Cuneiform, refer to Customize Cuneiform.
Congratulations on creating your profiling definition! You’ve learned how to target specific business data for profiling. Use these definitions to focus on crucial data and assess whether it meets its intended purpose.
Learn how to enhance your profiling with KPIs that measure data quality and business impact with Measure Data Quality and Business Impact.