Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-12034

Delete creating blank rows in Component Library / Collections / Sequence Column

    Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4
    • Fix Version/s: 2.4
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      UIF Component
    • Sprint:
      2.4.0-rc1 Sprint 4
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      On the Auto sequence example in the KRAD Sampleapp / Library / Collections page, the using the delete button on collection items is behaving strangely, adding blank lines at the top of the collection under certain circumstances.

      To reproduce:

      1. navigate to the KRAD Sampleapp / Library / Collections / Sequence Column
      2. Click the "Field 2" column heading to sort by that field
      3. Click the "Delete" button on several visible collection elements

      Result: After the second deletion (in my experience anyway), blank elements start appearing at the top of the collection

      Expected result: The deleted item will no longer show, the items below the deleted element all move up one element to fill the vacancy.

        Attachments

          Issue Links

            Activity

            Hide
            jruch Jeff Ruch added a comment -

            Once the collection hits 30 rows, it starts adding the blank rows rather upon row deletion.

            Show
            jruch Jeff Ruch added a comment - Once the collection hits 30 rows, it starts adding the blank rows rather upon row deletion.
            Hide
            jruch Jeff Ruch added a comment -

            The issue is caused by multiple collections in the same view, with the same property name. Changing each collection to use it's own property name resolved the issue. I confirmed with the dev group that there isn't an existing use case for multiple collections with the same property name in a view, so I won't attempt to update the code to support it.

            Show
            jruch Jeff Ruch added a comment - The issue is caused by multiple collections in the same view, with the same property name. Changing each collection to use it's own property name resolved the issue. I confirmed with the dev group that there isn't an existing use case for multiple collections with the same property name in a view, so I won't attempt to update the code to support it.
            Hide
            jruch Jeff Ruch added a comment -

            I should go through and make sure I haven't broken any of the AFTs

            Show
            jruch Jeff Ruch added a comment - I should go through and make sure I haven't broken any of the AFTs
            Hide
            jruch Jeff Ruch added a comment -

            test the sequence aft and it succeeded.

            Show
            jruch Jeff Ruch added a comment - test the sequence aft and it succeeded.
            Hide
            jruch Jeff Ruch added a comment -

            tested the collection sequence aft and it passed.

            Show
            jruch Jeff Ruch added a comment - tested the collection sequence aft and it passed.

              People

              • Assignee:
                jruch Jeff Ruch
                Reporter:
                gilesp Peter Giles (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 day, 4 hours
                  1d 4h
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 4 hours
                  1d 4h