Skip to Content
Menu
Musisz się zarejestrować, aby móc wchodzić w interakcje z tą społecznością.
To pytanie dostało ostrzeżenie
1 Odpowiedz
785 Widoki

I added this code for adding digits in price unit 


<xpath expr="//field[@name='invoice_line_ids']//field[@name='price_unit']" position="replace">
<field name="price_unit" digits="[12,12]" column_invisible="parent.cover_sheet_count == 0"/>
<field name="price_unit" digits="[12,2]" column_invisible="parent.cover_sheet_count != 0"/>
</xpath>


it is working perfectly in using replace , when coversheet count != 0 the price unit with 12 decimal precision . 

when coversheet count == 0 price unit with 2 decimal precision 


When i use attribute like this 


<xpath expr="//field[@name='invoice_line_ids']//field[@name='price_unit']" position="attributes">
<attribute name="digits">[12,12]</attribute>
<attribute name="column_invisible">parent.cover_sheet_count == 0</attribute>
</xpath>

<xpath expr="//field[@name='invoice_line_ids']//field[@name='price_unit']" position="attributes">
<attribute name="digits">[12,2]</attribute>
<attribute name="column_invisible">parent.cover_sheet_count != 0</attribute>
</xpath>

when coversheet count == 0 price unit with 2 decimal precision  , only one scenario is working , 
coversheet count !=0 case the price unit field is invisible not decimal precision with 12 digits 


What is the reason for this behaviour ??


Awatar
Odrzuć
Najlepsza odpowiedź

Your first example is removing the price_unit field and replacing it with two price_unit fields.

Your second example is finding the price_unit field and changing the attributes, then finding the price_unit field again (the same field) and changing the attributes again - so only the second change is actually being made.

Awatar
Odrzuć
Autor

Thanks. I understand

Powiązane posty Odpowiedzi Widoki Czynność
3
lip 25
2052
1
cze 25
2422
2
maj 25
2016
1
maj 25
1227
1
lut 25
38