# Thoughts About Row ID / Unique ID / Actions

**URL:** <https://community.glideapps.com/t/thoughts-about-row-id-unique-id-actions/25778>\
**Category:** Ask for Help\
**Created:** [April 19, 2021, 6:51pm UTC](https://community.glideapps.com/t/thoughts-about-row-id-unique-id-actions/25778 "2021-04-19T18:51:18Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![Mark](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mark/32/125_2.png) [@Mark](https://community.glideapps.com/u/Mark)\
**Post date:** [April 27, 2021, 7:47pm UTC](https://community.glideapps.com/t/thoughts-about-row-id-unique-id-actions/25778/21 "2021-04-27T19:47:15Z")

</div>

Both approaches should work. If they don’t then I’d consider that a bug.

---

<div class="post-metadata">

**Author:** ![Eitan](https://avatars.discourse-cdn.com/v4/letter/e/aca169/32.png) [@Eitan](https://community.glideapps.com/u/Eitan)\
**Post date:** [July 9, 2025, 11:22pm UTC](https://community.glideapps.com/t/thoughts-about-row-id-unique-id-actions/25778/22 "2025-07-09T23:22:33Z")

</div>

I realise this is an old thread but just wondering if there is a performance difference between these two approaches?

In my glide big tables, if I have a relation between two tables, parent and child, with a Unique Identifier Special Value in a text column of both of them or with a rowID from the parent table to relate to the child table?

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [July 10, 2025, 12:44am UTC](https://community.glideapps.com/t/thoughts-about-row-id-unique-id-actions/25778/23 "2025-07-10T00:44:21Z")

</div>

There shouldn’t be a difference in performance. Usually I just use rowIDs, but I haven’t had a case like what V88 suggested here recently.

> [@V88](#):
>
> - It needs to create a row in a “parent” sheet
> - It then needs to create a related row in a “child” sheet

 ![CleanShot 2025-07-10 at 07.43.04](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/9/f/9fea945897273fabf859a2de81f64adafea2a98f.png)

Nowadays, you do have the action to write a rowID somewhere after an Add Row action. You can write it to a User Profiles column, and then reference that column in the “child” Add Row.

---

<div class="post-metadata">

**Author:** ![Eitan](https://avatars.discourse-cdn.com/v4/letter/e/aca169/32.png) [@Eitan](https://community.glideapps.com/u/Eitan)\
**Post date:** [July 10, 2025, 12:47am UTC](https://community.glideapps.com/t/thoughts-about-row-id-unique-id-actions/25778/24 "2025-07-10T00:47:31Z")

</div>

great thanks! yeah that write row ID to is great, the problem is that I’m using the glide API to bulk add rows, so many different parent rows with many different child rows, might see if I can use the API response to query the right rows etc

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [July 10, 2025, 12:48am UTC](https://community.glideapps.com/t/thoughts-about-row-id-unique-id-actions/25778/25 "2025-07-10T00:48:35Z")

</div>

You would have to loop on the parent level to be able to do the same thing.

E.g: Loop #1 - Add parent: the API returns a rowID in the response - Use that for the loop on child rows.

Then loop #2 etc.

---

<div class="post-metadata">

**Author:** ![Eitan](https://avatars.discourse-cdn.com/v4/letter/e/aca169/32.png) [@Eitan](https://community.glideapps.com/u/Eitan)\
**Post date:** [July 10, 2025, 1:02am UTC](https://community.glideapps.com/t/thoughts-about-row-id-unique-id-actions/25778/26 "2025-07-10T01:02:28Z")

</div>

yep sounds like a plan! thank you

[Previous page](https://community.glideapps.com/t/thoughts-about-row-id-unique-id-actions/25778.md?page=1)
