We changed our privacy policy. Read more.

New answers tagged


Workflow Rules do exactly what you tell them to do when they are evaluated and the condition is true, and do nothing otherwise. You would need to have a second Workflow Rule that could undo the work of the first when the conditions are met, if that is what you want the system to do. Otherwise, nothing will be done with the conditions are not met.


Shortest solution I came up with, which does not ignore leap years. ADDMONTHS(Birthdate__c, (FLOOR((TODAY() - BirthdateGP__c) / 365.2425) + 1) * 12) Basically we takes the Birthday__c and add to that 12 * age months. Age is calculated using FLOOR. For 2000-02-29 the next birthday will be 2022-02-28.


$ is used for Global Variables. These are used in all kinds of formulas, including formula fields, validation rules, Process Builder, etc. They are used exactly as you would any other kind of variable, they just have special meaning in context (e.g. referencing the user's profile via $Profile).


In Validation Rules, Symbol "$" is used to identify the current record and user (whom create/update that record) field values. On your question, $Recordtype.Name points to current record's record type. $Profile.Name points current user's profile whom try to create/update that record. You can refer this kind things in here Please let me know if it ...


In your flow, while creating the opportunity in the Create Opportunity record element, you need to populate the ContactId with the Id which is created from your Create contacts record element. This will link the opportunity to the contact. Your flow would be something like below screenshot So in the Create Opportunity Record element, you need to map the ...


As a Workflow Rule, use the Formula Criteria option: And(IsPickVal(PriorValue(Status, 'New')), IsPickVal(Status, 'Approved')) Change Status in the above formula to whatever the API name is for the picklist field (custom fields send with "__c").


When you manually edit and save the "Status" field, the flow fires correctly, this means there is nothing wrong with the configuration of the flow. In your case, the process builder did not trigger the flow. A process builder field update does not trigger a "before flow" in the same transaction. A process builder field update will only ...

Top 50 recent answers are included