On 20 de juny de 2017 17.01.24 CEST, Maxime Richez
wrote:
>
>
>>
>> I agree with Cedric here. Specially if you want to use it on a
>domain. Let
>> me explain:
>>
>> If you store it on the configuration, changing the value on the
>> configuration may invalidate all the existing records domain
>
>
> No, any field can be stored on configuration but usually it is a
> Property/MultiValue because it depends on the company.
>
> Ok, i didn't know , as you said, in the code, it's usually
Property/Multivalue...
--
You received this message because you are subscribed to the Google Groups
>
> I agree with Cedric here. Specially if you want to use it on a domain. Let
> me explain:
>
> If you store it on the configuration, changing the value on the
> configuration may invalidate all the existing records domain. Creating a
> static category with xml records will prevent it.
>
>
On 2017-06-20 07:47, Maxime Richez wrote:
>
>
> >
> > Why using a Property field?
> >
> > The only way to store a value in configuration, no ? And it allows to
> choose an existing product category.
No, any field can be stored on configuration but usually it is a
Property/MultiValue because it
On 20 de juny de 2017 16.23.57 CEST, "Cédric Krier"
wrote:
>On 2017-06-20 06:20, Maxime Richez wrote:
>> Hi,
>>
>> Here's my small problem in Tryton 4.2, i want to filter products on a
>
>> specific product category. I define those category as a property in a
>
>> configuration.
>
>Why using a
>
> Why using a Property field?
>
> The only way to store a value in configuration, no ? And it allows to
choose an existing product category.
> Only field of a model can be evaluated by PYSON.
> There is the PYSON.Id but it will require that you create the category
> in XML.
>
I'll try
On 2017-06-20 06:20, Maxime Richez wrote:
> Hi,
>
> Here's my small problem in Tryton 4.2, i want to filter products on a
> specific product category. I define those category as a property in a
> configuration.
Why using a Property field?
> My code is here: https://pastebin.com/wDF8qGtX
>
> S
