0005196: Doc sequences and database restrictions - Openbravo Issue Tracking System

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0005196

Openbravo ERP

00. Application dictionary

public

2008-09-23 13:01

2009-01-25 19:22

Reporter

galderromo

Assigned To

alostale

Priority

high

Severity

major

Reproducibility

always

Status

closed

Resolution

fixed

Platform

OS Version

Gentoo 2.6.24

Product Version

Target Version

Fixed in Version

2.40MP2

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0005196: Doc sequences and database restrictions

Description

Right now, when working with Sales Invoices, WAD generated code updates the document's sequence before is sure the invoice has been created. This way it is possible to update the sequence but not to create the record due to database restrictions.

This issue is critica because can generate sequence jumps on Sales Invoices, which is ilegal.

In some how, this request is related to 4439 and 5054.

Steps To Reproduce

Suppose you do not want the user to create an invoice with no c_project_id or not user1_id. So you create on the database this restriction (there is no way to do it through the AP).

Then, when you press the SAVE button, the WAD generated code updates the sequence and later inserts the record on the database. But the restriction avoids this inserting, so the sequence has been lost.

Proposed Solution

Change the sequence control, and make sure the inserting has been properly done, before updating the sequence.

Additional Information

Tags

No tags attached.

Relationships

related to	defect	0006395		closed	shuehner	Inpossible to create a new document on Postgresql
blocks	defect	0005175		closed	alostale	Doc sequences and database restrictions