Openbravo Issue Tracking System - Localization Pack: Spain
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0047751Localization Pack: SpainSIIpublic2021-09-23 18:282021-09-24 14:53
Reportergorka_gil 
Assigned Tovmromanos 
PriorityurgentSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Regression date
Regression introduced by commit
Regression level
Review Assigned Tovmromanos
Support ticket
OBNetwork customer
Regression introduced in release
Summary0047751: Module ssi fails org.openbravo.test.security.AccessLevelTest.testADataAccessLevel junit test
DescriptionObject * (aeatsii_orglegal_v) has an invalid client/org 0/0 for the accesslevel of the entity/table: CLIENT_ORGANIZATION.

Version in which issue is found is commit:
https://gitlab.com/openbravo/product/pmods/org.openbravo.module.sii/-/commit/4ec87bbef3c050eaa85f76198dca4e3bc9b43fca [^]

That is 1 commit just before tag: 1.9.211700

Note: Unclear if that issue exists in master only as that module is not covered by SPLP jobs in builds.openbravo.com


Steps To Reproduceant run.run -Dtest=org.openbravo.test.security.AccessLevelTest
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0045414 closed shuehner Openbravo ERP Skip AccessLevelTest.testADataAccessLevel also for views 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2021-09-23 18:28gorka_gilNew Issue
2021-09-23 18:28gorka_gilAssigned To => Jorge Bravo
2021-09-23 18:30gorka_gilIssue Monitored: shuehner
2021-09-24 14:52vmromanosStatusnew => scheduled
2021-09-24 14:52vmromanosAssigned ToJorge Bravo => vmromanos
2021-09-24 14:52vmromanosRelationship addedrelated to 0045414
2021-09-24 14:53vmromanosReview Assigned To => vmromanos
2021-09-24 14:53vmromanosNote Added: 0132003
2021-09-24 14:53vmromanosStatusscheduled => closed
2021-09-24 14:53vmromanosResolutionopen => fixed

Notes
(0132003)
vmromanos   
2021-09-24 14:53   
The failure is in the test itself and it was fixed in 0045414.
I recommend to transplant that changeset to your environment