This content has been marked as final. Show 4 replies
DRM By default sorts the data in Alphan Numeric fashion,
Also you can define the sort order of you choice by assigning a derived property ( of SORT Data Type) to the Standard Hierarchy Sort Order on a Hieararchy or you can use Core.SortOrder if you wish to retain a specific order,
Reg '10010_dhfjf', I will answer shortly, need to test:-)
There is a possible solution to this...
- Assign Core.SortOrder to the StdHierSort Hierarchy property.
- Change the default value of Core.SortOrder to a value which you think possibly would be the maximum number of nodes under a parent eg. 10000
Once you do this try the operation you've been trying so far and let me know if it works.I think It should !! :)
Edited by: Denzz on Mar 22, 2013 11:25 PM
I have a SORT property defined and assigned to the StdHierSort hierarchy property. Not the Core.SortOrder - not sure of this makes a difference. I don't understand the second step of assigning a default value to the SORT property. Should this value be a maximum # of possible children (nodes) PER parent? And how is that used when ADDing a new member using an action script? The goal is to get the ADDed node in the right position during the action script add so the DRM admin does not need to move each node into the correct sort order.
Many, many thanks for your assistance!
I guess I misunderstood your requirement.. excuse me for that...Well if you are sending the sort order values on a Sort Property.. nothing like it for an action script.Using any sort property doesn't make any difference as long as you don't want different Sort Ordering for different users.