FastField Integration Is Inappropriate
Am I the only one who feels it is not appropriate for Quickbase to so ardently push a paid add-on product towards it's consumer base, to the point of giving it first-class representation in the main ...
Forum Discussion
Hey JoelHickok​ and KristaSibery​, sorry this has been a frustrating experience.
I'd love to learn a bit more about what you're seeing. Can we find a time to meet so you can walk me through the areas you're seeing FastField? I want to be in a place where I know exactly what you're referring to so I can take back to internal teams.
Calendly above if you're game for a quick call.
Thanks for raising this, let's see what we can do here.
-Ben
Hi Ben,
Thanks for the message. The main thing that I think both of us are pointing out is that FastField is a paid add-on, yet shows up by default in several places in the UI. We shouldn't see that unless we have opted in to that product. My org does now have at least one user trying out FastField, but even before that, I was seeing it promoted as a first-class citizen of the Quickbase platform, taking up space in the UI menus, etc. See Kristas screenshots for a couple examples.
Joel
