Hi everyone!
I've created a date-based workflow rule that sends an email alert to an opp owner when the opp's close date is a day away. I've created an email template and manually test it to make sure it is succesfully sent. In short, the email successfully goes through (whether manually triggered by testing or by the time-based Workflow Rule) and it is received by the Opp owner (me).
... However, the {!Opportunity.Id} seems to be truncated (effectively missing its last three characters); instead of
https://xyz-dev-ed.develop.lightning.force.com/lightning/r/Opportunity/006Hu00001Z2FlnIAF,
... the Opp Id only shows
https://xyz-dev-ed.develop.lightning.force.com/lightning/r/Opportunity/006Hu00001Z2Fln
I've created another time-based workflow just to rule out a one-off glith on my original workflow rule, but the {!Opportunity.Id} object will always be missing the last 3 chars in the body of the message.
I understand that Workflow Rules are to be deprecated but I wonder if anybody else has faced this situation any lately, and how it's been addressed; thank you for your time!
What you are seeing is the difference in the 15-digit (case sensitive) and the 18-digit (case insensitive) Record Ids. Both are valid and are used at different points in the system, although I can't always explain why. For example, if I want to use an ID in a VR (don't--it's bad practice but highlights the example here), I need the 15 digit version; the 18-digit version won't fire the rule. If I plan to do a data load to update records, the 18-digit version should be used to be absolutely sure you have the correct record because while really, SUPER unlikely, it is possible there would be another record with the same 15-digit Id. I've not personally experienced it, but I've heard horror stories.
