Find Listings Where
The listing id matches the value of the specified field (About Related Listing)
This type of relation requires having a related listing custom field available either in the same listing type, or a different listing type. You need to fill out the name of the field in the Field Name setting.
When creating new custom fields, if the field is assigned to a field group that's already associated with the listing type, then you are all set. However, if you also create a new field group for this field, you need to remember to associate the field group within the listing type settingds. If you use PaidListings, remember to include the field in your paid plans.
So how does this all work?
With Related Listing Field (Direct) relations, you specifically select the target listings that you want to connect with the source, or current listing.
This a direct relationship.
When a direct relationship is created using a related listing custom field. An indirect relationship becomes available. This indirect relationship goes from the target listing, back to source listing.
This can be more easily explained with an example. Our setup includes Venues and Events, end for Events we've created a related listing custom field where we can select the Venue.
- When creating Events, we can select the Venue (which is also a listing) where the Event will take place.
- Having selected the Venue for the Event, now the Venue itself is automatically connected to the event via an indirect relationship.
- The only way to visualize this indirect relationship is by using the Related Listing Field (Indirect Relation) widget type - which is the topic of this article.
Each time you select a Venue for an Event, that Venue gains a new indirect relation. The widget allows showing all events taking place in a venue, within the venue page, even when the relation is created in the event.
Related listings don't inherit custom field values from other listings. For example, if you connect an event listing with a venue listing, the event doesn't automatically have access to venue address fields, so it won't be possible to perform a search for the event based on the venue custom fields.
Back to listing relations