New Style Forms in Mobile - native Save button keeps user on Add Record form
Has anyone else run into this issue? We created a new style form for desktop and applied it to mobile as well. On desktop, when a user saves a new record by selecting the "Save" option (not Save and new or any of the other available options), they will re-direct as normal. But on mobile, when the user clicks the native save button that follows them down the form, the record saves, a "record saved" message briefly shows at the top of the screen, and then the user remains on the Add Record page with all of the information they just recorded. If you do not notice the message that flashes on and disappears from the screen, it appears as though no action occurred, which naturally makes a User want to click the save button again. This is causing many duplicate records to be created and causing confusion for users as they are unsure with what to do next. We created a work-around by adding a Rich Text field that will complete the save action and redirect the user as intended, but we are unable to completely remove the native save button which lingers. Does anyone know of a fix in the works for this, or even a way to completely hide the native save button from the form?17Views0likes2CommentsDisappearing Native Tool Bar on Mobile
Anyone else run into the native tool bar on the bottom of mobile (where it shows My Apps, App Home, Back, etc), will sometimes disappear on mobile? I'm pretty sure I have solved the mystery and will post back with the solution when I am sure, but wondering if others have run into this.18Views0likes0Comments%%rid%% has ceased working on mobile - be advised
In case others haven't realized, the %%rid%% has stopped working on mobile. If you attempt to use a button on mobile in add mode that is utilizing this feature, the URL button will not function at all, and will not even attempt to execute your URL. Customer support as recognized this and states they are working on it. However, they have not told me any more information (such as if they have prioritized it, or is in their bucket of working on but will never actually fix). This has been broken for about 4 days so I do not think it is a priority for them. Just want to be sure everyone else knows as well. It's dissapointing, I use this feature in probably 20 or 30 buttons so now I will need to take probably an entire day to find them all and come up with a work around. I do have one work around that uses a helper table and an action to always find the max record ID. If anyone is interested they can let me know. Though with actions going away, even that will now become difficult. Sadly, Quickbase is finding ways to make developing harder and harder.Solved97Views0likes4Comments