Saravanan666/pypi-org huggingface dataset:
Package: odoo-addon-base-time-window
This module provides base classes and models to manage time windows throughtime.window.mixin.Table of contentsUsageKnown issues / RoadmapBug TrackerCreditsAuthorsContributorsOther creditsMaintainersUsageExample implementation for the mixin can be found in moduletest_base_time_window.As a time window will always be linked to a related model thourgh a M2o relation,
when defining the new model inheriting the mixin, one should pay attention to the
following points in order to have the overlapping check work properly:Define class property_overlap_check_field: This must state the M2o field to
use for the to check of overlapping time window records linked to a specific
record of the related model.Add the M2o field to the related model in theapi.constrains:For example:classPartnerTimeWindow(models.Model):_name='partner.time.window'_inherit='time.window.mixin'partner_id=fields.Many2one(res.partner', required=True, index=True, ondelete='cascade')_overlap_check_field='partner_id'@api.constrains('partner_id')defcheck_window_no_overlaps(self):returnsuper().check_window_no_overlaps()Known issues / RoadmapStoring times usingfloat_timewidget requires extra processing to ensure
computations are done in the right timezone, because the value is not stored
as UTC in the database, and must therefore be related to atzfield.float_timein this sense should only be used for durations and not for a
“point in time” as this is always needs a Date for a timezone conversion to
be done properly. (Because a conversion from UTC to e.g. Europe/Brussels won’t
give the same result in winter or summer because of Daylight Saving Time).Therefore the right move would be to use aresource.calendarto define time
windows using Datetime with recurrences.Bug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsACSONE SA/NVCamptocampContributorsLaurent Mignon <laurent.mignon@acsone.eu>Akim Juillerat <akim.juillerat@camptocamp.com>TrobzDung Tran <dungtd@trobz.com>Other creditsThe development of this module has been financially supported by:CamptocampMaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.This module is part of theOCA/server-toolsproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-base-transaction-id
Adds transaction ID to invoice and sale models and views.On Sales order, you can specify the transaction ID used for the payment and it
will be propagated to the invoice (even if made from packing).
This is mostly used for e-commerce handling.You can then add a mapping on that SO field to save the e-commerce financial
Transaction ID into the Odoo sale order field.The main purpose is to ease the reconciliation process and be able to find the partner
when importing the bank statement.Table of contentsBug TrackerCreditsAuthorsContributorsOther creditsMaintainersBug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsCamptocampContributorsYannick Vaucher <yannick.vaucher@camptocamp.com>Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com>Alexandre Fayolle <alexandre.fayolle@camptocamp.com>Guewen Baconnier <guewen.baconnier@camptocamp.com>Lorenzo Battistini <lorenzo.battistini@agilebg.com>Iryna Vyshnevska <i.vyshnevska@mobilunity.com>Mykhailo Panarin <m.panarin@mobilunity.com>Simone Rubino <simone.rubino@agilebg.com>Trobz:Dzung Tran <dungtd@trobz.com>Other creditsThe migration of this module from 14.0 to 16.0 was financially supported by CamptocampMaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.This module is part of theOCA/account-reconcileproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-base-translation-field-label
This addon adds the field label on translated terms. Each translated term is
referencing an Odoo field, but the name stated there is not human readable at all,
instead, the field description is shown and the Translated field is hidden at first,
but it can be showed if needed.Table of contentsConfigurationBug TrackerCreditsAuthorsContributorsMaintainersConfigurationSimply install the module, to access the Settings > Translations > Application Terms
> Translated Terms menu you need to have the Developer Mode enabled.Bug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsForgeFlowContributorsForgeFlow S.L.:Guillem Casassas <guillem.casassas@forgeflow.com>MaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.Currentmaintainer:This module is part of theOCA/server-toolsproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-base-ubl
This is the base module for the implementation of theUniversal Business
Language (UBL)standard.  The UBL standard became theISO/IEC 19845standard in January 2016 (cf theofficial announce).This module contains methods to generate and parse UBL files. This module
doesn’t do anything useful by itself, but it is used by several other modules:purchase_order_ublthat generate UBL purchase orders,sale_order_import_ublthat imports UBL sale orders.account_invoice_import_ublthat imports UBL invoices,Table of contentsBug TrackerCreditsAuthorsContributorsOther creditsMaintainersBug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsAkretionOnesteinContributorsAlexis de Lattre <alexis.delattre@akretion.com>Andrea Stirpe <a.stirpe@onestein.nl>Jacques-Etienne Baudoux <je@bcim.be>Phuc (Tran Thanh) <phuc@trobz.com>Simone Orsi <simone.orsi@camptocamp.com>Other creditsThe development of this module has been financially supported by:CamptocampMaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-base-unece
This module adds the technical basis for the use of the code lists
standardized by theUnited Nations Economic Commission for Europe(which has 56 members states in Europe, America and Central Asia, cfWikipedia.
These code lists are sometimes called UNCL (United Nations Code List). UNECE
has standardized code lists for many different things: units of measure,
payment means, modes of transport, packaging, taxes, etc….Table of contentsConfigurationBug TrackerCreditsAuthorsContributorsMaintainersConfigurationThe configuration takes place in the menuSettings > Technical > Parameters > UNECE Code Lists.Bug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsAkretionContributorsAlexis de Lattre <alexis.delattre@akretion.com>Levent KarakaşPedro M. BaezaAndrea StirpeMaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.Currentmaintainers:This module is part of theOCA/community-data-filesproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-base-user-locale
This module allows overriding following settings for user or company:Time formatDate formatFirst day of the weekDecimal SeparatorThousands SeparatorTable of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageTo configure it at company level go toSettings / General Settingsand search
the sectionLocale.To configure it at user level go to your user preferences.Bug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsCorporateHubContributorsCorporateHubAlexey Pelykh <alexey.pelykh@corphub.eu>Miquel Raïch <miquel.raich@forgeflow.com>Lois Rilo <lois.rilo@forgeflow.com>MaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.This module is part of theOCA/server-uxproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-base-user-role
This module was written to extend the standard functionality regarding
users and groups management. It helps creating well-defined user roles
and associating them to users.It can become very hard to maintain a large number of user profiles over
time, juggling with many technical groups. For this purpose, this module
will help you to:define functional roles by aggregating low-level groups,set user accounts with the predefined roles (roles are
cumulative),update groups of all relevant user accounts (all at once),ensure that user accounts will have the groups defined in their
roles (nothing more, nothing less). In other words, you can not
set groups manually on a user as long as there is roles configured
on it,activate/deactivate roles depending on the date (useful to plan
holidays, etc)get a quick overview of roles and the related user accounts.That way you make clear the different responsabilities within a company,
and are able to add and update user accounts in a scalable and reliable
way.Table of contentsConfigurationUsageBug TrackerCreditsAuthorsContributorsOther creditsMaintainersConfigurationTo configure this module, you need to go toSettings / Users / Roles,
and create a new role. From there, you can add groups to compose your
role, and then associate users to it.You can also define default roles for a new user by editing the user
called “Default User”.Roles:Add groups:Add users (with dates or not):Instead of creating roles from scratch, it is possible to create a role
based on the groups of an existing user: select or open the user and
choose “Create role from user” in the action menu.UsageTo use this module, you need to:Go to Configuration / Users / Users choose user and set Roles:Bug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsABF OSIELLContributorsSébastien Alix <sebastien.alix@camptocamp.com>Duc, Dao Dong <duc.dd@komit-consulting.com>
(https://komit-consulting.com)Jean-Charles Drubay <jc@komit-consulting.com>
(https://komit-consulting.com)Alan Ramos <alan.ramos@jarsa.com.mx> (https://www.jarsa.com.mx)Harald Panten <harald.panten@sygel.es>Kevin Khao <kevin.khao@akretion.com>Tatiana Deribina <tatiana.deribina@sprintit.fi> (https://sprintit.fi)Guillem Casassas <guillem.casassas@forgeflow.com>Guillaume Pothier <gpothier@caligrafix.cl>Do not contact contributors directly about support or help with
technical issues.Other creditsImagesOxygen Team:Icon(LGPL)MaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.Currentmaintainers:This module is part of theOCA/server-backendproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-base-user-role-company
Enable User Roles depending on the Companies selected.A company specific Role will only be enabled
if it is set forallthe currently selected companies.For example, if a user is “Sales Manager” only for Company A,
it will see that role enabled only if Company A is selected.
If the user selects Company A and Company B,
then the “Sales Manager” role won’t be enabled.Table of contentsConfigurationUsageBug TrackerCreditsAuthorsContributorsMaintainersConfigurationRoles are set on the User form.The “Company” additional column allows to set a Role as only valid for specific companies.There is also a “Active Role” techincal field, only visible in developer mode.
It shows what roles are active, after applying the company selection rules.UsageSelect the active companies from the web client widget, near the top right corner.
When doing so, the User’s security Groups are recomputed, based on the Roles.When the user changes the company selection, only the groups available to all active companies will be activated.For example:A “SALES PERSON” and a “SALES MANAGER” roles are created.A user is assigned to the roles:“SALES PERSON”, with no specific company assigned (meaning all)“SALES MANAGER” only to “My Company (Chicago)”When selecting active companies from the UI widget:If only “My Company (San Francisco)” is active, “SALES PERSON” will be active.If only “My Company (Chicago)” is active, “SALES PERSON” and “SALES MANAGER” will be active.If both “My Company (San Francisco)” and “My Company (Chicago)” is active, “SALES PERSON” will be active.Bug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsOpen Source IntegratorsContributorsOpen Source IntegratorsDaniel Reis <dreis@opensourceintegrators.com>Chandresh Thakkar <cthakkr@opensourceintegrators.com>Urvisha Desai <udesai@opensourceintegrators.com>MaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.This module is part of theOCA/server-backendproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-base-user-role-history
This addon provides history for roles modifications on users.
Each time a role is added/updated/unlinked on a user, a new role history line
is created mentioning what changes were made and who made them.
Theses informations are directly accessible from users via a smart button.Table of contentsUsageKnown issues / RoadmapBug TrackerCreditsAuthorsContributorsMaintainersUsageChanges on user roles are easily accessible via a button on user form view.Known issues / RoadmapSince roles on role history line have ‘cascade’ ondelete, role deletion leads
to role history line deletion. In order to keep history even in the case of
a role deletion, module could be upgraded.Bug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsACSONE SA/NVContributorsBenoit Aimont <benoit.aimont@acsone.eu> (https://acsone.eu)Thomas Binsfeld <thomas.binsfeld@acsone.eu> (https://acsone.eu)MaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.Currentmaintainer:This module is part of theOCA/server-backendproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-base-user-show-email
In recent Odoo versions, the login field is tightly linked to the email field
(the field is displayed with an “Email” label, and it will populate the email of the user if it contains an “@” character).Yet for the users who uses a distinct login and email, this is confusing.The goal of this module is to untangle (a bit) these two fields. Here are the changes:In theres.usersform view:Display a “Login” label instead of “Email” on theloginfieldShow the currently invisibleemailfield and its labelIn theres.userstree view:Display theemailfield next to theloginfieldChange the login layout to prompt for a “Login” instead of an “Email” (compatible with the web_enterprise layout)Table of contentsBug TrackerCreditsAuthorsContributorsMaintainersBug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsCamptocampContributorsPatrick Tombez <patrick.tombez@camptocamp.com>MaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.This module is part of theOCA/server-authproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-base-user-signature
This module provides a new field on users to store the user’s digital signatureTable of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageGo toSettings > Users > Users.Open one of the existing users.You can set a digital signature for it on the field “Signature”.Bug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsCamptocampContributorsJay Vora <jay.vora@serpentcs.com>Lorenzo Battistini <lorenzo.battistini@agilebg.com>Pedro M. Baeza <pedro.baeza@gmail.com>Vicent Cubells <vicent@vcubells.net>Mayank Gosai <mgosai@opensourceintegrators.com>Maxime Chambreuil <mchambreuil@opensourceintegrators.com>Italo LOPES <contact@ilopes.me>MaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.Currentmaintainer:This module is part of theOCA/socialproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-base-vat-optional-vies
This module extends base_vat module features allowing to know if VIES
validation was passed or not.Then you can use “VIES validation passed” field in order to show VAT ID with
or without country preffix in invoices, for instance.NOTE: Although VIES validation is set in your company, this validation
will not block VAT ID write (main difference to Odoo standard behavior) if this
VAT ID is valid in its country.Table of contentsConfigurationUsageBug TrackerCreditsAuthorsContributorsMaintainersConfigurationIn order to activate VIES validation, you must set this option in Settings:
Settings > Account > Verify VAT NumbersUsageWhen VIES VAT Check is activated:Odoo will try to validate VAT against VIES online serviceIf passed, then “VIES validation passed” field will be TrueIf not passed, then try to validate using country validation methodIf validated, then “VIES validation passed” field will be FalseIf not validated, then a ValidationError will be shown to userWhen VIES VAT Check is not activated:“VIES validation passed” field will be always FalseYou must prefix VAT with country code (ISO 3166-1 alpha-2) and if you want to
bypass country validation you can use “EU” codeBug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsTecnativaContributorsRafael Blasco <rblasco@moduon.team>Antonio Espinosa <antonio.espinosa@tecnativa.com>Sergio Teruel <sergio.teruel@tecnativa.com>David Vidal <david.vidal@tecnativa.com>Rodrigo Bonilla <rodrigo.bonilla@factorlibre.com>Alexandre Díaz <alexandre.diaz@tecnativa.com>Harald Panten <harald.panten@sygel.es>Eduardo de Miguel <edu@moduon.team>Emilio Pascual <emilio@moduon.team>MaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.This module is part of theOCA/account-financial-toolsproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-base-view-inheritance-extension
This module was written to make it simple to add custom operators for
view inheritance.Table of contentsUsageKnown issues / RoadmapBug TrackerCreditsAuthorsContributorsMaintainersUsageChange a python dictionary (context for example)<fieldposition="attributes"><attributename="context"operation="update">{"key":"value",}</attribute></field>Note that views are subject to evaluation of xmlids anyways, so if you
need to refer to some xmlid, say%(xmlid)s.Add text after and/or before than original<attributename="$attribute"operation="text_add">$text_before{old_value}$text_after</attribute>Add domain with AND/OR join operator (AND if missed) allowing
conditional changes<attributename="$attribute"operation="domain_add"condition="$field_condition"join_operator="OR">$domain_to_add</attribute>Known issues / RoadmapSupport anevalattribute for our new node types.Bug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsTherp BVContributorsHolger Brunn <hbrunn@therp.nl>Ronald Portier <rportier@therp.nl>Tecnativa:Sergio TeruelCarlos DaudenIván Todorovich <ivan.todorovich@camptocamp.com>MaintainersThis module is maintained by the OCA.OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.This module is part of theOCA/server-toolsproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.