[KULRICE-8471] richTable "aoColumnDefs" property problem in M4 Created: 26/Oct/12 Updated: 03/Apr/13 Resolved: 31/Oct/12
|Project:||Kuali Rice Development|
|Fix Version/s:||2.2.0-rc1, 2.2|
|Security Level:||Public (Public: Anyone can view)|
|Reporter:||Bob Hurt (Inactive)||Assignee:||Brian Smith (Inactive)|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|KRAD Feature Area:||
|KAI Review Status:||Not Required|
|KTI Review Status:||Not Required|
in 2.2.0-M3 the following configuration sorted the collection on the second column (the "aaSorting" property) and made the third column non-sortable ("aoColumnDefs" property). in M4 the up/down arrow indicator for which column was used for sorting indicates that the second column was used (good), but actually no sort was done (bad). also, clicking on the second columns header changes the sort indicator from an up-arrow to a down-arrow, but the sorting remains the same. oddly enough tho sorting still works on the first and last column. if i change the non-sortable column to the 4th and final column, the first column can still be sorted but not the 2nd and 3rd.
|Comment by Brian Smith (Inactive) [ 31/Oct/12 ]|
This now works as it did in previous milestones, so the above will work as before.
To cause a complete aoColumnDefs override there is now a flag to do so which will overwrite aoColumnDefs completely (if you want to do this in RARE cases).