Blog Post
MichaelFrishma1
5 years agoQrew Cadet
I've worked with Quickbase for over 8 years and have seen some great improvements over the years. This is a HUGE step back and a big mistake. When a system has a large number of users having to create their own workarounds for functions that should be native, that should be an indication that those functions are needed.
Here, instead of Quickbase understanding WHY we're using these workarounds and building native functions to replace what we need, Quickbase chooses the other route, and removes what some of us need to do our jobs.
So if Quickbase really wants to be a real go-to low/no code solution, make the ability to create action buttons native. Wouldn't that be a better solution than breaking everyone's apps?
FIX the problem. Don't break the solution.
Here, instead of Quickbase understanding WHY we're using these workarounds and building native functions to replace what we need, Quickbase chooses the other route, and removes what some of us need to do our jobs.
So if Quickbase really wants to be a real go-to low/no code solution, make the ability to create action buttons native. Wouldn't that be a better solution than breaking everyone's apps?
FIX the problem. Don't break the solution.