0028584: Auxiliary input vs display logic does not work fine in all the cases

Notes
(0073468) alostale (manager) 2015-01-13 17:08	Moving to design defect: in order to properly implement it, it would be required to parse the SQL in the auxiliary input to detect which fields in the current window participate in that logic to mark those a dynamic columns. Once they are dynamic changes on them should trigger a backend call to recalculate the auxiliary input value. == Alternative solution with current platform == Do not use an auxiliary input. Instead set the displayLogic to something like: myFunction(@M_Product_Category_ID@, item, form, currentValues, context) where myFunction is a javascript function, in this way current parser would detect M_Product_Category_ID as dynamic and would invoke myFunction whenever it changes. To implement myFunction: If it is possible to evaluate the display logic synchronously based on local values, do it and return true if the field should be shown or false if not. If it requires backend evaluation, implement like: myFunction = function (newValue, item, form, currentValues, context) { var callback = function(data) { // evaluate here the display logic, item is the field to show/hide if (show) { item.show(); } else { item.hide(); } } invokeActionHandler(callback); return item.isVisible(); // keep visibility till callback is executed }