Profiling Exception Log Object
This page provides a purpose summary for Cuneiform® for CRM’s Profiling Exception Log custom object. Use this page to learn about this object, how it relates to the other custom objects used by Cuneiform for CRM and Cuneiform® for Data Cloud, and to access its data dictionary.
Applies TO | CUNEIFORM FOR CRM CUNEIFORM FOR DATA CLOUD
The Profiling Exception Log custom object captures logging and auditing exceptions or errors caught during application use. The object collects the following details:
The parent Profiling Definition (where applicable)
The exception summary and raw details (including the stack trace)
Any internal failed API calls made during profiling
The Apex class, method, and line number which sourced the exception
We use this object to audit specific events, exceptions, or errors that can be experienced while running profiling definitions within your Salesforce org. These exception details are valuable when troubleshooting profiling-related issues and are often requested by our Customer Service team when working with customers.
Access the Profiling Exception Log Data Dictionary via Google Sheets
Our Custom Object Data Dictionaries are available to Cuneiform for Salesforce customers via Google Worksheets. We align updates of these documents to product releases as fast as follows.
This Google Sheets worksheet captures the field descriptions for the Profiling Exception Log Custom Object as of release v2.8.0. Use this worksheet to review this custom object’s field configurations.
Access the Cuneiform for CRM: Profiling Exception Log: Data Dictionary Google Worksheet
Public Customer Facing Fields
(Use in Reports and CRM UI)
The customer-facing fields tab identifies fields exposed in our list views, record detail pages, and custom report types.
Internal Application-Facing Fields
(Do Not Use in Reports and CRM UI)
The Profiling Exception Log custom object has no internal application-facing fields; all fields are customer-facing.