<p>Looking at your screenshot it seems like you just want to list entries straight from the entries field. If that's the case, you won't need to use the <a href="http://buildwithcraft.com/docs/relations#the-relatedTo-param" rel="nofollow">relatedTo param</a>. Give this code a try:</p>

<pre><code>{% for entry in entry.fieldHandle %}
    &lt;p&gt;{{ entry.title }}&lt;/p&gt;
{% endfor %}
</code></pre>

CC BY-SA 3.0
2015-03-09T13:57:25.837Z
:D Ooops. You are right. My code is unnecessarily complicated.
KSPR
CC BY-SA 3.0
2015-03-09T14:31:07.010Z
@Kaspar The relatedTo param would have been ideal if, for example you wanted to find which entries have 'Anastasia' in the 'Musiker' entry field. But yes in this instance, a simple for loop is all that's needed :)
Jamie Wade
CC BY-SA 3.0
2015-03-09T12:36:54.930Z
2015-03-09T12:36:54.930Z
Jamie Wade
<p>It's <code>order('sortOrder')</code> instead of <code>fixedOrder(true)</code>.</p>

<pre><code>{% set entries = craft.entries({
    relatedTo: { sourceElement: entry, field: 'entriesFieldHandle' },
    order: 'sortOrder',
    limit: null
}) %}
</code></pre>

<p>If you don't make any further modifications to the params (i.e. reverse order, other limit) there's also the short syntax for the above that Jamie already suggested:</p>

<pre><code>{% set entries = entry. entriesFieldHandle %}
</code></pre>

CC BY-SA 3.0
2015-03-09T13:58:42.280Z
I tried that and it gave a error. I guess it was due to the related param. But no it's no longer needed.
KSPR
CC BY-SA 3.0
2015-03-09T14:53:42.517Z
Ahh that's strange, because I shamelessly copied it from [the docs](http://buildwithcraft.com/docs/entries-fields#templating).
carlcs
CC BY-SA 3.0
2015-03-09T15:02:28.793Z
Yes. I did the same. Thats Why I asked in the first place. I thought `sortOrder` must be a placeholder then.
KSPR
CC BY-SA 3.0
2015-03-09T12:57:04.870Z
2015-03-09T12:57:04.870Z
carlcs
<p>I want to order entries in an "Entries field" by the order I added them to the field. So Anastasia would be first and Beni would be last.</p>

<p><img src="https://i.sstatic.net/9fjbH.png" alt="enter image description here"></p>

<p>My only idea was <code>.fixedOrder</code> like you would do it with an asset field:</p>

<pre><code>{% for entry in craft.entries.section('musiker').relatedTo(entry).fixedOrder(true) %}
   {{ entry.name }}
{% endfor %}
</code></pre>

<p>But that does nothing.</p>

<ordering><entries-field>
Order "Entries Fields" by entry order
# Order "Entries Fields" by entry order

(Asked by: username_0 on 2015-03-09)

I want to order entries in an "Entries field" by the order I added them to the field. So Anastasia would be first and Beni would be last.

My only idea was .fixedOrder like you would do it with an asset field:
{% for entry in craft.entries.section('musiker').relatedTo(entry).fixedOrder(true) %}
   {{ entry.name }}
{% endfor %}

But that does nothing.

**Tags:** ordering, entries-field

---

## 2 answers

### Answer by username_1 on 2015-03-09. Score: 2 | Accepted answer

Looking at your screenshot it seems like you just want to list entries straight from the entries field. If that's the case, you won't need to use the relatedTo param. Give this code a try:
{% for entry in entry.fieldHandle %}
    {{ entry.title }}
{% endfor %}

> **Comments:**
> **username_0**: :D Ooops. You are right. My code is unnecessarily complicated.  
> **username_1**: @Kaspar The relatedTo param would have been ideal if, for example you wanted to find which entries have 'Anastasia' in the 'Musiker' entry field. But yes in this instance, a simple for loop is all that's needed :)  

---

### Answer by username_2 on 2015-03-09. Score: 3

It's order('sortOrder') instead of fixedOrder(true).
{% set entries = craft.entries({
    relatedTo: { sourceElement: entry, field: 'entriesFieldHandle' },
    order: 'sortOrder',
    limit: null
}) %}

If you don't make any further modifications to the params (i.e. reverse order, other limit) there's also the short syntax for the above that Jamie already suggested:
{% set entries = entry. entriesFieldHandle %}

> **Comments:**
> **username_0**: I tried that and it gave a error. I guess it was due to the related param. But no it's no longer needed.  
> **username_2**: Ahh that's strange, because I shamelessly copied it from [the docs](http://buildwithcraft.com/docs/entries-fields#templating).  
> **username_0**: Yes. I did the same. Thats Why I asked in the first place. I thought `sortOrder` must be a placeholder then.  

---

