Search Results

The difference between two time fields is a number so you would have to create a number type formula field. … divide by 1000 To get minutes: 1000ms/sec * 60sec/min = divide by 60,000 To get hours: 1000ms/sec * 60sec/min * 60min/hr = divide by 3,600,000 To get it in a time format (hh:mm), you could make your formula …

https://help.salesforce.com/articleView?id=custom_field_time_overview.htm https://help.salesforce.com/articleView?id=formula_using_date_datetime.htm&type=5 You'll need to enclose the text in TIMEVA …

As a note, I'd analyze why you're doing this and whether you really need it. You should be able to select the different combination of picklist values in reports/list view filters. Either way, you c …

You are returning dates from your conditions instead of true/false as you say you'd like to do. The syntax is IF(logical_test, value_if_true, value_if_false) As noted in the doc, replace value_if_tru …

The Name corresponds to the label of the role in the UI. You can see that type of information in UserRole. Required. Name of the role. Corresponds to Label on the user interface. What you're looking …

In this screen, your formula is about denoting whether the input is valid (true) or not (false). NOTE The formula expression must return a Boolean value (true or false). … If the formula expression evaluates to true, the input is valid. If the formula expression evaluates to false, the error message is displayed to the user. …

There's an ADDMONTHS function that would make this simpler assuming your duration and period fields are whole numbers. I will point out the highlighted point about how it will function if the month i …

There's some good resources: Formula Operators and Functions Use Formula Fields && Advanced Formulas trailheads The Build Formula insert actions within the Process Builder (see below). … Your original formula used CONTAINS correctly (but your additions did not) and the same format/syntax applies even if using a field instead of a custom metadata value. …

expects CASE(expression,value1, result1, value2, result2,..., else_result) and IMAGE expects IMAGE(image_url, alternate_text, height, width) Likewise, what you're trying to accomplish with the above formula … in the following terms to match with the parameters above For a given field (expression), depending on its data (value) - return a format (result) to be used within IMAGE If I format your existing formula …

I'm not sure your existing formula makes sense. … Then, in this flow you could add a formula to check how many days the Status has been unchanged {!$Flow.CurrentDate} - {!Record.Last_Status_Changed_Date__c} > 5. …

A formula isn't really scalable (ex. when you have more conditions, more counselors, to make frequent changes, etc), but if you simply have 4 conditions - it can work. …

And the following, when a formula field references another formula is not yet fixed. …

I presume you copied this formula from that site and then replaced the fields. It seems the minus sign (-) is actually an en dash instead of a hyphen-minus which is causing the generic issue. … You can copy and paste from that article or your formula into a ASCII Text to Hex Code Converter and see the difference when compared to typing on your keyboard. …

Also, converts picklist values to text in approval rules, approval step rules, workflow rules, escalation rules, assignment rules, auto-response rules, validation rules, formula fields, field updates, … As such, based on Flow not supporting it, your only workaround is what you mentioned - creating a custom formula field on the object that will support time field and provide Flow with the output. …

Now you can refer to the variable you created to display the value of the choice in your formula as UPPER({!Hold_Choice_Value} + '_PRODUCT_A') …