Field is still saved even though it is set to read-only about payload

[jmikrut]

Hey @CherryDT — there are a few complexities with this that make it somewhat difficult to accomplish what you're looking for without some side-effects.

Marking a field as readOnly indeed keeps the field in the form state so that you can access / manipulate it. It also means that when you run functions like form.getData(), that field will indeed be included in the data from the form. But you're right, the field's data will indeed be sent through the REST request for create / update.

There are some alternatives, though. You can use admin.disabled: true to completely disable the field, which will then completely hide the field from the admin UI. You could then use a custom UI component to show the field's value in a read-only fashion.

Alternatively, you could add a beforeValidate hook that simply takes the field's originalDoc value and returns that, omitting whatever was passed from the API, and reverting back to the value you want.

We might be able to solve for this at some point in the near-future, but it likely will be against 3.0. I will mark this as a Feature Request for now and we will keep an eye on interest for this topic. If more people show interest, we will prioritize a way to make this happen!