Sneak Peek: Type-Ahead Search Picker
While we at Quickbase love to work on great new features, like Kanban reports or Automations, we also take time to focus on the fundamentals. And what could be more fundamental to Quickbase th...
Forum Discussion
Harrison, I beg to differ! Today (not on EA), the user experience for [Related Parent] when there is no Proxy field set, is that in ADD and EDIT mode, is that the user sees the fields from the custom report on the form.
I'm happy to share an app which will duplicate this scenario with anyone in support.
For example
The custom report on the form is a single column drop down list of Defects from a related table. The current behavior is the user sees a nice clean single column list of defects and in edit mode while looking at the record, but not actually editing that field, sees words of the various defects.
In EA, that will display in edit mode like like "237" as the Defect. 237 is the Record ID# of the defect and is not meaningful to the user, when they expect to see the words, like "Low Tuft Lines".
I know that I can fix this by changing the app to use a reference proxy, but my concern is that this change will break functionality for thousands of apps. You don't want these support calls and I don't want to proactively search every app I have ever written looking for where I should have used a reference proxy for apps I built in the last 16 years. In the early 2000's like 2002 'ish I did not understand what a reference proxy was. Based on my consulting work where I coach and train, many new users do not understand reference proxies.
Hence I feel that if the developer who specified a report on the form to use for a drop down should continue to have their wishes respected and use that report for the drop down. If I wanted to expose the Record ID to the user I would have included that on my report used for the drop down. But its pretty rare to want to expose Record IDs to users, unless it happens to be used as a like an Order# off a number wheel.
I'm happy to share an app which will duplicate this scenario with anyone in support.
For example
The custom report on the form is a single column drop down list of Defects from a related table. The current behavior is the user sees a nice clean single column list of defects and in edit mode while looking at the record, but not actually editing that field, sees words of the various defects.
In EA, that will display in edit mode like like "237" as the Defect. 237 is the Record ID# of the defect and is not meaningful to the user, when they expect to see the words, like "Low Tuft Lines".
I know that I can fix this by changing the app to use a reference proxy, but my concern is that this change will break functionality for thousands of apps. You don't want these support calls and I don't want to proactively search every app I have ever written looking for where I should have used a reference proxy for apps I built in the last 16 years. In the early 2000's like 2002 'ish I did not understand what a reference proxy was. Based on my consulting work where I coach and train, many new users do not understand reference proxies.
Hence I feel that if the developer who specified a report on the form to use for a drop down should continue to have their wishes respected and use that report for the drop down. If I wanted to expose the Record ID to the user I would have included that on my report used for the drop down. But its pretty rare to want to expose Record IDs to users, unless it happens to be used as a like an Order# off a number wheel.