Can't write to dotwalked fields on form, but on main form can write

[Shane J]

I'm trying to get Request.Requested_For onto the RITM form, and though I can get it to show up, I can't seem to allow it to be writable.   If I go directly to the Request form itself, I can write to Requested_For just fine however.   I thought it may be field specific so I just added another field for fun and same thing - can't write to it if dotwalked.

I've checked UI Policies, Client Scripts, and ACLs and I can't find anything causing this.   Debug says I should be able to write to it.

I checked my developer instance and it looks this works OOB, but the reason isn't obvious to me.

Any idea why?

[Deepak Ingale1]

Hi,

I just checked on my personal instance. It is allowing me the write access to requested for field

One thing might be the case with you, please check if "Request" field is added on the form or not. If not, try to add it and see if it works.

[Shane J]

Yeah I tried that, no dice:

[ccajohnson · Accepted solution]

Since the request field is what you are dot-walking through, you may want to check ACL, UI Policies, etc. on that. It may just be that you cannot get to the dot-walked field if the reference field you are dot-walking through is read-only.

[Shane J]

OK, so basically I was making the entire record read-only by setting that fields Dictionary entry to read-only?