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

KIM lookups (Role) do not behave the same as other lookups with regards to the primary key


    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.1, 2.1.1
    • Fix Version/s: 2.6
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Similar issues:
      KULRICE-2948Rename TARGET_PRIMARY_KEY column on certain KIM tables
      KULRICE-10493Notification message that lookup is by primary key is not working.
      KULRICE-3928KIM Lookups not opening inquiries in new windows
      KULRICE-99if non-wildcard values are specified for all primary keys on a lookup, ignore other search criteria
      KULRICE-3173new issue with repeating primary key message on lookups
      KULRICE-3134In the lookup results, primary key is no longer a link to an inquiry
      KULRICE-4802Quickfinder error when searching for related object not by primary key
      KULRICE-8847Role lookups slow when there are over 200 roles
      KULRICE-4026Composite Primary Key class enforcement
      KULRICE-4234Add attribute to role type to indicate that derived roles of that type can be created in the user interface
    • Epic Link:
    • Rice Module:
    • Application Requirement:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      The KIM lookup screens do not ignore non PK criteria when all PK fields are specified. (E.g., to match the normal KNS lookups, if I enter a Role ID, then the lookup should ignore any other entered criteria and display a message that this was done. For an example, enter the campus code into the campus lookup.


        There are no comments yet on this issue.


          • Assignee:
            Jonathan Keller
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created:

              Structure Helper Panel