Archives
Contributors
contributors@odoo-community.org
-
pre-commit changes
Hi,quick question about pre-commit changes during migration.I'm migrating a module from 14.0 to 16.0. I've noticed that the first pre-commit related commit ("[IMP]: pre-commit stuff") takes care only of part of the changes needed to make pre-commit happy (it is possible due to the --no-verify). The missing part can be significant.
The following commit ("[MIG]: $MODULE: Migration to 16.0") must include those changes too, plus anything migration related.
So I was wondering if that defeats the purpose of having pre-commit changes separated in their own commit. Right now, my approach is to create a second commit, named "[IMP]: more pre-commit stuff", just to make pre-commit happy, and then add another commit with the migration stuff.
Alternatives I've considered: ignoring the issue and include both migration and the rest of pre-commit changes in one commit ("[MIG]: $MODULE: Migration to 16.0"), or do as I do now but squash the two pre-commit related commits before merge (or equivalently, get rid of the --no-verify in the first place, and manually add all changes to the first commit).
Thoughts / suggestions?
by Marco Colombo - 01:46 - 2 Dec 2022-
Re: pre-commit changes
The idea of the first pre-commit set is to store the automatic changes, so you don't have to review them extensively. The rest of the manual changes to make the linter happy must be on the migration commit, as a third extra commit doesn't make too much sense. You have to review these manual changes, and they can be even provoked by the new code you are introducing for the migration, so better to have all of them in the same migration commit.Regards.
by Pedro M. Baeza - 08:31 - 5 Dec 2022
-
-
XML errors when upgrading modules, because of fields in unrelated modules
Hello,
I've been finding this weird issue for a while, but decided to take some tome to write about it.
I've seen frequently the case where:
1. A custom module adds a field to a model and view. For example. to res.company.
2. Later, another (unrelated) custom module also adds a new field to that same model (model and view).
When installing or upgrading that second module, I see errors loading the XML with the form view.
The error says that the field added by module 1 is missing in the view.
But a) module 1 is installed an the field exists and b) the XML for the view in module 2 doesn't have any reference to that "missing" field!
I found this frequently in Odoo 14.
Honestly I'm not sure if it if also happens in other versions.
Has anyone else experienced this?
Thank you
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
by Daniel Reis - 02:30 - 25 Nov 2022-
Re: XML errors when upgrading modules, because of fields in unrelated modules
Hi Daniel,
I encountered a similar issue lately when developing a module in OCA/sale-workflow, everything was working fine locally, but the XML error you described was raised on the CI:
- my module was adding a field in the embedded tree view of sale order line in the SO form, which by default is in editable mode (no form)
- another module from OCA/sale-workflow disabled this editable mode so the form view of the SO line was open, on which my field wasn't added, so during tests when opening the form, the "field not found" error was triggered. Adding the field also on the embedded SO line form view fixed the issue.
Could it be the same kind of issue you are facing?
Regards,
Le 25/11/2022 à 14:31, Daniel Reis a écrit :
Hello,
I've been finding this weird issue for a while, but decided to take some tome to write about it.
I've seen frequently the case where:
1. A custom module adds a field to a model and view. For example. to res.company.
2. Later, another (unrelated) custom module also adds a new field to that same model (model and view).
When installing or upgrading that second module, I see errors loading the XML with the form view.
The error says that the field added by module 1 is missing in the view.
But a) module 1 is installed an the field exists and b) the XML for the view in module 2 doesn't have any reference to that "missing" field!
I found this frequently in Odoo 14.
Honestly I'm not sure if it if also happens in other versions.
Has anyone else experienced this?
Thank you
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Sébastien Alix Business Solutions Odoo Developer Camptocamp France SA https://www.camptocamp.com/
by Sébastien Alix - 09:46 - 28 Nov 2022 -
Re: XML errors when upgrading modules, because of fields in unrelated modules
Hi Danielthe error you describe usually comes when you remove a field from a model and view.If you now update both modules at the same time, it depends on how your Postgres server returns the modules.Because no explicit ordering is specified when loading the module.If the module is updated first that the field is not removed, an error occurs because the other view is still in the database and not updated.in this context, however, other errors can also occur.such as. when loading data via XML.I hope this helps.RegardsMichaelAm 25.11.2022 15:42 schrieb Daniel Reis <notifications@odoo-community.org>:Hi Moises,
I haven't found this to be easy reproductible.
The particular case I encountered today went away after I ran a "-u base" (that I really din't like to do).
On your questions:
1) Yes, In this case both inherited from "base.view_company_form".
2) No (see 1)
3) No groups set on model on view
4) Yes. View on Module 1 does not have a default priority (16 was assigned) and View in Module 2 has priority=100. This looked good to me.
5) Yes, tons of them, between core addons and other OCA modules :-)
I can give it a try at stripping the modules down and reproducing.
Thanks Moises
/Daniel
On 25/11/22 14:22, Moises Lopez wrote:
Hi Daniel
I have a few question related to reproduce the case
1) Do The third view is inherited from original one?
1. id=original2. id=inh_a inherit=original3. id=inh_b inherit=original
--2) Do The third view is inherited from 2nd one?
1. id=original2. id=inh_a inherit=original3. id=inh_b inherit=inh_a
3) Do the original field has "groups"?
4) Do the inherited views has "priority"?
5) Are there other views inheriting the same view?
Could you share the both modules with minimal code and the odoo-bin command to reproduce it, please?
Moisés López CalderónMobile: (+521) 477-752-22-30Twitter: @moylop260Twitter: @vauxoo_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Michael Tietz - 07:20 - 25 Nov 2022 -
Re: XML errors when upgrading modules, because of fields in unrelated modules
Hi Moises,
I haven't found this to be easy reproductible.
The particular case I encountered today went away after I ran a "-u base" (that I really din't like to do).
On your questions:
1) Yes, In this case both inherited from "base.view_company_form".
2) No (see 1)
3) No groups set on model on view
4) Yes. View on Module 1 does not have a default priority (16 was assigned) and View in Module 2 has priority=100. This looked good to me.
5) Yes, tons of them, between core addons and other OCA modules :-)
I can give it a try at stripping the modules down and reproducing.
Thanks Moises
/Daniel
On 25/11/22 14:22, Moises Lopez wrote:
Hi Daniel
I have a few question related to reproduce the case
1) Do The third view is inherited from original one?
1. id=original2. id=inh_a inherit=original3. id=inh_b inherit=original
--2) Do The third view is inherited from 2nd one?
1. id=original2. id=inh_a inherit=original3. id=inh_b inherit=inh_a
3) Do the original field has "groups"?
4) Do the inherited views has "priority"?
5) Are there other views inheriting the same view?
Could you share the both modules with minimal code and the odoo-bin command to reproduce it, please?
Moisés López CalderónMobile: (+521) 477-752-22-30Twitter: @moylop260Twitter: @vauxoo_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
by Daniel Reis - 03:41 - 25 Nov 2022 -
Re: XML errors when upgrading modules, because of fields in unrelated modules
Hi DanielI have a few question related to reproduce the case1) Do The third view is inherited from original one?1. id=original2. id=inh_a inherit=original3. id=inh_b inherit=original--2) Do The third view is inherited from 2nd one?1. id=original2. id=inh_a inherit=original3. id=inh_b inherit=inh_a3) Do the original field has "groups"?4) Do the inherited views has "priority"?5) Are there other views inheriting the same view?Could you share the both modules with minimal code and the odoo-bin command to reproduce it, please?Moisés López CalderónMobile: (+521) 477-752-22-30Twitter: @moylop260Twitter: @vauxoo
by Moisés López Calderón - 03:20 - 25 Nov 2022
-
-
OCA Financial Auditors Campaign Closes Today - 25th November
Hello OCA Contributors,Just a reminder our Financial Auditors Campaign closes today. So far we have only had 1 applicant. Preferably we would like to be able to vote for 3.
To apply as a candidate you do not need to be a delegate or member. Perhaps someone on your team has the skills to help the OCA with the annual audit?It isn't a huge task thankfully but does obviously require a certain skill set.Please fill in the survey below or share the link with colleagues who might be interested:Warmest regards,
Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 10:30 - 25 Nov 2022 -
Financial Auditor Campaign closes November 25th
Hello OCA Contributors,
I hope the week is going well for you!I just wanted to remind you our financial auditors campaign closes this coming Friday 25th of November.
To apply as a candidate you do not need to be a delegate or member. Perhaps someone on your team has the skills to help the OCA with the annual audit?Please fill in the survey below or share the link with colleagues who might be interested:--Warmest regards,
RebeccaRebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 04:51 - 23 Nov 2022 -
Module name, name collision
Hi all,It seems there are miscellaneous practices to deal with name collision in OCA, mainly regarding Odoo SA module nameshere mgmt is usedhere and in some other repos oca is usedIs there any other practice ?Should we converge on the same standard ? with a rename in future version with apriori openupgrade file ?Personally I prefer oca, but it probably needs to be voted !?What do you think?RegardsThanks
by David BEAL - 04:16 - 22 Nov 2022-
Re: Module name, name collision
This friends have it for free, it should be nice if OCA contacts them and let them serve something (may be paid).Regards.El mar, 22 nov 2022 a la(s) 09:17, David Beal (notifications@odoo-community.org) escribió:Hi all,It seems there are miscellaneous practices to deal with name collision in OCA, mainly regarding Odoo SA module nameshere mgmt is usedhere and in some other repos oca is usedIs there any other practice ?Should we converge on the same standard ? with a rename in future version with apriori openupgrade file ?Personally I prefer oca, but it probably needs to be voted !?What do you think?RegardsThanks_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Nhomar G Hernández
Vauxoo | CEO
¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomarMéxico · Venezuela · Costa Rica · Perú
by Nhomar Hernández - 10:51 - 15 Dec 2022 -
Re: Module name, name collision
IMHO.Avoid prefixes or suffixes.an script in the ci with a centralize DB with module names would be the practical solution.1. A quick service with elastic.2. An script that makes a push to such index.3. Serve a quick rest search.4. An script for the CI that makes:curl url/search/modules_here -r
read_response.json -> found5. Red if exists (with proper output).Why not the prefix/suffix.1. Nothing will avoid with such technique the duplication of functions and modules.2. In dev time the developer will know where the problem is (now I do simply a search in google, but as I said it can be automated).Regards.El mar, 22 nov 2022 a la(s) 09:17, David Beal (notifications@odoo-community.org) escribió:Hi all,It seems there are miscellaneous practices to deal with name collision in OCA, mainly regarding Odoo SA module nameshere mgmt is usedhere and in some other repos oca is usedIs there any other practice ?Should we converge on the same standard ? with a rename in future version with apriori openupgrade file ?Personally I prefer oca, but it probably needs to be voted !?What do you think?RegardsThanks_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Nhomar G Hernández
Vauxoo | CEO
¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomarMéxico · Venezuela · Costa Rica · Perú
by Nhomar Hernández - 10:46 - 15 Dec 2022 -
Re: Module name, name collision
Hello,It could be contextual, if we find that a better name would reflect what the module does.However, I would go with an `_oca` suffix by default to avoid the name collision.Cheers,YannickOn Tue, 22 Nov 2022 at 16:17, David Beal <notifications@odoo-community.org> wrote:Hi all,It seems there are miscellaneous practices to deal with name collision in OCA, mainly regarding Odoo SA module nameshere mgmt is usedhere and in some other repos oca is usedIs there any other practice ?Should we converge on the same standard ? with a rename in future version with apriori openupgrade file ?Personally I prefer oca, but it probably needs to be voted !?What do you think?RegardsThanks_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Yannick Payot - 05:26 - 15 Dec 2022
-
-
OCA - RFQ - Improving the Documentation of Open Upgrade
Hello OCA Contributors.Have you seen our latest RFQ for improving the Open Upgrade Documentation?
Please have a look here if you are interested in responding:Send your proposals in by December 4th. We look forward to hearing from you.Warmest regards,
Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 12:01 - 22 Nov 2022 -
Question about migration of account.tax and related entity (in my case on l10n_be)
Dear community, I'm currently migrating a database from version 9.0 to version 14.0. My problem is between 12.0 and 13.0 where accounting element has changed. The database is using Mis Builder to generate accounting reports. These reports are based on account.account.tag that are linked to account.tax (and also account.move.line in 13.0). As I have seen, in 9.0 (and until 12.0), account.account.tag are linked to an account.tax via a simple field tag_ids : https://github.com/OCA/OCB/blob/12.0/addons/account/models/account.py#L937 Starting from 13.0, tags are no more linked to account.tax directly. They are linked to an account.tax.repartition.line which is linked to an account.account.tax. https://github.com/OCA/OCB/blob/13.0/addons/account/models/account.py#L1340-L1341 In 13.0, the account.chart.template has been updated accordingly. As is, the migration did not succeed. At some point, odoo try to remove the old account.tag. But that's not possible because these tags are linked to existing account.move.line. https://github.com/OCA/OCB/blob/13.0/addons/account/models/account_move.py#L2792-L2796 To avoid such deletetion, I flagged existing account.account.tag as noupdate=True. When migrating the database the existing all account.account.tag linked to the account.tax are moved to all the account.tax.repartition.line of the account.tax. Meaning that if there is account.account.tag named "03", "49", "54" that are all linked to an account.tax. After migration each line of account.tax.repartition.line will have "03", "49" and "54" as tags. This does not reflect the new account.chart.template for belgium. So my first intention was to update the account.tax, particulary their account.tax.repartition.line to replace the old account.account.tag by the new one created during the migration. Using the new account.chart.template as an example. But that does not works, because existing account.move.line always points to the old account.account.tag. I have no idea how to update the tags on the account.move.line to reflects the new account.chart.template and the new tags. I tried to find the logic that computes tags on an account.move.line. But it's really obscure for me. And simply applying the following recompute method does not works (it causses issue about non balanced account element): https://github.com/OCA/OCB/blob/13.0/addons/account/models/account_move.py#L990-L1049 Anther option is to map the old tags to the new one. But here comes the problem that there is more new tags than old ones. So that I'm not sure how to perform the mapping. For example the following records: https://github.com/OCA/OCB/blob/12.0/addons/l10n_be/data/account_tax_template_data.xml#L16-L19 https://github.com/OCA/OCB/blob/13.0/addons/l10n_be/data/account_tax_report_data.xml#L45-L52 In 13.0 the account.account.tag created have sign. There exist two version for the tag 03: SELECT name, applicability, tax_negate FROM account_account_tag WHERE name ILIKE '%03'; name | applicability | tax_negate ---------------------------+---------------+------------ Belgium VAT Form: grid 03 | taxes | <- the old one -03 | taxes | t <-| +03 | taxes | f <-L the two new ones (3 rows) Should I replace the old "03" tag by the "+03" one, or should I sometimes replace it by the "-03" and when ? When this will be solved, I will still be wondering if such a line is ok ? SELECT account_move_line_id, name FROM account_account_tag_account_move_line_rel AS aatamlr JOIN account_account_tag AS aat ON aatamlr.account_account_tag_id = aat.id WHERE account_move_line_id = 9166; account_move_line_id | name ----------------------+--------------------------- 9166 | Belgium VAT Form: grid 03 9166 | Belgium VAT Form: grid 54 9166 | Belgium VAT Form: grid 49 9166 | Belgium VAT Form: grid 64 Where we see that an account.move.line is linked to 4 differents account.account.tag. I also take a look at this: - https://github.com/OCA/OCB/blob/12.0/addons/account/models/chart_template.py#L14-L52 - https://github.com/OCA/OCB/blob/13.0/addons/account/models/chart_template.py#L14-L31 But it does not seams to solve the previous issue. And finaly I looked at account_chart_update module, but it did not seams to solve the previous issues niether. https://github.com/OCA/account-financial-tools/tree/14.0/account_chart_update If you have any clue, it will be very helpfull. :) Regards, -- Rémy Taymans @ Coop IT Easy +32 493 02 69 85 - <https://github.com/remytms> <https://coopiteasy.be>
by Rémy Taymans - 04:06 - 21 Nov 2022-
Re: Question about migration of account.tax and related entity (in my case on l10n_be)
Dear Tom, Dear Danny, Thank you very much for your help. I will look at the resources you mentioned. :) Best regards, -- Rémy Taymans @ Coop IT Easy +32 493 02 69 85 - <https://github.com/remytms> <https://coopiteasy.be> Quoting Tom Blauwendraat (2022-11-22 15:46:48) > Hi Remy, > > We had the same problem in the migration of a few of our Dutch customers. My colleague Danny who is not on this list (yet, but he will sign up) worked on that and says the following: > > ----------------------------------------- > > Dear Remy, > > We have had a very similar thing happen in our migration from 10 to 14, between 12 and 13 yes. Although some of the things you mentioned we did not encounter, I had no problem with account.account.tag's being deleted for example. > > Part of the problem with the tags is this, in 13.0 a new model, called account.tax.report.line has been introduced. Now in 13, some tags are defined in xml files as account.tax.report.line instead of account.account.tag (as they were before). The report line model is responsible for creating new account.account.tag records in python, prefixed with a minus and plus sign. > > So you are dealing with new account.account.tag records, while all your account move lines and other stuff is still linked to the old account.account.tag records. There is no direct link to old and new tag records, so you kind of have to 'know' which old account.account.tag records are replaced with which new account.tax.report.line records, and then you could map them. > I took the route of remapping the old tags to the new tags, and that work can be viewed here: https://github.com/OCA/OpenUpgrade/blob/13.0/addons/l10n_nl/migrations/13.0.3.0/post-migration.py > I've moved some of the code into helper functions: https://github.com/OCA/openupgradelib/blob/master/openupgradelib/openupgrade_130.py > So I hope it will be easy enough to use those helper functions in your own script. Or maybe the convert_old_tax_tags_into_new_report_line_tags function of l10n_nl could even be completely reused? This is the function that does the mapping. > > Best regards, > Danny de Jong > > ------------------ > > With the following PS: ---> I noticed that the "l10n_be" migration scripts are missing from OpenUpgrade so that was the same as we encountered for l10n_nl
by Rémy Taymans - 05:35 - 22 Nov 2022 -
Re: Question about migration of account.tax and related entity (in my case on l10n_be)
Hi Remy,
We had the same problem in the migration of a few of our Dutch customers. My colleague Danny who is not on this list (yet, but he will sign up) worked on that and says the following:
-----------------------------------------
Dear Remy,
We have had a very similar thing happen in our migration from 10 to 14, between 12 and 13 yes. Although some of the things you mentioned we did not encounter, I had no problem with account.account.tag's being deleted for example.
Part of the problem with the tags is this, in 13.0 a new model, called account.tax.report.line has been introduced. Now in 13, some tags are defined in xml files as account.tax.report.line instead of account.account.tag (as they were before). The report line model is responsible for creating new account.account.tag records in python, prefixed with a minus and plus sign.
So you are dealing with new account.account.tag records, while all your account move lines and other stuff is still linked to the old account.account.tag records. There is no direct link to old and new tag records, so you kind of have to 'know' which old account.account.tag records are replaced with which new account.tax.report.line records, and then you could map them.
I took the route of remapping the old tags to the new tags, and that work can be viewed here: https://github.com/OCA/OpenUpgrade/blob/13.0/addons/l10n_nl/migrations/13.0.3.0/post-migration.py
Best regards,
I've moved some of the code into helper functions: https://github.com/OCA/openupgradelib/blob/master/openupgradelib/openupgrade_130.py
So I hope it will be easy enough to use those helper functions in your own script. Or maybe the convert_old_tax_tags_into_new_report_line_tags function of l10n_nl could even be completely reused? This is the function that does the mapping.
Danny de Jong
------------------
With the following PS: ---> I noticed that the "l10n_be" migration scripts are missing from OpenUpgrade so that was the same as we encountered for l10n_nl
------------------------------------------
On 11/21/22 16:07, Rémy Taymans wrote:
Dear community, I'm currently migrating a database from version 9.0 to version 14.0. My problem is between 12.0 and 13.0 where accounting element has changed. The database is using Mis Builder to generate accounting reports. These reports are based on account.account.tag that are linked to account.tax (and also account.move.line in 13.0). As I have seen, in 9.0 (and until 12.0), account.account.tag are linked to an account.tax via a simple field tag_ids : https://github.com/OCA/OCB/blob/12.0/addons/account/models/account.py#L937 Starting from 13.0, tags are no more linked to account.tax directly. They are linked to an account.tax.repartition.line which is linked to an account.account.tax. https://github.com/OCA/OCB/blob/13.0/addons/account/models/account.py#L1340-L1341 In 13.0, the account.chart.template has been updated accordingly. As is, the migration did not succeed. At some point, odoo try to remove the old account.tag. But that's not possible because these tags are linked to existing account.move.line. https://github.com/OCA/OCB/blob/13.0/addons/account/models/account_move.py#L2792-L2796 To avoid such deletetion, I flagged existing account.account.tag as noupdate=True. When migrating the database the existing all account.account.tag linked to the account.tax are moved to all the account.tax.repartition.line of the account.tax. Meaning that if there is account.account.tag named "03", "49", "54" that are all linked to an account.tax. After migration each line of account.tax.repartition.line will have "03", "49" and "54" as tags. This does not reflect the new account.chart.template for belgium. So my first intention was to update the account.tax, particulary their account.tax.repartition.line to replace the old account.account.tag by the new one created during the migration. Using the new account.chart.template as an example. But that does not works, because existing account.move.line always points to the old account.account.tag. I have no idea how to update the tags on the account.move.line to reflects the new account.chart.template and the new tags. I tried to find the logic that computes tags on an account.move.line. But it's really obscure for me. And simply applying the following recompute method does not works (it causses issue about non balanced account element): https://github.com/OCA/OCB/blob/13.0/addons/account/models/account_move.py#L990-L1049 Anther option is to map the old tags to the new one. But here comes the problem that there is more new tags than old ones. So that I'm not sure how to perform the mapping. For example the following records: https://github.com/OCA/OCB/blob/12.0/addons/l10n_be/data/account_tax_template_data.xml#L16-L19 https://github.com/OCA/OCB/blob/13.0/addons/l10n_be/data/account_tax_report_data.xml#L45-L52 In 13.0 the account.account.tag created have sign. There exist two version for the tag 03: SELECT name, applicability, tax_negate FROM account_account_tag WHERE name ILIKE '%03'; name | applicability | tax_negate ---------------------------+---------------+------------ Belgium VAT Form: grid 03 | taxes | <- the old one -03 | taxes | t <-| +03 | taxes | f <-L the two new ones (3 rows) Should I replace the old "03" tag by the "+03" one, or should I sometimes replace it by the "-03" and when ? When this will be solved, I will still be wondering if such a line is ok ? SELECT account_move_line_id, name FROM account_account_tag_account_move_line_rel AS aatamlr JOIN account_account_tag AS aat ON aatamlr.account_account_tag_id = aat.id WHERE account_move_line_id = 9166; account_move_line_id | name ----------------------+--------------------------- 9166 | Belgium VAT Form: grid 03 9166 | Belgium VAT Form: grid 54 9166 | Belgium VAT Form: grid 49 9166 | Belgium VAT Form: grid 64 Where we see that an account.move.line is linked to 4 differents account.account.tag. I also take a look at this: - https://github.com/OCA/OCB/blob/12.0/addons/account/models/chart_template.py#L14-L52 - https://github.com/OCA/OCB/blob/13.0/addons/account/models/chart_template.py#L14-L31 But it does not seams to solve the previous issue. And finaly I looked at account_chart_update module, but it did not seams to solve the previous issues niether. https://github.com/OCA/account-financial-tools/tree/14.0/account_chart_update If you have any clue, it will be very helpfull. :) Regards, -- Rémy Taymans @ Coop IT Easy +32 493 02 69 85 - <https://github.com/remytms> <https://coopiteasy.be>
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 03:46 - 22 Nov 2022
-
-
New OCA Delegates and Financial Auditors Campaign Open
Hello OCA Contributors,
I hope this finds you all well.
We've completed the Delegates campaign and now welcome 10 new Delegates to the OCA.Dora Jurcevic
Pierre Verkest
Jacques-Etienne Baudoux
Gijs-Jan Otten
Héctor Villarreal Ortega
Emeric Panisset
Quentin Dupont
Jean-Charles Drubay
Danny Adair
Nikolina Todorova
We were extremely fortunate this year with 23 members in total applying. Thank you to everyone who participated. It was energising to see so many great names put forward and I am sure for those voting it was difficult to choose just 10.
The process is now for the existing and new Delegates who wish to apply to become Board members, to do so - this stage closes on the 25th of November. The applicant survey has been shared on the Delegates mailing list.
The Financial Auditors campaign is now open too. The applicants for this do not need to be Delegates or Members, if you or someone in your organisation is interested in applying please complete this survey.
We'll keep you posted on the results of the voting in about a month's time when the Annual General Assembly is complete.Have a great week,Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 05:11 - 14 Nov 2022-
Re: New OCA Delegates and Financial Auditors Campaign Open
Congratulations and welcome, and hope to see at least as many applications as this year for 2023!How many Delegates do we have now?--
Virginie0477/64.17.20-----Original Message-----From: Maxime Chambreuil <notifications@odoo-community.org>Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>To: Contributors <contributors@odoo-community.org>Subject: Re: New OCA Delegates and Financial Auditors Campaign OpenDate: Mon, 14 Nov 2022 21:56:47 -0000Congratulations to the new elected delegates and welcome to the party!MAXIME CHAMBREUIL
DIRECTOR GENERAL LATAMM: +52 (442) 114-9164 / WhatsApp
E: MChambreuil@OpenSourceIntegrators.comAv. Paseo Tuna 18a, Local 217, Colonia Zibatá
El Marqués, Querétaro, 76269, México
On Mon, Nov 14, 2022 at 3:51 PM Jay Vora <notifications@odoo-community.org> wrote:Congratulations and good luck to Delegates!On Mon, 14 Nov 2022 at 8:17 AM, Rebecca Gellatly <notifications@odoo-community.org> wrote:Hello OCA Contributors,
I hope this finds you all well.
We've completed the Delegates campaign and now welcome 10 new Delegates to the OCA.Dora Jurcevic
Pierre Verkest
Jacques-Etienne Baudoux
Gijs-Jan Otten
Héctor Villarreal Ortega
Emeric Panisset
Quentin Dupont
Jean-Charles Drubay
Danny Adair
Nikolina Todorova
We were extremely fortunate this year with 23 members in total applying. Thank you to everyone who participated. It was energising to see so many great names put forward and I am sure for those voting it was difficult to choose just 10.
The process is now for the existing and new Delegates who wish to apply to become Board members, to do so - this stage closes on the 25th of November. The applicant survey has been shared on the Delegates mailing list.
The Financial Auditors campaign is now open too. The applicants for this do not need to be Delegates or Members, if you or someone in your organisation is interested in applying please complete this survey.
We'll keep you posted on the results of the voting in about a month's time when the Annual General Assembly is complete.Have a great week,Rebecca
by Virginie Dewulf. - 06:30 - 15 Nov 2022 -
Re: New OCA Delegates and Financial Auditors Campaign Open
Congratulations to the new elected delegates and welcome to the party!MAXIME CHAMBREUIL
DIRECTOR GENERAL LATAMM: +52 (442) 114-9164 / WhatsApp
E: MChambreuil@OpenSourceIntegrators.comAv. Paseo Tuna 18a, Local 217, Colonia Zibatá
El Marqués, Querétaro, 76269, MéxicoOn Mon, Nov 14, 2022 at 3:51 PM Jay Vora <notifications@odoo-community.org> wrote:Congratulations and good luck to Delegates!--On Mon, 14 Nov 2022 at 8:17 AM, Rebecca Gellatly <notifications@odoo-community.org> wrote:Hello OCA Contributors,
I hope this finds you all well.
We've completed the Delegates campaign and now welcome 10 new Delegates to the OCA.Dora Jurcevic
Pierre Verkest
Jacques-Etienne Baudoux
Gijs-Jan Otten
Héctor Villarreal Ortega
Emeric Panisset
Quentin Dupont
Jean-Charles Drubay
Danny Adair
Nikolina Todorova
We were extremely fortunate this year with 23 members in total applying. Thank you to everyone who participated. It was energising to see so many great names put forward and I am sure for those voting it was difficult to choose just 10.
The process is now for the existing and new Delegates who wish to apply to become Board members, to do so - this stage closes on the 25th of November. The applicant survey has been shared on the Delegates mailing list.
The Financial Auditors campaign is now open too. The applicants for this do not need to be Delegates or Members, if you or someone in your organisation is interested in applying please complete this survey.
We'll keep you posted on the results of the voting in about a month's time when the Annual General Assembly is complete.Have a great week,Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Technology Services @ www.serpentcs.comBusiness Solutions @ www.serpentcs.inEnterprise Mobile Apps @ www.odooonline.comQuality Assurance @ www.odooqa.comSAP Hana @ www.prozone-tech.comPortal & DMS @ www.alfray.inRegards,----------------------------------------------------------------------------------------------------------------------------Jay Vora Managing Director 
Direct: +91-9879354457 Office: +91-9033472982 Skype: jaynvora Twitter : jaynvora -------------------------------------------------------------------------------------------------
Visit our website : http://www.serpentcs.com_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Maxime Chambreuil - 10:55 - 14 Nov 2022 -
Re: New OCA Delegates and Financial Auditors Campaign Open
Congratulations and good luck to Delegates!--On Mon, 14 Nov 2022 at 8:17 AM, Rebecca Gellatly <notifications@odoo-community.org> wrote:Hello OCA Contributors,
I hope this finds you all well.
We've completed the Delegates campaign and now welcome 10 new Delegates to the OCA.Dora Jurcevic
Pierre Verkest
Jacques-Etienne Baudoux
Gijs-Jan Otten
Héctor Villarreal Ortega
Emeric Panisset
Quentin Dupont
Jean-Charles Drubay
Danny Adair
Nikolina Todorova
We were extremely fortunate this year with 23 members in total applying. Thank you to everyone who participated. It was energising to see so many great names put forward and I am sure for those voting it was difficult to choose just 10.
The process is now for the existing and new Delegates who wish to apply to become Board members, to do so - this stage closes on the 25th of November. The applicant survey has been shared on the Delegates mailing list.
The Financial Auditors campaign is now open too. The applicants for this do not need to be Delegates or Members, if you or someone in your organisation is interested in applying please complete this survey.
We'll keep you posted on the results of the voting in about a month's time when the Annual General Assembly is complete.Have a great week,Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Technology Services @ www.serpentcs.comBusiness Solutions @ www.serpentcs.inEnterprise Mobile Apps @ www.odooonline.comQuality Assurance @ www.odooqa.comSAP Hana @ www.prozone-tech.comPortal & DMS @ www.alfray.inRegards,----------------------------------------------------------------------------------------------------------------------------Jay Vora Managing Director Direct: +91-9879354457 Office: +91-9033472982 Skype: jaynvora Twitter : jaynvora -------------------------------------------------------------------------------------------------
Visit our website : http://www.serpentcs.com
by Jay Vora - 10:51 - 14 Nov 2022
-
PSC Members and Representatives - please complete activities for 2022 OCA AGA
HI all,
We've had a bit of response to my previous email as we check-in for the year on how everyone has gotten on.
Please if you haven't had a chance have a look at the working document here and fill in what you have been up to over the year.
I'll close this off next Wednesday the 16th, so you've got a week ;)
It doesn't need to be a long post, just a quick summary of what has been accomplished.
Thank you in advance.
Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 02:26 - 9 Nov 2022-
Re: PSC Members and Representatives - please complete activities for 2022 OCA AGA
Very much appreciated Nicolas! Thank you.On Wed, 9 Nov 2022 at 14:42, Nicolas Rodriguez <notifications@odoo-community.org> wrote:Hello Rebecca, I’m a quite new PSC but I completed the document with information of what I has been doing to payroll modules even before of becoming PSC.
Hope it helps. Regards.El 8 de nov. de 2022 22:26 -0300, Rebecca Gellatly <notifications@odoo-community.org>, escribió:
HI all,
We've had a bit of response to my previous email as we check-in for the year on how everyone has gotten on.
Please if you haven't had a chance have a look at the working document here and fill in what you have been up to over the year.
I'll close this off next Wednesday the 16th, so you've got a week ;)
It doesn't need to be a long post, just a quick summary of what has been accomplished.
Thank you in advance.
Rebecca--
Rebecca GellatlyGeneral SecretaryOdoo Community Association_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 02:56 - 9 Nov 2022 -
Re: PSC Members and Representatives - please complete activities for 2022 OCA AGA
Hello Rebecca, I’m a quite new PSC but I completed the document with information of what I has been doing to payroll modules even before of becoming PSC.
Hope it helps. Regards.El 8 de nov. de 2022 22:26 -0300, Rebecca Gellatly <notifications@odoo-community.org>, escribió:
HI all,
We've had a bit of response to my previous email as we check-in for the year on how everyone has gotten on.
Please if you haven't had a chance have a look at the working document here and fill in what you have been up to over the year.
I'll close this off next Wednesday the 16th, so you've got a week ;)
It doesn't need to be a long post, just a quick summary of what has been accomplished.
Thank you in advance.
Rebecca--
Rebecca GellatlyGeneral SecretaryOdoo Community Association_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Nicolas Rodriguez Sande - 02:41 - 9 Nov 2022
-
-
Inventory report / valuation loading time
Hi,do you have any solutions/suggestions to speed up inventory reports/valuation loading time?Thanks!--Francesco ForestiSicurpharma Srl
by Francesco Foresti - 12:51 - 7 Nov 2022-
Re: Inventory report / valuation loading time
Hi Francesco,For things like this, I use a SQL query, creating a new model, based on a database view. Here's a query that works for me in v12.Mattwith a as (
select
pp.id as product_id,
pc.id as category_id,
aa.id as account_id
from product_product pp
left join product_template pt on pt.id=pp.product_tmpl_id
left join product_category as pc on pc.id=pt.categ_id
left join ir_property as ip on ip.res_id='product.category,'||pt.categ_id and ip.name='property_stock_valuation_account_id'
left join account_account as aa on 'account.account,'||aa.id=ip.value_reference
where pt.type='product'
--and pt.active=true
)
select
pp.default_code,
pt.name as product_name,
pc.name as cat_name,
pt.type as product_type,
pt.tracking,
pt.active,
pt.deprecated,
uu.name as uom,
round(mv.avail_qty, 0) as stock_qty,
av.acct_value,
round(av.acct_qty, 0),
av.acct_qty - mv.avail_qty as diff
from a
left join (
select
a.product_id,
sum(aml.balance) as acct_value,
sum(aml.quantity) as acct_qty
from a
left join account_move_line as aml on aml.product_id=a.product_id and aml.account_id=a.account_id
left join account_move as am on am.id=aml.move_id
where am.state='posted'
and aml.date<'2022-01-01'
group by a.product_id
) as av on av.product_id=a.product_id
left join (
select
sm.product_id,
sum(
case when (ls.usage<>'internal' and ld.usage='internal') then sm.product_qty
else -sm.product_qty end
) as avail_qty
from stock_move as sm
left join stock_location as ls on ls.id=sm.location_id
left join stock_location as ld on ld.id=sm.location_dest_id
where sm.state='done'
and sm.date<'2022-01-01'
and (
(ls.usage<>'internal' and ld.usage='internal')
or
(ld.usage<>'internal' and ls.usage='internal')
)
group by sm.product_id
) as mv on mv.product_id=av.product_id
left join product_product as pp on pp.id=a.product_id
left join product_template as pt on pt.id=pp.product_tmpl_id
left join product_category as pc on pc.id=a.category_id
left join uom_uom as uu on uu.id=pt.uom_id
where pc.name like 'RM - %'
and av.acct_value<>0
and coalesce(mv.avail_qty, 0.0)<>0.0On Mon, Nov 7, 2022 at 5:12 AM Frederik Kramer <notifications@odoo-community.org> wrote:Hi Francesco,
that is genuinly one to the more ressource hungry processes in Odoo (and of course all ERP systems). It heavily depends on what report you exactly execute, configuration parameters like (use of serial numbers, concrete valuation method, amount of stock locations to consider) and last but certainly not least the overall amount of stock moves in you database (that are a subset of the concrete report under investigation), version of Odoo that you are using and many more.
As far as i know there is no simple method that helps everywhere (as the problem origins can be vast), but i would recommend to analyze / profile first what actually takes so much time while processing the report in the calculation before taking any measure in whatever direction. Depending on the version of Odoo you are using and the landscape you are running there are different tools to profile. If you tell us the version that you are running, the amount of stock movel lines and stock locations we are speaking about an generally a bit more detail about your case i am sure some more technical people among our community can recommend that to exactly analyze first.
Best Frederik
Am 07.11.22 um 12:51 schrieb Francesco Foresti:
Hi,
do you have any solutions/suggestions to speed up inventory reports/valuation loading time?
Thanks!
--
Francesco ForestiSicurpharma Srl_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Phone: +49 4181 13503-12 Fax: +49 4181 13503-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Matt - 08:18 - 7 Nov 2022 -
Re: Inventory report / valuation loading time
Hi Francesco,
that is genuinly one to the more ressource hungry processes in Odoo (and of course all ERP systems). It heavily depends on what report you exactly execute, configuration parameters like (use of serial numbers, concrete valuation method, amount of stock locations to consider) and last but certainly not least the overall amount of stock moves in you database (that are a subset of the concrete report under investigation), version of Odoo that you are using and many more.
As far as i know there is no simple method that helps everywhere (as the problem origins can be vast), but i would recommend to analyze / profile first what actually takes so much time while processing the report in the calculation before taking any measure in whatever direction. Depending on the version of Odoo you are using and the landscape you are running there are different tools to profile. If you tell us the version that you are running, the amount of stock movel lines and stock locations we are speaking about an generally a bit more detail about your case i am sure some more technical people among our community can recommend that to exactly analyze first.
Best Frederik
Am 07.11.22 um 12:51 schrieb Francesco Foresti:
Hi,
do you have any solutions/suggestions to speed up inventory reports/valuation loading time?
Thanks!
--
Francesco ForestiSicurpharma Srl_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Phone: +49 4181 13503-12 Fax: +49 4181 13503-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer. - 01:10 - 7 Nov 2022
-
-
Getting in touch
Hi,My name is Ludovic Gilardi, I am financial director and I have been using odoo for two years now.I discovered your association during the odoo experience 2022.Can you give me more information about your association and your activities?Best regard.Ludovic Gilardi
by "Chlorobike" <l.gilardi@chlorobike.com> - 11:46 - 2 Nov 2022-
Re: Getting in touch
Hi, Ludovic,Please check the website https://odoo-community.org/ and come with any doubt you have after that.Regards.
by Pedro M. Baeza - 01:06 - 2 Nov 2022
-
-
Help solving a CI issue
Hello, I’m the new PSC of l10n-Argentina. We are delayed with uploading the modules to the repository due to a issue that I’m trying to solve.
If you see this PR (https://github.com/OCA/l10n-argentina/pull/66) you will see that CI is trying to install pyafipws like an external dependency. The problem is that the pipx package is outdated and I need to instal pyafipws from a github repository and follow some specific install guidelines.
I need to install the version in this repo https://github.com/reingart/pyafipws - branch py3k and also execute this commands:
Go to installation directory of PyAFIPWS:cd /usr/local/lib/python3/dist-packages/pyafipws
Note: Replacepython3by the python version in the system (likepython3.9)
Create a folder with the name cache:sudo mkdir cache
Change permission of folder:sudo chmod -R 777 cache
* extracted from one of our local wikis
This instructions can be easily followed in a local or production installation but I’m having trouble to replicate this with OCA CI since oca tries to install it with pipx and it will not work because we need an specific version.
This library is essential to our Argentinian localization since it’s a wrapper of our country AFIP api, which is widely used across all our localization. So electronic invoice modules can not work without it.
So I’m thinking in writing a custom CI workflow with GitHub actions but don’t know if it’s allowed in OCA and also don’t know where to start.
I will be dedicating time to this next week so any input or suggestion of how to do that will be great.
Any of you had to do something similar in the past? If you can refer me to a repo which also need something similar or point me in the correct direction about this I will be very great
full since I want to do it without changing OCA CI configuration too much.
Help will be highly appreciated.
Also, if any of you with repo access can make branch 14.0 the default one in the repository, it will be great, since we are going to start migrating version 14.0 first, adapt the modules and add tests and the migrate to 15 and 16.
Sorry for the length of the email. Hope you can provide some input. Thanks and regards.
by Nicolas Rodriguez Sande - 01:21 - 2 Nov 2022-
Re: Help solving a CI issue
> I need to install the version in this > repo https://github.com/reingart/pyafipws - branch py3k and also execute > this commands: you can use external_dependencies_override (cf https://pypi.org/project/ setuptools-odoo/#controlling-setuptools-odoo-behaviour) where you can do something like pyafipws@https://github.com/reingart/pyafipws/archive/py3k.zip (cf https://pip.pypa.io/en/stable/reference/requirement-specifiers/ #requirement-specifiers) > Go to installation directory of PyAFIPWS: > cd /usr/local/lib/python3/dist-packages/pyafipws > Note: Replace python3 by the python version in the system (like python3.9) > Create a folder with the name cache: > sudo mkdir cache > Change permission of folder: > sudo chmod -R 777 cache > * extracted from one of our local wikis I'd strongly suggest to fix this in the python package itself, this will make stuff better for anyone involved anyways. Having a cache directory there is quite wrong, this should go to /var/cache or ~/.cache (cf https:// en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard), and you can create this for the global case (local can just create it on first run) during installation by overriding the install command class passing a custom cmdclass (cf https:// docs.python.org/3/distutils/extending.html#integrating-new-commands) dict. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 07:30 - 2 Nov 2022
-
-
Reconcile Widget with OWL
Hi!!I have been working this weekend on the new reconcile widget for v16 using OWL. It might be not mandatory yet, but, it is interesting to do this ASAP.I am trying to do it visually similar to Enterprise (UX), but the approach should be completly different.However, as we are still in a initial process, it is interesting to do some comments. On 14 and 15, when we reconciled bank statements, we modified a posted move. It was weird, but useful. Should we continue with this approach?I can show you a small gif of how it is going. Right now, only manual conciliation works (no models, no invoices), but it should be easy :D).I hope I can open a PR soon (at least, when minimal requirements are fulfilled)Kind regards,
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
by Enric Tobella Alomar - 06:30 - 1 Nov 2022-
Re: Reconcile Widget with OWL
I made a commit that allows you to define the reconcile mode on bank/cash journals, I think it is as you wished :D (the part of keeping the orginal lines )
From: "Marco Marchiori" <notifications@odoo-community.org>
To: "Contributors" <contributors@odoo-community.org>
Date: Thu, 03 Nov 2022 21:36:53 -0000
Subject: Re: Reconcile Widget with OWL
Maybe an alternative could be to post only the reconciled entries (and not the import or the synchro entries).I don't see the point in having temporary posted entries all with the same counterpart.Sooner or later I think odoo will decide to change.MarcoIl mer 2 nov 2022, 22:06 Cyril VINH-TUNG <notifications@odoo-community.org> ha scritto:Dear all,Here in PF (country of FR), we disagree with the modification of a posted entry.We still do like we did in v8.We had to hack both account_payment and reconciliation_widget in order to :- forbid deletion of a validated payment https://github.com/odoo/odoo/pull/96941- allow reconciliation of draft entries https://github.com/OCA/account-reconcile/pull/403We have to force journal setup to disable suspense accounts use. With that setup, the payment entries are validated with an intermediate account. This intermediate account is reconciled with the bank.As Odoo SA won't change the reconciliation process, I agree with Pedro that the module has to be flexible.@Alexis De Lattre what do you think ?Best regardsLe mer. 2 nov. 2022, 10:27, Pedro M. Baeza <notifications@odoo-community.org> a écrit :Although the purist approach would be to generate a new journal entry moving the balance from the suspense account to the definitive account matched on the reconciliation widget, I think we can keep current approach for not generating too much noise, and taking into account that you can't do this in a locked period. Maybe we can introduce a parameter for choosing which one to use...Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
by Enric Tobella Alomar - 09:21 - 21 Nov 2022 -
Re: Reconcile Widget with OWL
OK, then go ahead with it!Regards.
by Pedro M. Baeza - 12:36 - 6 Nov 2022 -
Re: Reconcile Widget with OWL
No, reconcile has two parts. One is the reconcile of bank statement lines, that is almost done. The second one is the reconcile of accounts used from invoicing / accounting/actions/reconciliation. I would like to do some big changes of the view, following a similar approach from the bankOn 6 Nov 2022 09:36, "Pedro M. Baeza" <notifications@odoo-community.org> wrote:About reconcile accounts, do you mean to use the suspense account in the journal? If so, I think that should be.Regards.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
by Enric Tobella Alomar - 12:15 - 6 Nov 2022 -
Re: Reconcile Widget with OWL
About reconcile accounts, do you mean to use the suspense account in the journal? If so, I think that should be.Regards.
by Pedro M. Baeza - 09:36 - 6 Nov 2022 -
Re: Reconcile Widget with OWL
The current behavior allows you to have the same result on your bank and your ERP for the bank account balance. So it is a good idea IMO.The bank reconcile widget is ready for review. A bug was found regarding the chatter, but I don't know how to fix it in an easy way.Next step is the reconcile accounts. I think it would be cleaner to reuse the same functionality (not the old one), as it seems cleaner to me. WDYT?
From: "Marco Marchiori" <notifications@odoo-community.org>
To: "Contributors" <contributors@odoo-community.org>
Date: Thu, 03 Nov 2022 21:36:53 -0000
Subject: Re: Reconcile Widget with OWL
Maybe an alternative could be to post only the reconciled entries (and not the import or the synchro entries).I don't see the point in having temporary posted entries all with the same counterpart.Sooner or later I think odoo will decide to change.MarcoIl mer 2 nov 2022, 22:06 Cyril VINH-TUNG <notifications@odoo-community.org> ha scritto:Dear all,Here in PF (country of FR), we disagree with the modification of a posted entry.We still do like we did in v8.We had to hack both account_payment and reconciliation_widget in order to :- forbid deletion of a validated payment https://github.com/odoo/odoo/pull/96941- allow reconciliation of draft entries https://github.com/OCA/account-reconcile/pull/403We have to force journal setup to disable suspense accounts use. With that setup, the payment entries are validated with an intermediate account. This intermediate account is reconciled with the bank.As Odoo SA won't change the reconciliation process, I agree with Pedro that the module has to be flexible.@Alexis De Lattre what do you think ?Best regardsLe mer. 2 nov. 2022, 10:27, Pedro M. Baeza <notifications@odoo-community.org> a écrit :Although the purist approach would be to generate a new journal entry moving the balance from the suspense account to the definitive account matched on the reconciliation widget, I think we can keep current approach for not generating too much noise, and taking into account that you can't do this in a locked period. Maybe we can introduce a parameter for choosing which one to use...Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
by Enric Tobella Alomar - 08:56 - 6 Nov 2022
-
-
Call for action - Metrics and KPIs for OCA accounting and finance dashboards
Hi all,As Odoo SA (Fabien himself) considers that we can't use code that has been open sourced for some time under a LGPL license should be used as a start for a community module, and the layers bill is expensive, let's start a new module from scratch.Can you please share here what are the main metrics and KPIs that you consider inside these areas for being included?Regards.
by Pedro M. Baeza - 02:25 - 30 Oct 2022-
Re: Call for action - Metrics and KPIs for OCA accounting and finance dashboards
As mentioned before, different goal will use different indicators.
For a dashboard analyzing past financial financial performance, a well known set of indicators is the DuPont analysis.
It is quite interesting because it starts with the ROI or ROE and decomposes it in more focused indicators.
See: https://en.wikipedia.org/wiki/DuPont_analysis
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
by Daniel Reis - 10:00 - 1 Nov 2022 -
Re: Call for action - Metrics and KPIs for OCA accounting and finance dashboards
As mentioned before, different goal will use different indicators.
For a dashboard analyzing past financial financial performance, a well known set of indicators is the DuPont analysis.
It is quite interesting because it starts with the ROI or ROE and decomposes it in more focused indicators.
See: https://en.wikipedia.org/wiki/DuPont_analysis
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
by Daniel Reis - 08:01 - 1 Nov 2022 -
Re: Call for action - Metrics and KPIs for OCA accounting and finance dashboards
I suggested edits for a couple of standard metrics: Current Ratio = current assets / current liabilities Quick Ratio = (cash and equivalent account + account receivable) / current liabilities Working Capital = current assets - current liabilities Cheers, Mike. On 31/10/2022 15:41, Pedro M. Baeza wrote: > I think both are interesting. Let's gather all together for now, with > an explanation, its goal and how to compute it, and then we can plan > which ones we implement first. I have opened this Google Docs document > for writing them in a collaborative manner: > > https://docs.google.com/document/d/1FDIud707XFMa08Q0U8UTJMa4UEp1rEEA1dx3P41XNew/edit# > > You can also comment on the structure of the document itself. > > Thank you very much for your interest. > > Regards. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe >
by Raphael Makonnen - 01:21 - 1 Nov 2022 -
Re: Call for action - Metrics and KPIs for OCA accounting and finance dashboards
I think both are interesting. Let's gather all together for now, with an explanation, its goal and how to compute it, and then we can plan which ones we implement first. I have opened this Google Docs document for writing them in a collaborative manner:You can also comment on the structure of the document itself.Thank you very much for your interest.Regards.
by Pedro M. Baeza - 01:41 - 31 Oct 2022 -
Re: Call for action - Metrics and KPIs for OCA accounting and finance dashboards
PedroHow are you? Great initiative! The field is a bit vast, what kind of KPI regarding Finance and Accounting would be preferable? The most daily operation ones, as liquidity, receivables, payables, etc or more strategic ones, referred to equities, operation results, etc?Thanks!El sáb, 29 oct 2022 a la(s) 22:27, Pedro M. Baeza (notifications@odoo-community.org) escribió:Hi all,As Odoo SA (Fabien himself) considers that we can't use code that has been open sourced for some time under a LGPL license should be used as a start for a community module, and the layers bill is expensive, let's start a new module from scratch.Can you please share here what are the main metrics and KPIs that you consider inside these areas for being included?Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Gonzalo Ruzafa - 01:11 - 31 Oct 2022
-
-
Company as maintainer
Hello,since we have several devs working on modules developed by our company in OCA, we'd like to attribute the role of "maintainer" of such modules to a company github account in order to centralize:- notifications about changes to modules we have originally developed- questions and communications about the aforementioned modules- merging of minor changes such as this oneWould it be possible for us to do so?Thanks for your opinion!--Francesco ForestiSicurpharma Srl
by Francesco Foresti - 04:20 - 27 Oct 2022-
Re: Company as maintainer
Hi, I think there are several interesting points in this conversation, as well as Jean-Charles' project which could be very useful in my opinion - keeping track of specific modules' improvement and/or bug reports would make our work quite easier.For example, knowing if a certain behavior has been fixed in a commit for the previous or next version of a module, and just migrating the commit instead of fixing it again.In general, as I mentioned in a previous email, I think it would be extremely convenient for PMs and devs alike to have some space where all things related to a module could be collected - PRs, known issues, general discussions, if module is or will be discontinued in future versions and why...But to keep discussion focus on maintainership:Let's say Company A contracts Dev X to develop Module 1Module 1 is built on specifications provided by Company A, to address use cases from customers of Company A, and ultimately it's PM from Company A who designs how the module should work functionally (of course based on technical expertise and guidance from Dev X)If Dev X stops working with Company A, takes a sabbatical, leaves odoo development altogether or simply does not check notifications on email related to github account...Are we sure that maintainership is better ensured by assigning the "maintainer" role to Dev X rather than Company A?Ultimately I don't think it's a bad idea to have them both.FrancescoIl giorno dom 30 ott 2022 alle ore 01:37 Jean-Charles Drubay <notifications@odoo-community.org> ha scritto:Hi,I share the same observation more and more: there is a need to track/manage modules instead of repositories.Going in this direction I started to work on this topic which started around OpenUpgrade only at first until I realized that this need was broader than OpenUpgrade only:I have prepared a prototype to share the information per module and which can be tested here https://oca-cm-15.komit.linkThe Issues and PRs are linked to the module base d on the name of the Issues/PRs so at this stage it's not reliable.But naming conventions could be enforced by github checks I guess, at least for the PRs.Adding a notification mechanism should not be complicated.I am currently working on a v2 of the prototype.I am open to sharing the code, which I already did upon request.I am also open to discussions.
Best regards,
Jean-CharlesOn Sat, Oct 29, 2022 at 4:57 PM Pedro M. Baeza <notifications@odoo-community.or g> wrote:I'm afraid I don't have a solution for that. I'm subscribed to everything... and yes, lots of noise. But it also serves for having a whole picture, as "what are the modules I am interested in?" Maybe a new module arises over a feature I want.I use my self-called "5 seconds rule" for dealing with the huge amount of notifications: 5 seconds to decide if to discard it, answer immediately if it takes less than a minute, which can be my distraction window, or let it in my inbox for a later and more calm answer. This allows me to be reactive enough as well as not requiring too much time.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ForestiSicurpharma Srl+39 333 8123 790
by Francesco Foresti - 02:46 - 31 Oct 2022 -
Re: Company as maintainer
Hi,I share the same observation more and more: there is a need to track/manage modules instead of repositories.Going in this direction I started to work on this topic which started around OpenUpgrade only at first until I realized that this need was broader than OpenUpgrade only:I have prepared a prototype to share the information per module and which can be tested here https://oca-cm-15.komit.linkThe Issues and PRs are linked to the module based on the name of the Issues/PRs so at this stage it's not reliable.But naming conventions could be enforced by github checks I guess, at least for the PRs.Adding a notification mechanism should not be complicated.I am currently working on a v2 of the prototype.I am open to sharing the code, which I already did upon request.I am also open to discussions.Best regards,
Jean-CharlesOn Sat, Oct 29, 2022 at 4:57 PM Pedro M. Baeza <notifications@odoo-community.org> wrote:I'm afraid I don't have a solution for that. I'm subscribed to everything... and yes, lots of noise. But it also serves for having a whole picture, as "what are the modules I am interested in?" Maybe a new module arises over a feature I want.I use my self-called "5 seconds rule" for dealing with the huge amount of notifications: 5 seconds to decide if to discard it, answer immediately if it takes less than a minute, which can be my distraction window, or let it in my inbox for a later and more calm answer. This allows me to be reactive enough as well as not requiring too much time.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Jean-Charles Drubay - 01:35 - 30 Oct 2022 -
Re: Company as maintainer
I'm afraid I don't have a solution for that. I'm subscribed to everything... and yes, lots of noise. But it also serves for having a whole picture, as "what are the modules I am interested in?" Maybe a new module arises over a feature I want.I use my self-called "5 seconds rule" for dealing with the huge amount of notifications: 5 seconds to decide if to discard it, answer immediately if it takes less than a minute, which can be my distraction window, or let it in my inbox for a later and more calm answer. This allows me to be reactive enough as well as not requiring too much time.Regards.
by Pedro M. Baeza - 11:55 - 29 Oct 2022 -
Re: Company as maintainer
That's nice to know all the pull requests from your company.But what I'm after is a mechanism to be notified when there are pull requests or issues opened against modules I'm interested in.GitHub per repo notifications are too coarse, that generate too much noise for many modules I don't care about.-sbiOn Sat, Oct 29, 2022 at 11:36 AM Pedro M. Baeza <notifications@odoo-community.org> wrote:What we do is to include in the pull request main comment `@Tecnativa` for later search for such pull requests, using `involves`. This is for example our current status:Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 11:45 - 29 Oct 2022 -
Re: Company as maintainer
What we do is to include in the pull request main comment `@Tecnativa` for later search for such pull requests, using `involves`. This is for example our current status:Regards.
by Pedro M. Baeza - 11:26 - 29 Oct 2022
-
-
URGENT Call to Action - OCA Delegates Campaign - extended till Friday 28th October
Hello OCA Contributors
I wanted to let you know we have extended the Delegate Campaign as part of the OCA Annual General Assembly. It will now close this Friday 28th October. If you are a current paid member of the OCA, you can apply to become a Delegate.
We have had only 7 applications so far - we vote each year to select 10. We would love to see more people apply. This step in the process of our Association happenings is what helps keep the community dynamic with fresh faces and voices coming in alongside our contributors of many years.
It is certainly not a hugely time-consuming task to be a Delegate, if this is a potential obstacle. We have the AGA once a year and it consists of:- voting for new Delegates (reading profiles then voting)
- reading the AGA documents for the year (basically an activities report, AGA specific items and financial statements)
- voting to accept the documents, board members and financial auditors
- this year, we will also be asking the Delegates to vote on whether or not we change the OCA Logo.
Occasionally, during the year we ask the Delegates to vote on other issues, but again this does not take huge amounts of time. Around OCA Days we may ask for some extra help from Delegates, if they are available.
This contribution, in terms of voting, is vital to keep the community vibrant and moving forward. If people are feeling they aren't able to contribute in this way, would you please reach out and let us know what might be stopping you as we would like to have the opportunity to address this and find out what obstacles may be hindering people.
All you need to do to apply is:sign the CLA (if not already done)
have a valid membership. Make sure to purchase your membership or renew it.
We've pushed everything out by a week to accommodate extending the voting. New dates are as follows:- 10th - 28th October - Week 1 & 3: OCA paid members of 2022 invited to apply their candidacy to become an OCA Delegate
- 31st October - 11th November - Week 4 & 5: Active OCA Delegates vote for 10 new OCA Delegates
- 14th - 25th November - Week 6 & 7: OCA Delegates announce their candidacy to become an OCA Board Member or Financial Auditor (for the FA the applicant does not need to be a Delegate)
- 28 November - 9th December - Week 8 & 9: OCA Delegates vote for board members, auditors, and financial statements
Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 11:35 - 24 Oct 2022-
Re: URGENT Call to Action - OCA Delegates Campaign - extended till Friday 28th October
Hello RebeccaI will also add my application. I am not much familiar with programming but that should not be a problem, given the list of duties.Regards
Julien Jézéquel-Bréard - Chargé de projetsNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada
Le lun. 24 oct. 2022 à 17:36, Rebecca Gellatly <notifications@odoo-community.org> a écrit :Hello OCA Contributors
I wanted to let you know we have extended the Delegate Campaign as part of the OCA Annual General Assembly. It will now close this Friday 28th October. If you are a current paid member of the OCA, you can apply to become a Delegate.
We have had only 7 applications so far - we vote each year to select 10. We would love to see more people apply. This step in the process of our Association happenings is what helps keep the community dynamic with fresh faces and voices coming in alongside our contributors of many years.
It is certainly not a hugely time-consuming task to be a Delegate, if this is a potential obstacle. We have the AGA once a year and it consists of:- voting for new Delegates (reading profiles then voting)
- reading the AGA documents for the year (basically an activities report, AGA specific items and financial statements)
- voting to accept the documents, board members and financial auditors
- this year, we will also be asking the Delegates to vote on whether or not we change the OCA Logo.
Occasionally, during the year we ask the Delegates to vote on other issues, but again this does not take huge amounts of time. Around OCA Days we may ask for some extra help from Delegates, if they are available.
This contribution, in terms of voting, is vital to keep the community vibrant and moving forward. If people are feeling they aren't able to contribute in this way, would you please reach out and let us know what might be stopping you as we would like to have the opportunity to address this and find out what obstacles may be hindering people.
All you need to do to apply is:sign the CLA (if not already done)
have a valid membership. Make sure to purchase your membership or renew it.
We've pushed everything out by a week to accommodate extending the voting. New dates are as follows:- 10th - 28th October - Week 1 & 3: OCA paid members of 2022 invited to apply their candidacy to become an OCA Delegate
- 31st October - 11th November - Week 4 & 5: Active OCA Delegates vote for 10 new OCA Delegates
- 14th - 25th November - Week 6 & 7: OCA Delegates announce their candidacy to become an OCA Board Member or Financial Auditor (for the FA the applicant does not need to be a Delegate)
- 28 November - 9th December - Week 8 & 9: OCA Delegates vote for board members, auditors, and financial statements
Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Julien Jézéquel-Bréard - 05:26 - 25 Oct 2022 -
Re: URGENT Call to Action - OCA Delegates Campaign - extended till Friday 28th October
Hello, I will be happy to be candidate if there is no other qualified applicants.
I will buy the subscription and sign the CLA by tomorrow. I you think my candidature will help please wait for me to do that.El 25 de oct. de 2022 10:12 -0300, Willem Hulshof <notifications@odoo-community.org>, escribió:
Dear OCA,
I’ll be happy to be candidate for delegate.
Met vriendelijke groet/Kind regards/Distinti saluti,
Magnus Red
Willem Hulshof+31 88 696 60 00 | +31 651 243 710 | www.magnus.nl
Van: Rebecca Gellatly <notifications@odoo-community.org>
Datum: maandag, 24 oktober 2022 om 23:36
Aan: Contributors <contributors@odoo-community.org>
Onderwerp: URGENT Call to Action - OCA Delegates Campaign - extended till Friday 28th OctoberHello OCA Contributors
I wanted to let you know we have extended the Delegate Campaign as part of the OCA Annual General Assembly. It will now close this Friday 28th October. If you are a current paid member of the OCA, you can apply to become a Delegate.
We have had only 7 applications so far - we vote each year to select 10. We would love to see more people apply. This step in the process of our Association happenings is what helps keep the community dynamic with fresh faces and voices coming in alongside our contributors of many years.
It is certainly not a hugely time-consuming task to be a Delegate, if this is a potential obstacle. We have the AGA once a year and it consists of:- voting for new Delegates (reading profiles then voting)
- reading the AGA documents for the year (basically an activities report, AGA specific items and financial statements)
- voting to accept the documents, board members and financial auditors
- this year, we will also be asking the Delegates to vote on whether or not we change the OCA Logo.
Occasionally, during the year we ask the Delegates to vote on other issues, but again this does not take huge amounts of time. Around OCA Days we may ask for some extra help from Delegates, if they are available.
This contribution, in terms of voting, is vital to keep the community vibrant and moving forward. If people are feeling they aren't able to contribute in this way, would you please reach out and let us know what might be stopping you as we would like to have the opportunity to address this and find out what obstacles may be hindering people.
All you need to do to apply is:· sign the CLA (if not already done)
· have a valid membership. Make sure to purchase your membership or renew it.
We've pushed everything out by a week to accommodate extending the voting. New dates are as follows:
· 10th - 28th October - Week 1 & 3: OCA paid members of 2022 invited to apply their candidacy to become an OCA Delegate
· 31st October - 11th November - Week 4 & 5: Active OCA Delegates vote for 10 new OCA Delegates
· 14th - 25th November - Week 6 & 7: OCA Delegates announce their candidacy to become an OCA Board Member or Financial Auditor (for the FA the applicant does not need to be a Delegate)
· 28 November - 9th December - Week 8 & 9: OCA Delegates vote for board members, auditors, and financial statements
Any issues, please do get in touch.
Rebecca
--
Rebecca Gellatly
General Secretary
Odoo Community Association
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Nicolas Rodriguez Sande - 03:50 - 25 Oct 2022 -
Re: URGENT Call to Action - OCA Delegates Campaign - extended till Friday 28th October
Dear OCA,
I’ll be happy to be candidate for delegate.
Met vriendelijke groet/Kind regards/Distinti saluti,
Magnus Red
Willem Hulshof+31 88 696 60 00 | +31 651 243 710 | www.magnus.nl
Van: Rebecca Gellatly <notifications@odoo-community.org>
Datum: maandag, 24 oktober 2022 om 23:36
Aan: Contributors <contributors@odoo-community.org>
Onderwerp: URGENT Call to Action - OCA Delegates Campaign - extended till Friday 28th OctoberHello OCA Contributors
I wanted to let you know we have extended the Delegate Campaign as part of the OCA Annual General Assembly. It will now close this Friday 28th October. If you are a current paid member of the OCA, you can apply to become a Delegate.
We have had only 7 applications so far - we vote each year to select 10. We would love to see more people apply. This step in the process of our Association happenings is what helps keep the community dynamic with fresh faces and voices coming in alongside our contributors of many years.
It is certainly not a hugely time-consuming task to be a Delegate, if this is a potential obstacle. We have the AGA once a year and it consists of:- voting for new Delegates (reading profiles then voting)
- reading the AGA documents for the year (basically an activities report, AGA specific items and financial statements)
- voting to accept the documents, board members and financial auditors
- this year, we will also be asking the Delegates to vote on whether or not we change the OCA Logo.
Occasionally, during the year we ask the Delegates to vote on other issues, but again this does not take huge amounts of time. Around OCA Days we may ask for some extra help from Delegates, if they are available.
This contribution, in terms of voting, is vital to keep the community vibrant and moving forward. If people are feeling they aren't able to contribute in this way, would you please reach out and let us know what might be stopping you as we would like to have the opportunity to address this and find out what obstacles may be hindering people.
All you need to do to apply is:· sign the CLA (if not already done)
· have a valid membership. Make sure to purchase your membership or renew it.
We've pushed everything out by a week to accommodate extending the voting. New dates are as follows:
· 10th - 28th October - Week 1 & 3: OCA paid members of 2022 invited to apply their candidacy to become an OCA Delegate
· 31st October - 11th November - Week 4 & 5: Active OCA Delegates vote for 10 new OCA Delegates
· 14th - 25th November - Week 6 & 7: OCA Delegates announce their candidacy to become an OCA Board Member or Financial Auditor (for the FA the applicant does not need to be a Delegate)
· 28 November - 9th December - Week 8 & 9: OCA Delegates vote for board members, auditors, and financial statements
Any issues, please do get in touch.
Rebecca
--
Rebecca Gellatly
General Secretary
Odoo Community Association
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Willem Hulshof - 03:11 - 25 Oct 2022 -
Re: URGENT Call to Action - OCA Delegates Campaign - extended till Friday 28th October
> wanted to let more senior/experienced/advenced members you are one of those by now. And please everyone who feels similarly come format -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 02:41 - 25 Oct 2022 -
Re: URGENT Call to Action - OCA Delegates Campaign - extended till Friday 28th October
Hello Rebecca, wanted to let more senior/experienced/advenced members to take care of this but if there's lack of interested parties I will try to help. Please find the CLA attached. My membership should be valid. I have filled in the survey. Best regards Radovan Skolnik On pondelok 24. októbra 2022 23:36:49 CEST Rebecca Gellatly wrote: > Hello OCA Contributors > > I wanted to let you know we have extended the Delegate Campaign as part of > the OCA Annual General Assembly. It will now close this Friday 28th > October. If you are a current paid member of the OCA, you can apply to > become a Delegate. > > We have had only 7 applications so far - we vote each year to select 10. We > would love to see more people apply. This step in the process of our > Association happenings is what helps keep the community dynamic with fresh > faces and voices coming in alongside our contributors of many years. > > It is certainly not a hugely time-consuming task to be a Delegate, if this > is a potential obstacle. We have the AGA once a year and it consists of: > > voting for new Delegates (reading profiles then voting) > reading the AGA documents for the year (basically an activities report, AGA > specific items and financial statements) voting to accept the documents, > board members and financial auditors this year, we will also be asking the > Delegates to vote on whether or not we change the OCA Logo. Occasionally, > during the year we ask the Delegates to vote on other issues, but again > this does not take huge amounts of time. Around OCA Days we may ask for > some extra help from Delegates, if they are available. > > This contribution, in terms of voting, is vital to keep the community > vibrant and moving forward. If people are feeling they aren't able to > contribute in this way, would you please reach out and let us know what > might be stopping you as we would like to have the opportunity to address > this and find out what obstacles may be hindering people. > > All you need to do to apply is: > > > > sign the CLA (if not already done) > > have a valid membership. Make sure to purchase your membership or renew it. > > fill in this survey > > We've pushed everything out by a week to accommodate extending the voting. > New dates are as follows: > > 10th - 28th October - Week 1 & 3: OCA paid members of 2022 invited to apply > their candidacy to become an OCA Delegate 31st October - 11th November - > Week 4 & 5: Active OCA Delegates vote for 10 new OCA Delegates 14th - 25th > November - Week 6 & 7: OCA Delegates announce their candidacy to become an > OCA Board Member or Financial Auditor (for the FA the applicant does not > need to be a Delegate) 28 November - 9th December - Week 8 & 9: OCA > Delegates vote for board members, auditors, and financial statements Any > issues, please do get in touch. > Rebecca > > > -- > > Rebecca Gellatly > General Secretary > Odoo Community Association > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 12:20 - 25 Oct 2022
