# Is there a way to reduce the number of clicks counted when using an incremental button?

**URL:** <https://community.glideapps.com/t/is-there-a-way-to-reduce-the-number-of-clicks-counted-when-using-an-incremental-button/66811>\
**Category:** Ask for Help\
**Created:** [October 6, 2023, 6:06pm UTC](https://community.glideapps.com/t/is-there-a-way-to-reduce-the-number-of-clicks-counted-when-using-an-incremental-button/66811 "2023-10-06T18:06:23Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![redleu](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/redleu/32/63303_2.png) [@redleu](https://community.glideapps.com/u/redleu)\
**Post date:** [October 6, 2023, 6:06pm UTC](https://community.glideapps.com/t/is-there-a-way-to-reduce-the-number-of-clicks-counted-when-using-an-incremental-button/66811/1 "2023-10-06T18:06:24Z")

</div>

Hi all,

I’m creating a small application to manage a stock of products for a small bar association.  
I ended up using a + or - button to speed up the inventory / purchase / replenishment process.  
Before, when I needed to buy 5 cans of soda, I typed 5 in the corresponding form (= select the field, delete the old value, enter the new one, validate).  
Now, all I have to do is click several times to obtain the same result.  
The problem is that the cost of this little feature is 5 times higher than before.  
I was wondering if there was another way of achieving this solution, but counting only one click instead of X : the intermediates values have no value at all and should not be decremented from the number of updates of the month.  
Best regards  
Emmanuel

---

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [October 6, 2023, 8:57pm UTC](https://community.glideapps.com/t/is-there-a-way-to-reduce-the-number-of-clicks-counted-when-using-an-incremental-button/66811/2 "2023-10-06T20:57:43Z")

</div>

If you use the buttons on an edit screen rather than a details screen, then it will only count as one update. Only caveat, is that it’s two extra clicks (one to get into the edit screen and one to submit).

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [October 6, 2023, 9:02pm UTC](https://community.glideapps.com/t/is-there-a-way-to-reduce-the-number-of-clicks-counted-when-using-an-incremental-button/66811/3 "2023-10-06T21:02:05Z")

</div>

An Edit form would save on updates since it doesn’t register an update until you submit the form, so you could maybe do your increment inside the form.

Another option would be multiple sets of increment buttons with different values, such as 1, 5, 10 to increment faster.

Another option is that if users are not signed in, you can actually update user specific columns without counting against your update limit. When users are not signed in, then user specific data is only stored locally and not synced to glide servers. You could use this trick along with a button to first increment the number, and then transfer the value in the user specific column to a regular column via the button action.

Either way, an update to live data within the database will count as an update every time you update the values in that data, so your best options are to utilize something like the edit form, or use the loophole if users aren’t signed in, or change or app flow.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [October 7, 2023, 3:23am UTC](https://community.glideapps.com/t/is-there-a-way-to-reduce-the-number-of-clicks-counted-when-using-an-incremental-button/66811/4 "2023-10-07T03:23:16Z")

</div>

Another option could be to use a choice component instead of an increment action.

---

<div class="post-metadata">

**Author:** ![gannonatwork](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gannonatwork/32/91717_2.png) [@gannonatwork](https://community.glideapps.com/u/gannonatwork)\
**Post date:** [November 9, 2024, 4:26pm UTC](https://community.glideapps.com/t/is-there-a-way-to-reduce-the-number-of-clicks-counted-when-using-an-incremental-button/66811/5 "2024-11-09T16:26:15Z")

</div>

Stumbled upon this thread while looking for something else. All of the discussion here is related to an “external” data source and not GT or GBTs correct? If using GTs exclusively aren’t all table edits included — meaning they don’t consume updates? I want to make sure I’m not missing something.

> Making changes in Glide Tables does not consume updates, unless you make changes through Glide API or have an Enterprise plan.

Source: [Glide Tables | Glide Docs](https://www.glideapps.com/docs/essentials/data-sources/glide-tables)

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [November 9, 2024, 4:30pm UTC](https://community.glideapps.com/t/is-there-a-way-to-reduce-the-number-of-clicks-counted-when-using-an-incremental-button/66811/6 "2024-11-09T16:30:07Z")

</div>

Consider that this thread is a year old. The free edits were introduced less than a year ago.

---

<div class="post-metadata">

**Author:** ![gannonatwork](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gannonatwork/32/91717_2.png) [@gannonatwork](https://community.glideapps.com/u/gannonatwork)\
**Post date:** [November 9, 2024, 4:32pm UTC](https://community.glideapps.com/t/is-there-a-way-to-reduce-the-number-of-clicks-counted-when-using-an-incremental-button/66811/7 "2024-11-09T16:32:01Z")

</div>

Thx, @Jeff_Hager. I knew there was something I missed. Sometimes hard to keep up with the ever changing pricing, what counts as an update, etc. 🤣
