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?
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!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.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.
