Loading

Salesforce Financial Services Cloud: FinServ.LeadTrigger AfterUpdate TriggerException on Lead Conversion

Udgivelsesdato: Jul 14, 2026
Beskrivelse

Converting a lead in Salesforce Financial Services Cloud (FSC) fails and the following error appears:

"There was an error converting the lead and referral. Please resolve the following error and try again: FinServ.LeadTrigger: execution of AfterUpdate caused by: FinServ.MoiExceptionWrapper.TriggerException: Something's not quite right. Try your action again, and if the issue continues, contact your administrator for help.: unexpected token: 'FROM' (System Code)"

 

 

Løsning

The steps below resolve lead conversion failures in Financial Services Cloud caused by the FinServ managed package trigger error FinServ.LeadTrigger: execution of AfterUpdate caused by: FinServ.MoiExceptionWrapper.TriggerException, and separately address why a custom field marked read-only remains editable for certain user profiles.

Cause 1: Missing field-level security or CRUD access on fields required by lead conversion

During lead conversion, FSC's MOI framework builds a dynamic SOQL query to read and update related records, including fields such as FinServ__ReferredByUser__c and FinServ__ReferredByContact__c. If the running user's profile or permission set does not grant Read access to one or more fields the query builder expects, FSC silently drops those fields from the field list rather than failing gracefully. If enough fields are dropped, the generated query ends up with an empty or malformed field list, for example "SELECT FROM Account WHERE Id IN (...)", which Apex rejects with an "unexpected token: 'FROM'" parse error. This surfaces to the user as the FinServ.LeadTrigger / MoiExceptionWrapper.TriggerException error. This is the confirmed root cause for this exact error signature, consistent with historical cases of this issue.

Steps to identify and fix the missing field access:

  1. Identify the profile (and any permission sets) assigned to the user who hit the error during lead conversion.
  2. Navigate to Setup, then Object Manager, then Lead, then Fields & Relationships. Separately check Account, Contact, and Opportunity as well, since conversion touches all of them.
  3. For each FSC-managed (FinServ namespace) custom field on these objects, particularly referral-related fields such as FinServ__ReferredByUser__c and FinServ__ReferredByContact__c, check field-level security (Set Field-Level Security or View Field Accessibility) for the affected user's profile and permission sets.
  4. Grant at least Read access to any FSC-managed fields that are currently inaccessible to that profile or permission set. Grant Edit access too if the user needs to modify the field directly.
  5. Re-attempt the lead conversion and confirm it completes without the FinServ.LeadTrigger: execution of AfterUpdate error.

Cause 2: Restrictive organization-wide sharing defaults causing mid-transaction record-visibility loss

In orgs with Private organization-wide defaults (OWD) on Account, Contact, or related FSC objects, sharing rules can occasionally fail to apply quickly enough during the multi-step lead conversion transaction, causing the converting user to temporarily lose visibility into a record the FinServ trigger needs to query, producing the same class of trigger exception. If Cause 1 does not resolve the issue, review sharing:

  1. Check the organization-wide default settings for Account, Contact, and any custom FSC objects involved (Setup, then Sharing Settings).
  2. Review whether the converting user has access to the target Account or Contact through role hierarchy, sharing rules, or manual sharing, not just through the Lead they own.
  3. As a diagnostic step, test the conversion with a user who has broader access (for example, System Administrator). If conversion succeeds for that user but not the original user, sharing and visibility is the contributing factor, and sharing rules or manual sharing should be adjusted for the affected user.

Cause 3: Custom field marked read-only is still editable for certain user profiles

Field editability in Financial Services Cloud is controlled by field-level security, which is set independently on each profile and permission set. A field can appear read-only on one profile while remaining editable on another, because a profile or permission set assigned to those users grants Edit access to the field. Field editability is not enforced by a single org-wide field setting.

Steps to enforce read-only on a custom field across profiles:

  1. Navigate to Setup, then Object Manager, select the object, then Fields & Relationships, then select the custom field.
  2. Click Set Field-Level Security (or View Field Accessibility).
  3. For each profile that should not edit the field, select Read Access and clear Edit Access (Read-Only).
  4. Review permission sets assigned to the affected users, as a permission set granting Edit access overrides the read-only setting on the profile.
  5. Save the field-level security changes.
  6. Log in as an affected user and confirm the custom field displays as read-only and cannot be edited.
Vidensartikelnummer

005388903

 
Indlæser
Salesforce Help | Article