-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Undefined
-
The position field of the fields definition is misconfigured on all fields definitions after one of them is updated.
For example
Values before:
{"fields_definition": {
"id": 9,
"target": "Account",
"position": 1}},
{"fields_definition": {
"id": 10,
"target": "User",
"position": 1,}},
{"fields_definition": {
"id": 12,
"target": "Cinstance",
"position": 1,}},
{
"fields_definition": {
"id": 11,
"target": "User",
"position": 2,}},
{
"fields_definition": {
"id": 13,
"target": "Cinstance",
"position": 2,}}
Updates the position of the fields definition with id 11:
curl -v -X PUT "http://provider-admin.3scale.localhost:3000/admin/api/fields_definitions/11.json" -d 'access_token=a4f50140881dc611d439bc5ba4183886a7d3d4ab6bd4ee6c89713f1d0a6e8215&position=1'
After the update:
{"fields_definition": {
"id": 11,
"target": "User",
"position": 1}},
{"fields_definition": {
"id": 9,
"target": "Account",
"position": 2,}},
{"fields_definition": {
"id": 10,
"target": "User",
"position": 2,}},
{"fields_definition": {
"id": 12,
"target": "Cinstance",
"position": 2}},
{"fields_definition": {
"id": 13,
"target": "Cinstance",
"name": "description",
"position": 2}}
The problem with the correct position also occures when the fields definitions are update via the UI.
