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
My point here is that I happened to be testing on an older app written around 2005 before I understood "Reference Proxies" in Relationships. So I did manual Proxies. I used [related parent] in add/edit mode on the form and [Parent name] in view mode.
On the Original app not in EA it works fine. The form is set to use a report where the drop down choices for the record picker is just the single field for Parent name. In edit mode it shows the Parent name field and the drop down choices are names.
But on a copy of the app moved into my EA testing Realm, in edit mode it shows the [Record ID#] which is clearly meaningless to users.
I suggest that there will be many many apps out there where the users, like myself in my early QuickBase (one word) days, didn't "get" Proxies and in fact they confused the heck out of me because when you build a relationship, it assumes that the very first lookup field is the reference Proxy and sometimes that was a not a good proxy or else i would end up with both the Proxy and the related parent on the same form in add/edit mode (which does not work to have the same field on the form twice in edit/add mode). So I avoided using them.
So my point is that if GA will show the Record ID and behave differently than the current behaviour, then that will break a lot of apps and cause a lot of support calls.
On the Original app not in EA it works fine. The form is set to use a report where the drop down choices for the record picker is just the single field for Parent name. In edit mode it shows the Parent name field and the drop down choices are names.
But on a copy of the app moved into my EA testing Realm, in edit mode it shows the [Record ID#] which is clearly meaningless to users.
I suggest that there will be many many apps out there where the users, like myself in my early QuickBase (one word) days, didn't "get" Proxies and in fact they confused the heck out of me because when you build a relationship, it assumes that the very first lookup field is the reference Proxy and sometimes that was a not a good proxy or else i would end up with both the Proxy and the related parent on the same form in add/edit mode (which does not work to have the same field on the form twice in edit/add mode). So I avoided using them.
So my point is that if GA will show the Record ID and behave differently than the current behaviour, then that will break a lot of apps and cause a lot of support calls.