Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014553Openbravo ERP00. Application dictionarypublic2010-09-14 18:332010-10-19 00:00
Reporternetworkb 
Assigned Tomarvintm 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionopen 
PlatformOS5OS Version
Product Version2.50MP21 
Target Version2.50MP23Fixed 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
Summary0014553: Dataset 'Client Definition' --> There are tables that do not meet the validation
DescriptionIn the dataset Client definiton there are tables that do not meet the validation, IE: M_Warehouse (it appears as **M_Warehouse)
Steps To Reproduce- As System Administrator go to Application Dictionary || Dataset || Dataset
- Select 'Client definiton'
- Go to Table, sekect M_Warehouse, realize that the name of the table appears with '**'
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to feature request 0014848 new Triage Platform Base Improvements in Import/Export Client 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-09-14 18:33networkbNew Issue
2010-09-14 18:33networkbAssigned To => alostale
2010-09-20 08:58alostaleTarget Version2.50MP22 => 2.50MP23
2010-09-20 08:58alostaleStatusnew => scheduled
2010-09-20 08:58alostalefix_in_branch => pi
2010-09-30 11:48alostaleAssigned Toalostale => adrianromero
2010-09-30 11:48alostaleNote Added: 0031508
2010-09-30 12:02psarobeStatusscheduled => feedback
2010-09-30 14:11networkbNote Added: 0031518
2010-09-30 14:12networkbAssigned Toadrianromero => alostale
2010-09-30 14:12networkbStatusfeedback => new
2010-10-04 08:41alostaleStatusnew => scheduled
2010-10-06 10:19alostaleAssigned Toalostale => marvintm
2010-10-18 16:18marvintmRelationship addedrelated to 0014848
2010-10-18 16:20marvintmNote Added: 0031916
2010-10-18 16:20marvintmStatusscheduled => closed
2010-10-19 00:00anonymoussf_bug_id0 => 3090007

Notes
(0031508)
alostale   
2010-09-30 11:48   
The problem is the validation checks tables access level with dataset access level.

Client Definition dataset has System Only access level, which seems to be incorrect. Can you confirm and change if it is wrong?
(0031518)
networkb   
2010-09-30 14:11   
This data set is defined as System only access what probably is wrong.
But Client definition dataset is used when exporting the client, so needs to export tables defined with "system/Client" access level and also tables with "client/organization" access level.

For example c_currency tables has "system/client" access level, and m_inout table
has "cliente/organization" access level, and both has to be exported as part of client definition dataset.

In this case the validation has not sense because the client definition dataset has to include tables with different type of access level.
(0031916)
marvintm   
2010-10-18 16:20   
The Import/Export client will be refactored in the comming months, according to the plan described in the following feature request:

https://issues.openbravo.com/view.php?id=14848 [^]

Therefore, this change will not be done. Instead, the way import client decides which tables it needs to export will be automatically computed. This feature request will be implemented before Openbravo 3.0.