Added a feedback alert to stop the arbitrary limits placed on an app.

  • 0
  • 1
  • Question
  • Updated 1 year ago
  • Doesn't Need an Answer
I added a software request to get QB to stop imposing arbitrary limits on the software.  Time and again, I see people ask how to get around this limit or that one, and QB will not help.  Seems like a simple thing to remedy.

https://quickbase.uservoice.com/forums/111823-quick-base-product-feedback/suggestions/20014867-remove-arbitrary-limits-imposed-in-the-software

Please read, and if you agree, vote.  Hopefully they will finally hear us, the USER, and do something about it!
Photo of Neil Shepard

Neil Shepard

  • 1,248 Points 1k badge 2x thumb
  • frustrated

Posted 1 year ago

  • 0
  • 1
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 53,842 Points 50k badge 2x thumb
I think that this would get more traction with QuickBase if these were entered as separate requests.  While I agree with most of them, each one will require a separate development effort and assignment of resources by QuickBase management and hence will need to be separately prioritized.
Photo of Neil Shepard

Neil Shepard

  • 1,248 Points 1k badge 2x thumb
I conceptually agree with you, and I have requested certain things be dealt with individually, and others have as well.  The issue is they don't seem to get any traction by themselves.  I see where some have minimal votes and others are flat denied by QB.  There are several requests that ask for the same limit to be removed in the feedback section and are also littered throughout the community posts.  The answer is usually, add a feature request.  

My post is not related to one particular failure of QB, but in the total program to introduce limits.  Software nowadays is able to do anything.  If there is a size limit to a table, or a limit to the number of items that can be plotted, this is a restriction that QB has placed.   

I personally have only encountered the plotting limit.  The others are me just trying to get the awareness out there and see if we can't get QB to modify their software, for the better, by finally getting people to put their weight behind the concept.  Here the concept is the limit.  
Photo of Kingsly SD Samuel

Kingsly SD Samuel

  • 776 Points 500 badge 2x thumb
I agree with Neil. I have faced similar issues, in terms of search, with default setting report, etc. They came back saying that they have been identified as a bug, but there is no ETA to be given at this time. I love QB, but as Neil said it is limiting its greatness. They are pretty simple functions that we get in other platforms, I wonder what is the reasoning behind QB not releasing these limitations.
Photo of Michael Barrow

Michael Barrow

  • 2,206 Points 2k badge 2x thumb
The arbitrary limit that kills me is the 500 MB maximum size per table. I have 2 tables that I'm always having to beat back. It is a ridiculous waste of time, and I have to lose historical information to fit. 500 MB!!

I migrated to QB from Salesforce 3 years ago, and am way beyond pleased with QB. But naggy stuff like this is a pain, and limits like these would throw a monkey wrench in any decent-sized company seriously considering migrating to QB. If I were in sales or marketing at QB, I would be screaming at the developers to get their priorities straight. Overall, though, QB is 10x better than Salesforce ever was at regularly releasing useful and requested updates to the platform.
Photo of Neil Shepard

Neil Shepard

  • 1,248 Points 1k badge 2x thumb
Please feel free to add votes to the feature request.  Maybe this will be the thing that gets a re-look at these limits.

I too like QB.  Before this I was building a SharePoint site for the company and I liked the fact of the limits not being an issue.  Need more space-buy more hardware or pay for more room on the cloud server.  Nothing thrown away.

I even forgot to add, if you have a time/date field then QB throws away seconds.  This is valuable data for my company as we do time series data collection in 15 or 30 second increments.  That's a limit that doesn't need to exist-very Y2K to me.   I did put a feature request in but there has been zero votes because apparently my company is the only ones that needs this data.

Ever onwards!