Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[14.0] Migration: l10n_it_split_payment #1959

Closed
wants to merge 36 commits into from

Conversation

Borruso
Copy link
Contributor

@Borruso Borruso commented Nov 20, 2020

Porting del modulo l10n_it_split_payment dalla versione 12.0 alla 14.0

--
Confermo di aver firmato il CLA https://odoo-community.org/page/cla e di aver letto le linee guida su https://odoo-community.org/page/contributing

@Borruso
Copy link
Contributor Author

Borruso commented Nov 20, 2020

Bisogna riscrivere i test. C'è qualcuno che mi può aiutare ??

@Borruso Borruso mentioned this pull request Nov 20, 2020
76 tasks
@Borruso Borruso force-pushed the 14.0-mig-l10n_it_split_payment branch from 9d4377d to fba9faf Compare December 4, 2020 12:04
Copy link
Member

@SimoRubi SimoRubi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grazie della PR!
So che hai problemi con i test, ma runbot ha un altro problema che secondo me si può correggere con quanto ti ho segnalato qui sotto.
Inoltre, Travis si ferma su black ancora prima di eseguirli, puoi correggere così vediamo che problemi riporta Travis per i test?

"name": "Split Payment",
"version": "12.0.1.0.1",
"name": "ITA - Split Payment",
"version": "14.0.1.0.0",
"category": "Localization/Italy",
"summary": "Split Payment",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


amount_sp = fields.Float(
string="Split Payment",
digits=dp.get_precision("Account"),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Riporto il warning di Runbot:

2020-12-04 12:14:55,969 160 WARNING openerp_test odoo.addons.base.models.decimal_precision: Deprecated call to decimal_precision.get_precision(<application>), use digits=<application> instead

Puoi correggere?

@SimoRubi
Copy link
Member

SimoRubi commented Dec 4, 2020

Bisogna riscrivere i test. C'è qualcuno che mi può aiutare ??

Ho fatto Borruso#3 che mette a posto parte dei problemi, ora non ho tempo per fare altre modifiche ma penso non manchi molto

@Borruso Borruso force-pushed the 14.0-mig-l10n_it_split_payment branch 3 times, most recently from 5ea081c to 0ee0be9 Compare December 11, 2020 16:07
@Borruso
Copy link
Contributor Author

Borruso commented Jan 29, 2021

Bisogna riscrivere i test. C'è qualcuno che mi può aiutare ??

Ho fatto Borruso#3 che mette a posto parte dei problemi, ora non ho tempo per fare altre modifiche ma penso non manchi molto

Aggiunto le modifiche ai test che mancavano

Copy link
Member

@SimoRubi SimoRubi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grazie della PR!
Ho fatto review del codice: ci sono un paio di modifiche che non mi sono del tutto chiare e qualche suggerimento.

"date": self.date_invoice,
"debit": self.amount_sp,
"credit": 0,
"date": self.invoice_date or self.invoice_date_due,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Come mai qui e sotto hai aggiunto invoice_date_due?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

modificato e tenuto solo self.invoice_date

{"credit": receivable_line_amount}
)
write_off_line_vals = self._build_debit_line()
write_off_line_vals["move_id"] = self.id
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perché non includerlo direttamente in _build_debit_line?

Mi pare che qui la logica sia cambiata: a quanto vedo prima veniva modificata la riga receivable e veniva creata la riga di write off, ora invece crei solo la riga di write off, come mai?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

non esiste il conto su account.move

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Se ho capito bene le nuove modifiche, ora modifichi la riga receivable (line_client, trovata grazie al conto configurato sul partner) se c'è già la riga di write off, mentre la crei quando manca.
Prima invece la riga di write off veniva creata sempre, in action_move_create; come mai hai dovuto modificarlo? Forse era sbagliato prima?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dato che ora il modulo account.invoice e account.move sono la medesima tabella, le registrazioni contabili vengono create da subito mentre sulla 12 la fattura veniva creata prima e dopo confermata venivano create le registrazioni

def action_post(self):
for move in self:
if move.split_payment:
if move.move_type in ["in_invoice", "in_refund"]:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Puoi usare invece move.is_purchase_document()?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

modificato e utilizzato move.is_purchase_document()

check = False
for line in self.line_ids:
if line.name == _("Split Payment Write Off"):
check = True
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Puoi usare anche for..else, che è fatto proprio per questo caso d'uso: https://docs.python.org/3.6/tutorial/controlflow.html#break-and-continue-statements-and-else-clauses-on-loops.

Se ho capito bene stai cercando se esiste già una debit_line, non sarebbe più sicuro cercarla magari tramite un flag aggiunto alla account.move.line invece che per un confronto di stringhe?

Ad esempio potresti creare un campo account.move.line.is_split_writeoff e settarlo a True solo in _build_debit_line, poi nel for cerchi in base a quel flag, che ne pensi?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

modificato logica dovuto all'unione di accoun.invoice con account.move

@Borruso Borruso force-pushed the 14.0-mig-l10n_it_split_payment branch 2 times, most recently from b544d68 to 74d915c Compare February 5, 2021 15:39
@MarcoCalcagni
Copy link
Contributor

nel fare i test ho trovato alcune cose che non vanno.
facendo una fattura con split payment sia con una riga che con più righe i calcoli e movimenti contabili sono corretti.
se duplico una fattura con split non ricalcola bene gli importi il conto di giro ha valori errati.
se faccio una fattura normale comunque aggiunge una riga del conto scissione di pagamenti a valore 0

@Borruso Borruso force-pushed the 14.0-mig-l10n_it_split_payment branch 2 times, most recently from 83b16c0 to eaa300b Compare February 12, 2021 16:05
Copy link
Contributor

@MarcoCalcagni MarcoCalcagni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested for me is OK it can be merged.

@eLBati go for merge please

@MarcoCalcagni
Copy link
Contributor

@Borruso many thanks for the job done ! :-) 👍

@eLBati
Copy link
Member

eLBati commented Feb 17, 2021

Ci sono dei commenti di @SimoRubi senza risposta apparentemente

@Borruso Borruso requested a review from SimoRubi February 26, 2021 13:35
Copy link
Member

@SimoRubi SimoRubi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ci sono un paio di punti in cui va controllato quello che trovi con filtered, vedi sotto

"debit": self.amount_sp,
"credit": 0,
"date": self.invoice_date,
"date_maturity": self.invoice_date,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Come mai serve aggiungere questo campo?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

posso anche togliere il date_maturity

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Se non serve toglilo grazie, ma come mai l'avevi aggiunto?

write_off_line_vals = self._build_debit_line()
line_sp = self.line_ids.filtered(lambda l: l.is_split_payment)
if line_sp:
dif_price = write_off_line_vals["price_unit"] - line_sp.price_unit
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Se qui line_sp contenesse più record, verrebbe sollevata un'eccezione Expected singleton, puoi aggiungere un controllo? O forse queste operazioni andrebbero fatte per tutte le line_sp?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Solo la riga che creo con la funzione _build_debit_line avrà il campo is_split_payment a True, quindi sarà sempre una sola riga.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

filtered può tornare più record, se deve tornarne solo uno va controllato sollevando un'eccezione o almeno aggiungendo un line_sp[0] da qualche parte per prevenire l'errore che ti ho indicato sopra

== self.partner_id.property_account_receivable_id.id
)
if line_client:
line_client.write({"price_unit": line_client.price_unit - dif_price})
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anche qui, va gestito il caso in cui ci siano più record in line_client, attualmente modificherebbe tutte le righe trovate ma non penso sia corretto.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

qui dovrei fare un controllo

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sei riuscito a fare questo controllo?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

controllo fatto

if line_client:
line_client.write({"price_unit": line_client.price_unit - dif_price})
else:
if self.id:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Come mai hai aggiunto questo controllo? Non ho trovato nulla di simile nel codice pre-migrazione.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Se la fattura è in creazione ma non salvata va in errore perché come id ha idNew

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Credo sia rischioso distinguere così il comportamento tra quando la fattura è in creazione rispetto a quando è già creata perché ci si aspetta che il comportamento sia lo stesso.
Potresti invece togliere il campo move_id dalla riga di write off e assegnarla direttamente al campo self.invoice_line_ids, facendo ad esempio

Suggested change
if self.id:
self.invoice_line_ids = [(0, 0, write_off_line_vals)]

o qualcosa di simile, che ne pensi?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

grazie per il suggerimento

Copy link
Contributor

@MarcoCalcagni MarcoCalcagni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Testato e funzione come dovrebbe

Copy link
Contributor

@andreampiovesana andreampiovesana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@Borruso Borruso force-pushed the 14.0-mig-l10n_it_split_payment branch from eaa300b to f34ac27 Compare April 2, 2021 16:05
@Borruso Borruso requested a review from SimoRubi April 2, 2021 16:05
@TheMule71
Copy link
Contributor

TheMule71 commented Apr 3, 2021

Nell'installare un nuovo db, ho trovato questo problema:

2021-04-03 11:45:37,870 10997 CRITICAL odoo14-oca odoo.service.server: Failed to initialize database `odoo14-oca`. 
Traceback (most recent call last):
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/service/server.py", line 1198, in preload_registries
    registry = Registry.new(dbname, update_module=update_module)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/modules/registry.py", line 89, in new
    odoo.modules.load_modules(registry._db, force_demo, status, update_module)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/modules/loading.py", line 455, in load_modules
    loaded_modules, update_module, models_to_check)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/modules/loading.py", line 348, in load_marked_modules
    perform_checks=perform_checks, models_to_check=models_to_check
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/modules/loading.py", line 198, in load_module_graph
    registry.init_models(cr, model_names, {'module': package.name}, new_install)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/modules/registry.py", line 420, in init_models
    env['base'].flush()
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/models.py", line 5434, in flush
    self.recompute()
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/models.py", line 5893, in recompute
    process(field)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/models.py", line 5877, in process
    field.recompute(recs)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/fields.py", line 1153, in recompute
    self.compute_value(recs)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/fields.py", line 1175, in compute_value
    records._compute_field_value(self)
  File "/home/marco/src/odoo/14/odoo/odoo/addons/mail/models/mail_thread.py", line 410, in _compute_field_value
    return super()._compute_field_value(field)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/models.py", line 4059, in _compute_field_value
    getattr(self, field.compute)()
  File "/home/marco/src/odoo/14/OCA/l10n-italy.odooita/l10n_it_split_payment/models/account.py", line 49, in _compute_amount
    move._compute_split_payments()
  File "/home/marco/src/odoo/14/OCA/l10n-italy.odooita/l10n_it_split_payment/models/account.py", line 111, in _compute_split_payments
    write_off_line_vals = self._build_debit_line()
  File "/home/marco/src/odoo/14/OCA/l10n-italy.odooita/l10n_it_split_payment/models/account.py", line 55, in _build_debit_line
    "Please set 'Split Payment Write-off Account' field in"
odoo.exceptions.UserError: Please set 'Split Payment Write-off Account' field in accounting configuration

non credo sia un problema mio locale...

Edit: ok ho visto adesso il log di runbot. Stesso problema.

@Borruso Borruso force-pushed the 14.0-mig-l10n_it_split_payment branch from f34ac27 to 8b58f61 Compare April 6, 2021 10:04
@Borruso
Copy link
Contributor Author

Borruso commented Apr 6, 2021

Nell'installare un nuovo db, ho trovato questo problema:

2021-04-03 11:45:37,870 10997 CRITICAL odoo14-oca odoo.service.server: Failed to initialize database `odoo14-oca`. 
Traceback (most recent call last):
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/service/server.py", line 1198, in preload_registries
    registry = Registry.new(dbname, update_module=update_module)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/modules/registry.py", line 89, in new
    odoo.modules.load_modules(registry._db, force_demo, status, update_module)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/modules/loading.py", line 455, in load_modules
    loaded_modules, update_module, models_to_check)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/modules/loading.py", line 348, in load_marked_modules
    perform_checks=perform_checks, models_to_check=models_to_check
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/modules/loading.py", line 198, in load_module_graph
    registry.init_models(cr, model_names, {'module': package.name}, new_install)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/modules/registry.py", line 420, in init_models
    env['base'].flush()
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/models.py", line 5434, in flush
    self.recompute()
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/models.py", line 5893, in recompute
    process(field)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/models.py", line 5877, in process
    field.recompute(recs)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/fields.py", line 1153, in recompute
    self.compute_value(recs)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/fields.py", line 1175, in compute_value
    records._compute_field_value(self)
  File "/home/marco/src/odoo/14/odoo/odoo/addons/mail/models/mail_thread.py", line 410, in _compute_field_value
    return super()._compute_field_value(field)
  File "/home/marco/src/odoo/14/odoo/odoo/odoo/models.py", line 4059, in _compute_field_value
    getattr(self, field.compute)()
  File "/home/marco/src/odoo/14/OCA/l10n-italy.odooita/l10n_it_split_payment/models/account.py", line 49, in _compute_amount
    move._compute_split_payments()
  File "/home/marco/src/odoo/14/OCA/l10n-italy.odooita/l10n_it_split_payment/models/account.py", line 111, in _compute_split_payments
    write_off_line_vals = self._build_debit_line()
  File "/home/marco/src/odoo/14/OCA/l10n-italy.odooita/l10n_it_split_payment/models/account.py", line 55, in _build_debit_line
    "Please set 'Split Payment Write-off Account' field in"
odoo.exceptions.UserError: Please set 'Split Payment Write-off Account' field in accounting configuration

non credo sia un problema mio locale...

Edit: ok ho visto adesso il log di runbot. Stesso problema.

Aggiunto controllo se fattura presenta split payment allora esegue le funzioni di split.
@TheMule71 potresti cortesemente rifare review ??

Copy link
Member

@SimoRubi SimoRubi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grazie delle modifiche!

"company_id",
"invoice_date",
"move_type",
)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Decorando il metodo con api.depends rimuovi tutti i campi impostati dal api.depends del metodo nel super, puoi verificarlo durante l'esecuzione guardando self._compute_amount._depends.
Se qui non ti serve aggiungere nuovi campi, puoi evitare del tutto l'aggiunta del decoratore per mantenere i campi del metodo originale, altrimenti temo tu debba riportare quelli del metodo originale (forse si può usare qualche barbatrucco richiamando self._compute_amount._depends) e aggiungere i nuovi campi che ti servono

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

eliminato api.depends

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mi pare ci sia ancora, ma direi che non è una modifica strettamente necessaria per il merge perché ho scoperto che non è necessario ripetere tutti i campi nel depends del metodo nel super grazie a https://github.com/odoo/odoo/blob/b2235e2749504e6eee9e6f8090d1df54cf5971b7/odoo/fields.py#L433

def set_receivable_line_ids(self):
self._recompute_dynamic_lines()
if self.move_type == "out_invoice":
line_client_ids = self.line_ids.filtered(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Qui e nel metodo sotto ripeti due volte praticamente lo stesso codice, riesci a evitare la duplicazione?

Nota che per accedere ad esempio al campo line_client.debit puoi anche usare line_client['debit']

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

evitato la duplicazione

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non mi pare, ma direi che non è una modifica strettamente necessaria per il merge

return vals

def set_receivable_line_ids(self):
self._recompute_dynamic_lines()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Puoi aggiungere qualche riga di documentazione ai nuovi metodi che spieghi cosa fanno?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

aggiunto commento

) / inv_total
else:
receivable_line_amount = 0
line_client.with_context(check_move_validity=False).write(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Questi metodi vengono spesso chiamati anche durante gli onchange, quindi è meglio evitare di chiamare i metodi CRUD come spiegato in https://github.com/odoo/odoo/blob/9b7a4e1815de580575bed6657f9f8915907ce534/odoo/api.py#L162-L171.
Puoi sostituire i vari write con update o semplicemente assegnare il valore ai campi?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sostituito write con update o assegnando il valore

if line_sp:
if (
self.move_type == "out_invoice"
and line_sp.debit != write_off_line_vals["debit"]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

aggiunto [0] al line_sp

@tafaRU
Copy link
Member

tafaRU commented Apr 23, 2021

Sostituita da #2234

@tafaRU tafaRU closed this Apr 23, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Apr 23, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Apr 23, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jun 6, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jun 18, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jun 18, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jul 2, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jul 2, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jul 9, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jul 9, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jul 9, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jul 9, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jul 17, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jul 20, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jul 30, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jul 30, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Aug 6, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Aug 20, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Sep 3, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Sep 17, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Oct 1, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Oct 8, 2021
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Oct 15, 2021
TheMule71 added a commit to TheMule71/l10n-italy that referenced this pull request Jan 21, 2022
TheMule71 added a commit to TheMule71/l10n-italy that referenced this pull request Jan 21, 2022
TheMule71 added a commit to odoo-italia/l10n-italy that referenced this pull request Jun 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.