Bug: POST CustomCharacter endpoints returns 409 error

[BillTheBeast]

What doesn't work?

POST CustomCharacter endpoints returns 409 error.

HTTP/1.1 409 Conflict: {"errors":[{"response":"NOT_UNIQUE","status":409,"message":"Field "name" with value "null" already exists","name":"","reason":"NOT_UNIQUE","field":"name","value":null,"additional":{"key":"name","value":null},"statusCode":409,"objectType":"APIError"}],"statusCode":409}

This means that because the POST endpoint only takes CharacterID and level. One cannot provide name to it (and even if you try is doesn't receive it)
This means that player cannot provide

What is the endpoint and method? (if applicable)

Endpoint: CustomCharacter/

Method: POST

How can it be reproduced?

1. Try to send character data to CustomCharacter endpoints while logged in (ie. have AccessToken) and one CustomCharacter has already been created.

What should it do instead?

Allow us to add a new CustomCharacter recardless if the name isn't unique.

[MikhailDeriabin]

@BillTheBeast

It is probably due to old database schema wasn't updated. It should not return 409 normally. I will have a look at it now

[MikhailDeriabin]

Now it is fixed by updating DB schema