Conditional Logic on the Edit Entry page
Please read this other article if the “Update” button is not showing up.
Are some of your fields not showing up on the Edit Entry screen? #
That’s because whether the field is shown or hidden might be controlled by a Conditional Logic rule applied to fields on your form.
An example of how Conditional Logic can hide fields:
In the image below, the field “Add your first choice” will only show up if the option “First Choice” is selected on the field “Choose an option below”:

In the Edit View GravityView page, we will add just the field “Add your second choice” to the Edit Entry screen…ย

…and then we will edit anย entry which has the “First Choice” option selected:

This is what happens:

The fix for the problem of the hidden field:
To make the field appear, we’ll remove all fields from the Edit Entry screen…

…and now the fields appear correctly when we try to edit that same entry:

The user now has the choice to select a different option on the field “Choose an option below” and then update this entry with another value:

Don’t want to display all your fields?
If you need to show only specific fields on the Edit Entry screen, then make sure the fields theyย depend on are added to this screen as well.
Troubleshooting validation errors on the Edit Entry page #
#
If you see a “validation error” or “there was a problem” message when saving on the Edit Entry page, but you can’t tell which field is causing it, the most likely cause is a required field that is hidden from the Edit Entry screen but still being validated by Gravity Forms.
This happens because of how conditional logic interacts with Edit Entry. When your form has required fields whose visibility depends on another field (the “controlling” field), and you only add some fields to the Edit Entry layout, the controlling field may not be present. Without it, Gravity Forms can’t evaluate the conditional logic rule, so the hidden required field stays in its default state and fails validation silently.
How to fix it:
- Option A: Add the controlling field. Identify which field controls the conditional logic for the hidden required field, and add it to your Edit Entry layout. This lets Gravity Forms properly evaluate the rule and skip validation on fields that should be hidden. You don’t need to add every field from the form, just the ones that other fields depend on.
- Option B: Remove all fields from the Edit Entry layout. If you leave the Edit Entry layout empty (no fields configured), GravityView will show all form fields. This guarantees every controlling field is present and conditional logic works correctly.
- Option C: Remove the required setting during editing. Use this code snippet to disable the “required” validation on all fields during Edit Entry. This is useful when the required fields already have values from the original submission and you only want users to edit specific non-required fields. See Where to put code samples for how to add it.
Multipage forms and validation errors
If your form uses multiple pages, there is an additional complication. By default, Edit Entry does not fully support multipage forms. Even if you configure Edit Entry to show only fields from one page, Gravity Forms still validates required fields on all other pages. This means required fields on pages you’re not editing can trigger validation errors.
To fix this, enable the beta multipage editing feature:
add_filter( 'gravityview/features/paged-edit', '__return_true' );This makes Edit Entry respect page boundaries so Gravity Forms only validates the fields on the current page. There are tradeoffs: your Edit Entry layout field configuration will be ignored (all fields on all pages are shown), and each page navigation saves the entry immediately. See Edit Entry: Multi-page form editing for full details and known limitations.
How to identify the problem field: If you’re unsure which field is causing the error, temporarily add debug="true" ย to your shortcode or check the form editor for fields marked as required that have conditional logic rules. Look for required fields whose controlling field is not included in your Edit Entry layout.