Editing data

Covers the everyday work of using an RLV Scribe grid: typing values in, adding and removing rows, and how and when those changes are actually saved.

Editing a value

Select any custom column’s cell and type or choose a new value - it behaves like the column type it is (a text box, a dropdown, a date picker, and so on). If the app author turned on Show Actions Column, you can instead select the Edit icon on a row to open it in a dedicated dialog, with Previous/Next buttons to move through rows without closing it.

Adding a row

If Allow Adding Rows is turned on for this table, select + in the toolbar. The dialog asks for the row’s key fields (the dimensions that identify it) separately from its custom fields - key values must be unique; RLV Scribe won’t let you create a row that already exists.

Note

Adding a row reloads the Qlik app so the new row’s real values appear in the data model - this is expected, and only affects this sheet’s data, not your other selections.

Deleting a row

If Show Actions Column and Enable ‘Delete Row’ Action are both on, select the Delete icon on a row. Confirm in the dialog that appears - deleting a row removes its data, and (if the app author configured it) reloads the app afterward so it disappears from the rest of the sheet too.

Saving your changes

RLV Scribe saves in one of two ways, set by the app author:

• Autosave off (the default) - after editing, Save and Discard buttons appear with a count of pending changes. Nothing is sent to the database until you select Save. If a save fails, the error stays visible and retryable rather than silently disappearing.
• Autosave on - changes save automatically a few seconds after you stop typing (the app author sets exactly how long). A small cloud icon shows how many changes are still waiting to be sent.

What can go wrong

Caution

A save keeps failing. The error message stays on screen until it succeeds or you discard the change - don’t assume a failed save went through. If it persists, check with whoever administers RLV Scribe; it usually means the backend can’t reach the target database right now.

Caution

Adding a row says the key already exists. Another row already has the same combination of key-field values - each row’s key fields must be unique. Check your Qlik selections; the existing row may simply be filtered out of view.

Worked example

A regional sales lead opens a budgeting sheet with autosave off. They update three cells, notice the pending-changes badge reads “3”, and select Save - the badge clears once the save succeeds. Later, they add a new row for a region that hasn’t been budgeted yet, filling in its key fields (Region, Year) and an initial Amount; the app reloads briefly and the new row appears alongside the others.