The Quick Edit feature allows users to edit fields directly a table view. The admin can determine which users can enable or disable Quick Edit within particular tables by setting up the required permissions. Before using Quick Edit, you must define two group permissions, enable Quick Edit for , and then create the view.
Using Quick Edit
In a quick edit view, a pencil icon appears in the column heading above each editable field. Two buttons, Save Changes and Cancel Changes, appear in the table's.
- Click the field to begin editing. The input aid depends on the type of field: for example, a choice list uses a drop-down selector, while an HTML field opens the HTML editor. Once finished, choose Next to move to the next editable field, Save, or Cancel.
- After editing several fields using Next, use the Save Changes button in the action bar to save. Click Cancel Changes to roll back all field edits since the last save.
Enabling Quick Edit for Fields
The option to allow a field to be quick edited is off by default. You can use the set field properties button to enable several fields at once for quick edit. To turn on Quick Edit for a field:
- Go to (Setup Table) > Fields > edit field.
- On the Permissions tab of the field wizard, scroll down to find the "Allow this field to be edited directly from a table view" option and select Yes.
- Once the field has been enabled with these permissions, the Quick Edit option will be available in the View wizard.
For additional information on using quick edit, see below:
Field Type Limitations
The following types of fields cannot be edited in a Quick Edit table view:
- Calculated Result
- Calculation on multiple linked records
- File (File with Versioning)
- Image (Image with Versioning)
- Action buttons
Hierarchically dependent fields can be edited in Quick Edit views. However, the parent field must also be included in the view. The reason for this is that the system must be able to read the data from the parent field in order to determine the allowed values in the dependent field.
For example, suppose you have two choice fields, Type and Subtype, and Subtype is hierarchically dependent on Type. If you want to use the Subtype field in a quick edit view, Type must also be added to the view.
Conditionally required fields can be added to quick edit views, and the requirement condition will be properly applied regardless of whether the parent field is included in the view. If a conditionally required field meets the requirement condition but does not appear in the view, it will not be required. This parallels the behavior of conditionally required fields in a record: if the user cannot see a field, it will not be required.
Visibility dependent fields appear in a view regardless of the visibility condition. However, if the condition is not met and the field should not appear in the record, users cannot edit the field. A warning icon is displayed if users attempt to edit a field which does not meet its visibility requirement.
If a field has been set up to allow editing based on the values in another field, and the condition is not met, users will see a warning icon as above.
Validation actions that present a pop-up message to the user are not applied during quick edit at this time.
The Save Changes / Cancel Changes buttons do not appear.
The Save / Cancel Changes buttons are part of the table’s action bar. You must include an action bar for the buttons to appear. With no action bar, users must save changes individually. If you want users to see only the Save / Cancel Changes buttons but no other action bar items, you can include an empty action bar.
When I use Quick Edit, sometimes the changes are not saved.
Validation actions are not presented to users when quick editing records from a table view. Depending on how the actions were set up, this can prevent record changes if the data entered does not meet a validation requirement.