Skip to main content

Discussion about all the "Updates" customers didn't ask for...

  • April 12, 2021
  • 0 replies
  • 134 views

Forum|alt.badge.img+7
Ok, I know for a fact that there are hundreds of feature tickets in the QB Dev Team queue that customers have asked for, as active users of the system. I feel like the endless stream of restrictive, useless, and annoying updates, have probably never been on that list.

Taking away simple things like Automations, ending the use of JavaScript in Rich Text fields, the dang "beta" report formatting that, if you accidentally click, is like herpes on your system, affecting every report you have... I mean REALLY????

We never asked for this. We do not want more limitations. How can you not see that? Do you not use the system? 

We want MORE space, MORE features, MORE flexibility, or maybe just the features that we have been asking for.

I urge other users to write below and add their comments to this thread. Maybe they will hear us. Because obviously having virtual Empowers has taken them away from hearing, from our own faces, what we really want and need.

------------------------------
QuickBase Girl
------------------------------
This topic has been closed for replies.

  • Quickbase Alumni
  • April 12, 2021
What she said.

------------------------------
Alan Turing
------------------------------

Forum|alt.badge.img+14
Can we add the rebranding to this list :). I haven't used QB for too long, but it seemed like when I first joined all everyone could talk about was how amazing QB was because of their dedication to their end users (and it seemed that way from my perspective). I agree that lately it has been an endless string of decisions that seem to not take any of their customers in mind.

Maybe we can add the fact that they also just randomly switched our sales reps on us?

------------------------------
Mike Tamoush
------------------------------

  • Quickbase Alumni
  • April 12, 2021
I have been feeling the same way. It feels to me like Pipelines has become a major priority and basics like a new form builder never seem to be discussed. If all this pipeline energy were put into making the integration with Zapier better, QuickBase could have gotten further faster. Are they really going to re-create every possible integration that already existing in Zapier? 

Form builder - Go take a look at Cognito Forms for a good idea of where they need to go in my opinion.

I also am not sure about the new reports. Feels like more clicks.

Also how about some actual email integration. I built a CRM but have to jump through hoops with external systems for true two-way communication via email which is a staple of any CRM.  Could add texting to this also.

------------------------------
Steve Laurel
------------------------------

Forum|alt.badge.img+7
  • Quickbase Alumni
  • April 13, 2021
I'm relatively new to QB, and not an IT person, but I did build our entire CRM system in QB.  I could set up the automations relatively easily. 

However, I have yet to figure out Pipelines.  I wish there were more examples because I just don't get it.  I've been through a few Pipelines trainings which either only scratched the surface or breezed through parts I wasn't able to follow.  I just got a survey about Pipelines that clearly showed me why I'm so lost.  The survey was clearly not made for someone of my IT skills.

I would love to be able to schedule outbound emails to outside contacts more easily.  I would love to be able to figure out how to integrate with MailChimp through Pipelines. I would love to be able to create a mail merge-type Google doc to create price quotes without needing a third party system.  If I can create an email with merge terms, how come I can't do the same to a Word or Google doc?

I also don't think the rebranding was necessary or useful (and I technically am a marketing person.)



------------------------------
Kim Gardner
------------------------------

JimHarrison
Forum|alt.badge.img+16
  • Quickbase Alumni
  • April 14, 2021

Quickbase Girl,

I can't agree more! I hear the frustration and know how it feels. It seems like there is a lot of incentive to come up with some really great solutions. I feel like the Quickbase employees I talk with are invested in the product and want to provide a good solution. The days of the Type Ahead Search picker seem to be gone - that change made a huge difference, as an example.

From my perspective, they are overwhelmed with the integration with Pipelines and there is little to no movement in any core product development. It seems like it has been this way since the purchase of Pipelines. Maybe they have a steep learning curve happening or something. 

I want to note the response from the Quickbase Support Team has improved for me. I don't feel like I get the "well it works for us" run around. 

I would like to see some of the UserVoice requests get handled on a regular basis. Like one per month or one per quarter.
I would also like to see more development on the Administrator side. Like not having to click 6 rows of little green checkboxes for each table one at a time. You can select all, or you can select one at a time but you cannot select all and unselect one or two. That is a lot of clicks. 
I never really embraced the JavaScript hack and don't mind it going away, we have been able to leverage URL-formulas and Rich-Text formulas to get what we need. Although I will miss the IOL to expand and collapse all the sections on a form, Dan Diebold made something simple and very useful! 
Being able to style a form, or align fields to a grid on a form would help.
Including HTML characters when exporting a Rich Text field to csv is not a feature.
The never ending Webhook error that never clears. Oh and no dev in Webhooks because Pipelines is the new Webhook, is not acceptable as a reason why the feature will remain broken.

On a plus of new development:
Dashboards are interesting but not really useful yet.
The Form rules applied to Grid Edit is looking functional. Although changing every Grid Edit report to the same set columns is not so good as a default.
Moving away from XML into JSON will be nice when it is done. Maybe we need more demos?

I appreciate your post and have placed the ideas that came to mind to add my support. I want this product to be successful as a cloud service. 

Regards,
Jim Harrison
Portland, OR







------------------------------
Jim Harrison
transparency = knowledge + understanding : The Scrum Dudes
------------------------------