won’t pre-populate price field with pods field info

You would pass that kind of information either as a query variable, from wherever you’re calling the field; that’s in the dynamic population of fields in gravity forms:

https://docs.gravityforms.com/using-dynamic-population/

You can pass a query variable to the form: ?price=2500
Set the value in the shortcode that you’re calling the form from (or where you’re inserting it, so if it’s on your post type or template, you could do field_values='price={@price}' or you can use the hook/filter method described above to load it with code. All of that is pretty much outside Pods or our plugin. We populate field values if you’re going to use the form to ‘edit’ the current post, or we populate drop-down values for selection fields.

If you’re still confused by all of that, please drop into our Slack Chat at https://pods.io/chat/ and I can try to help you do what you’re trying to accomplish.

thanks, Jim

I actually was able to get help from The GF people on this.

add_filter( 'gform_field_value_workshop_fee', 'workshop_fee_population_function' );
function workshop_fee_population_function() {
$price = pods_field( 'workshop', get_the_id(), 'workshop_cost', true);
return $price;
}

Strange thing is that I had no problem at all using your plugin to easily populate other gf fields, but for some reason, had trouble with the price field. Maybe because there were several variables or the decimals (ie. 2500.00).

thx

@grantatdesign What other GF Fields were you able to populate and what method were you using to populate them?

Thanks for this example; this looks like you’re using a form on the same page as the post you’re editing or at least populating a form with fields from the current post, correct?

yes that’s correct.

For the purpose of this form, I didn’t really need any other fields added to the form, but I did test several of them and they all worked fine.

Actually I see it’s not working.
I added a field in GF
https://www.dropbox.com/s/dop1g63oaukynzu/Screenshot%202018-01-24%2012.38.52.png?dl=0

here’s what gf looks like
https://www.dropbox.com/s/l8ce5ya1mkrqt6w/Screenshot%202018-01-24%2012.40.16.png?dl=0
https://www.dropbox.com/s/cx88sakwg9p8aw1/Screenshot%202018-01-24%2012.39.50.png?dl=0
https://www.dropbox.com/s/1fxlenvq0vlxa3g/Screenshot%202018-01-24%2012.40.43.png?dl=0
https://www.dropbox.com/s/58u13ilz4l4yjoy/Screenshot%202018-01-24%2012.40.58.png?dl=0

• This reply was modified 6 years, 10 months ago by granatdesign.

@granatdesign What were you using to populate the other fields? The checkbox on the Pods Feed Processor?

was this correct?

https://www.dropbox.com/s/58u13ilz4l4yjoy/Screenshot%202018-01-24%2012.40.58.png?dl=0

You’ve got two different things going on here:

The checkbox for ‘Enable populating of field values’ on the Pods Feed configuration is typically intended for ‘editing’ the current post, since it would be designed to be actually loading the values from the current post.

In the case of a registration to a conference, you need one form entry (and probably one ‘reservation post’ for every person registering to your conference, so you’re actually only pre-filling some specific fields with values from the conference (the conference ID and the amount of the registration), but the other fields might not have anything to do with the conference and instead have to be populated with values specific to the registration process.

What type of field is workshop_location? BTW, it’s much easier to discuss this kind of stuff on our Slack Chat at https://pods.io/chat/