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 mig l10n it rea #611

Merged
merged 16 commits into from
Oct 22, 2018
Merged

11.0 mig l10n it rea #611

merged 16 commits into from
Oct 22, 2018

Conversation

primes2h
Copy link
Contributor

@primes2h primes2h commented Oct 15, 2018

@primes2h primes2h mentioned this pull request Oct 15, 2018
35 tasks
@eLBati
Copy link
Member

eLBati commented Oct 16, 2018

@primes2h puoi dare un occhio anche a #612 e dirmi cosa ne pensi?

@primes2h primes2h force-pushed the 11.0-mig-l10n_it_rea branch from 06be032 to 358fb50 Compare October 16, 2018 14:21
@primes2h
Copy link
Contributor Author

@primes2h puoi dare un occhio anche a #612 e dirmi cosa ne pensi?

In effetti ci stavo pensando anch'io, mi sembra un'ottima idea.
Ti dirò, forse le informazioni REA meriterebbero anche una scheda a parte, a fianco delle "Informazioni generali" dell'Azienda.
Un'idea potrebbe essere quella di inserirle come sezione dn una scheda "Informazioni CCIAA" più ampia che comprenda i dati della Camera di Commercio.
Però a quel punto sarebbe da rivedere il modulo, a partire dal nome.

@eLBati eLBati mentioned this pull request Oct 18, 2018
primes2h and others added 2 commits October 18, 2018 17:58
ADD REA fields to copany and compute company_registry accordingly
@primes2h primes2h force-pushed the 11.0-mig-l10n_it_rea branch from 358fb50 to 5bfaa09 Compare October 18, 2018 16:27
Copy link
Member

@eLBati eLBati left a comment

Choose a reason for hiding this comment

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

thanks

@eLBati eLBati merged commit db8916d into OCA:11.0 Oct 22, 2018
('LN', 'Not in liquidation')], 'Liquidation State',
related='partner_id.rea_liquidation_state')

@api.onchange(
Copy link
Member

Choose a reason for hiding this comment

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

Changing the related data in the partner does not recompute the company_registry, here the steps:

  1. Fill the data in the company: the company_registry is correctly filled.
  2. Go to the partner bound to the company and change a field.
  3. Go back to the company: company_registry is incorrect (it still has the old computed value)

Maybe a computed field would fix this?

Copy link
Member

Choose a reason for hiding this comment

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

@SimoRubi it can't be a computed field because it must be freely editable for possible non Italian companies

Copy link
Member

Choose a reason for hiding this comment

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

Then maybe the behavior I described should be included in the 'known bugs`

@primes2h primes2h deleted the 11.0-mig-l10n_it_rea branch February 3, 2019 13:40
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.

9 participants