Hello Carlos,
El 05/12/16 a les 11:15, Carlos Eduardo Sotelo Pinto ha escrit:
What I have said is , there is no a way to manage indetifiers on this way:
- a Code
- a Description name
*CODE| Description *
==================================
* 0 | DOC.TRIB.NO.DOM.SIN.RUC
* 1 | DOC. NACIONAL DE IDENTIDAD
* 4 | CARNET DE EXTRANJERIA
* 6 | REG. UNICO DE CONTRIBUYENTES
* 7 | PASAPORTE
* A | CED. DIPLOMATICA DE IDENTIDAD
If identifiers has no a way to manage identifiers on this way, then
software doesnt work. just that, simple, since repots need that
codification, reports dont need names, reports need the *Code on Reports*
But is no legal having this:
- Many identifiers per party, this screen was observed. I have fixed it
on the implementartion, but on custom modules, anyway, the software
doesnt fill restrictions.
If you need to fill this requirements, you can add the Peruvian VAT as
custom type on the selection, and then add a new field (requied and only
visible for the peruvian Vat) to indicate the type. This new field can
be a many2one to a new model with code and description.
For the identifier uniqueness, you can add a check on identifier that
checks on creation/modification of an identifer that does not exist
another peruvian_vat for the party and raise and error (or maybe a
warning) if it exists.
Hope it helps.
--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk
--
You received this message because you are subscribed to the Google Groups
"tryton" group.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tryton/e4867cc9-822b-2f08-f47f-7dd3bf5d0ad2%40koolpi.com.
