# Xano UUID primary key issue **URL:** \ **Category:** Bugs\ **Created:** [September 30, 2024, 4:41pm UTC](https://community.noloco.io/t/xano-uuid-primary-key-issue/1282 "2024-09-30T16:41:43Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![lukebranford](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/lukebranford/32/32_2.png) [@lukebranford](https://community.noloco.io/u/lukebranford)\ **Post date:** [September 30, 2024, 4:41pm UTC](https://community.noloco.io/t/xano-uuid-primary-key-issue/1282/1 "2024-09-30T16:41:43Z")
Xano now allows you to use a UUID as the primary key for a table. I created a new table using UUID as the primary key and syncs to Noloco OK, but if I try to change any data on the Noloco end, it will not sync back to Xano and eventually throws an error. If this could be fixed it’d be amazing! Note that I truly believe that Xano and Noloco combined offers the most powerful and robust set-up available, so if you’ve searched for Xano and come across this post, feel free to DM me if you want any advice on whether it’s suitable for your project (no charge!) 🙂 ---
**Author:** ![lukebranford](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/lukebranford/32/32_2.png) [@lukebranford](https://community.noloco.io/u/lukebranford)\ **Post date:** [September 30, 2024, 4:57pm UTC](https://community.noloco.io/t/xano-uuid-primary-key-issue/1282/2 "2024-09-30T16:57:55Z")
Info in the Xano docs is here: [Database Tables | Xano Documentation](https://docs.xano.com/database/database/how-to-add-a-database-table#adding-a-new-database-table) ---
**Author:** ![lukebranford](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/lukebranford/32/32_2.png) [@lukebranford](https://community.noloco.io/u/lukebranford)\ **Post date:** [November 13, 2024, 10:27am UTC](https://community.noloco.io/t/xano-uuid-primary-key-issue/1282/3 "2024-11-13T10:27:53Z")
@darragh Morning! I know you got very close to a fix for this, which is hugely appreciated! Any progress on getting it tested and pushed to live? Is one of the last remaining issues with my app! Thanks 🙂 ---
**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\ **Post date:** [November 13, 2024, 10:39am UTC](https://community.noloco.io/t/xano-uuid-primary-key-issue/1282/4 "2024-11-13T10:39:25Z")
@lukebranford - we’re hoping to role this out today actually ---
**Author:** ![lukebranford](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/lukebranford/32/32_2.png) [@lukebranford](https://community.noloco.io/u/lukebranford)\ **Post date:** [November 13, 2024, 10:41am UTC](https://community.noloco.io/t/xano-uuid-primary-key-issue/1282/5 "2024-11-13T10:41:13Z")
Awesome, thank you! 🤘 ---
**Author:** ![lukebranford](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/lukebranford/32/32_2.png) [@lukebranford](https://community.noloco.io/u/lukebranford)\ **Post date:** [November 14, 2024, 12:48pm UTC](https://community.noloco.io/t/xano-uuid-primary-key-issue/1282/6 "2024-11-14T12:48:33Z")
@darragh Been testing this out and all working really well, thank you! 🙏 Shame there’s no way to do a 1:1 relationship from Xano, think it can be done via the metadata API using indexing, but one for another day! ---
**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\ **Post date:** [November 14, 2024, 1:01pm UTC](https://community.noloco.io/t/xano-uuid-primary-key-issue/1282/7 "2024-11-14T13:01:37Z")
Delighted to hear that @lukebranford ! Thanks for following-up Is there really no way of doing that? I suppose it is largely application logic rather than a DB constraint ---
**Author:** ![lukebranford](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/lukebranford/32/32_2.png) [@lukebranford](https://community.noloco.io/u/lukebranford)\ **Post date:** [November 14, 2024, 1:49pm UTC](https://community.noloco.io/t/xano-uuid-primary-key-issue/1282/8 "2024-11-14T13:49:26Z")
There doesn’t seem to be an easy native way to mark the linked record column to be unique, not as far as I can tell anyway. So I tried updating it in Noloco but it just kept changing back! So hacked my way round it by creating another auto-link field in Noloco which is set to 1:1, not ideal as feels a bit messy, but all my logic falls down otherwise!