Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0009923Openbravo ERPZ. Otherspublic2009-07-16 10:502009-07-22 00:00
Reportershuehner 
Assigned Topjuvara 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version2.50MP3 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0009923: API check: build 81 fails
DescriptionThis api check builds fails:

http://builds.openbravo.com/job/erp_devel_pi-module-integrity-test/81/console [^]

+++++++++++++++++++++++++++++++++++++++++++++++++++
  Errors in API model validation
+++++++++++++++++++++++++++++++++++++++++++++++++++
  Column size decreased from 10 to 0: column: C_TAXREGISTER.LASTREGACCUMAMT
  Column size decreased from 10 to 0: column: C_TAXREGISTER.TAXTOTALAMT
  Column size decreased from 10 to 0: column: C_TAXREGISTERLINE.TAXBASEAMT
  Column size decreased from 10 to 0: column: C_TAXREGISTERLINE.TAXAMT
  Column size decreased from 10 to 0: column: C_TAXREGISTERLINE.TOTALAMT
  Column size decreased from 10 to 0: column: C_TAXREGISTERLINE.TAXUNDAMT
  Column size decreased from 10 to 0: column: C_TAXREGISTERLINE.EXEMPTAMT
  Column size decreased from 10 to 0: column: C_TAXREGISTERLINE.NOVATAMT
Steps To Reproduce
Proposed Solution
Additional Information
Tags250MP3releasecandidate
Relationships
related to defect 0009823 closed vmromanos columns in table C_TAXREGISTERLINE are wrong defined 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-07-16 10:50shuehnerNew Issue
2009-07-16 10:50shuehnerAssigned To => vmromanos
2009-07-16 10:50shuehnerOBNetwork customer => No
2009-07-16 10:50shuehnerRelationship addedrelated to 0009823
2009-07-16 11:33vmromanosNote Added: 0018298
2009-07-16 11:33vmromanosAssigned Tovmromanos => pjuvara
2009-07-16 11:33vmromanosStatusnew => feedback
2009-07-16 13:28hgbotCheckin
2009-07-16 13:28hgbotNote Added: 0018314
2009-07-16 13:28hgbotStatusfeedback => resolved
2009-07-16 13:28hgbotResolutionopen => fixed
2009-07-16 13:28hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/api-checks/rev/4fc7544cf7a646f0b4d76881f5ee14bf9dd7ffcf [^]
2009-07-21 16:24psarobeFixed in Version => 2.50MP3
2009-07-21 16:26psarobeTag Attached: 250MP3releasecandidate
2009-07-21 17:11psarobeStatusresolved => closed
2009-07-22 00:00anonymoussf_bug_id0 => 2825068

Notes
(0018298)
vmromanos   
2009-07-16 11:33   
The previous definition of these columns was totally wrong, since they had a small length limitation (10) and, specially, they didn't allow decimals (so money amounts were always stored without decimals)


In this case the change in the API is mandatory, and it is not dangerous for previous installations, since there is no problem in updating from an integer to a decimal. I have tested an update.database and it's working fine.
(0018314)
hgbot   
2009-07-16 13:28   
Repository: erp/devel/api-checks
Changeset: 4fc7544cf7a646f0b4d76881f5ee14bf9dd7ffcf
Author: Víctor Martínez Romanos <victor.martinez <at> openbravo.com>
Date: Thu Jul 16 13:27:41 2009 +0200
URL: http://code.openbravo.com/erp/devel/api-checks/rev/4fc7544cf7a646f0b4d76881f5ee14bf9dd7ffcf [^]

Fixed bug 0009923: API check: build 81 fails. Change accepted

---
M model/model/tables/C_TAXREGISTER.xml
M model/model/tables/C_TAXREGISTERLINE.xml
---