• If you want to retain a reference to the original record id
    • FIELD(Id) – the field would contain the value of the original record’s Id.
  • If a date was null
    • y(+1) – the field value would still be null because arithmetic on a null value will result in an error.
    • CUR,y(+1) – the field value will first be set the the current date. Then a year will be added to the current date.
    • FIELD(MyOtherDateField__c),m(-1),LDM – the field will be set to the value of the other date field. Then one month will be subtracted, and finally the value will be set to the last day of the previous month.
  • If a date was 10/2/2016
    • y(2018),d(1) – the current field value will be used as the starting point, and the year will be set as 2018. Then the day is set to 1. The value of the field in the new record would be 10/1/2018.
    • y(+1),m(-1),LDM – the current field value will be used as the starting point, and one year will be added. Then one month subtracted, and the last day of the 9th month will be set. The value of the field in the new record would be 9/30/2017.
  • If you want a field to contain the value of a different field after cloning. For example, if you have a renewal rate on a current opportunity. Formula fields can be created and used in the Action Formula list to incorporate more complex logic.
    • FIELD(Proposed_Renewal_Rate__c) – the field would contain the value that was in the Proposed_Renewal_Rate__c field.
  • If you want to use a field to set another fields value using the action formula list.
    • mul(field(myfield__c)) – this will multiply the value of the field by the value in ‘myfield__c’.
    • suf(field(myfield__c)) – this will suffix the value of the field with the value in ‘myfield__c’.
    • m(+field(myfield__c)) – this will add a number of months to the field. The field would need to be a date or datetime and ‘myfield__c’ would need to be numeric in this scenario.
    • the “field( )” action formula keyword can be used in combination with most of the other actions.
  • If you want a sequential indicator of the cloned hierarchy when using the clone multiplier feature. You can assign values text fields like the name with sequences like  “My Opportunity – 1 of 6″, My Opportunity – 2 of 6”, etc.
    • >>,suf(” – “),suf(!index),suf(” of “),suf(!mult) – this suffixes the current value with a dash, inserts a sequence number, inserts a constant of ‘of’, and inserts the total number of clones requested.
  • If you want each cloned hierarchy to have a date that is incremented by 1 month, and each hierarchy’s date is set to last day of that respective month.
    • >>,m(-1),m(+!index),ldm – this takes the value in the field and subtracts one month to set a base. Then the “m(+!index)” will add back that number of months for each sequence. Finally, the date will be set to the last day in the respective month.
  • If you want to divide a number by the total number of clones. This can take a number entered into a field, and have it divided evenly among all of the requested cloned hierarchies.
    • >>,div(!mult)
  • Copy a custom Item object from an Opportunity to a Quote using the RELATIONSHIPID() keyword.
    • The custom Item object would need to have relationships to both the Opportunity and Quote.
    • The configuration would be created on the Opportunity.
    • The formula action “RELATIONSHIPID(CLEAR)” would be used on the lookup reference field to the Quote.
    • The copy page would be loaded with an “rid” URL parameter of the Quote record Id, and a “fromid” URL parameter of the Opportunity record Id.
    • To keep the reference to the Opportunity in the relationship field, the keyword “RELATIONSHIPID(fromid)” could be used.
    • The automatic copy of custom items could also be run from Process Builder on the creation of a Quote.