Hi Bruce,

I'm not sure, but it could be a minor difference in how they are querying for the value to display on the back end. I'm mentioning this because I have an active ticket open with a similar issue that is the result of Salesforce trying to get an ID, but mistakenly querying for a Name instead.

Is the ID still clickable?

If not, there are…

Read more

Hi Arun!

It's important that we use handlers for our triggers for many reasons:

• they keep logic out of the triggers themselves, which significantly improves legibility and ease of alteration because it allows the trigger itself to act as a sort of router, passing along tasks to the handlers
• Because the logic is separated out this way, it is…

Read more

If you did this, it would fail because you're essentially trying to make a duplicate record here. You are correct, however, in that the After context has access to the ID(s) of the updated record(s). In fact, with After Update we have use of trigger.new, which contains not only the ID(s) but all the fields for the updated records. To make…

Read more