"New Style"

Sam,

Completely agree with you. Still is impossibly slow, and half the time it shows a blank screen (maybe due to caching? bugs? not sure).

It's terrible. Why they can't default to the old style until they fix it is beyond me. It is undoubtedly the current worst part about Quickbase. I for one will advise people NOT to purchase Quickbase until they fix this. It's wildly important.​

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

Right. We have been hearing that same lip-service for over two years now.

Please default the "New Style" to off until you guys get your act together. It is quite an irritant for our entire company to have to turn it off on every app, on every table just to be able to use QuickBase.

Were tired of being your beta Guinea pigs.

------------------------------
Sam Lopresti
------------------------------

Agree with Sam. When our number 1 feedback is, please let us default the new report off until you have the main frustrations sorted out (particularly how painfully slow it is to load and that it conflicts with caching and simply doesn't even show your records), and we are still in the same situation over a year later, it discourages us from leaving any feedback because you are communicating that you don't care about our feedback.

To encourage feedback, you need to demonstrate our feedback matters.

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

I love quick base but I cannot stand that they release new features as beta versions (at best).  Not related to table reports but we have the new dashboard charts came in and messed up a few mission critical reports for us on our executive dashboard for revenue projections etc.  I reached out to support and the answer is we see the issue and are working on it.  I said can we revert back until its fixed, this is critical for me.  The answer was no we cannot and we will work on it but it might take some time to fix it.

Just put it back and do not test things until they are thoroughly tested and limited released.  Now I have to submit manual information outside of quick base for some financials as the charts dont scale right.

You cannot push out features as "beta versions". People need to sign up as beta users.  As the developer on our side I do not mind my view being a beta view so we can take advantage of new features and provide feedback.  But I cannot have the owner of my company in a beta environment.

------------------------------
Ivan Weiss
------------------------------

I would agree there is a heavy pause when loading pages with simple table views. The first thing I do after waiting for the page to load is disable the new style report, then I can get work done.

If you click the New Style toggle too soon, it loads the Add Page and then you have to navigate back to the New Style, wait 10-15 seconds for the page to load and then disable the New Style report. We are consistently seeing long load times across multiple apps with various table sizes.

I would really love a default setting at the app level to set the New Style to off so we can be democratic about the preferred report.

Please Quickbase can we have a disable New Style by default setting in the App Properties.

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

I think Christian is referring to Table Reports. 

my own opinion is that I don't hate the new reports, they just have their advantages and disadvantages compared to the old style. And I have long maintained that users should be able to decide which version they want on a particular report for their day-to-day work. I think about the worker bees, who just use Quickbase all day long and prefer one version over another.

Unfortunately, this forum is not an effective way to communicate with product managers.   

my understanding is that when you flipped to the old style report, it will remember your preference for the day, but then reset overnight. I have employed product managers to make that decision more sticky so it would stay with the user either forever, or at least a month.QuickBase engineers may feel that they still want the features of the new report to be discoverable as they plan enhancements in the future. So if you were locked into the old style report forever, you may not even realize that there are new features.

 quickBase engineers may feel that they still want the features of the new report to be discoverable as they plan enhancements in the future. So if you were locked into the old style report forever, you may not even realize that there are new features.

So having said all that the only way to affect basis to put in a  suggestion into the user voice tab, which is on my apps page at the left and suggest that the selection of old style for new style on a particular report should maintain your choice for a much longer time than just the current day.   

------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------

Thx Jim,
I have some examples of slow reports which may help them identify issues, so I'd appreciate if I  could also speak to the PM.

I have found that unlike the old report, the speed of the new ones is device dependent, especially where there are Rich Text fields on the report.  ie if you are on a hot machine, the reports render more quickly than if you are on say a slow iPad, whereas on the old reports they were device independent.

Mark Shnier
Your Quickbase Coach, QSP
mark.shnier@gmail.com

------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------

Today's meeting went well. It seems that summary and report link fields may be of interest in reducing performance. The QB Team was also very interested in the results of removing the "Searchable" property from fields that don't need to be searched.

ParkerC is going to arrange another meeting where he and I can look at performance stats in Chrome for sometime next week.

@Mark - if you have links to reports that are public? If not how do we arrange that other than setting up another meeting and getting you invited? I'll ask Parker if he's game.



​

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

The reports are not public as they are form a client app.  I would love to demo the speed differences on that particular report.

------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------

Jim/Mark,

Do you have some reports that load fast, and others slow? I find that any table or report on the new style is just agonizingly slow in every way - initial load time, load on scroll, filtering, searching, etc. To me it's not a specific issue, it's just every part of it is very slow. I'm not sure it matters if I have 20 records, or 200,000 records, though I haven't extensively tested that. Is this different than your experience?

------------------------------
Michael Tamoush
------------------------------

I find it unbelievable that the QBase Devs don't know that the "new style" is not hot garbage. 

We are being strung along in an endless, unwanted alpha-test.

------------------------------
Sam Lopresti
------------------------------

Hi Michael,

The jury is out. I really don't have the bandwidth to test times with precision. On average I would say we consistently see reports loading slowly in all Apps, there is some improvement when clearing the "Searchable" check box and removing summary and report link fields.

What we need is reproducible steps that we can all try out and compare notes. To investigate try loading on a different device. Using a different network bandwidth. Using a different network. Then change the field properties and remove fields until there is a difference.

Look forward to hearing your experience.


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

Quickbase has engaged with me to have a demo session next week for examples of reports where the load times are very different old vs new.  The underlaying report  takes under 2 seconds to process according to the performance Analyzer.  That is the same for the old and new report.  The old report loads in 5 seconds (so say 3 seconds to get the data onto my screen after the 2 seconds of processing time).  The new report is 10 - 15 seconds depending on the browser, so 8 to 13 seconds to get the data rendered on the screen after the Quickbase servers have assembled the data.

------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------

Here we are, two more months later with no change.

It is absurd that we have to endure a never-ending broken alpha test of a product that many of us are PAYING thousands of dollars a month for.

My entire company has just resigned themselves to coming in every morning, opening all the usual things they use and turning off the "New Style" on every one of them because it is just a pile of broken garbage.

------------------------------
Sam Lopresti
------------------------------

If it is any solace, I can tell you that they are aware of the slowness issue and are actively working to make improvements.   They told me it's high on their priority list.  I guess it's not an easy problem to solve.

------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------

Since they freaking know it is broken, why don't they make the default of the "New Style" equal to OFF.

You know, so we all don't have to waste our time turning it off on multiple apps every damn morning.

------------------------------
Sam Lopresti
------------------------------

From Porland OR, the latest release has caused significant performance degredation. We are seeing the same hang times as before we met with QB. Uncertain why but I am hoping @Boginya Ventsislavova is listening.​

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

A Recent Blog Article talks about the Performance Issue.
https://community.quickbase.com/blogs/brian-cafferelli1/2021/10/28/performance-improvements-coming-to-the-new-table-r

------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------

No thanks Evan,

I prefer it to be addressed publicly.

As MANY other posts in this chain have pointed out, there are big issues with QuickBase that are falling on deaf ears.

Many of us are tired of alpha-testing QuickBase changes (ie: unwanted experiments) that should not have been forced upon us in the first place.

Find another Guinea pig.

------------------------------
Sam Lopresti
------------------------------

Hi Sam,

Thank you for letting us know that you would rather not schedule time to share feedback directly with the product team. When someone active in community shares their frustrations, we want to make sure we record their feedback accurately and that we aren't missing out on the specifics of their experiences. To do that, we give them the chance to voice their concerns in a live conversation so we may directly address them.

As Mark mentioned above, we do have a recent article addressing plans to continue investing in performance for the new table report style. All of our community members can expect to hear more from us on new table reports in the community and in our future release notes as we continue to roll out enhancements. Performance is an ongoing process here at Quickbase, so as we make adjustments to our plans to address new table reports and customer experience we will communicate them.

------------------------------
Evan Martinez
------------------------------

>"As Mark mentioned above, we do have a recent article addressing plans to continue investing in performance for the new table report style."

The original post: 12-31-2020

It's been almost a year.


------------------------------
Sam Lopresti
------------------------------

It's now 05/20/2022 ..... and the "New Interface" still slow.... and still sucks.

------------------------------
Sam Lopresti
------------------------------

Thank you for the feedback - it's important that you tell us when things are working well and, more importantly, when things aren't working the way you expect. It helps us build a better product, and we appreciate the passion around making the product better.

Due in large part to your feedback, we're fixing many of the issues that have been discussed in this thread. Please keep an eye on our release notes for information about future improvements to the table report. We plan to make exciting progress in this area in the very near future.

In addition, we will continue to release features in a beta state so that we can gather customer input. We will release bugs. We will also fix those bugs. In the case you mentioned, Ivan, we plan to deploy a fix this week. If you haven't already, please submit a support case so we can tie it to the issue in our systems. This ensures you are updated once the issue is resolved.

Again, while we appreciate the candor here, there are better avenues to raise issues like this to get a response from the Quickbase Product Team.

1. For any bugs or performance issues you encounter while using any part of the product, please submit a tech support case. Our team will help you triage the issue, determine if there is a product bug you've encountered, and recommend performance optimizations if applicable.

2. For any feedback regarding the Quickbase Product, we encourage you to post that in our Feedback platform which can be found by clicking the Give Feedback Icon to the left of the apps on your My Apps page. To learn how we use your feedback, you can watch this Quick Hit from Empower 2022, recorded by one of our product managers.

Thanks again for the discussion,

Brian

------------------------------
Brian Cafferelli
Product Marketing Manager | Quick Base
------------------------------

+1  Style should come second to performance. I'd suggest Quickbase Product Team should be required to submit all their reports, forms, etc. internally solely within Quickbase so they can truly get a pulse on what matters to the end user. Loading time is one of the biggest factors in any service and just a small delay creates a whole different experience.

------------------------------
Justin Burchell
------------------------------

Please, please have an option to disable this feature.  The first thing I do in every report I view is disable it.  I have given it a chance and it's just not better than the old set up.  We used the dynamic filters all the time to drill down in our reports.  The old set up was so much cleaner and easier to quickly see the data for what it is.  Also, really miss the summary reports.  Please bring these back.

------------------------------
jonathan duke
------------------------------