Forum Discussion
KingslySamuel
7 years agoQrew Cadet
Customize this form" to select and remove the field from the "elements" tab or go to "dynamic rules" and enable a rule to "hide" the field under certain conditions.
- QuickBaseCoachD7 years agoQrew CaptainBrad is looking to disable that top line of the address field which is a search box. I don't think that there is a way to do that.
- KingslySamuel7 years agoQrew CadetOh ok. I thought there was a way before (at the user level or report level), for I remember having issues displaying that option for one of my users in the past. Any case, now it does look like a default search area.
- BradLemke7 years agoQrew Assistant CaptainCorrect on the first comment, Coach. I've been looking for ways to disable or hide it for a few months now, but it's been a passive search due to the low-priority of the issue in relation to the other tasks I needed to knock out. It's becoming a higher-than expected-priority item now that i'm training more and more non-power users for the app.
- QuickBaseCoachD7 years agoQrew CaptainAn option is to not use that field type at all and just back to the way we used to do it with separate fields.
Add 1
Add 2
City, State, Postal
You would lose the embedded map, but it still easy to make a formula URL that will pop up a google map by feeding the address components in the correct syntax.
The separate fields can be displayed in an single address block formula in View mode.
List("\n",
[Street 1],
[Street 2],
List(", ", [City], [State]),
[Postal Code]) - BradLemke7 years agoQrew Assistant CaptainI've entertained that idea. There's a great deal of app re-programming that will result, however. The entire Dispatch system integration, 11 exact forms, unique workorder ID programming based on the street address (to prevent duplicate order entry), and several other internal systems/filters/reports/functions that are based solely off of this field.
I'm not saying I won't do it, but I would need to set aside a few days to QC the system before sending it live.