Allow 'one to many' fields to be set to read only

What is the challenge?

'One to many' fields are a custom table relationship field that allows users to add custom table rows directly associated to a record.

At some point a team may decide they no longer want to store data in this way. Today, the only option is to remove the custom table relationship field from the layout.

However the team may still want to see the existing data on the record.

What is the impact?

The only way to stop new entries from being added to a 'one to many' field is to remove it from a layout.

This means users are not able to see historical information any longer without viewing the custom table from workspace settings > custom table.

Describe your idea

Allow 'one to many' fields to be set to read only.