Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0050571Retail ModulesWeb POSpublic2022-10-18 14:492022-10-19 10:03
ReporterXABIER_AGUADO 
Assigned ToRetail 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0050571: A key Map layout for Products on a parent organization must apply to the lowest organizations
DescriptionA key Map layout for Products on a parent organization must apply to the lowest organizations but it doesnt.
Steps To ReproduceDefine a Schema for a parent organization
Dont define a Schema for the child store
Try logging in on the store
We are stuck on an endless loop
Proposed SolutionChilds should inherit parents schemas
Additional Information
TagsFASH
Relationships
related to feature request 0049661 new Retail Openbravo ERP Copy Retail Store: Organization || Schema configuration is not copied 
Attached Filespng imgpsh_fullsize_anim (2).png (31,393) 2022-10-18 14:49
https://issues.openbravo.com/file_download.php?file_id=17675&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2022-10-18 14:49XABIER_AGUADONew Issue
2022-10-18 14:49XABIER_AGUADOAssigned To => Retail
2022-10-18 14:49XABIER_AGUADOFile Added: imgpsh_fullsize_anim (2).png
2022-10-18 14:49XABIER_AGUADOTriggers an Emergency Pack => No
2022-10-18 14:49XABIER_AGUADOTag Attached: FASH
2022-10-18 16:49rafarodaSeverityminor => major
2022-10-18 16:50rafarodaRelationship addedrelated to 0049661
2022-10-19 10:03marvintmReview Assigned To => marvintm
2022-10-19 10:03marvintmNote Added: 0142272
2022-10-19 10:03marvintmStatusnew => closed
2022-10-19 10:03marvintmResolutionopen => no change required

Notes
(0142272)
marvintm   
2022-10-19 10:03   
The correct way to approach this problem is to copy the entity as part of the copy store process, not to change the filtering of the data here, as that would open a different kind of problems related to master data management and refresh.