Magento2: Ui_component column sortOrder doesn't work

[OlehWolf]

I creating a new adminhtml grid, and I have found a problem with setting up columns positions.

Steps to reproduce

1. For example open the ui_component of adminhtml catalog product list Magento/Catalog/view/adminhtml/ui_component/product_listing.xml.
2. Section "columns". Elements "column" have "sortOrder" config, which should sort columns in grid.

3. Decrease value "sortOrder" of "name" column to 15.
   

   Expected result

4. The column "name" should be moved between ID and Thumbnail
   

   Actual result

5. Column aren't being moved.

I assume the bug is in Ui module. The file Magento/Ui/view/base/web/js/grid/listing.js contains mehtod "updatePositions" that setting up columns position by their index instead of element sortOrder. The working solution for me is replace "index" for "elem.sortOrder".

[guz-anton]

Hi @rawick ,
Thanks for catch! We will investigate issue under MAGETWO-53310 task.

Stay in touch.

[guz-anton]

@rawick could you do:

TRUNCATEui_bookmark; in scope of your MYSQL db.
Grids UI have such feature as _"Bookmarks"_. It allows to save Grid's state per user. It's ON by default. Looks like you got cached value.

[OlehWolf]

@guz-anton I cleared all the caches, include this table and pub/static/ content. the problem is exactly in ignoring xml attribute "sortOrder". Yes, you can replace columns in ui_component, clear cached table and it will be ok, but attribute "sortOrder" won't has any usage anyway.

[guz-anton]

@rawick
sortOrder is used on upper level than you point. Before Grid (via listing.js) applying position some actions are done by layout.js.

On Grid level with position works Bookmark UI component. It uses component's indexes. And it expected behavior. position has other value than sortOrder.

You can find in mysql db records in ui_bookmark table. If you drop it your changes from xml will be applied.

So under "clear caches" after changing "sortOrder" in xml you should do:

• clear mysql table ui_bookmark. E.g.:
  mysql -uroot -p -e 'USEmagento_db_name;TRUNCATEui_bookmark;'
• clear caches for xml configuration. E.g.:
  sudo -u www-data rm -rf var/cache/*

[guz-anton]

Currently I'm closing issue as one that "Cannot reproduce".

@rawick please comment here if any additional info you'll have.

[JanisE]

Deleting the related ui_bookmark table rows fixed this for me, but is that really the expected behaviour - to not be able to (re-)define the column order by XML or at least reset the order by clearing a cache, instead of manually editing database?

[PivitParkour94]

Is clearing the ui_bookmark table supposed to be built into a cache type or something in the future? It seems a little bit too devvy for someone who's just testing a new version of a ui_component...

[PivitParkour94]

If anyone is interested, I made a Feature Request with a proposed solution to the clearing of the ui_bookmark table that doesn't require technical DB knowledge
https://github.com/magento/community-features/issues/215

[dchaykas]

2.2.8 same issue, adding "sortOrder" attribute to node has no effect (even with clearing cache) until the table ui_bookmark is truncated.