Update 303 file with new format

The 303 file was modified so the format is no longer accepted by the tax authority website. Here is the official announce of the change:

https://www.boe.es/buscar/doc.php?id=BOE-A-2018-14901

assigned to @pokoli

added accounting type::feature + 1 deleted label

New review68421002 at https://codereview.tryton.org/68421002/#ps1

How is this working? Should the system need to be able to generate the former format for the past period? Is not there any version system? Is it common to have format changes?

> How is this working?

Since 2019 only the new format can be used to upload the file

> Should the system need to be able to generate the former format for the past period? Is not there any version system?

No, I've tested using the new format for older periods and it works as expected

> Is it common to have format changes?

It's not so common but it may happen

added 1 deleted label and removed 1 deleted label

But how did it happen that a format introduced in Tryton in 2018-10-01 is already invalid 2 months later? How are we going to prevent this from happening in the future?

> But how did it happen that a format introduced in Tryton in 2018-10-01 is already invalid 2 months later?

Because the tax authority published a Modification on 31-10-2018.

> How are we going to prevent this from happening in the future?

I do not think we can do anything to prevent tax authorities from modifying it's file formats. Just keep eyes opens and update them.

Seriously, the authorities have given only 2 months to update all the systems in the country? If this is a frequent risk, we should probably about a way to update those report without the need to provide a new release.

Format changes are frequent, indeed. We (NaN-tic) currently support 4 reports and I'd say that you can expect at least one change per year.

WTF, what is that for a country? Are they doing on purpose to fail the country business?
So we need a proper solution for such screwed behavior, we are not going to change and make release every time some moron in the country decide to make changes.

For me there is no need of a new release. As far as new versions support the new changes older versions templates can be manually updated on the database.

I can propose a change (or upload a new template) for released versions which avoids changing python code.

Is each future evolution would be solvable by just updating the template?
Should not we version the templates?

> Is each future evolution would be solvable by just updating the template?

Well normally the file does not work because new fields are added and the previous template does not set any value for it. This is a fixed size file, so when setting new fields they are normally added at the end. Updating the template sets a fixed value for the previous format so the file will be read correctly after updating it.

> Should not we version the templates?

I do not think it's worth because only the latest file format is accepted by tax authority.

OK so as it is a report using the template engine, I think we could just update the report and avoid having to change the python code. So users from old version can use the new template on their version.

I've implemented msg46181 on latest patchset

review68421002 updated at https://codereview.tryton.org/68421002/#ps20001

New changeset f552c1e2a74a by Sergi Almacellas Abellana in branch 'default':
Update model 303 to new format
https://hg.tryton.org/modules/account_es/rev/f552c1e2a74a

added 1 deleted label and removed 1 deleted label

closed

New changeset ecf29a696deb by Sergi Almacellas Abellana in branch 'default':
Update model 303 to new format
https://hg.tryton.org/tryton-env/rev/ecf29a696deb

mentioned in issue #13652