Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0049029
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] A. Platformmajoralways2022-04-11 15:432022-04-28 09:31
Reporterkousalya_rView Statuspublic 
Assigned ToTriage Platform Base 
PriorityhighResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0049029: 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.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0136831)
AugustoMauch (administrator)
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.

- Issue History
Date Modified Username Field Change
2022-04-11 15:43 kousalya_r New Issue
2022-04-11 15:43 kousalya_r Assigned To => Triage Platform Base
2022-04-11 15:43 kousalya_r Modules => Core
2022-04-11 15:43 kousalya_r Triggers an Emergency Pack => No
2022-04-28 09:31 AugustoMauch Note Added: 0136831
2022-04-28 09:31 AugustoMauch Type defect => design defect


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker