Rows on question matrix gets rearranged

ghernandezprdp4a · October 13, 2021, 6:59am

stephanealoo · October 13, 2021, 8:03pm

Hi @ghernandezprdp4a
Welcome to the community forum. Could you please confirm exactly is the issue you are experiencing?

Stephane

ghernandezprdp4a · October 14, 2021, 1:00am

After saving a project with a question matrix, the order of the rows get rearranged. it happens regularly. How can i keep this from happening? I downloaded the xls and it seemed that the rows were jumbled there as well.

Kal_Lam · December 11, 2021, 4:33pm

@ghernandezprdp4a, we have an issue for this in our GitHub:

github.com/kobotoolbox/kpi

Matrix question rows and choices rearranged in form-builder (only)

opened 07:28PM - 21 May 21 UTC

joshuaberetta

bug formbuilder frontend

## Description Originally posted in the community forum here: https://communi…ty.kobotoolbox.org/t/order-of-questions-rearranged-in-question-matrix/2087 Internal discussion: https://chat.kobotoolbox.org/#narrow/stream/7-UX.2FUI/topic/Order.20of.20questions.20rearranged.20in.20Question.20Matrix/near/32235 If a `matrix` question is created in the form-builder with several rows and some `select_*` type questions in the column then the order of those rows and the choices is rearranged when the builder is reopened. The bug appears to be isolated to the form-builder as the asset's content remains correct. ## Steps to Reproduce 1. Create a survey with a `matrix` type question in the form-builder 2. Create some rows and a column with a `select_*` type question that has 6 or more choices (I only seemed to get this behaviour with more than 5) 3. Save and exit the form-builder 4. Re-enter form-builder ### Before saving in form-builder <img width="1353" alt="Screen Shot 2021-05-21 at 12 14 21 PM" src="https://user-images.githubusercontent.com/50016008/119187741-9a9a5680-ba2e-11eb-9452-8c0221970290.png"> ### After saving in form-builder <img width="1352" alt="Screen Shot 2021-05-21 at 12 14 46 PM" src="https://user-images.githubusercontent.com/50016008/119187761-a259fb00-ba2e-11eb-8492-6b38803c0723.png"> ### `asset.content.choices` ```json [ { "name": "a", "$kuid": "tl6uj02", "label": [ "a" ], "list_name": "matrix_zl5ns72", "$autovalue": "a" }, { "name": "b", "$kuid": "ah8st95", "label": [ "b" ], "list_name": "matrix_zl5ns72", "$autovalue": "b" }, { "name": "c", "$kuid": "el8ij96", "label": [ "c" ], "list_name": "matrix_zl5ns72", "$autovalue": "c" }, { "name": "d", "$kuid": "tu7gr17", "label": [ "d" ], "list_name": "matrix_zl5ns72", "$autovalue": "d" }, { "name": "option_1", "$kuid": "zp0ja19", "label": [ "Option 1" ], "list_name": "kq2bn83", "$autovalue": "option_1" }, { "name": "option_2", "$kuid": "he0kt05", "label": [ "Option 2" ], "list_name": "kq2bn83", "$autovalue": "option_2" }, { "name": "option_3", "$kuid": "um6lt39", "label": [ "Option 3" ], "list_name": "kq2bn83", "$autovalue": "option_3" }, { "name": "option_4", "$kuid": "pv71q93", "label": [ "Option 4" ], "list_name": "kq2bn83", "$autovalue": "option_4" }, { "name": "option_5", "$kuid": "nm88a61", "label": [ "Option 5" ], "list_name": "kq2bn83", "$autovalue": "option_5" }, { "name": "option_6", "$kuid": "vx5jj91", "label": [ "Option 6" ], "list_name": "kq2bn83", "$autovalue": "option_6" } ] ``` ## Expected behavior Matrix question rows and choices remain in the original order. ## Actual behavior Matrix question rows and choices are shuffled.

sclateri · April 5, 2022, 5:06pm

I have reviewed the post on GitHub. I am not a member there, but as far as I can tell – there is still no solution to this problem for users using form builder. So we are unlikely to be able to use matrix questions for our project it seems.

Kal_Lam · April 6, 2022, 5:44am

@sclateri, maybe you could download your survey project in an XLSForm and then upload them back to the server.

gre6oire · July 28, 2025, 6:40am

Hello, be aware that If you export to XLSForm then import you will no longer be able to edit the question matrix as a matrix in Kobotoolbox form builder.. I am wondering if the issue of matrix question jumbled has been solved? It was put in github on may 2021..