Unlearn Series - Workaround - Avoid update to dot walked fields

[Kalaiarasan Pus]

Adding dot walked field to the form provides a quick way to see the related information on the same form without requiring you to hover over fields or navigating to the related records. It also saves us from creating extra fields or scripts to display the information required.

I ran into a strange issue and had opened a question on community.

How to avoid updates to dot walked fields

The issue was simple. I had dot walked a list field on the form and had made it read-only. But even when the field was read-only, it was getting updated/was replacing the content of the original record's field, when the form containing the dot walked field was being saved. I had opened up HI ticket in parallel which ended up being recognized as a problem.

In the meantime to resolve the issue, I came up with a simple workaround using a before update business rule. Create a business rule on the table whose record is dot walked on the form.

Add a condition as below and abort the action using 'Abort action' checkbox.

Condition :

gs.getSession().isInteractive() && gs.action.getGlideURI().toString().indexOf('table name on which the record is dot walked.do?')>-1

Example: Let us consider that Change request's watchlist field is being dot-walked on incident table. Then the business rule would need to be created on change request table and the condition would be as below

gs.getSession().isInteractive() && gs.action.getGlideURI().toString().indexOf('incident.do?')>-1

Hope this helps someone in need.