Gravity Forms Populate Anything

What does it do?

GF Populate Anything allows you to dynamically filter and populate field choices and values with posts, users, taxonomies, terms, Gravity Forms entries, and databases. Pretty much anything! Choices and values can be filtered based on the values entered/selected in other fields allowing you to fetch and populate fresh, dynamic data as the user interacts with the form.

GF Populate Anything also provides support for Live Merge Tags which allow you to display dynamic, filterable data in your field labels, descriptions, and content.

Features

Documentation

1. How do I enable this functionality?
2. Feature Details
   1. Populating Choices Dynamically
      1. Example Configuration
      2. Frontend
   2. Populating Values Dynamically
      1. Example Configuration
      2. Frontend
   3. Filtering Objects
      1. Filter Groups
      2. Filter Operators
      3. Filter Property
         1. Post
         2. Taxonomy Term
         3. User
         4. Gravity Forms Entry
         5. Database
      4. Filter Values
         1. Default
         2. Form Field Values
   4. Field Value Objects
      1. Example Field Value Object Configuration
      2. Example Field Value Object Frontend
   5. Live Merge Tags
      1. Example Live Merge Tag
3. Known Limitations
4. Hooks

How do I enable this functionality?

After GF Populate Anything is installed, you’ll want to enable “Populate Choices Dynamically” or “Populate Value Dynamically” for a given field in the Gravity Forms Form Editor. Here’s what that looks like when populating choices.

	Add a field that supports choices such as Drop Down or a text-based field such as Single Line Text.
	Enable dynamic population for the fields that you wish to dynamically populate.
	Select an object type that you wish to populate the field with.
	Optionally add filters to show the desired objects.
	Designate what object properties should be displayed by setting the Choice or Value Template.

Feature Details

Populating Choices Dynamically

If you wish to dynamically populate a choice-based field’s choices, you can do so by enabling “Populate choices dynamically” in the field’s settings.

Example Configuration

In the example below, we configured a radio button field to have its choices dynamically populated with users who have the “Administrator” role.

Frontend

Here’s what the configured radio button field looks like on the frontend.

Populating Values Dynamically

Populating values with GF Populate Anything is similar to how populating choices work. Enable “Populate value(s) dynamically” in the field’s settings and then configure it accordingly.

Example Configuration

In the example below, we configured a single line text field to have its value populated with the post title of the most recently added post.

Frontend

Here’s what the configured single line text field looks like on the frontend.

Filtering Objects

Filter Groups

Create groups of conditions that filter which objects are populated into the field. Add a condition to your group with the (+)/(-) icons to the right. All conditions in a group must be true for the group to match. Add another group by clicking the “Add Filter Group”. Objects that match any group will be populated into the field.

Filter Operators

• is
• is not
• > (greater than)
• < (less than)
• >= (greater than or equal to)
• <= (less than or equal to)
• contains
• starts with
• ends with
• is LIKE
  • Available wildcards
    • % – Zero, one, or multiple characters
    • _ – Single character

Filter Property

Depending on the object type you select, you will have different properties to select from.

Post

• Author
• Parent Post
• Post Content
• Post ID
• Post Status
• Post Title
• Post Type
• Post Taxonomies (Dynamic)
• Post Meta (Dynamic)

Taxonomy Term

• Name
• Parent Term
• Slug
• Taxonomy Term
• Term ID

User

• Display Name
• Role
• User Email
• User ID
• User URL
• Username
• User Meta (Dynamic)

Gravity Forms Entry

• Created by (User ID)
• Entry ID
• Fields (Dynamic)

Database

The Database Object Type’s properties are dependent on the table you select. Once you select a table, the properties will be all available columns on the MySQL Table.

Filter Values

Default

After selecting the filter property, the Filter Value dropdown will be populated with a list of values that apply for that property. For example, if you are populating posts into a field and add a filter condition for the “Post Status” property, the Filter Value dropdown would be populated with a list of available post statuses (e.g. Draft, Pending Review, Published).

Form Field Values

Objects can also be filtered by values entered by the user when the form is filled out. After selecting the filter property and operator, select the desired field from the Form Field Values option group. When a user enters a value into the specific field, the objects populated into this field will be filtered by that value.

Field Value Objects

One common use case with GF Populate Anything is populating field values from a field with dynamically populated choices. You can do this by manually configuring the Object Type and Filters to use field values, but an even easier way is to use a Field Value Object.

Field Value Objects are available on any field that supports values when there is another choice-based field that has dynamically populated choices on the same form.

Example Field Value Object Configuration

In the example below, we wired up a single text field to display the user ID of the selected user in the radio field above it.

Example Field Value Object Frontend

Live Merge Tags

When GF Populate Anything is activated, merge tags anywhere on a page with a Gravity Form will be automatically re-populated when any field is changed.

Live Merge Tags can be used anywhere on a page including field labels, post content, or even widgets.

Example Live Merge Tag

Known Limitations

• Dynamic choices are not yet available in conditional logic.

Hooks

• gppa_missing_filter_value
  
• gppa_no_choices_text
  
• gppa_no_choices_value
  
• gppa_process_template
  
• gppa_query_limit