openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #01437
Re: Problem with recreating standard-data
-
To:
openerp-community@xxxxxxxxxxxxxxxxxxx
-
From:
Marvin Hass <m.hass@xxxxxxxxxxxxx>
-
Date:
Tue, 16 Oct 2012 15:37:38 +0200
-
In-reply-to:
<CANeyZjC4Fn_=BJ-pxKRoZf3jJeXo4TNBNGYFettjsh6WUFuctA@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120912 Thunderbird/15.0.1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I don't agree with you! Not all object can be disabled! What do you
propose to do with the product categories? If you delete one of it (many
of our customers delete the categors "All Products") you will find it
again in your ERP after updating the module. Deleted data have to be
deleted!
If the ERP gets buggy when you delete the 'worng' data is in my oppinion
an huge issue!
What do you tell your customers?
Am 16.10.2012 15:14, schrieb Humberto Arocha:
>
> Deleting should come as a last resource measure, if you do not want to
have that "useless" data, you should deactive it, that is What best
practice mandates, no record should be deleted,
>
> Regarding ORM control over this issues would be a waste of time and
money, would it worth?
>
> Regarding documentation, this is not a tuna can or a microwave oven,
which you buy at the grocery store, and come with directions,
>
> The Day OPENERP comes with a book of how-to's, I'll take my suitcases
and say good bye because there will be no more space for me as an open
source Partner in here, because that Day openerp will on close source code,
>
> Openerp is plenty of information and documentation on its code lines,
>
> Would you say, Aha! What about me as a partner I should have those
docs as a prime time because I am at partner, well, let me say it, and I
will be tougher, you have not understood the openerp business model, and
again this is not a tuna can,
>
> Openerp takes in charge of R&D, marketing, we, as partners, take in
charge of the convincing the costumer this platform, this "perfectly
unfinish product" is the right choice for them, we are in charge of
keeping well acknowledged, this we keep competitive toward other
partner, if just buying documentation is the way for me keeping
competitive, then again we are using the wrong platform,
> Am I lame? , maybe, I cant be less straightforward, I try to be
crystal claro.
>
> Best Regards to the whole community & partner community
>
> Hbto [Vauxoo]
>
> On Oct 16, 2012 4:31 AM, "Marvin Hass" <m.hass@xxxxxxxxxxxxx
<mailto:m.hass@xxxxxxxxxxxxx>> wrote:
>
>
> The question is: why did you delete Andorra to recreate it later?
>
> Why not? I'm able to delete the objects without a warning! On the other
> hand -> what should i tell customers (as an OpenERP-Partner)? 'It's not
> recommended to delete some standard-data (which are not documentated) in
> OpenERP because we aren't able to update the server without problems'.
>
> I understand that deleting countries not typical but the problem is
> present on every object which is created while a moduleinstallation.
>
> We have the same problem with the pricelists! Costumers create his own
> pricelist and deletes the old ones.
>
> Kind regards,
>
> Marvin Hass
>
> Am 16.10.2012 10:24, schrieb Olivier Dony:
> > On 10/16/2012 10:05 AM, Marvin Hass wrote:
> >> ValueError: No such external ID currently defined in the system:
> >> base.ad <http://base.ad> 2012-10-16 06:58:00,734 5905 ERROR max_61
openerp.netsvc:
> >> No such external ID currently defined in the system: base.ad
<http://base.ad>
> >>
> >> If you want to generate this error -> follow this steps: 1. I
> >> deleted all countries from res.country (which are not important
> >> for my busseness) 2. I added Andorra (code = ad) to res.country
> >> 3. Start the server with --update=all
>
> > The question is: why did you delete Andorra to recreate it later?
> > The list of countries is part of the base data of OpenERP, and
> > several
> things
> > depend on it (similarly to the list of currencies). That's why the
> system will
> > try to re-create it at each update. You should not delete them,
> especially to
> > recreate conflicting countries afterwards.
>
> > If the size of the list really bothers you, look into alternative
> > customizations, like setting a default value for the country field
> > and
> then
> > hiding it from the view, or adding a custom filter on these fields
> > to
> only let
> > Andorra appear (this requires some knowledge in OpenERP
> > customization).
>
>
> >> I think it is a big issue! If i delete standard-data and recreate
> >> the entry i'm not able to update my system anymore!
>
> > Well this is the expected behavior, and only happens because each
> country is
> > (fortunately!) required to be unique, and the list of countries is
> part of the
> > base data of the system, re-created at each update. You should be
> > able to fix your problem by deleting the Andorra record you
> > manually created, then performing the update again, to let the
> > system
> re-create
> > the countries. If you can't delete your Andorra record because
> > many
> documents
> > reference it already, you could rename it or (harder) manually
> > create an 'ir.model.data' entry to make the system believe this is
> > the original
> 'Andorra'
> > record. Ask for more details if you don't know how to do this.
>
> > Hope this helps..
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
<mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~openerp-community
> More help : https://help.launchpad.net/ListHelp
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQEcBAEBAgAGBQJQfWMhAAoJELPuL5Oa1N8GznoH/0j5ViyZUqYbitrdYKe3bWMu
afOF1O/i+upQPhzBIEX2F3qNDeIqz3xU5jLSVDYUg8fF2nZ3QGAPqjDmEj10abxb
ogWt1TeX1Qo8Vq659RsWVpJbwMb/gAnEEEGgzEJznHgMMdsHBQK2U8FVNWr3sX4N
MCQRjaRUSEmUWD/7ozT9URcH1N4SPs3YXzqzyM1PHcrBdAZZWGBD8UYbwTO4nzzL
O2FiI+B2f+/V4o4syWOGUm54LST2hYmuNA3r1XvsDhoP3lfI8eH9r1/mRwtELqqc
RLere8CK98Xws8y4f1wexjpBe5OpMJXsJxeJDJ+VU/1d3/Wd0yj8NDtFAyUm7U8=
=0e7C
-----END PGP SIGNATURE-----
Follow ups
References