![]() ![]() pcify.CaseTrigger: execution of BeforeUpdate caused by: System.NullPointerException: Attempt to de-reference a null object Cause Newer versions of Compliance automatically truncate these fields. Update your Compliance version to 3.7 or newer. In older versions of PCIFY, processing Cases or Email Messages that are being truncated by Salesforce caused these errors. Salesforce automatically truncates very long emails that are over 32,000 characters. CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY : pcifye2c.EmailMessageTrigger: data changed by trigger for field HTML Body: data value too large Cause If any of these Detection Patterns have the same Label, then you'll need to either change the name, deactivate the pattern, or delete it. Please navigate to Setup > Custom Code > Custom Metadata Types > DetectionPattern > Manage DetectionPattern. This error is caused by having multiple active Detection Patterns with the same DeveloperName. System.ListException: Row with duplicate DeveloperName Cause Put field API names in excess of 255 characters into the new field DetectionFieldsPlus.Add the new field DetectionFieldsPlus to the Manager Custom Metadata Type Page Layout.Upgrade Compliance to the latest version.All characters over 255 are getting automatically truncated, which is causing Compliance to throw an exception when attempting to access a field with an incorrect API name. You are over the 255 character limit for DetectionFields. System.SObjectException: Invalid field CustomFieldName_ for Case Cause The newer versions of Compliance have been rearchitected to require zero SOQL queries in processing new records in Triggers. If one of Blackthorn Compliance Apex Triggers or your custom Apex Triggers are giving you this error message, then you need to update your Compliance version to 3.71 or newer. ![]() System.LimitException: pcify:Too many SOQL queries: 101 Resolution ![]()
0 Comments
Leave a Reply. |