edit_square Data Entry & Forms

Use generated IDs and custom forms to make data entry faster and safer.

play_circle Video Walkthrough

Step 1: Automate Key Generation

  1. Open the databook and select the table.
  2. Go to DesignSettingsFields.
  3. Find the key column, such as Geography Key.
  4. Change the data type from Number to Generated ID.

Result: The key column becomes read-only. New rows show a placeholder until the record is saved, then Clarity assigns the ID automatically.

Step 2: Enter Data Through Forms

  1. Click Add to create a new row.
  2. Use the form to fill the editable fields.
  3. Leave auto-generated fields alone because they remain read-only.
  4. Click Save.

If you selected hierarchy values before you opened the form, Clarity pre-populates those fields for you. For example, if Africa is selected in the hierarchy, the continent field is already filled in for the new row.

Clarity Databook form showing generated ID behavior, editable fields, and a streamlined governed data entry layout.
Screenshot placeholder: form entry screen with read-only generated ID and hierarchy-driven defaults.

Step 3: Customize Forms for Faster Entry

  1. Click Add to create a new form layout.
  2. Select the columns you want to include.
  3. Remove unnecessary fields, such as a generated key that no user should edit.
  4. Name the form, for example Shorter Form.
  5. Save the form.

You can create multiple forms for different tasks. A short form works well for quick entry, while a broader form can support detailed editing. Forms can also be docked to the side or bottom of the interface.

Tip. Select multiple hierarchy levels before you add a row. Clarity will pre-populate each selected level, so users only fill in the remaining fields.

Key Takeaways

  • Use Generated ID when the system should create and protect the key.
  • Forms provide a cleaner alternative to direct grid editing.
  • Hierarchy selection reduces repeated typing because Clarity can pre-populate matching fields.
  • Custom form layouts reduce noise and keep users focused on the fields they actually need.
  • Generated IDs and hierarchy-derived values stay read-only throughout the workflow.
Last updated
April 2026
Audience
Data owners and form-based data entry users
v3.0 | 20260402