There is another solution, but there is quite a bit of work.
You can build a website that interacts with Quickbase. It is not a simple as the native UI but it is less complex than a full blown application.
So if you absolutely have to have a specific workflow for business reasons that QB will not support. We had to do this for a client with a field services requirement.
------------------------------
Don Larson
------------------------------
Original Message:
Sent: 02-19-2023 14:08
From: Mark Shnier (Your Quickbase Coach)
Subject: How the heck do we hide native features in a post JavaScript QB?
I think your only hope is the new forms design which will include the same form working on mobile. They are due to release New Forms sometime this calendar year. I know it's not a quick answer but at least there's some hope on the horizon.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
Original Message:
Sent: 02-19-2023 13:16
From: David Rascon
Subject: How the heck do we hide native features in a post JavaScript QB?
Yes I always use ifv=1 in all the pages under desktop but now I have the requirement for mobile app for Field engineers.
------------------------------
David Rascon
Original Message:
Sent: 02-19-2023 13:11
From: Mark Shnier (Your Quickbase Coach)
Subject: How the heck do we hide native features in a post JavaScript QB?
It's possible by using a suffix on the URL of &ifv=1
But that is only on the desktop interface, not in mobile web or mobile app mode.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
Original Message:
Sent: 02-19-2023 13:00
From: David Rascon
Subject: How the heck do we hide native features in a post JavaScript QB?
Hi Meredith...
Did you find the way to hide the native buttons?
The buttons are causing a lot of flow issues in my app and I have to hide them.
I will appreciate any help.
Thank you!
------------------------------
David Rascon
Original Message:
Sent: 06-23-2021 17:42
From: Meredith Moore
Subject: How the heck do we hide native features in a post JavaScript QB?
I have some big problems. I need to hide native buttons on mobile, as well as other QB features, and I don't know how to do it without IOL. This is what we all used it for.
My issue is I have an EOTI role that needs to save using my custom buttons, in order to direct them down the application path. However, despite my role management, form management / rules, etc, QB has seen it fit that the native buttons (and their app pimping) MUST show.
I need to hide this ASAP, as this launch is already late. Help!!!
------------------------------
Meredith Moore
------------------------------