Search Field Mapping
Introduction
Field mapping connects fields from the optional frontend search form to fields stored in the Target Form.
When a visitor supplies a value, Gravity Search uses the corresponding mapping to determine which Target Form field to query and which comparison operator to apply.
Field mapping is required only when visitor-facing search fields should affect the results. A Search using initial-load settings, defaults, and predefined filters can operate without field mappings or a frontend search form.
How Field Mapping Works
Each mapping rule connects a source field from the frontend search form to a field in the Target Form.
When the source field contains a value, Gravity Search compares that value with the stored Target Form field using the selected operator.
A mapping rule contains:
- Source Field: The search form field that supplies the visitor’s value.
- Target Field: The Target Form field whose stored entry value will be queried.
- Operator: The comparison performed between the supplied and stored values.
Incomplete or incompatible mappings are ignored when the query is generated.
Mapping Rules
You can add one or more mapping rules under Search Form → Filter Mappings.
For example:
- Keyword → Business Name
- City → City
- Category → Business Category
Each applicable rule adds a condition to the query. You can also map the same source field to multiple Target Form fields, such as mapping a Keyword field to both Business Name and Business Description.
Select a source field and click Add Rule, then choose its Target Field and Operator.
Supported Field Types
Eligible source fields from the Search Form Builder include:
- Single Line Text
- Paragraph Text
- Number
- Checkboxes
- Radio Buttons
- Drop Down
- Multi Select
- Date
- Time
- Hidden
- Name
- Address
Eligible Target Form fields include compatible text, choice, numeric, date, time, contact, Name, and Address fields.
Gravity Search determines the available operators from the selected source-field type and limits the available fields and operators to compatible options.
For date comparisons, use a Date source field whenever possible. If a Drop Down or Radio Buttons field supplies preset dates, store its option values in Y-m-d format, such as 2026-01-05.
Filter Match Mode
Filter Match Mode determines how multiple applicable mapping rules are combined.
Match All Rules (AND)
An entry must satisfy every applicable mapping rule to appear in the results.
For example:
- Category = Restaurant
- City = Miami
Only restaurants located in Miami will be returned.
Match Any Rule (OR)
An entry can satisfy any applicable mapping rule to appear in the results.
For example, map the same Keyword source field to:
- Business Name
- Business Description
An entry will be returned when the supplied keyword matches either Target Form field.
Field Mapping Examples
Keyword Search
Map a text source field to a Target Form text field using Contains or Equals.
Single-Choice Search
Map a Drop Down or Radio Buttons source field to a compatible Target Form field using Is.
Multiple-Choice Search
Map a Checkboxes or Multi Select source field to a compatible Target Form choice field using In or Not In.
Date Search
Map a Date source field to a Target Form Date field using Equals, Greater Than, Greater Than or Equal, Less Than, or Less Than or Equal.
Numeric Search
Map a Number source field to a compatible Target Form field using the available numeric comparison operators.
Best Practices
- Add and label fields clearly in the Search Form Builder.
- Include only the fields visitors need to refine the results.
- Use Match All Rules (AND) when every supplied filter must match.
- Use Match Any Rule (OR) when matching any applicable rule should return the entry.
- Use a Date source field for date comparisons whenever possible.
- Review field mappings after Target Form fields are added, removed, or changed.
- Test the Search using empty, partial, and complete visitor input.