I have a lookup project for markets and many of them are 1:1 with a single city. If someone chooses a market and there is only one city resulting, is there any way to autoselect that value instead of them manually having to select the single result from the dropdown? Is this a place where a Fusion scenario might be a better fit than an external lookup field?
Hey Greg - I get that; but if an external lookup is a single-select, it works like a normal dropdown - you still have to click the choice. (or maybe I'm still missing what you mean?)
Would be cool though if we could have a calculated field that can make the API call and just display the returned value.
Actually, @sven-ix and @gregorybu5 , I think I have noticed something lately - perhaps this has happened with a recent update. I am seeing behavior now that if the result of the external lookup query is a list, the list is shown in the dropdown, but if the result has a determinate, single value, that is shown in the field (even though the dropdown arrow is still there) and the field takes on the value immediately without selection. I tested it by adding a calculated field that only contains the external lookup field.
If the query results in a list, the calculated field waits until a selection is made to populate.
But if the query only pulls one result, both the external lookup field and the calculated field update without requiring selection!
This also works if you use a function like length() in your JSON path that results in a definite value - as in returning the number of results based on another field.
So it looks like this is now working as I had hoped it would!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.