Immediately show lookup value before hitting save
Jon Darbyshire
Hey Madeline Yang, thanks for your feedback! I have a few more questions for you:
- What specific scenarios or use cases are impacted by the current behavior of the lookup fields?
- Are there any specific types of lookup fields or data that are more critical to display immediately?
- How does the current delay in displaying lookup values affect your workflow or productivity?
M
Madeline Yang
Hi Jon Darbyshire,
- Ideally, this fix should be implemented for all use cases of the lookup field.
In one specific scenario, our user selects from a linked record dropdown of budgets, which is then used to lookup and display the budget 1st tier owner, 2nd tier owner, and 3rd tier owner (see screenshot attached)
Another example would be if you select a job position from a linked record drop down and it looks up the hiring manager.
- All data types for the lookup field should have the same priority to be displayed immediately. The goal is for the user to understand the lookup value will be automatically generated instead of them seeing an empty value in the lookup field and wondering if there is a mistake or missing information (also shown in screenshot attached).
- The current delay affects our workflow because it adds an unnecessary step to save the record before continuing to work on it, rather than just being able to fill out all the information and hit save once. It makes the user feel as though they are missing information, adding confusion and requiring more training to overcome the issue.