Skip to main content
Question

When two task look ups share columns, how to prevent emptying of one when other is filled in?

  • March 9, 2026
  • 1 reply
  • 11 views
R
Apprentice
Forum|alt.badge.img+1

I am facing this issue with a task default:

 

The task has the parameters

warehouse_id - look up table: item_warehouse; look up columns: item_id, warehouse_id

to_warehouse_location_id - look up table: warehouse_location; look up columns: warehouse_id, warehouse_location_id

item_id - look up table: item, look up column: item_id

 

warehouse_id and to_warehouse_location_id are filled in automatically by the table task parameters (on the warehouse_location table),

but when item_id is filled in by the user, warehouse_id and to_warehouse_location_id are emptied,

even though the item_id chosen exists as item_id + warehouse_id combination in the item_warehouse table.

 

I chose to show item_warehouse as look up table on warehouse_id instead of the warehouse table because the table has more useful information.

 

Is there a way to prevent the emptying of the warehouse_id parameter?

I have not yet added a default script.

    1 reply

    E
    Moderator

    I believe this to be a bug. In the gui you would not be able to set warehouse_id without first setting the item_id. So assigning only the warehouse_id in task parameters does not make sense in this situation. If the goal is to let the user select a item based on the warehouse the references should be:

    warehouse_id - look up table: warehouse; look up columns: warehouse_id

    item_id - look up table: item_warehouse, look up column: warehouse_id, item_id

    But if this reference is not unique you could create a view with all the possible combinations. To make sure you don’t get duplicates. 

    Terms & ConditionsCookie settingsAccessibility statement