[KULRICE-8471] richTable "aoColumnDefs" property problem in M4 Created: 26/Oct/12  Updated: 03/Apr/13  Resolved: 31/Oct/12

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: 2.2.0-m4
Fix Version/s: 2.2.0-rc1, 2.2
Security Level: Public (Public: Anyone can view)

Type: Bug Fix Priority: Critical
Reporter: Bob Hurt (Inactive) Assignee: Brian Smith (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Rice Module:
KRAD
KRAD Feature Area:
UIF Component
Application Requirement:
KS
KAI Review Status: Not Required
KTI Review Status: Not Required

 Description   

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.

<bean parent="KS-KitchenSink-Collection-Base">
   <!-- 
      KS-KitchenSink-Collection-Base parent="Uif-TableCollectionSection" 
   -->
   <property name="layoutManager.richTable">
      <bean parent="Uif-PagedRichTable">
         <property name="templateOptions">
            <map merge="true">
               <entry key="aaSorting" value="[[1,'asc']]"/>
               <entry key="aoColumnDefs"
                      value="[ {'aTargets':[2], 'bSortable':false}
                           ]"/>
            </map>
         </property>
      </bean>
   </property>
</bean>


 Comments   
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).

Generated at Sun Sep 20 12:34:56 CDT 2020 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.