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

[11.0] l10n_es_aeat_sii: Se comprueba el campo correcto de núm. factura proveedor #1154

Closed
wants to merge 1 commit into from

Conversation

omar7r
Copy link
Contributor

@omar7r omar7r commented Jul 23, 2019

Hola,

Esta comprobación parece que ha quedado sin migrar, ya que ahora el campo que se usa como número de factura de proveedor es "reference" y es el que se está enviando al SII como tal.

@pedrobaeza pedrobaeza added this to the 12.0 milestone Jul 23, 2019
Copy link
Member

@pedrobaeza pedrobaeza left a comment

Choose a reason for hiding this comment

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

Desde luego. ¿Te importaría añadir un test para que no vuelva a pasar?

@pedrobaeza pedrobaeza modified the milestones: 12.0, 10.0, 11.0 Jul 23, 2019
@pedrobaeza
Copy link
Member

Esto se quedó aquí pendiente. ¿Sigue vigente?

@github-actions
Copy link

github-actions bot commented Nov 7, 2021

There hasn't been any activity on this pull request in the past 4 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 PR 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 Nov 7, 2021
@pedrobaeza
Copy link
Member

Esto no se llegó a fusionar, pero sigue siendo necesario, y veo que en todas las versiones posteriores. Como hay conflicto, lo he empujado directamente haciendo cherry-pick en 370a2e3, y ahora haré fw-port a las nuevas versiones (donde cambia el nombre del campo también).

@pedrobaeza pedrobaeza closed this Nov 18, 2021
@pedrobaeza
Copy link
Member

Cherry-pick a:

@HaraldPanten
Copy link
Contributor

Gracias Pedro.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants