Cuneiform for Salesforce Custom Objects

Applies TO | CUNEIFORM FOR CRM CUNEIFORM FOR DATA CLOUD

Supported Custom Objects

Cuneiform® for CRM and Cuneiform® for Data Cloud share seven custom objects to store profiling definitions and the metadata generated by running them. These custom objects are created in your Salesforce org when you install Cuneiform for CRM: Field and Data Management, a prerequisite for installing all other Cuneiform for Salesforce products. Most fields on these objects are external-facing (or reportable), meaning you can use them in reports.

Open

Cuneiform for CRM and relies on these seven custom objects to manage Profiling Definitions
and persist profiling field, field value, and KPI results in your Salesforce org.

Captured Profiling Definitions

Profiling Definitions are the configurations describing how Salesforce or Data Cloud objects will be profiled. Each definition includes the object, fields, and record filters used to profile objects.

Profiling Definition Object

The Profiling Definition custom object captures profiling definitions describing the Salesforce objects and fields being profiled. This is the parent object for all other custom objects in Cuneiform for CRM.

The Profiling Definition represents the top-level parent object for Cuneiform for CRM custom objects.

Captured Profiling Results

Profiling Results include field utilization, value frequency, and KPI calculations when profiling Salesforce Standard, Custom, or Data Lake objects. Every time an object is profiled, a new set of profiling results is created using these custom objects.

Profiling Summary Object

The Profiling Summary custom object captures the summary-level profiling results for a given profiling definition. Every profiling operation performed by Cuneiform for CRM generates a summary representing the profiling results. The summary record captures record volume, estimated storage, and field population counts.

Profiling Summaries are associated directly to their parent Profiling Definition record and represent the Salesforce Object that was profiled (ex. Standard Object, Custom Object, or Data Lake Object).

Profiling Field Results Object

The Profiling Field Result custom object captures field-specific profiling results for a given profiling definition. Field Result records capture all field-specific profiling statistics, such as fill rate, percentage of populated and empty records, and counts of distinct and default records.

Profiling Field Results are associated directly to their parent Profiling Summary and Profiling Definition records. They represent the profiling results for each field that was profiled.

Profiling Value Result Object

The Profiling Value Result custom object captures value-specific profiling results for a given profiling field result. All value-specific results, including top [x] and bottom [x] values and value fill-rate results, are captured in Value Result records.

Profiling Value Results are associated directly to their parent Profiling Field Result, Profiling Summary, and Profiling Definition records. They represent individual values that were profiled for a parent field record.

Profiling KPI Result Object

The Profiling KPI Result custom object captures aggregated KPI calculations and KPI calculation density statistics. All aggregated KPI Results, including averages, minimums, maximums (with and without zeros), and sums, are stored in this object. Additionally, KPI fill rate and density calculations are stored with aggregated results.

Profiling KPI Results are associated directly to their parent Profiling Field Results and Profiling Summary records. They represent the KPI calculations performed during profiling.

Captured Profiling Requests and Queueing

When you run a profiling definition, a profiling request is created to manage queueing for that action to avoid overloading and bogging down your org with simultaneous calls.

Profiling Request Object

The Profiling Request custom object captures profiling definition details as well as whether or not the request was successfully run, how long it took before it ran (once profiling was initiated), and whether or not it was scheduled as part of an automated flow.

Profiling request objects are tied to the profiling definition queued to run and the subsequently created profiling summary.

Captured Profiling Errors and Exceptions

Whenever Cuneiform for CRM or Cuneiform for Data Cloud generates an exception or error, the exception details are audited so customers can review them and share them with PeerNova Support.

Profiling Exception Log Object

The Profiling Exception Log custom object captures logging and auditing events caught during exception use (e.g., profiling). We use this object to audit specific events, exceptions, or errors that can be experienced while running profiling definitions within your Salesforce org. This is valuable to your Admins and our support team if we need to inspect those details to troubleshoot an issue.

Profiling Exceptions can be independent records with no associations. They also can be associated associated directly to their parent Profiling Definitions.