My Issue: The app has a “multi-step” form with “page views” controlled by visibility conditions (Progress = empty, 1, 2 or 3) and buttons (Next and Back) with an increment number action. It has been working flawlessly for years until a few days ago.
The “Next” button should be visible by default when the form is open but it’s not visible. The Next button’s visibility is set to show when “Progress” is empty OR “Progress” is less or equal to 2. I duplicated the button, removed the visibility conditions, and the button is still not visible.
I tried starting from scratch by adding a new button. The button was visible until I add the increment number action. Possibly a bug since there is no conditional visibility logic applied to the button.
This is a classic app on a legacy non-profit plan, which doesn’t include support and I can’t get a support link. So, any community help or insight is appreciated.
I used the simple, built in action because it’s only purpose is to hold a temporary value (1-3) that controls content visibility based on conditional logic.
As suggested, I configured an action to increment number and cannot select the destination table as the data source. Rather, the data source is locked to another table that is used to display an inline list of projects (users open the form from the detail view screen). The message below the Data Source suggests that I could select a different table if it wasn’t used by more than one component. However, the button (i.e., USED BY) is one and the same. Either way, the button is not visible after I Save and close the action window (I did add the appropriate “Progress” column to the Data Source). If the custom action did work, it wouldn’t be compatible with the component visibility options connected to the destination table.
It been a while since I’ve worked inside the Design view for this or similar components. In the past, I recall that actions were applied to the destination table.
I also tried using Action Text to handle the increment action. The text is visible but the action is not responsive.
As a quick hack, I added a rating component that writes to the Progress column. It works but it’s not an intuitive or long term solution for app users.
Thanks for the suggestions. I have used the custom form method to build more complex forms within this app. A valid solution, but for my use case I’m hesitant to add more relations and actions to handle something that should be so simple.
To keep the existing forms working, my solution was to emulate pagination with a choice component (segmented or chips), which uses a lookup list (1,2,3) to write values to the Progress column. The components within the “page view” have visibility conditions (e.g., show component when Progress equals 1).
I refreshed the page to get the latest Glide updates and the bug has been fixed; the original buttons within the form are visible and the increment number actions work.
That’s … weird. I don’t know if any behind-the-scenes structures they build in the new Glide has affected the classic Glide. Still, glad it’s sorted for you!
I refreshed the page to get the latest Glide updates and the bug has been fixed; the original buttons within the form are visible and the increment number actions work.