Search Results

You are missing a concatenation operator in several places IF(RecordType.Name== 'Purchase Order', Name='po-' & CC_OrderNumber__c & '-' & CC_Sales_Order__r.CC_OrderNumber__c , Name ='so-' & CC …

The workaround is an Apex trigger and a custom field Is_Changed_Workflow__c (checkbox). Use the trigger (before update) to set the value to true when Workflow__c has changed and then use a final act …

Check the documentation - purpose is to see if digits are entered into a text field ISNUMBER(sometextfield) only takes text fields as argument - not currency which are decimal fields Validation …

If the formula field is on Contact, then "https://linkurl.com/somapage?e=" + Id + "&s=" + FirstName Labels are typically used for constants. …

Convert to a CASE statement so Score__c is referenced only once , assumes values are 0,1,2, ...13+. Solution is practical as long as scores are integers within a small range. Would not work if scores …

If you care, you can deal with that by wrapping the formula with some additional logic to strip it out - an exercise left for the reader …

In the past, I've left in the OR ( condition ) if in dealing with the business, I've gotten "vibes" that a second, third, ... condition is likely to be added "soon" so I might as well get the struct …

What you want to assemble in a formula field is mantissa x 10 <some superscripted exponent> Let's assume the base value is in a custom field Measurement__c We know that FLOOR(LOG(Measurement__c)) is … So, putting this altogether into a new formula field (1,344 compiled characters) Measurement_Friendly__c we have: /* Generates n.nnnn x10<superscriptedExponent> e.g. 8.923x10¹ Notes: 1. …

You have several issues with your formula CASE({! … varlatestProjectId}, 4)) + 1),4,"0")" has double quotes around a formula expression, turning all of that into a literal string You want UPPER(LEFT({! …

In a workflow rule, the rule criteria is either 'criteria are met' or 'formula evaluates to true'. … fields have utility in other use cases and can inspire extension to do other relative date criteria in 'formula evaluates to true' scenarios. …

is the cause of your issues - because you reference it three times, the number of compiled characters in Formula_SUM_ALL__c is multiplied by three (3) when calculating the size of the image generation formula … And of course, the size of Formula_Sum_All__c depends on any formula fields it references! …

Try this as your custom formula field (type Number) R_Complex__c * CASE (Plan_Object__c, "Low",1, "Medium",2, "High",3, "None",0, NULL) where the values …

As Jagular says, doing this in formula fields is hard when you have special cases - I've included an apex utility class I wrote that I used in a trigger. …

You are using the wrong operator for concatenation You have: IF(ISPICKVAL(Service__c,"") || ISNULL(BusinessID__c), NuLL,Service__c && BusinessID__c) This is "anding" Service__c and BusinessId__c …

This is a partial answer that may not meet your requirements TEXT(Day( DATEVALUE(CreatedDate) )) & "/" & TEXT(Month( DATEVALUE(CreatedDate) ))&"/"& TEXT(Year( DATEVALUE(CreatedDate) )) & " " & MID(TEX …