Row locking

Row locking makes individual rows read-only - useful once a row is “final” (approved, closed, past a deadline) and shouldn’t be edited further.

Who does this

Set up in the property panel by whoever builds the Qlik app.

Steps

1. In the property panel, go to Data → Scribe Configuration → Service Settings → Row Locking and turn on Enable Row Locking.
2. Choose a Lock condition:
   • By column value - pick a Driver column (one of your custom columns) and a comma-separated list of Lock values. Any row whose driver column currently holds one of those values is locked. Turn on Keep driver editable if that same column should stay editable even on a locked row - useful so someone can unlock a row by changing its status back.
   • By Scribe expression - a condition referencing other custom columns with [ColumnName] syntax (for example, [Status] = "Approved").
   • By Qlik expression - a full Qlik engine expression, evaluated per row, for conditions based on the underlying data rather than another custom column.
3. Save the app. Locked rows disable every custom column’s input (except a driver column kept editable), and disable that row’s Edit/Delete actions if present.

Worked example

A budget approval sheet has a Status dropdown column (Draft / Submitted / Approved). Row locking is set to By column value, driver column Status, lock value Approved, with Keep driver editable turned on. Once someone sets a row’s Status to Approved, every other field on that row locks - but Status itself stays editable, so a manager can reopen it by setting it back to Submitted if a correction is needed.

What can go wrong

Caution

A row won’t unlock even after changing the driver value. Confirm Keep driver editable is turned on - without it, the driver column locks along with everything else once its own value matches a lock value, and there’s no way to change it back from the grid.