Friday, July 11, 2025
1 change · master
Code cleanup and technical improvements
Messages no longer keep a separate stored record name, reducing outdated or inconsistent labels and simplifying how message context is displayed. Related areas such as Helpdesk, Appraisals, Sign, WhatsApp, Frontdesk, and mobile messaging now rely on the current record name or explicitly provide one when needed.
Original PR description
Reasons to remove record_name
* it is not synchronized, and synchronizing it would be very costly.
This makes searching on record_name / grouping / ... useless;
* some flows even set it to False to speedup sub records creation
and avoid calling display_name on a lot of records e.g. mass
mailing;
* it is unnecessary to store it in most cases;
* its main usage is in discuss / chatter where it is anyway based
on actualy display_name;
In conclusion: get rid of stored 'record_name' field, simplify message
model by making it a computed field displaying the related record
display_name, and let flows displaying / managing messages handle
record names as they want to.
Task-4690371