We are not seeing multiple entries like that.
Our form is not public and has Save and Continue enabled in addition to the Partial Entries (PE) Add-on. We are using PE to trigger submission of the form values to Zapier when a “Ready to Review” checkbox is checked by the user. This keeps the entry open for editing using Save and Continue instead of closing it as would happen with a normal submission button, which we have disabled.
Have you enabled logging for GF? If not, go to GF Settings > Logging and enable. This will give you more info on what is happening.
We have zeroed in on the Partial Entries Add-on - or more specifically the custom code that triggers the submission to Zapier - not working with Zapier Add-on 4.0. Here is the current code we are using:
add_action( ‘gform_partialentries_post_entry_saved’, ‘send_to_zapier_on_partial_entry_saved’, 10, 2 );
function send_to_zapier_on_partial_entry_saved( $partial_entry, $form ) {
if ( class_exists( ‘GFZapier’ ) ) {
GFZapier::send_form_data_to_zapier( $partial_entry, $form );
} elseif ( function_exists( ‘gf_zapier’ ) ) {
gf_zapier()->maybe_process_feed( $partial_entry, $form );
}
}
add_action( ‘gform_partialentries_post_entry_updated’, send_to_zapier_on_partial_entry_updated’, 10, 2 );
function send_to_zapier_on_partial_entry_updated( $partial_entry, $form ) {
if ( class_exists( ‘GFZapier’ ) ) {
GFZapier::send_form_data_to_zapier( $partial_entry, $form );
} elseif ( function_exists( ‘gf_zapier’ ) ) {
gf_zapier()->maybe_process_feed( $partial_entry, $form );
}
}
add_action( ‘gform_after_update_entry’, ‘send_to_zapier_on_update’, 10, 2 );
function send_to_zapier_on_update( $form, $entry_id ) {
$entry = GFAPI::get_entry( $entry_id );
if ( class_exists( ‘GFZapier’ ) ) {
GFZapier::send_form_data_to_zapier( $entry, $form );
} elseif ( function_exists( ‘gf_zapier’ ) ) {
gf_zapier()->maybe_process_feed( $entry, $form );
}
}
The only real difference between this code and the code we were running without issue with ZA 3.3 is the addition of the elseif and the entire 3rd function.
Additionally, the logs for PE when running ZA 4.0 will show this:
DEBUG → GF_Partial_Entries::maybe_save_partial_entry() Running.
DEBUG → GF_Partial_Entries::create_partial_entry() Aborting; Not enabled.
instead of something like this when running ZA 3.3:
DEBUG → GF_Partial_Entries::maybe_save_partial_entry() Running.
DEBUG → GFFeedAddOn::maybe_process_feed(): Checking for feeds to process for entry #5 for gravityformspartialentries.
DEBUG → GFFeedAddOn::maybe_process_feed(): No feeds to process for entry #5.
DEBUG → GF_Partial_Entries::maybe_save_partial_entry(): Updating existing partial entry. Success. Entry ID = 5.
Even though it says PE is not enabled, it is.
Really frustrating. We rolled back to 3.3, but two of our Zaps were auto-migrated to 2.0 so they no longer function with ZA 3.3 and never worked with ZA 4.0 + PE.
