Details
-
Type:
Bug Fix
-
Status:
Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 2.4, 2.4.1
-
Fix Version/s: 2.6
-
Component/s: Development, User Experience (UX)
-
Security Level: Public (Public: Anyone can view)
-
Labels:
-
Similar issues:
KULRICE-7986 Problems with multiple refreshWhenChangedPropertyNames KULRICE-13892RefreshWhenChangedPropertyNames not working with multiple dialogs KULRICE-5713KRAD: Need classnames for collections' nested items KULRICE-7365refreshWhenChangedPropertyNames bug in 2.2.0-M1 KULRICE-12885 CleanContextDeep naming problem and nesting problems KULRICE-10688Binding path is lost after refresh of parent collection for child ajax retrieved components KULRICE-3851Nested collections of a reference throwing exception when maintenance document is canceled and not validating required KULRICE-11181 Custom Inquirables not considered in nested inquiries KULRICE-10075Clicking delete on collection within row details of a table with forceLocalJsonData causes escaping problem KULRICE-6312DictionaryObjectAttributeValueReader does not handle AttributeDefinitions that refer to a nested property within a collection (for usage in lookups) -
Rice Team:Framework
-
Rice Module:KRAD
-
Application Requirement:Rice
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
-
Code Review Status:Not Required
-
Include in Release Notes?:Yes
-
Story Points:5
Description
Need create a lab that demonstrates a structure that has
ListCollection-ListCollection-ListCollection-ListCollection-TableCollection
In which changing a radio value on the 2nd collection refreshes the 3rd collection and its items have a render condition based on the value set by the radio at the 2nd collection level.
May be able to demonstrate bug or reproduce bug with only 3/4 levels instead of 5.
What we are seeing is that collection is refreshed but the wrong component is returned.
This is happening in ViewLifecycle.performComponentLifecycle where it is pulling the wrong component path from the RefreshPathMappings for the CORRECT id (the one we are expecting to refresh)
FYI I spent 2-3 hours with the dev tracking down this bug and verifying that something is going wrong here