#Formulas40 personnes en discutent

Hi Sean,

Yes, the Known Issue indicates that ISCLONE() in the Start/entry criteria of a record-triggered Flow cannot be used with Flow Debugging. The limitation is specifically with debugging the flow when ISCLONE() is part of the entry criteria. 

And I agree that moving the check into a Decision element isn't exactly equivalent—the flow has already started, so it doesn't test the same entry-condition behavior. 

For testing, one workaround is to temporarily move the ISCLONE() logic into a Decision element while validating the rest of the flow, then restore it to the Start criteria. For the actual platform limitation, I'd also keep an eye on the Known Issue for any status/update from Salesforce. 

Hi @Scott Holmes

Yes, you can check the formula syntax directly in Flow Builder. Formula resources are created within the Flow, so you won't find their syntax in Object Manager.

To view the syntax:

1. Open your Flow in Flow Builder.
2. Go to the Manager tab.
3. Under Resources, select your Formula resource (Due in 7 Days / Due in 2 Days).
4. Open the formula to view or edit its syntax.

For example:

Due in 7 Days:

{!$Record.ActivityDate} = TODAY() + 7

Due in 2 Days:

{!$Record.ActivityDate} = TODAY() + 2

You can also review Salesforce's formula documentation for additional functions and syntax. 

Hope this helps!  

 If you find this response helpful, please mark it as the Accepted Answer, as it may also help other Trailblazers facing a similar issue. 😊 

@Craig Munster

Ah, that's the missing piece — and you're right, I was wrong to steer you off your formula field. On an Opportunity Product button the native OpportunityId genuinely isn't exposed in the merge-field picker (annoying known quirk). Your Opportunity_Id__c CASESAFEID field is exactly the right workaround, so keep it — custom fields DO show up under Insert Field. Just reference that one instead of OpportunityId: 

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

}&retURL=/lightning/r/Opportunity/{!OpportunityLineItem.Opportunity_Id__c}/related/OpportunityLineItems/view 

That sends them back to the Products related list on the parent Opp. Sorry for the runaround getting there! 

If this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂

Hi Tarah, 

I have reviewed the Row-Level Formula and identified the issue with the formula structure. The IF() statements were being used inside the OR() condition, which was causing the “Missing )” error.

I have restructured the formula to validate the required conditions correctly: 

 IF( Churn_Event__c.Effective_Date__c > TODAY(), IF( OR( AND( ISPICKVAL(Churn_Event__c.Save_Successful__c, "yes"), Churn_Event__c.Total_Amount_of_ARR_Churned__c < Churn_Event__c.Churned_Revenue__c ), AND( ISBLANK(Churn_Event__c.Save_Successful__c), Churn_Event__c.Total_Amount_of_ARR_Churned__c = Churn_Event__c.Churned_Revenue__c ), AND( ISPICKVAL(Churn_Event__c.Save_Successful__c, "no"), Churn_Event__c.Total_Amount_of_ARR_Churned__c = Churn_Event__c.Churned_Revenue__c ) ), "Yes", "No" ), "No" )  

This formula returns

@Alex Valavanis

Because the status lives on the Fund record, reach it cross-object — a lookup lets you reference the parent's fields with the __r syntax, so Fund__r.Fund_Status__c works even though it's a formula field. Put this on the Opportunity validation rule (it fires / blocks the save when TRUE): AND( RecordTypeId = "01220000000AOdBAAW", OR(ISNEW(), ISCHANGED(Fund__c)), OR(Fund__r.Fund_Status__c = "Liquidated", Fund__r.Fund_Status__c = "Liquidating") ). The OR(ISNEW(), ISCHANGED(Fund__c)) limits it to when the Fund is actually being set or changed, so records that already point to a fund aren't locked if that fund later goes into liquidation. Two tips: match the exact text your Fund_Status formula outputs (the comparison is case-sensitive), and consider RecordType.DeveloperName = "Your_RT_API_Name" instead of the hardcoded Id so it survives sandbox refreshes and deploys. if this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂

@Blake Swan

Hi, you may use:

SUM({ FIXED  [Charter Product Type],
    [Customer Name],
    [Customer Number],
    [Market Segment],
    [Product Type],
[Month Number In Relation To Current]:
SUM(
    IF [Month Number In Relation To Current] = 0
    THEN [Actual Demand]
    END
)
})
+
SUM({ SUM([Line Weekly Past Due Tons])
})

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you. 

Regards, 

Diego Martinez 

Tableau Visionary and Tableau Ambassador 

Yes — the issue is very likely that Account.SL_BWM_Birthdate__c is a Text field, and DATEVALUE() only reliably converts text when it is in Salesforce's expected date format.

If your text field contains dates like 07/27/1985, try explicitly parsing the text into year/month/day rather than relying on DATEVALUE():   

DATE( 

    YEAR(TODAY()), 

    VALUE(MID(Account.SL_BWM_Birthdate__c, 1, 2)), 

    VALUE(MID(Account.SL_BWM_Birthdate__c, 4, 2)) 

) 

Two things: 

1) your formula structure is quite strange. You are saying "if this condition, then return a number, but hten convert that number back to text" 

If you want text, just return text immediately e.g.

IF(ISPICKVAL(Type_of_Grant__c, "Other") && Funding_Source__c = "Marc Berman", 23, 
IF(ISPICKVAL(Type_of_Grant__c, "PHP-Security Deposit (Non-Subsidized)"), 20, 

can simply become:

IF(ISPICKVAL(Type_of_Grant__c, "Other") && Funding_Source__c = "Marc Berman", "23", 
IF(ISPICKVAL(Type_of_Grant__c, "PHP-Security Deposit (Non-Subsidized)"), "20", 

Then you no longer need to wrap everything in a TEXT() function. 

2) You should avoid multiple IF statements on picklist functions. It will massively increase your compile size. CASE() is far more efficient and easier to read. 

CASE(
    Type_of_Grant__c,
    "Rent", "23",
    "Utility", "23",
    "Pharmacy", "23",
    "Move-in", "23",
    "Aging in Place", "23",
    "PHP-Security Deposit (Non-Subsidized)", "20",
    "PHP-Security Deposit (Subsidized Housing)", "20",
    "PHP-First Month's Rent (Non-Subsidized)", "20",
    "PHP-First Month's Rent (Subsidized Housing)", "20",
    "PHP-Utility (Non-Subsidized)", "20",
    "PHP-Utility (Subsidized Housing)", "20",
    "STRMU-Rent", "20",
    "STRMU-Mortgage", "20",
    "STRMU-Utilities", "20",
    "C19R-Rent", "20",
    "C19R-Mortgage", "20",
    "C19R-Utilities", "20",
    "Measure A", "07",
    "DHSP Emergency Financial Assistance", "20",
    "Other",
        IF(
            Funding_Source__c = "Marc Berman",
            "23",
            NULL
        ),
    NULL
)