Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0014806Openbravo ERPA. Platformpublic2010-10-07 11:172010-11-09 22:46
networkb 
alostale 
highminoralways
closedduplicate 
20Community Appliance
2.50MP22 
2.50MP24 
Core
No
0014806: auxiliar input belonging to module distinct that core module, the behaviour is distinct to "auxiliar input" belonging to core
. 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.
. 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.
No tags attached.
duplicate of feature request 0004350 acknowledged iciordia Calls to ComboReload callouts on Auxiliar Inputs 
Issue History
2010-10-07 11:17networkbNew Issue
2010-10-07 11:17networkbAssigned To => alostale
2010-10-11 09:06alostaleStatusnew => scheduled
2010-11-04 15:59alostaleRelationship addedduplicate of 0004350
2010-11-04 15:59alostaleNote Added: 0032393
2010-11-04 15:59alostaleStatusscheduled => closed
2010-11-04 15:59alostaleResolutionopen => duplicate
2010-11-09 22:46anonymoussf_bug_id0 => 3106257

Notes
(0032393)
alostale   
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 [^]