# Changing version counter during stage

**URL:** <https://www.finalbuilder.com/forums/t/changing-version-counter-during-stage/5480>\
**Category:** Discussion\
**Created:** [May 11, 2016, 2:22am UTC](https://www.finalbuilder.com/forums/t/changing-version-counter-during-stage/5480 "2016-05-11T02:22:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![christian.leh](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/c/67e7ee/32.png) [@christian.leh](https://www.finalbuilder.com/forums/u/christian.leh)\
**Post date:** [May 11, 2016, 2:22am UTC](https://www.finalbuilder.com/forums/t/changing-version-counter-during-stage/5480/1 "2016-05-11T02:22:42Z")

</div>

Is its possible to set the version counter using an action during a stage?

---

<div class="post-metadata">

**Author:** ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)\
**Post date:** [May 12, 2016, 2:13am UTC](https://www.finalbuilder.com/forums/t/changing-version-counter-during-stage/5480/2 "2016-05-12T02:13:55Z")

</div>

Hi Christian,  
  
You cannot update the version counter (also known as build number) via an action. The only way this can be changed during the build is via the “option reuse build number if previous build was discarded, stopped or failed while initialising” option in the configuration details.  
  
You can, however, update the version string, $Build.Version$, via a [Set Build Version](http://wiki.finalbuilder.com/display/continua/Set+Build+Version+Action)&nbsp;action.&nbsp;The version string can also be based on a separate counter variable, which can be incremented using the [Set Variable Action](http://wiki.finalbuilder.com/display/continua/Set+Variable+Action),&nbsp;and persisted at the end of the stage or build using the [Persist Build Variables build event handler](http://wiki.finalbuilder.com/display/continua/Persist+Build+Variables). If you do this, you will need to manage concurrency issues, either by using the “Do not persist if modified” option of the build event handler or by using Shared Resources to prevent multiple concurrent builds.  
  
If this doesn’t help, let us know your use case and we’ll look into whether we need to make any improvements.&nbsp;
