Skip to Content

Contributors

  • Re: Functional Question: Year End Closing in Odoo (OPEJ)
    Functional speaking, it is only a waste of time, the only utility is showing how the annual result come from by printing it in a clearly (and not modifiable) way on the company accounting.
    Sergio Corato


    Il giorno gio 19 mar 2020 alle ore 08:37 Kitti Upariphutthiphong <kittiu@ecosoft.co.th> ha scritto:
    Thank you Sergio,

    Surely +1 for me.

    Also want to understand why many people think it is not needed anymore. I try to find from issue, but see no explanation, just says it is not needed. May be functionally, there are good reasons not to have it?

    Thanks!

    On Thu, Mar 19, 2020 at 2:17 PM Sergio Corato <sergiocorato@gmail.com> wrote:
    Hi Kitti,
    the account year closing module wich was in account-closing repo until v. 10.0, and was moving to 11.0 with this PR but closed as not needed anymore, is mandatory in Italy, so I recovered it with this PR for 12.0.
    If it can be useful in other countries, I can move to account-closing repo if accepted from its PSC.
    Sergio Corato


    Il giorno gio 19 mar 2020 alle ore 03:57 Kitti Upariphutthiphong <kittiu@ecosoft.co.th> ha scritto:
    Dear community,

    We are quite amused that now that Odoo no longer have "Generate Fiscal Year Opening Entries" which create OPEJ like in V8.

    Someone suggest to just use the report to close year end. But functional people see it as not a proper way to work.

    How do you guys process year end closing? Or should we bring back the same feature as in V8 to OCA?

    Kitti

    _______________________________________________
    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


    by Sergio Corato - 09:26 - 19 Mar 2020
  • Re: Functional Question: Year End Closing in Odoo (OPEJ)
    Thank you Sergio,

    Surely +1 for me.

    Also want to understand why many people think it is not needed anymore. I try to find from issue, but see no explanation, just says it is not needed. May be functionally, there are good reasons not to have it?

    Thanks!

    On Thu, Mar 19, 2020 at 2:17 PM Sergio Corato <sergiocorato@gmail.com> wrote:
    Hi Kitti,
    the account year closing module wich was in account-closing repo until v. 10.0, and was moving to 11.0 with this PR but closed as not needed anymore, is mandatory in Italy, so I recovered it with this PR for 12.0.
    If it can be useful in other countries, I can move to account-closing repo if accepted from its PSC.
    Sergio Corato


    Il giorno gio 19 mar 2020 alle ore 03:57 Kitti Upariphutthiphong <kittiu@ecosoft.co.th> ha scritto:
    Dear community,

    We are quite amused that now that Odoo no longer have "Generate Fiscal Year Opening Entries" which create OPEJ like in V8.

    Someone suggest to just use the report to close year end. But functional people see it as not a proper way to work.

    How do you guys process year end closing? Or should we bring back the same feature as in V8 to OCA?

    Kitti

    _______________________________________________
    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 Kitti Upariphutthiphong - 08:36 - 19 Mar 2020
  • Re: Functional Question: Year End Closing in Odoo (OPEJ)
    Hi Kitti,
    the account year closing module wich was in account-closing repo until v. 10.0, and was moving to 11.0 with this PR but closed as not needed anymore, is mandatory in Italy, so I recovered it with this PR for 12.0.
    If it can be useful in other countries, I can move to account-closing repo if accepted from its PSC.
    Sergio Corato


    Il giorno gio 19 mar 2020 alle ore 03:57 Kitti Upariphutthiphong <kittiu@ecosoft.co.th> ha scritto:
    Dear community,

    We are quite amused that now that Odoo no longer have "Generate Fiscal Year Opening Entries" which create OPEJ like in V8.

    Someone suggest to just use the report to close year end. But functional people see it as not a proper way to work.

    How do you guys process year end closing? Or should we bring back the same feature as in V8 to OCA?

    Kitti

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Sergio Corato - 08:15 - 19 Mar 2020
  • Functional Question: Year End Closing in Odoo (OPEJ)
    Dear community,

    We are quite amused that now that Odoo no longer have "Generate Fiscal Year Opening Entries" which create OPEJ like in V8.

    Someone suggest to just use the report to close year end. But functional people see it as not a proper way to work.

    How do you guys process year end closing? Or should we bring back the same feature as in V8 to OCA?

    Kitti

    by Kitti Upariphutthiphong - 03:55 - 19 Mar 2020
  • Backport base_iban widget 13->12
    Hello,

    I made kind of backport of base_iban widget from v13 to v12 for my needs, here it'is https://github.com/article714/base_iban_widget. I was wondering if maybe it could be officially backported by OCA? To have something cleaner that what i have done, especially about scss. I had to add "position: static !important;" to see icon at the right place and it slightly modify account_number widget look.

    Best regards,

    Damien Couppé


    by Damien Couppé <damien.couppe@gmail.com> - 11:26 - 16 Mar 2020
  • Information on GitHub PR Reviewers
    Hi all,
    I have some PR open in OCA/management-system, OCA/manufacture and OCA/l10n-italy.
    When I opened them I was able to manage the Reviewers, the gear icon near the label on the right was visible, and this was valid until 2-3 week ago when the icon desapeared.

    So my question is, something is changed on GitHub level or OCA level to leave only PSC able to manage Reviewers?
    This is only a curiosity, I can live without this option active ;-)

    Stefano Consolaro
    www.mymage.it

    by Stefano Consolaro - 09:35 - 16 Mar 2020
  • Re: Leave + Employee departing
    Yes, emptying allowances with a new line or other model depending on rules you set on leave days remaining.

    I have not yet seen a module for the "magic button" you are thinking.
    Maybe you can have a look to OCA repo of course, and some repo as https://github.com/CybroOdoo/OpenHRMS

    Have a nice day!
    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter


    Le dim. 15 mars 2020 à 03:37, Alexey Pelykh <alexey.pelykh@gmail.com> a écrit :
    Hi Bruno,

    Emptying the allowances - by creating a leave request you mean?
    I’m thinking of some magic button “convert leaves to cash” sort of module.

    Kind regards,
    Alexey

    On 14 Mar 2020, at 16:22, Bruno Joliveau <bruno.joliveau@numigi.com> wrote:

    Hi Alexey,

    I dismiss the legal aspects, different from country to country.

    You must purge his bank of holidays by emptying his allowances on his last day.

    If you make his pay with Odoo, the credit of his bank of holidays is compensated by an equivalent amount in money.

    Hope it helps you!
    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter


    Le sam. 14 mars 2020 à 05:42, Alexey Pelykh <alexey.pelykh@gmail.com> a écrit :
    Dear community,
    
    How to workaround following thing in Odoo: there’s an employee who has 10 paid annual leave days remaining and who have decided to depart from company. Those 10 days are subject to be paid out, yet is there even a way to “deduct those days from leaves and convert them to payroll”? After some consideration, creating a post-depart leave is not really an option it seems.
    
    Kind regards,
    Alexey

    _______________________________________________
    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 Bruno Joliveau - 03:50 - 15 Mar 2020
  • Re: Leave + Employee departing
    Hi Bruno,

    Emptying the allowances - by creating a leave request you mean?
    I’m thinking of some magic button “convert leaves to cash” sort of module.

    Kind regards,
    Alexey

    On 14 Mar 2020, at 16:22, Bruno Joliveau <bruno.joliveau@numigi.com> wrote:

    Hi Alexey,

    I dismiss the legal aspects, different from country to country.

    You must purge his bank of holidays by emptying his allowances on his last day.

    If you make his pay with Odoo, the credit of his bank of holidays is compensated by an equivalent amount in money.

    Hope it helps you!
    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter


    Le sam. 14 mars 2020 à 05:42, Alexey Pelykh <alexey.pelykh@gmail.com> a écrit :
    Dear community,
    
    How to workaround following thing in Odoo: there’s an employee who has 10 paid annual leave days remaining and who have decided to depart from company. Those 10 days are subject to be paid out, yet is there even a way to “deduct those days from leaves and convert them to payroll”? After some consideration, creating a post-depart leave is not really an option it seems.
    
    Kind regards,
    Alexey

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    by Alexey Pelykh <alexey.pelykh@gmail.com> - 08:36 - 15 Mar 2020
  • Re: Your opinion and experience about "Point Bank Management"
    Many thanks for your contributions Dominic, Jonathan and Graeme!

    I understand your feedback regarding analytics, and I will rule out this assumption.

    I am reluctant to add the stock module and its dependencies for that.

    I like the idea of a register, like a new Odoo model. I do not have fluent English and it is also in this sense that I asked the community in the case of a similar project that has not yet been listed in OCA.

    Regarding multi-currency, this is a point that we had hypothesized. I did not put all the ideas in my initial email ;-)

    I add one of them that we had discarded and partially corresponds to comments that you shared.

    As we need to manage price lists both for sale and in point consumption actions that we will recover from third-party solutions and integrate into Odoo, we had considered using:
    1 - multicurrency by creating a new virtual currency "POINTS", the "POINTS" have a rate translation with existing real currencies, as Odoo knows how to do
    2 - the customer buys product A ($ 100 for a quantity of 1), we use the standard "Sales" features
    3 - when its payment is established, its bank of "POINTS" is credited with the correspondence $ »" POINTS ". Is this a new object like the register you were sharing, why not?
    4 - the customer consumes his "POINTS" by various actions through third-party software. Some of identical actions have different prices in "POINTS" from one customer to another. We had considered using Odoo's sale.order with sale_order_type (from OCA) which would also allow us to use price lists and all the sales functionalities. The payment of these sale.order is done by purging the bank of "POINTS".
    5 - We have discarded the consideration of purchase workflow to avoid considering the customer as a supplier as well. However, this could be reconsidered to distinct the purchase / sale price list from the same partner.

    In the meantime, thank you for your comments which help guide our decisions. We are continuing our reflections before next steps (estimation and costing of this project).
    This is really what I appreciate in our ecosystem, and any link or comment is welcome :)

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter


    Le ven. 13 mars 2020 à 23:46, Graeme Gellatly <gdgellatly@gmail.com> a écrit :
    I'm still not seeing the issue. If the points are worth nothing then they wont be on balance sheet. If points are worth something then clearly they must be on balance sheet AND a revenue reduction on p&l.  It is no different to any other kind of revenue recognition such as warranty provisions under IFRS. 

    Accruing points on an invoice is nothing more than an account id on an invoice line. But even then it doesn't matter, anglosaxon has always created extra entries per invoice line. The identical logic applies. 

    Whether odoo is the accounting system or not seems irrelevant. Fundamentally this is accounting whether you want to call it something else or not.  Balances are maintained, there are debits and credits based on activity. 

    On Sat, 14 Mar 2020, 4:32 PM Dominique k, <dominique.k@elico-corp.com.sg> wrote:
    you need to be able to have an invoice in a currency, AND at the same time  records the number of points used or earned.

    Beside not all business will want having the points on their balance sheet and odoo may not always be the accounting system. 





    On Sat, 14 Mar 2020 at 10:02 AM, Graeme Gellatly <gdgellatly@gmail.com> wrote:
    Maybe I'm missing something but isnt this really just a receivable account in a different currency. 

    Everything else is just transactions in that currency. 

    On Sat, 14 Mar 2020, 2:01 PM Jonathan Wilson, <jonathan.wilson@willdooit.com> wrote:
    Hi Bruno

    I'm thinking along the line of a register, ie rather like a share register. The register is updated by strategically coded actions and keeps a complete translation/audti trail of all ins and outs. I'm assuming there will also be a financial implication when points are earned, ie they become a liability in the balance sheet, when redeemed they are removed. If a register is used the balance sheet figure can always be reconciled against the register. Additionally, a register will be an easy way to report to the customer. 

    I agree with Dominique in not using analytics - sometimes it just easier and cleaner to use our own model, and it also makes upgrades easier.

    Hope I understood it correctly and it is of some use to you.

    Kind regards

    Jonathan Wilson

    Chief Sales and Innovation Executive

    WilldooIT Pty Ltd





    First Australian Odoo GOLD partner
    2017, 2015 & 2013 Odoo Best Partner Asia/Pacific
    Creators of  Odoo-Pentaho integration project

    "Making growth through technology easy"


    E: jonathan.wilson@willdooit.com

    P: +61 3 9135 1900

    M: +61  4 000 17 444

    Linkedin

    10/435 Williamstown Road

    Port Melbourne VIC 3207

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by Willdoo IT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.




    On Sat, 14 Mar 2020 at 03:33, Bruno Joliveau <bruno.joliveau@numigi.com> wrote:

    Hi Community,


    I am writing to get your point of view or maybe, share on existing modules.


    As part of a new client project, we need to:

    - sell products whose consumption is done at a different rate and volume.

    - the customer must have their consumption history and their balance


    Relatively classic and common so far ;-)


    It is a service activity, but the unit of value is not time. And, a priori, there is no stock management.


    Summary customer process:


    The customer purchases product A (for example $ 100 for 1 quantity)

    In return, the client benefits from a capital of 250 points, for example.

    The customer consumes his points by different actions. These actions are reported by several applications. We can collect those actions and create events in Odoo.

    The customer must be able to know the evolution of his capital of points.


    At this step, several hypothesis considered:


    1 - sale order and analytic

    - addition of a second unit of measurement in SO

    - when the SO is confirmed, this quantity corresponding to the second unit feeds an analytical account

    - for a better reading the analytical lines could take advantage of a new type as they already have with timesheets

    - each action performed by the customer that triggers consumption creates a new line as a deduction in his capital of points

    - the customer has access to his analytical account to view the balance of his capital of points


    2 - sale order and product_pack

    - rather than adding secondary units in the sale order, the customer buys a pack

    - the capital points is a product in its own right with a quantity of 250 (child of the initial product with its quantity 1)

    - it is only this product which feeds an analytical account

    - the following steps are the same as the previous assumption


    3 - sale order and stock

    - although there is no need to manage the inventory, we activate and configure the stock features

    - the customer orders a product in quantity 1

    - an equivalence in stock management is made on a storable product of 250 points

    - each action carried out by the customer which triggers consumption creates a new line as a deduction in the inventory management of his capital of points

    - the customer has access to his own stock location to view the balance of his capital of points with his history


    Thank you for taking the time to read, I hope this is clear enough.

    Look forward to your comments and suggestions!

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedin youtube custom-icon twitter

    _______________________________________________
    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

    --
    Dominique KON-SUN-TACK  [Project Manager]
    Odoo Gold Partner, best Odoo Partner 2014 for APAC

    Mobile: + 65 8502 2399
    Skype: dominique_elico


    _______________________________________________
    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 Bruno Joliveau - 05:10 - 14 Mar 2020
  • Re: Pre-commit updates
    Hi all,

    The new configurations have been pushed. Let me know of any issue.

    Take care,

    -sbi

    On Sat, Mar 7, 2020 at 1:43 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
    Okay folks, after a few weeks of fine tuning we are ready to launch this update.


    I just wanted to insist on the fact that all XML files on the 13.0 branches are going to be reformatted.
    This is for the better, IMO, but if you have major refactorings in progress this may disturb your workflow.

    So if any PSC want to temporarily opt-out some repos of this update, let me know before Friday March 13th.

    Best regards,

    -sbi

    --
    Stéphane Bidoul | @SBidoul
    Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

    On Fri, Jan 24, 2020 at 3:02 PM Jairo Llopis <jairo.llopis@tecnativa.com> wrote:
    tl;dr: pre-commit is getting updated, expect conflicts in your PRs. XML and JS autoformatting!

    Hi community.

    As you might know, for v13 we took a big step forward in our coding standards introducing pre-commit in our workflow, which rewrites all python code in a beautiful-enough fashion.

    After the work we've done in https://github.com/OCA/maintainer-quality-tools/pull/618, our dear Stéphane Bidoul will soon update the pre-commit configuration and it will enable even more code automatic standardization.

    In this case, the main change comes from the inclusion of Prettier and ESLint --fix in our pipeline. They will take the job of prettifying code of these files:
    • .scss/.css
    • .js
    • .xml (via prettier plugin)
    • Others not so common in our codebase: .md, .html, .less, .yaml
    • Before you ask, files created or modified by bots are excluded from the reformat.
    • Only for v13+
    The case for JS is a little bit special in the sense that style changes will be done by Prettier, and AST changes will be done by ESLit, but ESLint still have some linter rules that are not autofixable, and in such case your commit will fail until you satisfy them manually.

    Given this will produce a big diff commit (just like isort+black did), I took this chance to update some of the tools that we were already using, so there could be a little more diff in python maybe. It shouldn't be too much.

    We hope this saves you a lot of time and pain when writing these files. Just write ugly & quick code, and pre-commit will handle the rest 😁

    How does this affect you?

    Really not much; just:
    1. Your open PRs could get conflicts. Rebase it and fix them as usual.
    2. Remember to do pre-commit install when you clone a repo.
    3. JS code might need an update to satisfy the linter.
    4. You are encouraged to enable eslint, black, prettier and editorconfig plugins in your favourite IDE, as you probably already did with flake8 and pylint. They should work out of the box, although pre-commit is the maximum authority regarding code reformatting because it works exactly the same in all envs.
    The change is planned for february 15th, although Stéphane will tell more details in this thread if needed (please) and I'm advancing it for web and website where the change is most interesting.

    Have a nice day!
    --
    Jairo Llopis

    _______________________________________________
    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 - 05:10 - 14 Mar 2020
  • Re: Leave + Employee departing
    Hi Alexey,

    I dismiss the legal aspects, different from country to country.

    You must purge his bank of holidays by emptying his allowances on his last day.

    If you make his pay with Odoo, the credit of his bank of holidays is compensated by an equivalent amount in money.

    Hope it helps you!
    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter


    Le sam. 14 mars 2020 à 05:42, Alexey Pelykh <alexey.pelykh@gmail.com> a écrit :
    Dear community,
    
    How to workaround following thing in Odoo: there’s an employee who has 10 paid annual leave days remaining and who have decided to depart from company. Those 10 days are subject to be paid out, yet is there even a way to “deduct those days from leaves and convert them to payroll”? After some consideration, creating a post-depart leave is not really an option it seems.
    
    Kind regards,
    Alexey

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Bruno Joliveau - 04:21 - 14 Mar 2020
  • Leave + Employee departing
    Dear community,
    
    How to workaround following thing in Odoo: there’s an employee who has 10 paid annual leave days remaining and who have decided to depart from company. Those 10 days are subject to be paid out, yet is there even a way to “deduct those days from leaves and convert them to payroll”? After some consideration, creating a post-depart leave is not really an option it seems.
    
    Kind regards,
    Alexey

    by Alexey Pelykh <alexey.pelykh@gmail.com> - 10:41 - 14 Mar 2020
  • Re: Your opinion and experience about "Point Bank Management"
    I'm still not seeing the issue. If the points are worth nothing then they wont be on balance sheet. If points are worth something then clearly they must be on balance sheet AND a revenue reduction on p&l.  It is no different to any other kind of revenue recognition such as warranty provisions under IFRS. 

    Accruing points on an invoice is nothing more than an account id on an invoice line. But even then it doesn't matter, anglosaxon has always created extra entries per invoice line. The identical logic applies. 

    Whether odoo is the accounting system or not seems irrelevant. Fundamentally this is accounting whether you want to call it something else or not.  Balances are maintained, there are debits and credits based on activity. 

    On Sat, 14 Mar 2020, 4:32 PM Dominique k, <dominique.k@elico-corp.com.sg> wrote:
    you need to be able to have an invoice in a currency, AND at the same time  records the number of points used or earned.

    Beside not all business will want having the points on their balance sheet and odoo may not always be the accounting system. 





    On Sat, 14 Mar 2020 at 10:02 AM, Graeme Gellatly <gdgellatly@gmail.com> wrote:
    Maybe I'm missing something but isnt this really just a receivable account in a different currency. 

    Everything else is just transactions in that currency. 

    On Sat, 14 Mar 2020, 2:01 PM Jonathan Wilson, <jonathan.wilson@willdooit.com> wrote:
    Hi Bruno

    I'm thinking along the line of a register, ie rather like a share register. The register is updated by strategically coded actions and keeps a complete translation/audti trail of all ins and outs. I'm assuming there will also be a financial implication when points are earned, ie they become a liability in the balance sheet, when redeemed they are removed. If a register is used the balance sheet figure can always be reconciled against the register. Additionally, a register will be an easy way to report to the customer. 

    I agree with Dominique in not using analytics - sometimes it just easier and cleaner to use our own model, and it also makes upgrades easier.

    Hope I understood it correctly and it is of some use to you.

    Kind regards

    Jonathan Wilson

    Chief Sales and Innovation Executive

    WilldooIT Pty Ltd





    First Australian Odoo GOLD partner
    2017, 2015 & 2013 Odoo Best Partner Asia/Pacific
    Creators of  Odoo-Pentaho integration project

    "Making growth through technology easy"


    E: jonathan.wilson@willdooit.com

    P: +61 3 9135 1900

    M: +61  4 000 17 444

    Linkedin

    10/435 Williamstown Road

    Port Melbourne VIC 3207

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by Willdoo IT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.




    On Sat, 14 Mar 2020 at 03:33, Bruno Joliveau <bruno.joliveau@numigi.com> wrote:

    Hi Community,


    I am writing to get your point of view or maybe, share on existing modules.


    As part of a new client project, we need to:

    - sell products whose consumption is done at a different rate and volume.

    - the customer must have their consumption history and their balance


    Relatively classic and common so far ;-)


    It is a service activity, but the unit of value is not time. And, a priori, there is no stock management.


    Summary customer process:


    The customer purchases product A (for example $ 100 for 1 quantity)

    In return, the client benefits from a capital of 250 points, for example.

    The customer consumes his points by different actions. These actions are reported by several applications. We can collect those actions and create events in Odoo.

    The customer must be able to know the evolution of his capital of points.


    At this step, several hypothesis considered:


    1 - sale order and analytic

    - addition of a second unit of measurement in SO

    - when the SO is confirmed, this quantity corresponding to the second unit feeds an analytical account

    - for a better reading the analytical lines could take advantage of a new type as they already have with timesheets

    - each action performed by the customer that triggers consumption creates a new line as a deduction in his capital of points

    - the customer has access to his analytical account to view the balance of his capital of points


    2 - sale order and product_pack

    - rather than adding secondary units in the sale order, the customer buys a pack

    - the capital points is a product in its own right with a quantity of 250 (child of the initial product with its quantity 1)

    - it is only this product which feeds an analytical account

    - the following steps are the same as the previous assumption


    3 - sale order and stock

    - although there is no need to manage the inventory, we activate and configure the stock features

    - the customer orders a product in quantity 1

    - an equivalence in stock management is made on a storable product of 250 points

    - each action carried out by the customer which triggers consumption creates a new line as a deduction in the inventory management of his capital of points

    - the customer has access to his own stock location to view the balance of his capital of points with his history


    Thank you for taking the time to read, I hope this is clear enough.

    Look forward to your comments and suggestions!

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedin youtube custom-icon twitter

    _______________________________________________
    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

    --
    Dominique KON-SUN-TACK  [Project Manager]
    Odoo Gold Partner, best Odoo Partner 2014 for APAC

    Mobile: + 65 8502 2399
    Skype: dominique_elico


    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Graeme Gellatly - 04:45 - 14 Mar 2020
  • Re: Your opinion and experience about "Point Bank Management"
    you need to be able to have an invoice in a currency, AND at the same time  records the number of points used or earned.

    Beside not all business will want having the points on their balance sheet and odoo may not always be the accounting system. 





    On Sat, 14 Mar 2020 at 10:02 AM, Graeme Gellatly <gdgellatly@gmail.com> wrote:
    Maybe I'm missing something but isnt this really just a receivable account in a different currency. 

    Everything else is just transactions in that currency. 

    On Sat, 14 Mar 2020, 2:01 PM Jonathan Wilson, <jonathan.wilson@willdooit.com> wrote:
    Hi Bruno

    I'm thinking along the line of a register, ie rather like a share register. The register is updated by strategically coded actions and keeps a complete translation/audti trail of all ins and outs. I'm assuming there will also be a financial implication when points are earned, ie they become a liability in the balance sheet, when redeemed they are removed. If a register is used the balance sheet figure can always be reconciled against the register. Additionally, a register will be an easy way to report to the customer. 

    I agree with Dominique in not using analytics - sometimes it just easier and cleaner to use our own model, and it also makes upgrades easier.

    Hope I understood it correctly and it is of some use to you.

    Kind regards

    Jonathan Wilson

    Chief Sales and Innovation Executive

    WilldooIT Pty Ltd





    First Australian Odoo GOLD partner
    2017, 2015 & 2013 Odoo Best Partner Asia/Pacific
    Creators of  Odoo-Pentaho integration project

    "Making growth through technology easy"


    E: jonathan.wilson@willdooit.com

    P: +61 3 9135 1900

    M: +61  4 000 17 444

    Linkedin

    10/435 Williamstown Road

    Port Melbourne VIC 3207

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by Willdoo IT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.




    On Sat, 14 Mar 2020 at 03:33, Bruno Joliveau <bruno.joliveau@numigi.com> wrote:

    Hi Community,


    I am writing to get your point of view or maybe, share on existing modules.


    As part of a new client project, we need to:

    - sell products whose consumption is done at a different rate and volume.

    - the customer must have their consumption history and their balance


    Relatively classic and common so far ;-)


    It is a service activity, but the unit of value is not time. And, a priori, there is no stock management.


    Summary customer process:


    The customer purchases product A (for example $ 100 for 1 quantity)

    In return, the client benefits from a capital of 250 points, for example.

    The customer consumes his points by different actions. These actions are reported by several applications. We can collect those actions and create events in Odoo.

    The customer must be able to know the evolution of his capital of points.


    At this step, several hypothesis considered:


    1 - sale order and analytic

    - addition of a second unit of measurement in SO

    - when the SO is confirmed, this quantity corresponding to the second unit feeds an analytical account

    - for a better reading the analytical lines could take advantage of a new type as they already have with timesheets

    - each action performed by the customer that triggers consumption creates a new line as a deduction in his capital of points

    - the customer has access to his analytical account to view the balance of his capital of points


    2 - sale order and product_pack

    - rather than adding secondary units in the sale order, the customer buys a pack

    - the capital points is a product in its own right with a quantity of 250 (child of the initial product with its quantity 1)

    - it is only this product which feeds an analytical account

    - the following steps are the same as the previous assumption


    3 - sale order and stock

    - although there is no need to manage the inventory, we activate and configure the stock features

    - the customer orders a product in quantity 1

    - an equivalence in stock management is made on a storable product of 250 points

    - each action carried out by the customer which triggers consumption creates a new line as a deduction in the inventory management of his capital of points

    - the customer has access to his own stock location to view the balance of his capital of points with his history


    Thank you for taking the time to read, I hope this is clear enough.

    Look forward to your comments and suggestions!

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedin youtube custom-icon twitter

    _______________________________________________
    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

    --
    Dominique KON-SUN-TACK  [Project Manager]
    Odoo Gold Partner, best Odoo Partner 2014 for APAC

    Mobile: + 65 8502 2399
    Skype: dominique_elico



    by dominique.k - 04:31 - 14 Mar 2020
  • Re: Github OCA do not have runbot and codecov in v13
    Thank you Mosie, for clarifying :)

    On Thu, Mar 12, 2020 at 1:22 PM Moises Lopez <moylop260@vauxoo.com> wrote:
    Hi Kitti,
    I check the URL that you sent but it looks fine to me since that it is using runbot correctly and green status.

    For the codecov, there is an opened issue about:

    Regards!

    El mié., 11 mar. 2020 a las 21:27, Kitti Upariphutthiphong (<kittiu@ecosoft.co.th>) escribió:
    Hi again,

    Since there was no answer. May I ask again. Do I miss something?

    image.png

    No codecov anymore?
    Thanks!

    On Mon, Feb 17, 2020 at 3:10 PM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
    Dear contributors,

    Has been  experiences this a while now. For example,

    Only Travis seem working.
    Thank you,


    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Moisés López Calderón
    Mobile: (+521) 477-752-22-30
    Twitter: @moylop260
    hangout: moylop260@vauxoo.com
    http://www.vauxoo.com - Odoo Gold Partner
    Twitter: @vauxoo

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Kitti Upariphutthiphong - 04:06 - 14 Mar 2020
  • Re: Your opinion and experience about "Point Bank Management"
    Maybe I'm missing something but isnt this really just a receivable account in a different currency. 

    Everything else is just transactions in that currency. 

    On Sat, 14 Mar 2020, 2:01 PM Jonathan Wilson, <jonathan.wilson@willdooit.com> wrote:
    Hi Bruno

    I'm thinking along the line of a register, ie rather like a share register. The register is updated by strategically coded actions and keeps a complete translation/audti trail of all ins and outs. I'm assuming there will also be a financial implication when points are earned, ie they become a liability in the balance sheet, when redeemed they are removed. If a register is used the balance sheet figure can always be reconciled against the register. Additionally, a register will be an easy way to report to the customer. 

    I agree with Dominique in not using analytics - sometimes it just easier and cleaner to use our own model, and it also makes upgrades easier.

    Hope I understood it correctly and it is of some use to you.

    Kind regards

    Jonathan Wilson

    Chief Sales and Innovation Executive

    WilldooIT Pty Ltd





    First Australian Odoo GOLD partner
    2017, 2015 & 2013 Odoo Best Partner Asia/Pacific
    Creators of  Odoo-Pentaho integration project

    "Making growth through technology easy"


    E: jonathan.wilson@willdooit.com

    P: +61 3 9135 1900

    M: +61  4 000 17 444

    Linkedin

    10/435 Williamstown Road

    Port Melbourne VIC 3207

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by Willdoo IT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.




    On Sat, 14 Mar 2020 at 03:33, Bruno Joliveau <bruno.joliveau@numigi.com> wrote:

    Hi Community,


    I am writing to get your point of view or maybe, share on existing modules.


    As part of a new client project, we need to:

    - sell products whose consumption is done at a different rate and volume.

    - the customer must have their consumption history and their balance


    Relatively classic and common so far ;-)


    It is a service activity, but the unit of value is not time. And, a priori, there is no stock management.


    Summary customer process:


    The customer purchases product A (for example $ 100 for 1 quantity)

    In return, the client benefits from a capital of 250 points, for example.

    The customer consumes his points by different actions. These actions are reported by several applications. We can collect those actions and create events in Odoo.

    The customer must be able to know the evolution of his capital of points.


    At this step, several hypothesis considered:


    1 - sale order and analytic

    - addition of a second unit of measurement in SO

    - when the SO is confirmed, this quantity corresponding to the second unit feeds an analytical account

    - for a better reading the analytical lines could take advantage of a new type as they already have with timesheets

    - each action performed by the customer that triggers consumption creates a new line as a deduction in his capital of points

    - the customer has access to his analytical account to view the balance of his capital of points


    2 - sale order and product_pack

    - rather than adding secondary units in the sale order, the customer buys a pack

    - the capital points is a product in its own right with a quantity of 250 (child of the initial product with its quantity 1)

    - it is only this product which feeds an analytical account

    - the following steps are the same as the previous assumption


    3 - sale order and stock

    - although there is no need to manage the inventory, we activate and configure the stock features

    - the customer orders a product in quantity 1

    - an equivalence in stock management is made on a storable product of 250 points

    - each action carried out by the customer which triggers consumption creates a new line as a deduction in the inventory management of his capital of points

    - the customer has access to his own stock location to view the balance of his capital of points with his history


    Thank you for taking the time to read, I hope this is clear enough.

    Look forward to your comments and suggestions!

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedin youtube custom-icon twitter

    _______________________________________________
    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 Graeme Gellatly - 03:01 - 14 Mar 2020
  • Re: Your opinion and experience about "Point Bank Management"
    Hi Bruno

    I'm thinking along the line of a register, ie rather like a share register. The register is updated by strategically coded actions and keeps a complete translation/audti trail of all ins and outs. I'm assuming there will also be a financial implication when points are earned, ie they become a liability in the balance sheet, when redeemed they are removed. If a register is used the balance sheet figure can always be reconciled against the register. Additionally, a register will be an easy way to report to the customer. 

    I agree with Dominique in not using analytics - sometimes it just easier and cleaner to use our own model, and it also makes upgrades easier.

    Hope I understood it correctly and it is of some use to you.

    Kind regards

    Jonathan Wilson

    Chief Sales and Innovation Executive

    WilldooIT Pty Ltd





    First Australian Odoo GOLD partner
    2017, 2015 & 2013 Odoo Best Partner Asia/Pacific
    Creators of  Odoo-Pentaho integration project

    "Making growth through technology easy"


    E: jonathan.wilson@willdooit.com

    P: +61 3 9135 1900

    M: +61  4 000 17 444

    Linkedin

    10/435 Williamstown Road

    Port Melbourne VIC 3207

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by Willdoo IT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.




    On Sat, 14 Mar 2020 at 03:33, Bruno Joliveau <bruno.joliveau@numigi.com> wrote:

    Hi Community,


    I am writing to get your point of view or maybe, share on existing modules.


    As part of a new client project, we need to:

    - sell products whose consumption is done at a different rate and volume.

    - the customer must have their consumption history and their balance


    Relatively classic and common so far ;-)


    It is a service activity, but the unit of value is not time. And, a priori, there is no stock management.


    Summary customer process:


    The customer purchases product A (for example $ 100 for 1 quantity)

    In return, the client benefits from a capital of 250 points, for example.

    The customer consumes his points by different actions. These actions are reported by several applications. We can collect those actions and create events in Odoo.

    The customer must be able to know the evolution of his capital of points.


    At this step, several hypothesis considered:


    1 - sale order and analytic

    - addition of a second unit of measurement in SO

    - when the SO is confirmed, this quantity corresponding to the second unit feeds an analytical account

    - for a better reading the analytical lines could take advantage of a new type as they already have with timesheets

    - each action performed by the customer that triggers consumption creates a new line as a deduction in his capital of points

    - the customer has access to his analytical account to view the balance of his capital of points


    2 - sale order and product_pack

    - rather than adding secondary units in the sale order, the customer buys a pack

    - the capital points is a product in its own right with a quantity of 250 (child of the initial product with its quantity 1)

    - it is only this product which feeds an analytical account

    - the following steps are the same as the previous assumption


    3 - sale order and stock

    - although there is no need to manage the inventory, we activate and configure the stock features

    - the customer orders a product in quantity 1

    - an equivalence in stock management is made on a storable product of 250 points

    - each action carried out by the customer which triggers consumption creates a new line as a deduction in the inventory management of his capital of points

    - the customer has access to his own stock location to view the balance of his capital of points with his history


    Thank you for taking the time to read, I hope this is clear enough.

    Look forward to your comments and suggestions!

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedin youtube custom-icon twitter

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Jonathan Wilson - 02:00 - 14 Mar 2020
  • Re: Your opinion and experience about "Point Bank Management"
    Hello,

    this is an interesting topic.

    [1] and [2] I would not use analytic accounts. They have already too many possible uses (departments, budgets, project costing etc..). Beside maintaining a good sync on modifications, and traceability is a nightmare.
    [3] sounds interesting and low code. As the inventory module is now a lot more flexible (editing the quantity is now possible), it seems a better idea - the bad thing, is that is another module to install

    [4] how about simply using a computed field with res.partner, that query sale.order.line, for a special product ? When the client buys something, add a sale order line for qty, and when he uses points, add a line for usage. The balance is calculated on the partner form view ?

    my 2 cents,
    Cheers,

    Dominique KON-SUN-TACK  [Project Manager]
    Odoo Gold Partner, best Odoo Partner 2014 for APAC




    On Sat, 14 Mar 2020 at 00:32, Bruno Joliveau <bruno.joliveau@numigi.com> wrote:

    Hi Community,


    I am writing to get your point of view or maybe, share on existing modules.


    As part of a new client project, we need to:

    - sell products whose consumption is done at a different rate and volume.

    - the customer must have their consumption history and their balance


    Relatively classic and common so far ;-)


    It is a service activity, but the unit of value is not time. And, a priori, there is no stock management.


    Summary customer process:


    The customer purchases product A (for example $ 100 for 1 quantity)

    In return, the client benefits from a capital of 250 points, for example.

    The customer consumes his points by different actions. These actions are reported by several applications. We can collect those actions and create events in Odoo.

    The customer must be able to know the evolution of his capital of points.


    At this step, several hypothesis considered:


    1 - sale order and analytic

    - addition of a second unit of measurement in SO

    - when the SO is confirmed, this quantity corresponding to the second unit feeds an analytical account

    - for a better reading the analytical lines could take advantage of a new type as they already have with timesheets

    - each action performed by the customer that triggers consumption creates a new line as a deduction in his capital of points

    - the customer has access to his analytical account to view the balance of his capital of points


    2 - sale order and product_pack

    - rather than adding secondary units in the sale order, the customer buys a pack

    - the capital points is a product in its own right with a quantity of 250 (child of the initial product with its quantity 1)

    - it is only this product which feeds an analytical account

    - the following steps are the same as the previous assumption


    3 - sale order and stock

    - although there is no need to manage the inventory, we activate and configure the stock features

    - the customer orders a product in quantity 1

    - an equivalence in stock management is made on a storable product of 250 points

    - each action carried out by the customer which triggers consumption creates a new line as a deduction in the inventory management of his capital of points

    - the customer has access to his own stock location to view the balance of his capital of points with his history


    Thank you for taking the time to read, I hope this is clear enough.

    Look forward to your comments and suggestions!

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by dominique.k - 01:41 - 14 Mar 2020
  • Your opinion and experience about "Point Bank Management"

    Hi Community,


    I am writing to get your point of view or maybe, share on existing modules.


    As part of a new client project, we need to:

    - sell products whose consumption is done at a different rate and volume.

    - the customer must have their consumption history and their balance


    Relatively classic and common so far ;-)


    It is a service activity, but the unit of value is not time. And, a priori, there is no stock management.


    Summary customer process:


    The customer purchases product A (for example $ 100 for 1 quantity)

    In return, the client benefits from a capital of 250 points, for example.

    The customer consumes his points by different actions. These actions are reported by several applications. We can collect those actions and create events in Odoo.

    The customer must be able to know the evolution of his capital of points.


    At this step, several hypothesis considered:


    1 - sale order and analytic

    - addition of a second unit of measurement in SO

    - when the SO is confirmed, this quantity corresponding to the second unit feeds an analytical account

    - for a better reading the analytical lines could take advantage of a new type as they already have with timesheets

    - each action performed by the customer that triggers consumption creates a new line as a deduction in his capital of points

    - the customer has access to his analytical account to view the balance of his capital of points


    2 - sale order and product_pack

    - rather than adding secondary units in the sale order, the customer buys a pack

    - the capital points is a product in its own right with a quantity of 250 (child of the initial product with its quantity 1)

    - it is only this product which feeds an analytical account

    - the following steps are the same as the previous assumption


    3 - sale order and stock

    - although there is no need to manage the inventory, we activate and configure the stock features

    - the customer orders a product in quantity 1

    - an equivalence in stock management is made on a storable product of 250 points

    - each action carried out by the customer which triggers consumption creates a new line as a deduction in the inventory management of his capital of points

    - the customer has access to his own stock location to view the balance of his capital of points with his history


    Thank you for taking the time to read, I hope this is clear enough.

    Look forward to your comments and suggestions!

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter

    by Bruno Joliveau - 05:31 - 13 Mar 2020
  • Re: Attachments via S3?
    Seeing this thread and the interest in it we could move one of those modules to OCA.
    Where would it be the best suited?

    Or a new repo like OCA/server-storage ?

    Cheers,
    Yannick Vaucher
    Business Solutions Architect

    Camptocamp SA
    PSE A, CH-1015 Lausanne
    Phone: +41 21 619 10 30
    Office: +41 21 619 10 10


    On Fri, 13 Mar 2020 at 09:21, Mignon, Laurent <laurent.mignon@acsone.eu> wrote:
    No stress @Miku.. just wanted to point out that if we want to make open source sustainable, it's always good to give back the improvements made on the work of others . I know it's not always easy and I don't question at all your commitment into the Opensource values. My comment is meant to be friendly ;-)

    lmignon

    On Fri, Mar 13, 2020 at 9:02 AM Miku Laitinen <miku@avoin.systems> wrote:

    I'd facepalm right now, but we're not supposed to touch our faces :) It's for a different repository and a different module. My bad. I will open a PR today.

    Miku Laitinen

    Teknologiajohtaja / Odoo-arkkitehti / AVOIN.SYSTEMS 

    miku.laitinen@avoin.systems



    Lue tuoreimmat kuulumiset blogistamme!


    Facebook | LinkedIn | Instagram | Twitter 



    On Fri, Mar 13, 2020 at 9:50 AM Miku Laitinen <miku@avoin.systems> wrote:
    Laurent, I could've sworn that I made a pull request but it wasn't accepted because "it was out of scope" of this module. But now I can't find that pull request. If you would accept these changes, I'd be happy to contribute.


    Miku Laitinen

    Teknologiajohtaja / Odoo-arkkitehti / AVOIN.SYSTEMS 

    miku.laitinen@avoin.systems



    Lue tuoreimmat kuulumiset blogistamme!


    Facebook | LinkedIn | Instagram | Twitter 



    On Fri, Mar 13, 2020 at 9:47 AM Mignon, Laurent <laurent.mignon@acsone.eu> wrote:
    Miku,

    Nice to see that you've extended the C2C addon to support Minio. It would be even better to propose these changes back to C2C ;-)

    Kind regards

    lmignon

    On Thu, Mar 12, 2020 at 4:17 PM Miku Laitinen <miku@avoin.systems> wrote:
    Also, if you're interested in a self-hosted solution, we modified Camptocamp's attachment_s3 a bit to work with Miniohttps://github.com/avoinsystems/odoo-cloud-platform/commit/4f4670f28917e482645c66b8c58e92126b4c48c8

    We've been running it in production for over a year now without any issues.

    Miku Laitinen

    Teknologiajohtaja / Odoo-arkkitehti / AVOIN.SYSTEMS 

    miku.laitinen@avoin.systems



    Lue tuoreimmat kuulumiset blogistamme!


    Facebook | LinkedIn | Instagram | Twitter 



    On Thu, Mar 12, 2020 at 5:08 PM Miku Laitinen <miku@avoin.systems> wrote:
    The attached files are stored on the disk by default. I believe they were stored in the database only in OpenERP 7 and before.

    Check out these modules:

    On Thu, Mar 12, 2020 at 5:02 PM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:
    Dear community,
    
    Has anyone seen a module that allows attached files to be stored outside of database?
    
    Kind regards,
    Alexey

    _______________________________________________
    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

    _______________________________________________
    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 Yannick Payot - 12:56 - 13 Mar 2020