I would recommend using a UI-Only checkbox field instead of a template field with custom html. Then, you can add actions to the model of the UI-Only field with logic to update the rows you’d like. However, doing this declaratively would be difficult and require use of other UI-Only fields with a MODEL_LOOKUP function to see whether a row has already been checked or not.

I see a few different options depending on what version of Skuid you are using.

(a) use a js snippet that is triggered by the update of the UI-Only checkbox field to loop through the model in question and run logic with if/else field updates using the Skuid Javascript API.

(b) If using Skuid on Salesforce, potentially use a new boolean field, validation rules, roll-up summary fields, and flows to prevent a user from making the field updates on the server-side instead of on the client-side.

Yup – What Sam Said. Use Skuid’s declarative tools for the Control. Then think through the easiest way to control the data entry rules… which will be the hard part.