Drill down function showing lists in incorrect format
Wanted to ask for a best solution of this question if possible.
I have a set of data which is populated by a subset. When I drill down into the data, the order of the lists are not in the order they should be. I have checked the list which shows the correct order. Is it possible to change the mappings/settings of the drill down options to show the lists in the correct order?
Screenshots attached below showing the correct order vs the incorrect order in the drill down function
After conducting some testing of my own I found that @JaredDolich point about reloading data in the order you want them to be sorted is correct.
We began to reorder data in the format that we wished for it to be populated in (e.g. directorate levels in numerical as the screenshot attached shows) and then switched to entering data for the last directorate (7) and then moved back to doing it for directorate 4. This then began to throw out the order of the drill down views as you can see in the screenshot.
We realised that selecting the data in the order we want them to be sorted in will bring back the correct results but after a forecast/actual is added – it will then throw out the order of the list.
Looking forward to see what the next steps might be.
I found this useful instruction online regarding reorganising list items and it seems to be the only way to do it at the moment (thanks to @davy_widianto )
"Re: Numbered Lists renumbering
To physically sort list members, you need to destroy the list (delete all members) and reload the members sorted. If this list is not used in too many line items that contain stored data, you can create a process that include the following (assume that the list that you want to sort is called LIST_A):
1. Copy all members of LIST_A to another temporary list (call it tmpLIST_A). Create a module dimensioned by tmpLIST_A (call it tmpMODULE_A). The line items in the module should include at least the name, code, parent name, and parent code of the list members. All other property values should also be included in this module.
2. Copy parent-child information (name, code, parent name, parent code) of the list along with other properties to tmpMODULE_A. In tmpMODULE_A, create a view that shows all line items sorted by the member list name (call this view vwSortedView).
3. Copy the contents of all line items (dimensioned by tmpLIST_A) to temporary modules.
4. Delete all members of LIST_A.
5. Import vwSortedView back to LIST_A
6. Import back the line items that contain data. This are the line items that are backed up in Step-3.
7. Finally, delete all members in tmpLIST_A so that it is ready for the next sort.
All of the above actions can be place in a single process so that the admin can just run the process to sort the list."
Did this issue ever make it through to a resolution?
I have encountered this on a list where a member was split into two and a new parent was added. The list isn't a numbered list. The old member was renamed to child 1 and had a sibling added (child 2) under a new parent.
When using drill down to analyse variances at the total level, child 2 appears at the bottom of the list after items which were created before it so looks to still be happening.
I have not been able to replicate the issue, but I did check that when the list is sorted through the new action, the drill down does correctly reflect the new order, including for new items that were added