How to avoid updates to dot walked fields

Kalaiarasan Pus · ‎04-26-2017

Let's a scenario of two tables incident and change.

I have dot walked the change reference field on incident and dot walked it's change type field and added to the form layout of incident.

Tab 1 - Open a incident record.

Tab 2 - Open the change record that is related to tab 1 incident and change it's type field.

Tab 1 - Save the record.

The changes done on tab-2 is lost and the type value is overwritten. How do avoid this behaviour?

Kalaiarasan Pus · ‎05-24-2017

I created a HI ticket for this as even when the dot walked fields were read-only on the form, the fields were getting updated. They have created a problem for this.

I ended up coming up with a workaround to resolve this. Here is the link of the blog if someone needs a workaround for this.

Unlearn Series - Workaround - Avoid update to dot walked fields.

View solution in original post

Mihir Mohanta · ‎04-26-2017

Hi Kalai,

It is an expected behavior because , type field is a field of change form and you have extended it and displayed in incident form.

You can make the extended (dot walked)field readonly by writing client script in the incident table to avoid update in the change form.

Kalaiarasan Pus · ‎04-26-2017

The field is already read only. I am trying to make it read-only in true sense.

And I know it is expected behaviour and I am just trying to overcome that.

Pradeep Sharma · ‎04-26-2017

Hello Kalai,

How about creating a client script and compare the Old value with the new value and return false wit the alert statement?

Kalaiarasan Pus · ‎04-26-2017

I have made the fields read-only. So adding a script would cause annoyance at best. There are around 15 dot walked fields from 2 different reference fields. So adding a script would not look great.

No OOB way or property to overcome this?