Compiled formula is too big to execute (6,581 characters). Maximum size is 5,000 characters

Compiled formula is too big to execute (6,581 characters). Maximum size is 5,000 characters

Face the issue when compiling this formula :

IF (Country_Code__c ='GB' || Country_Code__c ='IE' || Country_Code__c ='ZA' || Country_Code__c ='KE' || Country_Code__c ='MA' || Country_Code__c ='TZ' || Codes__c ='BH' || Country_Code__c ='OM' || Country_Code__c ='AE' || Country_Code__c ='QA' || Country_Code__c ='SA','EMEA_REGION',null )

Requirement if the country field fall into certain code it will be labelled as 'EMEA_REGION' .

The formula is very simple but it still throws the exception because Country_Code__c is the formula field itself and it depend on how many times it being called.In this case,Country_Code__c is being called 11 so these will be pulled in formula compilation.

The issue can be solved by reducing the calling;

IF( CONTAINS("GB:IE:ZA:KE:MA:TZ:BH:OM:AE:QA:SA",Country_Code__c),"EMEA_REGION",null)

Also this is how we can check multiple value.

Reference(PDF) How to reduce formula size.

Comments

Search Solution Basics

When is it a good time to create a customized search solution? You're developing an external knowledge base for user support. You're in the mood for a fun Friday night. The sales reps just started using the Sales Cloud in Lightning Experience. You want to put your company branding in the search bar. What differentiates SOSL from SOQL? Syntax SOSL searches the search index instead of the org database. SOSL searches more efficiently when you don't know in which object the data resides. All of the above. SOSL works with: REST only SOAP only REST, SOAP, and Apex SOQL only What does a search for a single object look like in SOSL? FIND {cloud} RETURNING Account FIND in ACCOUNT RETURNING "cloud" FIND "cloud" in ACCOUNT FIND (cloud) RIGHT NOW! What does a search for multiple objects look like in SOSL? FIND {sneakers} RETURNING ALL ARTICLES FIND {sneakers} in ALL OBJECTS FIND {sneakers} RETURNING Product2, Content

Process Builder is not fired when field update is called from Approval Process

Scenario In Final Approvals section ; in Approval Process we have field update to update Status field. In Process Builder , we have some action that need to be done when Status field is updated in Approval Process.However this process builder is not fired. Solution To handle this, in Field Update in Approval Process , check Re-evaluated Workflow Rules after Field Change as picture below. What happen if field updated from Approval Process. Workflow - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Process Builder - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Trigger - will fire if conditions are matched This is explained in article here . Field Updates That Re-evaluate Workflow Rules If Re-evaluate Workflow Rules After Field Change is enabled for a field update action, Salesforce re-evaluates all workflow rules on the object if the field update results in a change to the value of the fi

Tips and Tricks : Test class for Invocable method

Issue : I got 100% coverage in my sandbox but when run validation for deployment it returns 0% coverage It turn out that in my sandbox, I am depending on Process Builder to Invocable Apex class, as long I manipulate test data that fire Process Builder it will call Invocable class. This is not useful when deploying it to Production although it gets deployed together with Process Builder. The correct way is to direct call Invocable method inside test class itself. Example of class : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 global class MyCustomObject_StatusUpdate_Util { @InvocableMethod ( label = ' Update Quote Status ' ) public static void updateQuote ( Request [] requests ) { Set < Id > setOppId = new Set < Id >(); List < SBQQ__Quote__c > listQuoteToUpdate = new List < SBQQ__Quote__c >(); for ( Request request : requests ) {

shelovestocode♥

Search This Blog