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!)
@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
@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!
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!
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!