Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-7058

Required field getting removed on collection refresh


    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: 2.2.0-m2, 2.2
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-5299Add line on collections not checking required fields and not refreshing just the collection group
      KULRICE-6461PeopleFlow member field doesn't get refreshed after the member type changes
      KULRICE-6409Field groups in collection lines do not get binding correctly prefixed
      KULRICE-13001Logic for paging request on collections gets hit for non-refresh components
      KULRICE-7851Dirty field indicator not working on Collections
      KULRICE-7870Tooltips are not removed if a timed refresh occurs while they are open
      KULRICE-13301Refresh in Edit dialogs
      KULRICE-12543Support progressive disclosure and refresh of collection lines
      KULRICE-4103JPA refresh strategy won't work with Orphan Removal
      KULRICE-8000Collections are lost when refresh is done on a collection
    • Rice Module:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      I have a TableCollectionSection with 10 InputFields. Most of the fields are not required, and one of these fields, for whatever reason makes it special, is experiencing some odd behavior. For items in the collection (class Holiday) there is a lone action button, 'delete'. When this button is pressed, the record is removed from the database and then removed from the form's List<Holiday> property, like so:


      and for some bizarro reason, when the UI makes the item disappear from the page, that one special field is blanked out on the row directly beneath the deleted one. There are 5 other controls which are also not required, but they are not being blanked out. This field is a DateControl but I've changed it to a TextControl and I get the same behavior. I've also moved the field around and that doesn't change anything.

      Here is the field definition, way stripped down but still causing the weird problem:

      <bean parent="Uif-InputField" p:propertyName="endDate">
      <property name="control">
      <bean parent="Uif-DateControl" />

      And here's some more weirdness for you: if I add the property readOnly="@

      {#lp.dateRange eq false}

      ", so in this case it's readonly=true because 'dateRange' is unchecked, that takes away the odd behavior. However, it adds new odd behavior which I'm not going to throw in here, but I have to pick between one bad behavior or the other.


        No work has yet been logged on this issue.


          • Assignee:
            Matthew Wuertz (Inactive)
            Jerry Neal (Inactive)
          • Votes:
            0 Vote for this issue
            1 Start watching this issue


            • Created:

              Structure Helper Panel