isUnreadByOwner Field on Lead Updates to 'False' When Non-UI Changes Are Made Following Campaign Member Update
Last updated 2021-09-14 ·Reference W-5850255 ·Reported By 24 users
Our current documentation regarding the isUnreadByOwner field on Lead object reads:
“A lead will only be considered "Read" when the owner of that lead views / edits that lead in the UI. It will remain "Unread" even if someone other than the owner views or edits the lead record or some mass action is taken outside of the UI (i.e. a mass email to many leads sent via the API)...The only type of mass action that can affect it would be to update the specific 'Unread by Owner' field using the API (e.g. using the Excel Connector or the Dataloader). Specifically if the owner of a Lead edits it through a list view using the "Change Status" button or "Inline Editing" the Unread checkbox will NOT be updated.”
However, it's been found that in some situations this flag can be set to 'False' when the lead is updated via a process builder or trigger, followed by an update to the campaign member associated with the lead being updated. The downstream effects of this can vary depending on your implementation but it can for example impact user list views if they are filtered to only show Leads that are unread by their owner.
> Insert a lead via workbench/API so that the unread flag is true.
> Create a Campaign and add this lead to the campaign.
> Create a process (using process builder) on Campaign member object.
> For the condition choose when Campaign Member status changes
> For the update action choose the action on related lead record. Update the lead source to any value from the available picklist. Save and activate the process.
> Now run a select query on the Lead created above to ensure that the isUnreadByOwner flag is True.
> Edit the Campaign Member from UI to set the the status to say “Responded” and save.
> This should trigger the process created earlier and update the lead source on the related lead.
> Now run the select query on the same lead created above and not that the isUnreadByOwner flag is False.
Note: While this is one reproducer, we've also see that once a lead changes ownership from a queue to an individual, when that user nagivates from the "My unread leads" listview on the leads tab, to anywhere else in the app (home tab, cases tab, etc) and back to the leads tab, the record in question will no longer show in the "My Unread Leads" listview, and the isUnreadByOwner flag is set to false with no action taken to do so.
Note: If the lead is updated (following an update to campaign member) within a trigger context instead of the process builder context you will still see the flag getting updated.
No known workaround at this time.
Reported By (24)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.