0014806: auxiliar input belonging to module distinct that core module, the behaviour is distinct to "auxiliar input" belonging to core

Description

. if you create a new auxiliar input, with db prefix, the behaviour is not equal that core auxiliar input.

. in sales order line, there is an auxiliar input HASSECONDUOM asociated to columns "C_ORDER_UOM" and "QTY_ORDERED"
. when you select a product with second UOM, the fields ORDER UOM and QTY ORDERED are shown automatically.
. this fields are shown because they have a display logic "@HASSECONDUOM@ = 1"

. But if you try the same with auxiliar input belong to module distinct of core module, the fields are not shown.

Steps To Reproduce

. create new module (type module, name TEST) with db_prefix "TEST"
. Application Dictionary || Setup || Auxiliary Input || Auxiliary Input
  new record:
   module: TEST
   tab: Lines - Sales Order
   name: TEST_HASSECONDUOM
   validation code:
@SQL=SELECT (CASE COUNT(*) WHEN 0 THEN 0 ELSE 1 END) AS TOTAL FROM M_PRODUCT_UOM WHERE M_PRODUCT_ID=@M_Product_ID@

. Application Dictionary || Windows, Tabs, and Fields || Window
record: Sales Order
. Application Dictionary || Windows, Tabs, and Fields || Window >> Tab
record: lines
. Application Dictionary || Windows, Tabs, and Fields || Window >> Tab >> Field
record: order UOM
modify the display logic to @TEST_HASSECONDUOM@=1

record: Order Quantity
modify the display logic to @TEST_HASSECONDUOM@=1

. compile sales order window

. when you select a product with second UOM, the fields are not shown.
If you save the record, the fields are shown.

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

duplicate of

feature request

0004350

acknowledged

iciordia

Calls to ComboReload callouts on Auxiliar Inputs

Notes
(0032393) alostale (manager) 2010-11-04 15:59	The problem is the one explained in 0004350: auxiliary inputs are not refreshed when the fields they depend on are modified, that's why the fields are not shown when the product is selected but they are when the record is saved. Auxiliary in modules behave in the same way as ones in core. This can be workarounded by adding a callout that sets the auxiliary input value after selecting the product. Which is in the way that is done for core sales order [1]. [1] https://code.openbravo.com/erp/devel/pi/file/3ad12ab37ec5/src/org/openbravo/erpCommon/ad_callouts/SL_Order_Product.java#l172 [^]

Issue History
Date Modified	Username	Field	Change
2010-10-07 11:17	networkb	New Issue
2010-10-07 11:17	networkb	Assigned To	=> alostale
2010-10-11 09:06	alostale	Status	new => scheduled
2010-11-04 15:59	alostale	Relationship added	duplicate of 0004350
2010-11-04 15:59	alostale	Note Added: 0032393
2010-11-04 15:59	alostale	Status	scheduled => closed
2010-11-04 15:59	alostale	Resolution	open => duplicate
2010-11-09 22:46	anonymous	sf_bug_id	0 => 3106257