Archives
Contributors
-
Re: Access to runbot1, runbot1-2 and runbot1-3
Hello, situation is back to normal. Best regards Alexandre On 31/05/2021 08:24, Alexandre Fayolle wrote: > Hello everyone, > > Our hoster informed me this morning that a network switch fault is > causing an outage on one of the runbot servers of the OCA. I redirected > the web frontend to a different server, but builds on runbot1, runbot1-2 > and runbot1-3 could be unreachable until the equipment is replaced. > > I'm sorry for the inconvenience and will post an update when I get more > information from the hoster. > -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 03:15 - 31 May 2021 -
Access to runbot1, runbot1-2 and runbot1-3
Hello everyone, Our hoster informed me this morning that a network switch fault is causing an outage on one of the runbot servers of the OCA. I redirected the web frontend to a different server, but builds on runbot1, runbot1-2 and runbot1-3 could be unreachable until the equipment is replaced. I'm sorry for the inconvenience and will post an update when I get more information from the hoster. -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 08:25 - 31 May 2021 -
Re: Combined view for view List and view Timeline
I wonder if you could do something real simple like have a stored functional field called planned_or_unplanned_date / planned_unplanned or something. If it is unplanned set the date to something which is viewable on timeline with its own swim lane, otherwise set it to the planned date. So that way you can see it and drag drop. Have an inverse which sets the planned date when moved.On Sun, May 30, 2021 at 4:42 AM Sandip Mangukiya <smangukiya@opensourceintegrators.com> wrote:Hi Pedro, We have put that option on the table as well. Thanks for confirming it as valid :)SANDIP MANGUKIYA
TEAM LEAD MANAGERO: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236 
On Sat, May 29, 2021 at 12:56 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:The view by definition is a single thing. The dashboard suggested by Daniel combines view, but with no interaction between them.The best approach is to expand timeline view for having a placeholder to show the records that doesn't have a value for the field that you are grouping (or you can add an option for setting this field), and present there such records in a different way (not attached to any date component), and allowing to drag and drop. The bad part of this is that you need JS + Odoo JS framework skills for it.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Graeme Gellatly - 11:16 - 29 May 2021 -
Re: Combined view for view List and view Timeline
Hi Pedro, We have put that option on the table as well. Thanks for confirming it as valid :)SANDIP MANGUKIYA
TEAM LEAD MANAGERO: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236 On Sat, May 29, 2021 at 12:56 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:The view by definition is a single thing. The dashboard suggested by Daniel combines view, but with no interaction between them.The best approach is to expand timeline view for having a placeholder to show the records that doesn't have a value for the field that you are grouping (or you can add an option for setting this field), and present there such records in a different way (not attached to any date component), and allowing to drag and drop. The bad part of this is that you need JS + Odoo JS framework skills for it.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Sandip Mangukiya - 06:41 - 29 May 2021 -
Re: Combined view for view List and view Timeline
Thank you, Daniel, I did look at that option and will require work on top of that in order to communicate with each other.On Sat, May 29, 2021, 12:47 AM Daniel Reis <dreis@opensourceintegrators.com> wrote:Hello Sandip, you could try the”board” view, that allows to compose several views in the same page.--drNo dia 29/05/2021, às 00:31, Sandip Mangukiya <smangukiya@opensourceintegrators.com> escreveu:
Hello Contributors,I would like to see if there are any pointers for the below requirements, thanks in advance.In Field Service, we are using the Timeline view (https://github.com/OCA/web/tree/14.0/web_timeline) to schedule field service orders, which is working great.but we need to show view List side by side of the timeline in order to drag and drop from list view to timeline for orders which are not scheduled yet. In order to schedule them faster and giving users more flexibility.I find one paid app web_splitview but has limited features like it doesn't support search function, limited to some views, etc.Have a good weekend!SandipSANDIP MANGUKIYA
TEAM LEAD MANAGERO: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236 _______________________________________________
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 Sandip Mangukiya - 06:35 - 29 May 2021 -
Re: Combined view for view List and view Timeline
The view by definition is a single thing. The dashboard suggested by Daniel combines view, but with no interaction between them.The best approach is to expand timeline view for having a placeholder to show the records that doesn't have a value for the field that you are grouping (or you can add an option for setting this field), and present there such records in a different way (not attached to any date component), and allowing to drag and drop. The bad part of this is that you need JS + Odoo JS framework skills for it.Regards.
by Pedro M. Baeza - 09:55 - 29 May 2021 -
Re: Combined view for view List and view Timeline
Hello Sandip, you could try the”board” view, that allows to compose several views in the same page.--drNo dia 29/05/2021, às 00:31, Sandip Mangukiya <smangukiya@opensourceintegrators.com> escreveu:
Hello Contributors,I would like to see if there are any pointers for the below requirements, thanks in advance.In Field Service, we are using the Timeline view (https://github.com/OCA/web/tree/14.0/web_timeline) to schedule field service orders, which is working great.but we need to show view List side by side of the timeline in order to drag and drop from list view to timeline for orders which are not scheduled yet. In order to schedule them faster and giving users more flexibility.I find one paid app web_splitview but has limited features like it doesn't support search function, limited to some views, etc.Have a good weekend!SandipSANDIP MANGUKIYA
TEAM LEAD MANAGERO: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236 _______________________________________________
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 Reis - 09:46 - 29 May 2021 -
Re: Problem with fiscal year starting on 1 October to 30 September
and Odoo BI Report
Just for the finding record, OCA has a solution which is based on date_range. Which requires to work model by model.On Wed, May 26, 2021 at 10:01 PM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:Dear community,For the fiscal year that starts from October and ending September. So, on the Odoo BI view, we expect to see that 2021 / Q1 means 1 October to 31 December.I think this is not possible in Odoo, as it only use "Date" to interpret the report, right?To achieve the expected result, I can only think of adding fiscalyear_id, and quarter as computed stored field in every models needed, which is very inefficient.Anyone have better way to achieve this?Many thanks,Kitti U._______________________________________________
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 - 05:05 - 29 May 2021 -
Combined view for view List and view Timeline
Hello Contributors,I would like to see if there are any pointers for the below requirements, thanks in advance.In Field Service, we are using the Timeline view (https://github.com/OCA/web/tree/14.0/web_timeline) to schedule field service orders, which is working great.but we need to show view List side by side of the timeline in order to drag and drop from list view to timeline for orders which are not scheduled yet. In order to schedule them faster and giving users more flexibility.I find one paid app web_splitview but has limited features like it doesn't support search function, limited to some views, etc.Have a good weekend!SandipSANDIP MANGUKIYA
TEAM LEAD MANAGERO: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236
by Sandip Mangukiya - 01:30 - 29 May 2021 -
Re: Migration to v14 requirement - readony / invisible
On Sun, Oct 18, 2020 at 4:22 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:so the sentence is correct. It seems the only exception is to get the value from the context (example: `invisible=context.get("key")`).So, are you saying that we can accept dynamic expressions as that one contained in https://github.com/odoo/odoo/blob/d9b794480a5ab7f7d6a1e0d92601eb737175e212/addons/account/views/account_move_views.xml#L413 ?--Alex Comba
Tel (CH): +41 91 210 23 40
by Alex Comba. - 03:35 - 28 May 2021 -
Re: [Compta] Generation des FEC et non assujetti TVA
Hi Mathieu,Alexis De lattre (OCA responsible of l10n_france) worked today on that point (it seems) for v14.Could you review and talk on this PR ? https://github.com/OCA/l10n-france/pull/288kind regards.GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)Site Web | FramaSphere | Facebook
3 Grande rue des Feuillants, 69001 Lyon
Standard : (+33) 09.72.32.33.17Service Informatique : (+33) 09.73.79.64.40Astreinte Informatique : (+33) 06.81.85.61.43Member of the OCA (Odoo Community Association)Le jeu. 27 mai 2021 à 10:26, Mathieu C. <mathieu@matmicro.net> a écrit :Hello,(English below)J'utilise une version Odoo 10, pour une entreprise qui n'est pas assujettie à la TVA, comment générer les Fichiers d'Ecriture Comptable (FEC) ?
Actuellement le systeme oblige à rentrer un numéro de TVA.
Impossible de générer le FEC sans numéro de TVA.
Quelle est la méthode pour y remèdier ?Cordialement
------- (English version)I am using an Odoo 10 version, for a company that is not subject to VAT, how do I generate the Accounting Entry Files (FEC)?
Currently the system requires entering a VAT number.
Cannot generate FEC without VAT number.
What is the method to remedy it?Regards--Mathieu_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Sylvain LE GAL - 11:01 - 28 May 2021 -
Re: [Compta] Generation des FEC et non assujetti TVA
You're right, generating FEC should also work for companies without VAT.I fixed it in this PR on l10n_fr_fec_oca (the OCA "improved" version to generate FEC) for odoo v14.0 :You can backport it to v10, it's very easy.AlexisLe jeu. 27 mai 2021 à 10:26, Mathieu C. <mathieu@matmicro.net> a écrit :Hello,(English below)J'utilise une version Odoo 10, pour une entreprise qui n'est pas assujettie à la TVA, comment générer les Fichiers d'Ecriture Comptable (FEC) ?
Actuellement le systeme oblige à rentrer un numéro de TVA.
Impossible de générer le FEC sans numéro de TVA.
Quelle est la méthode pour y remèdier ?Cordialement
------- (English version)I am using an Odoo 10 version, for a company that is not subject to VAT, how do I generate the Accounting Entry Files (FEC)?
Currently the system requires entering a VAT number.
Cannot generate FEC without VAT number.
What is the method to remedy it?Regards--Mathieu_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Alexis de Lattre - 11:01 - 28 May 2021 -
question about payroll and attendance
Hello, I was wondering if there can be a link between payroll and attendances (hr.attendance) in Odoo ? The payroll module has a link with attendance (work calendar attendences) but not hr.attendences, AFAICT, so it seems weird to not be able to record overtime. But maybe I'm missing something obvious? -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 11:06 - 27 May 2021 -
Problem with fiscal year starting on 1 October to 30 September and
Odoo BI Report
Dear community,For the fiscal year that starts from October and ending September. So, on the Odoo BI view, we expect to see that 2021 / Q1 means 1 October to 31 December.I think this is not possible in Odoo, as it only use "Date" to interpret the report, right?To achieve the expected result, I can only think of adding fiscalyear_id, and quarter as computed stored field in every models needed, which is very inefficient.Anyone have better way to achieve this?Many thanks,Kitti U.
by Kitti Upariphutthiphong - 05:01 - 26 May 2021 -
Re: Discover the OCA priorities for 2021 proposed by the board
Ok, I'm agree with you too.Now, I'm understanding that the documentation project take in account many things, besides Functional/Technical docs, like:- Transversal topics ( queue, connector, connector-odoo2odoo ...) depending the Business Objectives and the Technical requirements, so it depends on the specific implementation. So, maybe some sections with recipes for different Business Cases should be appreciate.- Versioning documentation is another gap, for example ReadTheDocs, like many others, manage versioning/branching/languages... and can be integrated with GitHub easily.I appreciate your answers,El lun, 24 may 2021 a las 11:42, Jairo Llopis (<jairo.llopis@tecnativa.com>) escribió:I agree with Tom.Also, having that /docs folder would make migrations even harder. Would make it very hard to find docs of several modules. Would force us to maintain one docs version per module version.El sáb, 22 may 2021 a las 18:42, Tom (<tom@sunflowerweb.nl>) escribió:I am with you except for 1 thing: I think documentation is central and not tied to specific repositories. Because if you want to make a doc about one topic such as "syncing data" it will involve many repositories: queue, connector, connector-odoo2odoo, server-tools, bank-statement, edi....
The e-learning system is good but it is not so strong in wiki-like editing.
The "Migration" docs and "OCA guidelines" have become powerful docs that are much referred to; i think a central place such as that would be better for the docs, and then organized per each topic. Either on Github Wiki or on Github pages.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--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 Juan Del Castillo Gómez - 02:31 - 24 May 2021 -
Re: v14 accounting changes
I'm not actually using v14, but I've play with it a little bit some time ago and there were some things that IMHO where a loss (between v13 and v14).- Now a payment only impacts the outstanding account (cash and bank journals). So, to see the actual balance of those journals
- you must use statements (I like statements but I don't like to be force to use them on all customers and all journals)
- after the v14 release, odoo add a patch that allows you to select the same journal liquidity account as the outstanding account as a way to bypass the outstanding. If you do so:
- The journal dashboard gives wrong data
- you can't use statements for this journal, and if you decide to use them later you are not going to be able to reconcile any previous payment.
- also, the setup to bypass outstanding is not user friendly
- payment + reconcile later vs paying from reconciliation
- In the previous version, if you pay from a bank statement a bill (black line) or if you create the payment and later reconcile it (blue line) the behaviour was the same, one payment. The only difference was the workflow
- on v14, if you create the payment and reconcile later you will have one payment + one statement journal entry. If you pay from the statement you only have one journal entry
- I don't like it because:
- what odoo is doing is not the same regarding the workflow
- If you pay from statements you don't have a payment so you won't see the payment on your payments lists and also you can't send a receipt/payment
- If we make the payment before we have 2 journal entries (the one from the payment plus the one from the statement) for the same operation. In previous version being one journal entry was clearer for me
That's my quick feeback for v14 reconciliationEl vie, 21 de may. de 2021 a la(s) 12:27, Oleg Kuryan (oleg.kuryan@xpansa.com) escribió:I agree with Pedro. I do not see problem statement in an email. Moreover in all above features I see only pluses that finally started to work properly.--On Fri, 21 May 2021 at 17:42, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:Unless you specify the problems, I don't see such problems in the new "features", except train users on them.If you go to specific things, then the debate can go on. You can do it by topic for not getting a laberintic thread.Regards._______________________________________________
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 | ventor.tech | Building Personalized Inventory and Product Management System
/// mail : oleg.kuryan@xpansa.com
/// phone : +375293358638
/// skype : kuryan.oleg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Juan José Scarafía - 12:45 - 23 May 2021