+3Hi Bram!
You would really help us if you gave more context to the problem. What is your end user doing to need this extra information?
Kind regards,
Bart
Indeed, the current screenshot does not represent our business case very well. But we mainly miss this functionality when the choice is derived from multiple attributes, as for example in a hierarchical treeview with product locations, or a product category structure. We can then choose as location, for example, District A, but not everyone knows which location is meant by the name “District A” alone. District A is in a warehouse, which in turn belongs to a factory and is in a location. In the lookup, a user could then “peel off” the hierarchy treeview in the lookup to get to his desired level/record. By configuring a single lookup here, we avoid needing 4 fields and 4 references, all of which a user would have to fill in to arrive at District A. And if it turns out that a wrong plant was chosen, the user no longer needs to refill 4 fields to re-enter his choice, but can do so within one lookup and one filter. Now to accomplish this, we either need 4 fields or a lookup concatenating the 4 hierarchy level lookups, which looks plain aweful and is not presented well or readable.
Bram
+3Thanks for the clarification Bram!
+10
+12Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
