Introduction

When users edit data in a grid, the Save button and save counter work together to track and commit changes. As a Grid Administrator, understanding how the save mechanism works helps you configure grids that provide users with clear feedback on their pending changes and prevent accidental data loss.

Prerequisites

Whether working in PqW or PrW, you must have the XRL_Admin permission set to configure grid save behavior. Familiarity with the XRL Configure panel and Table Settings.

How the Save Button Works

The Save button appears in the grid toolbar (typically as a disk/save icon).

• It remains inactive/disabled until the user makes at least one edit in the grid.
• Once a change is made, the Save button becomes active — indicating there are unsaved changes.
• Clicking Save commits all pending changes in the grid to the database in a single operation.

After a successful save, a success toast notification confirms how many records were updated. For example, in the 

The Save Counter

1. The save counter displays the number of records with pending (unsaved) changes.
2. As users edit more cells or rows, the counter increments.
3. After saving, the counter resets to zero.
4. This gives users a clear visual indicator of how much uncommitted work exists.

Changed Field Highlighting

When a user edits a cell, the changed field is highlighted (similar to Salesforce's native style) to visually distinguish modified values from original values. On hover, some grids show the original value in a tooltip (e.g., green row showing previous prices in PqW Edit Quote Grid).

Highlighting persists until the changes are saved or discarded.

Save Restrictions

The grid will block or partially block a save in these scenarios:

• Mandatory field empty — If a required field is left blank, the save is blocked, and an error is displayed.
• Validation rule failure — Custom validation rules configured on the object will fire during save. Failed records show error messages.
• Partial success — If some records save successfully and others fail validation, the grid shows both a success count and error messages for the failed records.
• Record locks — Records locked by approval processes or workflows cannot be saved until unlocked.

Discard / Navigate Away Behavior

If a user has unsaved changes and attempts to navigate away from the grid or close the browser tab, a confirmation prompt warns them that unsaved changes will be lost. Choosing to leave discards all pending edits and resets the save counter to zero. There is no "Undo" once changes are discarded — users must re-enter their edits.

If a user wants to intentionally discard changes without navigating away, they can refresh the grid. The save counter resets and all highlighted fields revert to their original values.

Configuration Options

As an admin, you can influence save behavior through:

Where This Applies in PqW and PrW

Summary

This article explains how the Save button and save counter work in XRL grids, including how pending changes are tracked, how changed fields are highlighted, what conditions can block a save, and how administrators can configure save behavior.