search

camptocamp / odoo-dj

Odoo modules to help exporting / importing data in a consistent way via anthem songs
GNU Affero General Public License v3.0
3 stars 8 forks source link

Move companies and lang setup from odoo template to dj tool #48

Closed grindtildeath closed 7 years ago

grindtildeath commented 7 years ago

Prototype export uses new XMLIDs for res.company records, but the generated zip doesn't include a song with a res.company.csv to load these.

simahawk commented 7 years ago

we usually have companies setup beforehand in songs. We might want to change this indeed. @yvaucher ? /cc @guewen

yvaucher commented 7 years ago

Here we could probably add this step in base_dj as we always will need it

yvaucher commented 7 years ago

I mean adding a song generation which generates the company. Currencies and languages should go there as well.

yvaucher commented 7 years ago

(currencies because we set it on the company, unless we load company with active_test = False, and then we can keep currencies in accounting I guess)

simahawk commented 7 years ago

@yvaucher then how do we handle this? Companies are required for every "genre" so we cannot add it to all compilations. I wonder if we should include it automatically w/out configuration. An alternative might be to allow cross-compilation song-dependency and have a base compilation that contains only companies and languages.

yvaucher commented 7 years ago

It could be a base compilation on it's own

We could add a wizard and or a route to select a list or all of compilations and modifiy the part of the compression in zip to return multiple compilations in one (or call the generation of data bypassing the compression and do the zipping inside wizard code)

grindtildeath commented 7 years ago

Label changed to bug because we can't use any data generated by the prototyper until this is fixed.

simahawk commented 7 years ago

@yvaucher we can bundle compilations and do a "Collection". By default each compilation would depend on the base one. We can have another button to burn the collection with all the compilations linked. Not sure if we want yet another model to hold this.

@grindtildeath as of today we still have company setup in proj setup so if you have the company setup there it's fine. Not to mention that when you don't have multicomp you already have the base company w/ its xmlid.

simahawk commented 7 years ago

depends on #49

simahawk commented 7 years ago

I'm including dj_core for core compilations into https://github.com/camptocamp/odoo-prototype/pull/72 as it is the perfect use case for handling different file fieds (logo, rml, etc)