Search Results

As an alternative, consider this formula, which uses YEAR and MONTH functions instead of depending on days: 12*(YEAR(TODAY()) - YEAR(Date__c)) + (MONTH(TODAY()) - MONTH(Date__c)) …

Instead of trying to backwards-engineer and extra the Opportunity Name from the concatenated value, I'd suggest storing the original Opportunity Name in a separate field (e.g. 'Original Opportunity Na …

You need to make the formula a bit smarter. Looks like there are some fixed factors that you are using in the calculating. …

So you formula should probably be: AND( ISPICKVAL(StageName , "4. Proposal"), OR( Max_Discount__c <= 5, Special_Pricing_Approved__c = true ) ) …

If the picklist values are hardcoded pieces of text, you can interpret them in your formula, using an IF or a CASE statement e.g.: Volume__c * CASE(TEXT(Trade__c), 'picklist1',2900, 'picklist2',4000, …

You will have to create the formula field on the Opportunity object. On reports you can only do 'aggregate' kind of formulas, no record-specific logic. …

ISPICKVAL(Reason_for_OF_referral__c, "Parallel Process"), I don't think that comma should be there at the end as it's the last parameter you're providing to your AND operator.

The outcome of your formula, however, is a Boolean, i.e. the fact whether or not the field contains the value 'EMEA': CONTAINS(Activity.SalesLoft1__SalesLoft_Cadence_Name__c,"EMEA") You could convert … that to a number (e.g. 0 or 1) quite simply by surrounding your formula with an IF statement, that outputs 1 if true and 0 if false.: IF(CONTAINS(Activity.SalesLoft1__SalesLoft_Cadence_Name__c,"EMEA"), …

You'll want to create a formula field that outputs the 'category' your record belongs to, in text form. In order to do so, create a formula field of type 'text'. … The DeveloperName, however, will have less change of being changed as it is clear that is could be referenced in code and other logic, such as formula fields. …

If you are sure that State HQ is used for AMER region while Country HQ is used for EMEA region, you could replace State HQ by Country HQ for those regions in the formula field. … id=sf.customize_functions_blankvalue.htm&type=5 You might hit formule field limits, though, because it's quite a large formula already. If that happens, you might need to explore other options. …

So you could represent your formula 1 by: 1 + MCEILING( 12 * ( (EndDate - StartDate) / 365) / 3) NOTE: this is not taking into account leap year. …

id=90630000000gh0qAAA However, looking at the formula you have here, which has multiple references to PV and a lot of extra calculations, you run a serious risk of hitting the salesforce formula field … You will find this out while composing the formula. I'd recommend cutting the calculation up in separate formula fields (just like in the link above), so you can validate intermediate results. …

That will save you 25% of formula size (I hope that is enough). …

If you have percentage values (whole numbers) with a decimal, then try the following: interpret the percentage field as a text field - TEXT() strip off the percentage sign - SUBSTITUTE() An alternat …

If the 3rd party update uses a workflow field update to update the status value (e.g. as part of the approval process), make sure that that field update has the checkbox 'Re-evaluate Workflow Rules af …