# Global varaibles auto update
**URL:** https://www.finalbuilder.com/forums/t/global-varaibles-auto-update/7781
**Category:** Discussion
**Created:** [April 16, 2026, 1:09pm UTC](https://www.finalbuilder.com/forums/t/global-varaibles-auto-update/7781 "2026-04-16T13:09:42Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@k3tchup](https://www.finalbuilder.com/forums/u/k3tchup)
#### Post date: [April 16, 2026, 1:09pm UTC](https://www.finalbuilder.com/forums/t/global-varaibles-auto-update/7781/1 "2026-04-16T13:09:42Z")
We use global (server) variable for storing possible test scenarios which is shared among multiple configurations. We always have to update this list manually when a new scenario is created. I wonder if there is or could be a way to look up current list, similary as a property collection works.
Ex. read file on Continua server and store it in a variable
---
### Author:  [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [April 16, 2026, 11:03pm UTC](https://www.finalbuilder.com/forums/t/global-varaibles-auto-update/7781/2 "2026-04-16T23:03:41Z")
Hi Michal,
Continua doesn’t currently provide built-in actions, event handlers, or property collectors for reading variables directly from files.
However, it is possible to read values from a file and set a Continua variable via a FinalBuilder project (which includes specific actions for interacting with Continua). Alternatively, you can emit custom log messages (see [Continua CI Custom Log Messages documentation](https://docs.finalbuilder.com/ci/1.0/extending-continua-ci/custom-log-messages.html)) from a PowerShell script, batch file, or executable to populate variables during a build.
If you’re able to share a bit more detail about your use case - for example, the file format, whether you need the full contents or just part of it, and how the variable is being used - we can take a closer look at whether there’s scope to support this more directly.
Regards,
Dave Sparks
---
### Author:  [@k3tchup](https://www.finalbuilder.com/forums/u/k3tchup)
#### Post date: [April 17, 2026, 8:10am UTC](https://www.finalbuilder.com/forums/t/global-varaibles-auto-update/7781/3 "2026-04-17T08:10:13Z")
During the build is not sufficient as we need it in the build queue dialog.
The use case is that we have couple of configurations that as a input have a dropdown selection which is populated by a global CI variable, so it’s always the same in all of those configurations.
The variables is a list of names of test cases:
```plaintext
testcase1
testcase2
...
```
To update this variable, we need a person with admin privilages to update global variables.
So the best flow would be that this would be updated automatically. Either by a separate conifguration which download repository and generates a new list or by reading a file from a network location or something similar.
---
### Author:  [@k3tchup](https://www.finalbuilder.com/forums/u/k3tchup)
#### Post date: [April 17, 2026, 8:26am UTC](https://www.finalbuilder.com/forums/t/global-varaibles-auto-update/7781/4 "2026-04-17T08:26:09Z")
Hmm, I just looked through Set Variable action and it seems it might have what I need:
I will try that 😛
---
### Author:  [@k3tchup](https://www.finalbuilder.com/forums/u/k3tchup)
#### Post date: [April 17, 2026, 9:51am UTC](https://www.finalbuilder.com/forums/t/global-varaibles-auto-update/7781/5 "2026-04-17T09:51:12Z")
So I have a problem, I am trying to append to new variable via script using:
@@continuacontinua[setVariable name=‘{name}’ value=‘{value}’ appendOrIncrement=‘true’ updateBuildVariable=‘true’]"
But on execution the variable is set, not appended:
`Build variable 'new_list' has been set to 'ALL'.`
I got around this by setting the variable with table joined with escaped new line character.
And this works ! 😛
---
### Author:  [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [April 17, 2026, 1:07pm UTC](https://www.finalbuilder.com/forums/t/global-varaibles-auto-update/7781/6 "2026-04-17T13:07:37Z")
Hi Michal,
Great to hear you found a workaround.
We’ve confirmed this is a bug in the `setVariable` custom log message - the appendOrIncrement` parameter is not being passed through correctly.
We expect to release an update with a fix early next week.
Thanks for reporting this.