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.

Sign up for GitHub

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

Jump to bottom

l10n_it_fatturapa_in: Il codice fiscale non sembra corretto #3528

Closed
1 of 3 tasks
eLBati opened this issue Aug 18, 2023 · 1 comment · May be fixed by #3996
Closed
1 of 3 tasks

l10n_it_fatturapa_in: Il codice fiscale non sembra corretto #3528

eLBati opened this issue Aug 18, 2023 · 1 comment · May be fixed by #3996
Labels
12.0 14.0 16.0 bug stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@eLBati
Copy link
Member

eLBati commented Aug 18, 2023 •
edited by francesco-ooops
Loading

Module

l10n_it_fatturapa_in

Describe the bug

Ricevendo un XML dove il CodiceFiscale è una P.IVA ma manca Denominazione, il sistema crea un fornitore di tipo "persona" e il controllo sul codice fiscale fallisce

To Reproduce

Affected versions:

Steps to reproduce the behavior:

  1. Ricevere un file tipo https://gist.github.com/eLBati/6eacfe15adb17ef82747d897c53b84f5
  2. Ottenere "Il codice fiscale non sembra corretto"

Expected behavior

Il fornitore viene creato come azienda
@eLBati eLBati added the bug label Aug 18, 2023
@SirTakobi SirTakobi mentioned this issue Aug 18, 2023
Closed
@francesco-ooops francesco-ooops linked a pull request Dec 19, 2023 that will close this issue
[FIX] l10n_it_fatturapa_in: Il codice fiscale non sembra corretto #3529
Closed
@eLBati eLBati mentioned this issue Feb 27, 2024
Open
@francesco-ooops francesco-ooops linked a pull request Feb 27, 2024 that will close this issue
[16.0] [FIX] l10n_it_fatturapa_in: Il codice fiscale non sembra corretto #3996
Open
@github-actions GitHub Actions
Copy link

github-actions bot commented Sep 1, 2024

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Sep 1, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
12.0 14.0 16.0 bug stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Milestone
No milestone
2 participants
@eLBati @francesco-ooops