Forced to use new dashboards?
Whare are everyones thoughts on the new switch to Upgraded Dashboards? I had just spent a year making Dashboards (they are great), and now suddenly they upgraded the design (tabs on top and a bit of a different look). I like the new look, but I already built quite a few with the old look, and my users just got used to the tabs on the bottom. I am creating my last dashboard, and BOOM, it defaults and forces you to the new style (when creating a new dashboard). There is a cheat code (copy an old style dashboard), but this seems to be another example of Quickbase simply not listening to the end user any more. I do like the new design, and will likely eventually switch, but to force the issue immediately without warning, feels rough. It makes consistency in my apps very difficult. What do others think?Side Bar Navigation SUCKS.
Am I to understand that top navigation is going to be permanently moved to side navigation beginning in 2025? If so, that is one really dumb move. We have ALOT of reports that are designed to fit on the screen exactly as they are. Now they will all have a horizontal scroll bar which makes it an unnecessary waste of time having to scroll left to right to see the entire report. Why do you guys arbitrarily change stuff nobody really asked for? And why don't you just give us the option to stay with what we are comfortable with. Removing choices in preference is really stupid.
Remove the save button when from new forms format when applying I-forms (IFV=1) #354382
I posted this feedback in hopes of getting attention of R&D, but it has been more than 5 months since the new forms were released. I'm certain I'm not the only person using Iforms. The failure to make the new forms capable to remove all user access but what is required for better handling of large populations of users for input is inhibiting every Quickbase developer from moving forward with new forms. Any work done to build out new forms results in a backlog to have to either go back and use a legacy form, or simply wait to release the new functionality in our apps. My hope in posting this here is to raise awareness that there is a feedback items out there that needs your support by acknowledging it, and ask you to also comment here to expand awareness. It's best practice to transition to new forms and features to allow Quickbase to grow and improve. It should be best practice for R&D to complete the task in a reasonable period of time when asking customers to use their new features. Please raise your voice and be heard!
The New Pipeline Builder UI is a downgrade overall: Please adjust it
This will probably be a hot topic, but it needs to be said since the better legacy builder UI is being removed soon. Posting here rather than a "suggestion" because in my 6 years of doing QuickBase Development, the suggestions page has proven to be basically useless at getting the word out on issues. Overall the new PL Builder UI only offers ONE feature that is a benefit, which is full step-reordering. But, this should have just been added to the old UI. Who asked for a new UI? The new UI, overall, is just cumbersome/slow and annoying to use. I have waited for a long time now, expecting the UI to be improved, but I've see no such fixes to the issues the new UI has, as such it is now time to talk about it. See my images below with added notes. Below is probably one of the absolute worse design choices overall; Why do we have to OPEN each section of the step? What value does this add? All this does is slow down the process by forcing me to go "open, open, open" when in the old one I can see ALL THREE items at once. The old view is beyond better: Open the step, take a glance, bam, done. This adds literally ZERO benefit to admins/devs. The old UI has too much white-space, but at least I can see everything.Anyone heard updates on Webhooks End of Service?
Wondering if anyone has heard any updates on the plan to phase out Webhooks in June. It seemed to me that idea had perhaps the most backlash of any, and by a lot of the most prominent users and QSPs. It is seemingly unanimous by the community that it is a very bad idea. I am very curious to see if they actually respond to feedback as they promise they will, or continue on with their plan.
Document Template/Creation (PDF)
First off, loving the document/pdf creation function. Has opened some new areas of opportunity in a few tables. One thing I am having trouble with, maybe a setting/enablement I am overlooking , but I want to enable a user to generate a document from any given filtered view or a customized report view. For example I have material requests for various jobs, if I create a report to filter to just by job and visibly only see that job's requests, we'd want to a user to have the ability to just click generate a document and it makes it off that view's records. If I do that now, it actually generates the document for the whole overall table, not what report I'm in and what records I visibly see from that report.How to add a link to new notifications?
Does anyone know how to add a link to new notifications? In old notifications you can simply make a rich text link and reference the field, but in the new notifications it just shows the rich text field as text. My use case is: The notification fires from a child record, but I want to be able to have a link to the parent record in the email.
