Custom fields

Kernel's AI Cleaning & Hierarchies module comes with 23 custom fields.

Custom fields

Kernel provides 23 custom fields that provide direct recommendations, insights, or explanations behind the cleaning recommendations.

Field Label	Field Name	Type	Length	Help Text	Read Only	Visible	Category
Kernel - Cleaning action	kernel_cleaning_action	Text	255	Suggested data cleanup action	Yes	Yes	required
Kernel - Duplicate group	kernel_duplicate_group	Number		Unique number which groups duplicate accounts together	Yes	Yes	required
Kernel - Duplicate type	kernel_duplicate_type	Text	255	PRIMARY = Main account EXACT = Exact match via cleaned URLs. REGIONAL = Regional variants (e.g., amazon.ca vs amazon.com). SUBDOMAIN = Subdomain variants (e.g., shop.acme.com vs acme.com). POTENTIAL = Careers, marketing, or product sites that may be duplicates.	Yes	Yes	required
Kernel - Parent Account ID	kernel_parent_account_id	Lookup	18	Reference to parent account record	Yes	Yes	required
Kernel - Account identity type	kernel_account_identity_type	Text	255	The type of account identity mismatch present on the account	Yes	Yes	recommended
Kernel - Cleaning action (Reasoning)	kernel_cleaning_action_reasoning	Text (Long)	1000		Yes	Yes	recommended
Kernel - Hierarchy sub-type	kernel_hierarchy_subtype	Text	255	Further Kernel classification of the corporate hierarchy type (holding company, operational parent, standalone subsidiary, regional office, or an absorbed subsidiary)	Yes	Yes	recommended
Kernel - Hierarchy type	kernel_hierarchy_type	Text	255	Whether an account is a 'Parent' or 'Child'	Yes	Yes	recommended
Kernel - LinkedIn URL	kernel_linkedin_url	URL	255	Company LinkedIn profile URL	Yes	Yes	recommended
Kernel - Risk score	kernel_risk_score	Number		Associated risk of taking a mass action on this account	Yes	Yes	recommended
Kernel - Suggested Name	kernel_suggested_name	Text	255	Kernel's suggested name based on cleaning of the account	Yes	Yes	recommended
Kernel - Suggested URL	kernel_suggested_url	URL		Kernel's suggested URL based on cleaning of the account	Yes	Yes	recommended
Kernel - Account identity issues	kernel_account_identity_issues	Text (Long)	1000	Reasoning behind account identity analysis	Yes	Yes	optional
Kernel - Associated duplicates	kernel_associated_duplicates	Text Area (Long)	5000	List of all associated duplicates of this account	Yes	Yes	optional
Kernel - Duplicate of	kernel_duplicate	Text	255	Which ID the account is a duplicate of	Yes	Yes	optional
Kernel - Duplicate (Reasoning)	kernel_duplicate_reasoning	Text Area (Long)	5000		Yes	Yes	optional
Kernel - Hierarchy (Reasoning)	kernel_hierarchy_reasoning	Text Area (Long)	5000	Explanation for parent/child determination	Yes	Yes	optional
Kernel - Parent URL	kernel_parent_url	URL		URL of the identified parent	Yes	Yes	optional
Kernel - Resolved domain	kernel_resolved_domain	URL	255	Cleaned company website domain	Yes	Yes	optional
Kernel - Ultimate parent ID	kernel_ultimate_parent_id	Text	255	The ID of the top parent that is present in the CRM	Yes	Yes	optional
Kernel - Ultimate parent name	kernel_ultimate_parent_name	Text	255	The name of the top parent that is present in the CRM	Yes	Yes	optional
Kernel - User type	kernel_user_type	Text	255	Whether the Owner of account is an active, inactive, or integration user	Yes	No	optional
Kernel - Is the website working?	kernel_website_status	Text	255	Status of company website (Working, Not working, or Unknown)	Yes	Yes	optional

Standard vs. custom fields

While Kernel can write to both standard and custom Salesforce fields, we strongly recommend a safer approach to prevent accidental data overwrites.

The best practice is to have Kernel write its findings to a dedicated, read-only custom field. This isolates Kernel's data, allowing you to use Salesforce logic to control how the primary field is populated. As shown in the example, this gives your team the ability to create manual overrides that always take precedence, ensuring you have final say over your data.