Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Re: Download Sale Orders from Magento 2.3 to Odoo14
    Simone, thank you for sharing your POV, I see that we are more or less aligned on the point of making our own solution, it's useful to have enforcements/confirmation about this topic from different people, I appreciated the hint about EDI, I will take a loot at it : )

    Oleg Kuryan

    In community you will never find good and well supported connector. This is community, nobody will respond to you for free for bugfixing. You need to fix and contribute yourself. It is very rare case that people will fix your reported bugs. And it is more based on enthusiasm of individual person in case he has free time / desire / good mood :) 

    I disagree with this. At least on the message that carries... but we might have just a "translation" problem, so please take this as a way to help improving this conversation  ;)
    We have plenty of people - me included - that fix bugs for free or that help (w/ reviews, tests, comments, etc).
    Moreover the "fix and contribute yourself" does not mean that you shouldn't do it in the OCA. (at least partially) ;)
    And yeah, that might not be so "common" but I think it comes most of the time from "fear", "shyness" or the feeling that you've just expressed here ;)

    About this point, I think I got both point from Oleg and Simone ; ) We probably all agree that when people work for the money in the context of a company that is supposed to provide a service, it's almost automatic that they will be (or at least do their best to be) as responsive and efficient as they can. 

    BUT that doesn't exclude the fact that sometimes community can be even more responsive and efficient, but you might have to deal with a lot of variables. 

    I think the fact Oleg wants to point out is that when you rely on community you "have to be lucky", while if you rely on a professional company you can litterally claim to have the assistance you need. On the other hand this still doesn't always mean that official assistance is always better than the community service, I think we're just talking about two very different approach that somehow lead in the same way and they have both pro and cons. Very interesting point to discuss : )

    Sorry for the late answer, I was not in Milan unfortunately, I hope I can go to Odoo days next year !

    Privo di virus.www.avast.com

    Il giorno mer 3 mag 2023 alle ore 16:42 Simone Orsi <notifications@odoo-community.org> ha scritto:
    Ciao Francesco,

    Here's my POV:

    1. your scope sounds too small to use connector-magento (that should be migrated, etc) or any other "existing" connector
    2. this does not mean that you cannot create a connector. The connector module proposes a pattern to handle inbound/outbound sync. That's it. I won't exclude this idea a priori.
    3. you mention "receiving and processing XML files and sending out some other files": sounds more like an EDI exchange than a connector -> I encourage you to have a look at the EDI framework.

    I'm going to the Odoo Italia days in Milan: if you come, we can have a chat ;)

    Finally, a few words for Oleg regarding

    Oleg Kuryan

    In community you will never find good and well supported connector. This is community, nobody will respond to you for free for bugfixing. You need to fix and contribute yourself. It is very rare case that people will fix your reported bugs. And it is more based on enthusiasm of individual person in case he has free time / desire / good mood :) 

    I disagree with this. At least on the message that carries... but we might have just a "translation" problem, so please take this as a way to help improving this conversation  ;)
    We have plenty of people - me included - that fix bugs for free or that help (w/ reviews, tests, comments, etc).
    Moreover the "fix and contribute yourself" does not mean that you shouldn't do it in the OCA. (at least partially) ;)
    And yeah, that might not be so "common" but I think it comes most of the time from "fear", "shyness" or the feeling that you've just expressed here ;)
     
    So yes, in your case it is better to develop your own script that you will understand yourself and will support it yourself 
    I know this 100% as we are developing Connectors to e-commerce systems and we know how much time it takes to support them, constantly develop, fix bugs, respond in reasonable time.
    I see your point but there's always the other side of the medal: go always fully this way and you'll always be by yourself. Fully. Forever :)

    My $0.02.

    Bests

    --
    Simone Orsi

    Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

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

    by Francesco Ballerini - 06:30 - 7 May 2023
  • Re: New repository OCA/sign
    Thanks!
    by Pedro M. Baeza - 11:16 - 7 May 2023
  • Re: New repository OCA/sign
    Dear Pedro,

    Sorry for the late reply. The repo is available now.
    I've assigned  it to "Document" PSC for now.

    Bests,
    S

    On Fri, Apr 21, 2023 at 6:17 PM Pedro M. Baeza <notifications@odoo-community.org> wrote:
    We are starting to develop some modules for signing things (for now, Odoo records, ala base_tier_validation, which is also linked, but in the future, PDF documents, etc).


    so I think it would be very good to have a new repository to host them for having them properly placed from the beginning.

    Is that possible?

    Regards.

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



    --
    Simone Orsi

    Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
    by Simone Orsi - 10:25 - 7 May 2023
  • Re: Clear Customer Invoice and Vendor Bills

    Hello Rafael,

     

    Did you develop the module?

     

    Regards,

    Daniel

     

    From: Rafael Blasco <notifications@odoo-community.org>
    Date: Sunday, 2 April 2023 at 1:47 PM
    To: Contributors <contributors@odoo-community.org>
    Subject: RE: Clear Customer Invoice and Vendor Bills

    Thank you Yoshi but as I said Odoo CE has it for journal items in core.

     

    IMHO account_neeting is not needed anymore in v14+ as can be done with “Automatic Entries” for selected Journal Items.

     

    We will develop this UX Easy module for invoicing user in the next 2 weeks 😊

     

    Best regards

    Rafael

     

     

    De: Yoshi Tashiro <notifications@odoo-community.org>
    Enviado el: sábado, 1 de abril de 2023 14:22
    Para: Contributors <contributors@odoo-community.org>
    Asunto: Re: Clear Customer Invoice and Vendor Bills

     

     

    On Sat, Apr 1, 2023 at 9:12 PM Rafael Blasco <notifications@odoo-community.org> wrote:

    Dear Contributors,

     

    I have been looking for a module which help to clear customer invoices with vendor bill from the invoices in the 2 directions.

     

    I look for it in

     

    We will develop a module account_invoice_clearing

     

    From customer invoice o vendor bill you can bottom clear and a wizard will help you to clear with bill or viceversa

    From list same with an action

     

    Actually,  this can be done by accountants really easy from account.move.lines but the module wants to provide this tool for invoicing department.

     

    If any feedback, thank you!

     

    Regards,

    Rafael

     

    MT-2035

     

    _______________________________________________
    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 daniel - 01:55 - 7 May 2023
  • Re: OCA/bank_statement_import - Odoo 16, Switzerland
    Hi Alex and Virginie,

    Thanks for the quick reply and providing the links.

    Kind regards
    Elmar

    Am Mi., 3. Mai 2023 um 11:42 Uhr schrieb Alex Comba <notifications@odoo-community.org>:
    Hi Elmar,

    please have a look at https://github.com/OCA/bank-statement-import/issues/503 where you can find the links to open PRs not yet migrated.

    I hope it helps you.

    Best regards

    On Wed, May 3, 2023 at 11:27 AM Elmar Hardenack <notifications@odoo-community.org> wrote:
    Hi there,

    We are currently upgrading a Swiss customer from Odoo V13 to V16.

    In V13 the customer uses the following modules from the OCA/bank_statement_import Project:

    - account_bank_statement_import_camt_oca
    - acclount_bank_statement_import_oca_camt54

    As far as I checked, based on modules available for V15, we would need:

    1. account_statement_import_camt
    2. account_statement_import_camt54

    and the base modules:
    3. account_stamement_import(_file)
    4. account_statement_import_base

    3. and 4. are available for V16, 1. and 2. are not, yet, as per https://github.com/OCA/bank-statement-import/tree/16.0

    Is there any plan to upgrade 1. and 2., and if so when? Or would you be willing to upgrade them now? Or did they get replaced with other OCA modules or maybe even Odoo standard features I'm not aware of?

    Thanks in advance.

    Kind Regards
    Elmar

    --
    Beste Grüße / Kind Regards
    Elmar Hardenack
    Managing Partner



    Aphora GmbH i.G.
    Represented by: Adam Hussein, Elmar Hardenack

    Rehringhauser Str. 7a | DE-57462 Olpe (HQ)
    Rudolfplatz 3 | DE-50674 Köln

    This message is exclusively intended for its addressee and may contain confidential information that is protected by professional privilege. If you are not the intended recipient, you are hereby notified that any copy, disclosure or dissemination of this communication is strictly prohibited by law. If this message has been received by error, please notify us immediately via e-mail and delete it.

    _______________________________________________
    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



    --
    Beste Grüße / Kind Regards
    Elmar Hardenack
    Managing Partner

    Aphora GmbH i.G.
    Represented by: Adam Hussein, Elmar Hardenack

    Rehringhauser Str. 7a | DE-57462 Olpe (HQ)
    Rudolfplatz 3 | DE-50674 Köln

    This message is exclusively intended for its addressee and may contain confidential information that is protected by professional privilege. If you are not the intended recipient, you are hereby notified that any copy, disclosure or dissemination of this communication is strictly prohibited by law. If this message has been received by error, please notify us immediately via e-mail and delete it.
    by Elmar Hardenack - 06:35 - 4 May 2023
  • Re: OCA/bank_statement_import - Odoo 16, Switzerland
    Hello Elmar,

    We also have customers using the Swiss localization and we want to migrate them from v12 to v16 in the following months (or year, depending on the work to be done).
    Maybe there are other modules that our respective customers use and we could cofinance part of them or split the work in a synchronized way.
    Don't hesitate to contact me directly (virginie@coopiteasy.be).

    By the way both modules you're interested in are here:

    - account_bank_statement_import_camt_oca


    account_bank_statement_import_oca_camt54

    Have a nice day,
    --
    Virginie
    0477/64.17.20

    -----Original Message-----
    Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>
    Subject: Re: OCA/bank_statement_import - Odoo 16, Switzerland
    Date: Wed, 03 May 2023 09:42:26 -0000

    Hi Elmar,

    please have a look at https://github.com/OCA/bank-statement-import/issues/503 where you can find the links to open PRs not yet migrated.

    I hope it helps you.

    Best regards

    On Wed, May 3, 2023 at 11:27 AM Elmar Hardenack <notifications@odoo-community.org> wrote:
    Hi there,

    We are currently upgrading a Swiss customer from Odoo V13 to V16.

    In V13 the customer uses the following modules from the OCA/bank_statement_import Project:

    - account_bank_statement_import_camt_oca
    - acclount_bank_statement_import_oca_camt54

    As far as I checked, based on modules available for V15, we would need:

    1. account_statement_import_camt
    2. account_statement_import_camt54

    and the base modules:
    3. account_stamement_import(_file)
    4. account_statement_import_base

    3. and 4. are available for V16, 1. and 2. are not, yet, as per https://github.com/OCA/bank-statement-import/tree/16.0

    Is there any plan to upgrade 1. and 2., and if so when? Or would you be willing to upgrade them now? Or did they get replaced with other OCA modules or maybe even Odoo standard features I'm not aware of?

    Thanks in advance.

    Kind Regards
    Elmar

    --
    Beste Grüße / Kind Regards
    Elmar Hardenack
    Managing Partner



    Aphora GmbH i.G.
    Represented by: Adam Hussein, Elmar Hardenack

    Rehringhauser Str. 7a | DE-57462 Olpe (HQ)
    Rudolfplatz 3 | DE-50674 Köln

    This message is exclusively intended for its addressee and may contain confidential information that is protected by professional privilege. If you are not the intended recipient, you are hereby notified that any copy, disclosure or dissemination of this communication is strictly prohibited by law. If this message has been received by error, please notify us immediately via e-mail and delete it.

    _______________________________________________
    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 Virginie Dewulf. - 05:01 - 3 May 2023
  • Re: Download Sale Orders from Magento 2.3 to Odoo14
    Ciao Francesco,

    Here's my POV:

    1. your scope sounds too small to use connector-magento (that should be migrated, etc) or any other "existing" connector
    2. this does not mean that you cannot create a connector. The connector module proposes a pattern to handle inbound/outbound sync. That's it. I won't exclude this idea a priori.
    3. you mention "receiving and processing XML files and sending out some other files": sounds more like an EDI exchange than a connector -> I encourage you to have a look at the EDI framework.

    I'm going to the Odoo Italia days in Milan: if you come, we can have a chat ;)

    Finally, a few words for Oleg regarding

    Oleg Kuryan

    In community you will never find good and well supported connector. This is community, nobody will respond to you for free for bugfixing. You need to fix and contribute yourself. It is very rare case that people will fix your reported bugs. And it is more based on enthusiasm of individual person in case he has free time / desire / good mood :) 

    I disagree with this. At least on the message that carries... but we might have just a "translation" problem, so please take this as a way to help improving this conversation  ;)
    We have plenty of people - me included - that fix bugs for free or that help (w/ reviews, tests, comments, etc).
    Moreover the "fix and contribute yourself" does not mean that you shouldn't do it in the OCA. (at least partially) ;)
    And yeah, that might not be so "common" but I think it comes most of the time from "fear", "shyness" or the feeling that you've just expressed here ;)
     
    So yes, in your case it is better to develop your own script that you will understand yourself and will support it yourself 
    I know this 100% as we are developing Connectors to e-commerce systems and we know how much time it takes to support them, constantly develop, fix bugs, respond in reasonable time.
    I see your point but there's always the other side of the medal: go always fully this way and you'll always be by yourself. Fully. Forever :)

    My $0.02.

    Bests

    --
    Simone Orsi

    Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
    by Simone Orsi - 04:40 - 3 May 2023
  • Re: Datev data

    Many thanks Holger Brunn for linking the appropriate PR´s. I´ll have a closer look.

     

    @Thomas Pot: i would appreciate sharing your experience. Even if i am not involved in the dev of the mentioned modules yet…

    I think we can only benefit from it.

    BTW: I am facing this issue now on v16.

     

    I´ll give it a try modifying the odoo functions manually and see, what kind of problems will occur.

    It sounds like, that a corresponding module would be of interest to many users?! 
     

    All the best

    Nils

    -- 

    NICO SOLUTIONS - ENGINEERING & IT 
    Inhaber (Owner): Nils Coenen 
    Dr.-Ruckert-Str.     1G 
    28865 Lilienthal 
    Deutschland (Germany) 
    Ust.-Idnr. (VAT-ID): DE341437044 

     

     

    Von: Thomas Pot <notifications@odoo-community.org>
    Antworten an: "Odoo Community Association (OCA) Contributors" <contributors@odoo-community.org>
    Datum: Mittwoch, 3. Mai 2023 um 14:41
    An: Contributors <contributors@odoo-community.org>
    Betreff: Re: Datev data

     

    Hello All,

     

    We encountered also several issue's in the DATEV export function in Odoo EE. because of the urgent matters at that point we decided to override the default functions in Odoo.

    We reported our issue's to Odoo but as far as I know, there are no actions taken for some.

    It also depends on the used version; v15 is different from V13. (and already better)

     

    But we would be happy to share our experience with the community? 

     

     

    Met vriendelijke groet - Kind Regards - Mit freundlichen Grüßen,

    Thomas Pot

     

    Open2Bizz - dé Odoo specialist

    Mauritslaan 56 | 6161 HW | Geleen

     

    Maak meteen een afspraak voor een online demo van Odoo / Open2Ortho:

    Klik hier

     

    Van: "Holger Brunn" <notifications@odoo-community.org>
    Aan: "Contributors" <contributors@odoo-community.org>
    Onderwerp: Re: Datev data

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

    by Nils Coenen - 03:00 - 3 May 2023
  • Re: Datev data
    Hello All,

    We encountered also several issue's in the DATEV export function in Odoo EE. because of the urgent matters at that point we decided to override the default functions in Odoo.
    We reported our issue's to Odoo but as far as I know, there are no actions taken for some.
    It also depends on the used version; v15 is different from V13. (and already better)

    But we would be happy to share our experience with the community? 


    Met vriendelijke groet - Kind Regards - Mit freundlichen Grüßen,
    Thomas Pot

    Open2Bizz - dé Odoo specialist
    Mauritslaan 56 | 6161 HW | Geleen

    Maak meteen een afspraak voor een online demo van Odoo / Open2Ortho:
    Klik hier

    Van: "Holger Brunn" <notifications@odoo-community.org>
    Aan: "Contributors" <contributors@odoo-community.org>
    Onderwerp: Re: Datev data
    by "Thomas Pot" <thomas@open2bizz.eu> - 02:40 - 3 May 2023
  • Re: Datev data 
    > i know that Thorsten Vocks and Holger Brunn, are currently working the old

> CSV tooling for Datev Back and Forth (in a specific customer project). The

> code is not yet published but if i am not mistaken it will be soon.

you can find both on https://github.com/OCA/l10n-germany/pulls in #118 and #121


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
    by Holger Brunn - 01:25 - 3 May 2023

    1 attachments 1 attachments

    signature.asc
  • Re: Datev data

    Hi Frederick,

    many thanks for your reply.

     

    If there is something in progress for sharing with the OCA… would be great to have a feedback about the status.

     

    I would like to provide input as well on this task. For now, I am not able to say if my dev skills will be sufficient in this case.

    Still learning a lot. Especially in terms of using git in collab. Considering to keep it economic, i decided to ask here first.

     

    I think a contribution by the customer can be achieved. Depending an the budget needed of course.

     

    I will have an eye on OCA/l10n-germany and i will talk to the customer.

     

    If Thorsten Vocks and/or Holger Brunn are willing to provide some infos… that would be great.

     

    And many thanks for the offer of calling you on your mobile. I will fall back on it if necessary.

     

    All the best

    Nils

     

    -- 

    NICO SOLUTIONS - ENGINEERING & IT 
    Inhaber (Owner): Nils Coenen 
    Dr.-Ruckert-Str.     1G 
    28865 Lilienthal 
    Deutschland (Germany) 
    Ust.-Idnr. (VAT-ID): DE341437044 

     

    Von: Frederik Kramer <notifications@odoo-community.org>
    Antworten an: "Odoo Community Association (OCA) Contributors" <contributors@odoo-community.org>
    Datum: Mittwoch, 3. Mai 2023 um 12:52
    An: Contributors <contributors@odoo-community.org>
    Betreff: Re: Datev data

     

    Hi Nils,

    i know that Thorsten Vocks and Holger Brunn, are currently working the old CSV tooling for Datev Back and Forth (in a specific customer project). The code is not yet published but if i am not mistaken it will be soon. So maybe either of those two can comment. Definitely most of your feedback (or better the one of your consultant) is somewhat known already within the group of OCA contributors working on the OCA Datev modul set. If you don't have own development skill but your customer is willing to contribute financially to develop an Open Source solution thats is typically the easiest and fastest way to get contributors attention. If you have further questions or suggestions to make you can always give me a call on my mobile

    Best Frederik

    Am 03.05.23 um 12:27 schrieb Nils Coenen:

    Dear OCA,

    i got an issue from a customer, that uses a very specific accounting chart in germany.

    As they want to perform the accounting on their own before sending it to the acc. Consultant, some adaption seem to be mandatory.

    In order to create smooth convertability between the datev-export provided by odoo and the import in the system of t he accounting consultant, the data needs to be modified. So this is the feedback i got from the consultant about the export data.

     

    • The code number for the account number extension (KNE) needs to start with digit number 4 instead of a 8 digit number. This is not a problem and provided by the Odoo enterprise core export tool.

    • Exported CSV-files needs to be encoded in Windows ANSI

    • Debit/credit indicators are only allowed in capital letters "S" or "H". The standard Odoo export provides small letters

    • EXTF Version 700 instead of 510 is important when recording with empty and modified headings in the header

     

    The export is provided by the modules „l10n_de_datev_reports“ & „l10n_de_reports“

    The encoding can be changed after exporting, same for the capital letters. But to keep it as simple as possible for the customer, it would be great to have this included in the export function. Covering the other way as well would be awesome.

     

    Is anbody aware of a solution, that already provides this kind of modification?

     

    Would be very thankful for some hints concering that topic.

     

    All the best

    Nils

    -- 


    NICO SOLUTIONS - ENGINEERING & IT 
    Inhaber (Owner): Nils Coenen 
    Dr.-Ruckert-Str.     1G 
    28865 Lilienthal 
    Deutschland (Germany) 
    Ust.-Idnr. (VAT-ID): DE341437044 

     

    -- 
    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 Nils Coenen - 01:21 - 3 May 2023
  • Re: Datev data

    Hi Nils,

    i know that Thorsten Vocks and Holger Brunn, are currently working the old CSV tooling for Datev Back and Forth (in a specific customer project). The code is not yet published but if i am not mistaken it will be soon. So maybe either of those two can comment. Definitely most of your feedback (or better the one of your consultant) is somewhat known already within the group of OCA contributors working on the OCA Datev modul set. If you don't have own development skill but your customer is willing to contribute financially to develop an Open Source solution thats is typically the easiest and fastest way to get contributors attention. If you have further questions or suggestions to make you can always give me a call on my mobile

    Best Frederik

    Am 03.05.23 um 12:27 schrieb Nils Coenen:

    Dear OCA,

    i got an issue from a customer, that uses a very specific accounting chart in germany.

    As they want to perform the accounting on their own before sending it to the acc. Consultant, some adaption seem to be mandatory.

    In order to create smooth convertability between the datev-export provided by odoo and the import in the system of t he accounting consultant, the data needs to be modified. So this is the feedback i got from the consultant about the export data.

     

    • The code number for the account number extension (KNE) needs to start with digit number 4 instead of a 8 digit number. This is not a problem and provided by the Odoo enterprise core export tool.
    • Exported CSV-files needs to be encoded in Windows ANSI
    • Debit/credit indicators are only allowed in capital letters "S" or "H". The standard Odoo export provides small letters
    • EXTF Version 700 instead of 510 is important when recording with empty and modified headings in the header

     

    The export is provided by the modules „l10n_de_datev_reports“ & „l10n_de_reports“

    The encoding can be changed after exporting, same for the capital letters. But to keep it as simple as possible for the customer, it would be great to have this included in the export function. Covering the other way as well would be awesome.

     

    Is anbody aware of a solution, that already provides this kind of modification?

     

    Would be very thankful for some hints concering that topic.

     

    All the best

    Nils

    -- 

    NICO SOLUTIONS - ENGINEERING & IT 
    Inhaber (Owner): Nils Coenen 
    Dr.-Ruckert-Str.     1G 
    28865 Lilienthal 
    Deutschland (Germany) 
    Ust.-Idnr. (VAT-ID): DE341437044 

     

    _______________________________________________
    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 - 12:51 - 3 May 2023
  • Datev data

    Dear OCA,

    i got an issue from a customer, that uses a very specific accounting chart in germany.

    As they want to perform the accounting on their own before sending it to the acc. Consultant, some adaption seem to be mandatory.

    In order to create smooth convertability between the datev-export provided by odoo and the import in the system of t he accounting consultant, the data needs to be modified. So this is the feedback i got from the consultant about the export data.

     

    • The code number for the account number extension (KNE) needs to start with digit number 4 instead of a 8 digit number. This is not a problem and provided by the Odoo enterprise core export tool.

    • Exported CSV-files needs to be encoded in Windows ANSI

    • Debit/credit indicators are only allowed in capital letters "S" or "H". The standard Odoo export provides small letters

    • EXTF Version 700 instead of 510 is important when recording with empty and modified headings in the header

     

    The export is provided by the modules „l10n_de_datev_reports“ & „l10n_de_reports“

    The encoding can be changed after exporting, same for the capital letters. But to keep it as simple as possible for the customer, it would be great to have this included in the export function. Covering the other way as well would be awesome.

     

    Is anbody aware of a solution, that already provides this kind of modification?

     

    Would be very thankful for some hints concering that topic.

     

    All the best

    Nils

    -- 

    NICO SOLUTIONS - ENGINEERING & IT 
    Inhaber (Owner): Nils Coenen 
    Dr.-Ruckert-Str.     1G 
    28865 Lilienthal 
    Deutschland (Germany) 
    Ust.-Idnr. (VAT-ID): DE341437044 

     

    by Nils Coenen - 12:26 - 3 May 2023
  • Re: OCA/bank_statement_import - Odoo 16, Switzerland
    Hi Elmar,

    please have a look at https://github.com/OCA/bank-statement-import/issues/503 where you can find the links to open PRs not yet migrated.

    I hope it helps you.

    Best regards

    On Wed, May 3, 2023 at 11:27 AM Elmar Hardenack <notifications@odoo-community.org> wrote:
    Hi there,

    We are currently upgrading a Swiss customer from Odoo V13 to V16.

    In V13 the customer uses the following modules from the OCA/bank_statement_import Project:

    - account_bank_statement_import_camt_oca
    - acclount_bank_statement_import_oca_camt54

    As far as I checked, based on modules available for V15, we would need:

    1. account_statement_import_camt
    2. account_statement_import_camt54

    and the base modules:
    3. account_stamement_import(_file)
    4. account_statement_import_base

    3. and 4. are available for V16, 1. and 2. are not, yet, as per https://github.com/OCA/bank-statement-import/tree/16.0

    Is there any plan to upgrade 1. and 2., and if so when? Or would you be willing to upgrade them now? Or did they get replaced with other OCA modules or maybe even Odoo standard features I'm not aware of?

    Thanks in advance.

    Kind Regards
    Elmar

    --
    Beste Grüße / Kind Regards
    Elmar Hardenack
    Managing Partner



    Aphora GmbH i.G.
    Represented by: Adam Hussein, Elmar Hardenack

    Rehringhauser Str. 7a | DE-57462 Olpe (HQ)
    Rudolfplatz 3 | DE-50674 Köln

    This message is exclusively intended for its addressee and may contain confidential information that is protected by professional privilege. If you are not the intended recipient, you are hereby notified that any copy, disclosure or dissemination of this communication is strictly prohibited by law. If this message has been received by error, please notify us immediately via e-mail and delete it.

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



    --
    by Alex Comba. - 11:41 - 3 May 2023
  • OCA/bank_statement_import - Odoo 16, Switzerland
    Hi there,

    We are currently upgrading a Swiss customer from Odoo V13 to V16.

    In V13 the customer uses the following modules from the OCA/bank_statement_import Project:

    - account_bank_statement_import_camt_oca
    - acclount_bank_statement_import_oca_camt54

    As far as I checked, based on modules available for V15, we would need:

    1. account_statement_import_camt
    2. account_statement_import_camt54

    and the base modules:
    3. account_stamement_import(_file)
    4. account_statement_import_base

    3. and 4. are available for V16, 1. and 2. are not, yet, as per https://github.com/OCA/bank-statement-import/tree/16.0

    Is there any plan to upgrade 1. and 2., and if so when? Or would you be willing to upgrade them now? Or did they get replaced with other OCA modules or maybe even Odoo standard features I'm not aware of?

    Thanks in advance.

    Kind Regards
    Elmar

    --
    Beste Grüße / Kind Regards
    Elmar Hardenack
    Managing Partner



    Aphora GmbH i.G.
    Represented by: Adam Hussein, Elmar Hardenack

    Rehringhauser Str. 7a | DE-57462 Olpe (HQ)
    Rudolfplatz 3 | DE-50674 Köln

    This message is exclusively intended for its addressee and may contain confidential information that is protected by professional privilege. If you are not the intended recipient, you are hereby notified that any copy, disclosure or dissemination of this communication is strictly prohibited by law. If this message has been received by error, please notify us immediately via e-mail and delete it.
    by Elmar Hardenack - 11:26 - 3 May 2023
  • Re: suggestion for monitoring error 500
    Hi Dominique

    If you have Odoo running behind NGINX, you can parse the access log file to get some statistics about the timestamps around which this occurs, and on which urls. I have a way of doing that with command line tools such as "awk", "sort" and "uniq" (for hourly statistics), but regular "grep" can also yield you the info.

    Armed with that knowledge you can then check the Odoo log file around those times, sometimes it will also display "Internal error" or even a useful traceback, and you can then use "grep" again to extract relevant patterns over the course of a day or so.

    If not enough information is given, then you could resort to modifying the Odoo source code to add some more exception-catching.

    1 mei 2023 06:57:22 Holger Brunn <notifications@odoo-community.org>:

    > It is a bit of a catchall... Would anybody have any suggestion, to monitor

> such error, and possibly get an email, or a warning as a system

> administrator? Is there a way to catch at odoo level, if there is such

> error and send an email ?

all requests go through
https://github.com/OCA/OCB/blob/16.0/odoo/addons/base/models/ir_http.py#L153
so that seems the best place to catch your exception


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.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 Tom Blauwendraat - 05:56 - 1 May 2023
  • RE: suggestion for monitoring error 500

    Hi Dominique,

    I normally use the try … except like below:

     


    try:

     

    except Exception as e:

        mail_smtp_server = self.env["ir.mail_server"].sudo().search([], limit=1)

        email_vals = {"state": "outgoing" ,

            "subject": str(self.env.cr.dbname) + " Error in demo 1 controller  " ,

            "body_html": """Error in demo 1 controller  :  """ + str(e.message) + " " + str(e.args) ,

            "auto_delete": True,

            "email_from": mail_smtp_server.smtp_user ,

            "email_to": madeb@regious.co.zw ,

            }

        self.env["mail.mail"].create(email_vals)

     

     

    Regards,

     

    Bill Made

    +263 733 419 060

     

     

     

    From: Dominique k <notifications@odoo-community.org>
    Sent: Monday, May 1, 2023 7:29 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: suggestion for monitoring error 500

     

    Hi,

     

    We have a case where odoo is used as an e-commerce + portal system (with quite a lot of customisation).

    Times to times, the end user (e-commerce customer) will receive an error 500.

     

    It is a bit of a catchall... Would anybody have any suggestion, to monitor such error, and possibly get an email, or a warning as a system administrator? Is there a way to catch at odoo level, if there is such error and send an email ?

    Or could we "monitor" the log file ? <-- any suggestion on possible tool ?

     

    Thanks,

    Dominique

    by Bill Made - 08:51 - 1 May 2023
  • Re: Download Sale Orders from Magento 2.3 to Odoo14
    Francesco,

    Yes, demo is on Enterprise but our connectors of course working on Community Edition. 

    About library to use. Magento has simple rest api. So we investigated available libs. But as result created our own simple one class wrapper. It is very easy. Just we didn’t want to be limited with some library. We faced this with some other libraries for other e-commerce systems because as result we had not only develop our own connector, but also make fixes to library.


    On Sun, 30 Apr 2023 at 19:36, Francesco Ballerini <notifications@odoo-community.org> wrote:


    Romualdo Briosos Jrsab 29 apr, 20:12 (22 ore fa)
    In your situation, I would recommend developing a Python program that can connect to both the Magento API and Odoo API. This would give you greater control over

     

    Oleg Kuryan

    In community you will never find good and well supported connector. This is community, nobody will respond to you for free for bugfixing. You need to fix and contribute yourself. It is very rare case that people will fix your reported bugs. And it is more based on enthusiasm of individual person in case he has free time / desire / good mood :) 
    So yes, in your case it is better to develop your own script that you will understand yourself and will support it yourself 
    I know this 100% as we are developing Connectors to e-commerce systems and we know how much time it takes to support them, constantly develop, fix bugs, respond in reasonable time. 

    Thanks for your feedbacks, it really helps in the decision process! 

    It is very likely that we will proceed this way:

    1) we will make a temporary implementation of the old workflow as I described in the first message for 2 reasons
       - it's more "cluncky" but it's (at least for me) faster to develope and requires less code updates in the future
       - this would also allow us to have a low-level fallback import system, which we can use if "something breaks" after an update 

    2) one day not too far, is very likely that we will implement our own API as you both suggested. About this I'd like to ask if you have specific libraries to recommend, I see there are different libraries and I think this one might be a good point to start https://pypi.org/project/magento/, but I'm not sure about version compatibility. 
    It would be great to know your recommendations about libraries, if you'd like to share any.

    Thanks for the video suggestion Oleg, I have almost finished it, I see the connector Demo is on Odoo Enterprise but VentorTech solutions can also be found for Odoo Community is it correct?

    Thanks,
    Francesco B.


    Privo di virus.www.avast.com

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

    --
    ///

    Best Regards,
    Oleg Kuryan

    CEO & COO, VentorTech OÜ |     Building Personalized Inventory and Product Management Systems

    | ph PL: +48 573 992 456
    | skype: kuryan.oleg
    by "Oleg Kuryan" <oleg@ventor.tech> - 08:16 - 1 May 2023
  • Re: suggestion for monitoring error 500 
    > It is a bit of a catchall... Would anybody have any suggestion, to monitor

> such error, and possibly get an email, or a warning as a system

> administrator? Is there a way to catch at odoo level, if there is such

> error and send an email ?

all requests go through
https://github.com/OCA/OCB/blob/16.0/odoo/addons/base/models/ir_http.py#L153
so that seems the best place to catch your exception


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
    by Holger Brunn - 07:56 - 1 May 2023

    1 attachments 1 attachments

    signature.asc
  • suggestion for monitoring error 500
    Hi,

    We have a case where odoo is used as an e-commerce + portal system (with quite a lot of customisation).
    Times to times, the end user (e-commerce customer) will receive an error 500.

    It is a bit of a catchall... Would anybody have any suggestion, to monitor such error, and possibly get an email, or a warning as a system administrator? Is there a way to catch at odoo level, if there is such error and send an email ?
    Or could we "monitor" the log file ? <-- any suggestion on possible tool ?

    Thanks,
    Dominique
    by dominique.k - 07:21 - 1 May 2023