# Unique value for records
**URL:** https://community.thunkable.com/t/unique-value-for-records/2658905
**Category:** Questions about Thunkable X
**Created:** [October 23, 2023, 10:31am UTC](https://community.thunkable.com/t/unique-value-for-records/2658905 "2023-10-23T10:31:20Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@rusticone](https://community.thunkable.com/u/rusticone)
#### Post date: [October 23, 2023, 10:31am UTC](https://community.thunkable.com/t/unique-value-for-records/2658905/1 "2023-10-23T10:31:20Z")
Ciao!
I have to store an unique value for every record in my customer table.
I used this escamotage:
Is there a better way to do that?
Grazie
GM
---
### Author:  [@jared](https://community.thunkable.com/u/jared)
#### Post date: [October 23, 2023, 11:47am UTC](https://community.thunkable.com/t/unique-value-for-records/2658905/2 "2023-10-23T11:47:53Z")
That’s 1 way
Another would be hitting an api to generate a uuid and saving that to the record
> **[UUID Generator API | UUIDTools.com](https://www.uuidtools.com/docs)**
>
> Free UUID/GUID Generator API. Create single or bulk UUIDs. UUID v1, v3, v4, and v5.
```auto
https://www.uuidtools.com/api/generate/timestamp-first
```
---
### Author:  [@tthompson41231](https://community.thunkable.com/u/tthompson41231)
#### Post date: [October 23, 2023, 12:35pm UTC](https://community.thunkable.com/t/unique-value-for-records/2658905/3 "2023-10-23T12:35:27Z")
What structure are you looking for? Example: 7t89-G14L
---
### Author:  [@rusticone](https://community.thunkable.com/u/rusticone)
#### Post date: [October 23, 2023, 1:56pm UTC](https://community.thunkable.com/t/unique-value-for-records/2658905/4 "2023-10-23T13:56:38Z")
> [@tthompson41231](#):
>
> What structure are you looking for?
Thanks.
No matter about the structure…
But, in your example, how we can assure the univocity of the “account number”?
---
### Author:  [@tatiang](https://community.thunkable.com/u/tatiang)
#### Post date: [October 23, 2023, 2:49pm UTC](https://community.thunkable.com/t/unique-value-for-records/2658905/5 "2023-10-23T14:49:03Z")
A simple method would be to initialize a variable to 1 or 10000 or something like that and add 1 to it before you create each row. And then use that as the unique record ID.
---
### Author:  [@tthompson41231](https://community.thunkable.com/u/tthompson41231)
#### Post date: [October 23, 2023, 8:39pm UTC](https://community.thunkable.com/t/unique-value-for-records/2658905/6 "2023-10-23T20:39:21Z")
This is for creating a unique ID. For an account number use Tatiang’s method.
---
### Author:  [@vishruth-ram](https://community.thunkable.com/u/vishruth-ram)
#### Post date: [October 24, 2023, 7:11am UTC](https://community.thunkable.com/t/unique-value-for-records/2658905/7 "2023-10-24T07:11:44Z")
Best to use Supabase
---
### Author:  [@jared](https://community.thunkable.com/u/jared)
#### Post date: [October 24, 2023, 10:23am UTC](https://community.thunkable.com/t/unique-value-for-records/2658905/8 "2023-10-24T10:23:03Z")
Are you creating rows in a local table or a cloud environment? Most DBs have this value available on records already.
Just was wondering about my question there
---
### Author:  [@rusticone](https://community.thunkable.com/u/rusticone)
#### Post date: [October 24, 2023, 10:28am UTC](https://community.thunkable.com/t/unique-value-for-records/2658905/9 "2023-10-24T10:28:23Z")
> [@jared](#):
>
> cloud environment
Google sheets…
---
### Author:  [@system](https://community.thunkable.com/u/system)
#### Post date: [January 22, 2024, 10:29am UTC](https://community.thunkable.com/t/unique-value-for-records/2658905/10 "2024-01-22T10:29:01Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.