David,
great job!!! Development hints like this one are key to take advantage of
the "community development model". But we should go one step further: this
info should be written in our developers guide, and you should send a link
to that documentation. This way this info is easily available in the life
cycle.
I suggest to place this explanation here:
http://wiki.openbravo.com/wiki/ERP/2.50/Developers_Guide/Concepts/Modularity
#Reference_Data
as a new section titled "Advanced topics".
Can you please send us a new mail pointing to that documentation?
Thanks a lot,
Ismael
-----Mensaje original-----
De: staff.engineering-boun...@openbravo.com
[mailto:staff.engineering-boun...@openbravo.com]en nombre de David Alsasua
Egea
Enviado el: viernes, 26 de noviembre de 2010 11:15
Para: openbravo-development; staff.engineer...@openbravo.com
Asunto: [staff.engineering] Issue with Document Sequence Numbers reset in
case of applying dataset second time
Dear all,
This e-mail is intended to alert about one issue I've suffered, and seems
more developers may be facing as well.
What?
In case you are developing a module, that contains a dataset at a
System/client, Client/Organization or Organization data access level
(actually all the possible ones, in except of System only), and you need to
add records belonging to AD_Sequence table, you must NOT INCLUDE (or
EXCLUDE) the CurrentNext column.
Why?
User applies dataset, and everything goes fine: sequence is imported to
database (with let's say, CurrentNext='1000000'). User starts to use the
sequence, so CurrentNext value is incremented (let's say is now ='1000123').
New version of the dataset is published because, for example, some more
sequences are included in a new version of the module. User updates module,
and updates dataset in Enterprise Module Management window. In that action,
the CurrentNext value of the original sequence is reset from '100123' to
'1000000' again.
How to avoid?
Let's NOT INCLUDE THE CurrentNext COLUMN IN THE DATASET. The CurrentNext
column is a mandatory one, but it do have a default value set to '1000000'.
There exists two ways of defining a dataset: including all columns of the
defined table at Application Dictionary || Dataset || Dataset >> Table,
or defining the columns to be included, one by one. If you include columns
one by one, just don't include the CurrentNext one. In case you added the
whole table, just as exclude the column, as shown in the attached image.
Thanks. Regards.
David Alsasua Egea
Openbravo Localization Team
e: david.alsa...@openbravo.com
m: +34.607.867.908
p: +34.948.287.507 ext: 3422
sk: david.alsasua
---------- Forwarded message ----------
From: Dmitry Mezentsev <dmitry.mezent...@openbravo.com>
Date: 25 November 2010 20:31
Subject: Issue with Document Sequence Numbers reset in case of applying
dataset second time
To: David Alsasua <david.alsa...@openbravo.com>
Hello David,
We fixed this issue in the Core.
But today I discovered that the same exists in the APRM.
Could you please do the following?
* Notify staff.engineering and openbravo.development about this case and
the correct way to define Document Type datasets?
* Check with the help of RM Team through our repository in case there are
any other document types defined the same way?
Thanks,
Dmitry.
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Openbravo-development mailing list
Openbravo-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbravo-development
