Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ]

[ Issue History ] [ Print ]

ID

0014553

Type

Category

Severity

Reproducibility

Date Submitted

Last Update

defect

[Openbravo ERP] 00. Application dictionary

major

always

2010-09-14 18:33

2010-10-19 00:00

Reporter

networkb

View Status

public

Assigned To

marvintm

Priority

urgent

Resolution

open

Fixed in Version

Status

closed

Fix in branch

pi

Fixed in SCM revision

Projection

none

ETA

none

Target Version

2.50MP23

OS

Any

Database

Any

Java version

OS Version

Database version

Ant version

Product Version

2.50MP21

SCM revision

Review Assigned To

Web browser

Modules

Core

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

No

Summary

0014553: Dataset 'Client Definition' --> There are tables that do not meet the validation

Description

In 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 '**'

Tags

No tags attached.

Relationships [ Relation Graph ] [ Dependency Graph ]

related to

feature request

new

Triage Platform Base

Improvements in Import/Export Client

Notes
(0031508) alostale (manager) 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 (developer) 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 (developer) 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.

Issue History
Date Modified	Username	Field	Change
2010-09-14 18:33	networkb	New Issue
2010-09-14 18:33	networkb	Assigned To	=> alostale
2010-09-20 08:58	alostale	Target Version	2.50MP22 => 2.50MP23
2010-09-20 08:58	alostale	Status	new => scheduled
2010-09-20 08:58	alostale	fix_in_branch	=> pi
2010-09-30 11:48	alostale	Assigned To	alostale => adrianromero
2010-09-30 11:48	alostale	Note Added: 0031508
2010-09-30 12:02	psarobe	Status	scheduled => feedback
2010-09-30 14:11	networkb	Note Added: 0031518
2010-09-30 14:12	networkb	Assigned To	adrianromero => alostale
2010-09-30 14:12	networkb	Status	feedback => new
2010-10-04 08:41	alostale	Status	new => scheduled
2010-10-06 10:19	alostale	Assigned To	alostale => marvintm
2010-10-18 16:18	marvintm	Relationship added	related to 0014848
2010-10-18 16:20	marvintm	Note Added: 0031916
2010-10-18 16:20	marvintm	Status	scheduled => closed
2010-10-19 00:00	anonymous	sf_bug_id	0 => 3090007

Copyright © 2000 - 2009 MantisBT Group