On 02 Jan 16:54, Albert Cervera i Areny wrote: > 2015-01-02 16:41 GMT+01:00 Cédric Krier <[email protected]>: > > > On 02 Jan 16:23, Albert Cervera i Areny wrote: > > > 2015-01-02 16:02 GMT+01:00 Cédric Krier <[email protected]>: > > > > > > > On 02 Jan 15:32, Albert Cervera i Areny wrote: > > > > > To be honest, I was thinking more on the new asset modules and the > > fact > > > > > that some of our customers do asset mantenance for third parties and > > > > > frequently they really have sold the Good (that it is an asset from > > their > > > > > customer's POV). But then, I think that the asset_owner [1] module > > could > > > > > change the domain of product field on asset model to allow choosing > > goods > > > > > as well as assets. > > > > > > > > You mean the asset module: > > > > > > > > http://codereview.tryton.org/5781002 > > > > > > > > So I'm wondering if the product should not be optional but required if > > > > used for depreciation in account_asset module. > > > > > > > > > > We're currently using the product just as a category. Is this asset a > > car, > > > a motorbike, etc. It wouldn't be strictly necessary. > > > > > > I'm not sure, however, if to create an account_asset, an asset should be > > > required. It probably is consistent but it also forces the user to > > create a > > > new object he may not be interested in for somebody that just want to do > > > the accounting part. > > > > See my comment on https://code.google.com/p/tryton/wiki/Assets > > > I knew that.. > > Clearly account_asset was designed without the idea that asset could be > > used for other usage. But once those module land in Tryton, > > account_asset must be adapted to prevent duplication of data and allow > > reuse of existing feature. > > > > The thing is that I don't see there's duplicated data. If a user just wants > to manage the accounting part he currently has to create a product + the > account.asset. With your proposal he also has to create the 'asset', but I > don't see the benefit of creating this if you just need accounting. Why not > just let "account.asset" have a m2o to "asset" which is optional (though > constrained to have the same product, of course)?
The duplicate data is the asset identifier. You need one in both case and duplicate them will be a nightmare for users. -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
