Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0049029Openbravo ERPA. Platformpublic2022-04-11 15:432022-04-28 09:31
Reporterkousalya_r 
Assigned ToTriage Platform Base 
PriorityhighSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0049029: Session Property is Empty
DescriptionSession property being empty when the child tab feeds from the same table as its parent tab.

Need to bring sales order lines in Purchase Order window at tab level 2. When they select purchase order line they want to show sales order lines in tab level 2.
Steps To Reproduce1. In Purchase Order window create a tab level 2 under 'Lines' tab setting 'Disable Parent Key Property' to true and set product id as stored in session.
Table : C_OrderLine
HQL Where Clause : e.product.id=@M_Product_ID@

2. Create fields.

3. Build and check the Purchase Order window if order line is selected and check tab level 2 the product should be shown but the session property is null because child table has the same table as parent tab.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2022-04-11 15:43kousalya_rNew Issue
2022-04-11 15:43kousalya_rAssigned To => Triage Platform Base
2022-04-11 15:43kousalya_rModules => Core
2022-04-11 15:43kousalya_rTriggers an Emergency Pack => No
2022-04-28 09:31AugustoMauchNote Added: 0136831
2022-04-28 09:31AugustoMauchTypedefect => design defect

Notes
(0136831)
AugustoMauch   
2022-04-28 09:31   
This is not an easy problem to solve, it is working as designed. I am changing its type to Design Defect

If a tab and a subtab share the same table, the names of the properties sent to the backend when creating a new record is the same, and the values of those properties will be filled with the values of the subtab with the highest depth. If the record is edited it will contain the current values of the subtab, so if a new record is created it makes sense to set those values to null because they have not been initialized yet.