If you are using the Gravity Forms Extension for WooCommerce you may want to discuss this with their developers as i'm not familiar enough with what is going on under the hood with that extension to be able to provide you with guidance on how to filter what is passes to the WooCommerce cart.
If what you want to do is not store the value of some fields that are used solely for conditional logic purposes then you can use ANOTHER hook, the gform_pre_submission hook, to execute custom code that will set the value of the field you want to update so that it is empty.
The gform_pre_submission hook is triggered AFTER validation has occurred but BEFORE notifications and the entry itself is created. You an find documentation on the gform_pre_submission hook here:
But please note, the hook is just a code hook... by itself it doesn't implement any code or customizations. You have to write the custom PHP necessary to accomplish what you want to do as part of the code that you use with that hook.
As for your question regarding your date date fields...
The gform_after_submission hook just gives you access to the entry object to both get data from the entry object and update data in the entry object. It doesn't send data to 3rd party applications, whatever custom PHP you write is what sends data to 3rd party applications. So if you don't want to send a particular field to the 3rd party application then don't write the code to do so.
If you want to pass your three drop downs as a single date value then you would write custom PHP using the gform_after_submission hook to get the value of those fields from the entry object and then combine them into a single value that you then pass to another application OR store as the value of a field in the entry object and update/replace an existing value.
You can do whatever you want with the gform_after_submission hook as long as you know how to do what you want to do using PHP.
Posted 7 years ago on Tuesday February 21, 2012 | Permalink