Using uuid as primary key on tables breaks reference fields

I’m encountering the issue again. It’s happens when adding a reference field while using the Advanced view in the Database Manager. Advanced view exposed some properties (allow null, unique, & primary key) in the field properties section that do not show in Basic view.

Sequence of events.

  1. I tried to add the field in Advanced view and got the error
  2. Switched to Basic view and it worked.

But here’s the weird part. I then switched back to Advanced view to attempt to add another field and the field properties no longer showed the extra properties (allow null, unique, & primary key), but I still received the error when I tried to apply the database changes.

Fixed in Wappler 5.3.3

This topic was automatically closed after 26 hours. New replies are no longer allowed.