Section position should not be set on the client

[UnspeakableHorror]

I do not know how but after a lot of section creation and sorting somehow I ended up with two sections with a similar position (1).

It will be set as follows:

• New sections will always be set as the first one after Summary.

[UnspeakableHorror]

Turns out it's already set on the backend therefore it's a bug.