<p>Craft has a pretty extensive <a href="https://craftcms.com/docs/relations" rel="nofollow noreferrer">relationship</a> system, which is what you'd probably want to take advantage of here.</p>

<p>You could make another channel called "Offers" and each offer would be an entry in that section.</p>

<p>Then you could create an <a href="https://craftcms.com/docs/entries-fields" rel="nofollow noreferrer">entries field</a> called "Ad" and save it in your "Offers" section's field layout and have its source set to "Ad".</p>

<p>Then, when saving an offer, you'd select the ad(s) in the ad field the offer belongs.</p>

<p>You'd be able to query those relationships from the template side like so: <a href="https://craftcms.com/docs/entries-fields#examples" rel="nofollow noreferrer">https://craftcms.com/docs/entries-fields#examples</a></p>

CC BY-SA 3.0
2017-03-21T18:41:22.160Z
2017-03-21T18:41:22.160Z
Brad Bell
<p>Let's say I have an auction website:</p>

<ol>
<li>'Ads' would be a section -> channel <br></li>
<li>The ads in it would be entries in the channel</li>
</ol>

<p>Let's say guest users can make an offer on the action/ad. I would like to save all the offers in the entry, so I could read them out front-end.</p>

<p>What would be the best way to save these entries? I'm having difficulty understanding this structure-wise.</p>

<entries><entry><structure><guest>
Structure question (entry in entry?)
# Structure question (entry in entry?)

(Asked by: username_0 on 2017-03-21)

Let's say I have an auction website:

1. 'Ads' would be a section -> channel
2. The ads in it would be entries in the channel

Let's say guest users can make an offer on the action/ad. I would like to save all the offers in the entry, so I could read them out front-end.

What would be the best way to save these entries? I'm having difficulty understanding this structure-wise.

**Tags:** entries, entry, structure, guest


---

## 1 answers

### Answer by username_1 on 2017-03-21. Score: 1

Craft has a pretty extensive [relationship](https://craftcms.com/docs/relations) system, which is what you'd probably want to take advantage of here.

You could make another channel called "Offers" and each offer would be an entry in that section.

Then you could create an [entries field](https://craftcms.com/docs/entries-fields) called "Ad" and save it in your "Offers" section's field layout and have its source set to "Ad".

Then, when saving an offer, you'd select the ad(s) in the ad field the offer belongs.

You'd be able to query those relationships from the template side like so: <https://craftcms.com/docs/entries-fields#examples>


---

