so suppose i have table user and table clinic, i should create an enum-{OS} in user say doctor / patient that is a column and a colum in clinic type enum-{OS} for hospital / clinic and any table with an OptionSet
Hey there - to create the user from Bubble -> Xano, it follows the same idea as the login flow @9:17. I would approach this with the Bubble user being created first, and once the Bubble user is created, you can then create the Xano user. The Xano user can then be passed the bubble user's id if necessary, or you can update the current user in Bubble with the id from the response received from Xano. Since the Bubble platform leverages the current user, I would want to first make sure the Bubble user account can be created; if it can, then we create the Xano user. Let me know if this makes sense or if I can clarify!
Hey, great question! Options sets within Bubble are super powerful and can be reused throughout the app. If we are expecting to use the same set of options, we can implement something similar within Xano on the data table level. We'd create a new column of type 'enum' and then set the values that we want to use. Anytime we are writing to this table, we can supply a value as found in our enum list, and the record will update with that value. If we supply a value to our enum column that wasn't defined (that is, we didn't add it as an option within our enum column), then an error will be thrown. We may need to make a video on enums and option sets! Let me know if I can clarify!
Thank you!
you saved me
so suppose i have table user and table clinic, i should create an enum-{OS} in user say doctor / patient that is a column
and a colum in clinic type enum-{OS} for hospital / clinic
and any table with an OptionSet
What I am not understanding is that if we are logging in with bubble, what is the workflow for creating this user In Xano.
Hey there - to create the user from Bubble -> Xano, it follows the same idea as the login flow @9:17.
I would approach this with the Bubble user being created first, and once the Bubble user is created, you can then create the Xano user. The Xano user can then be passed the bubble user's id if necessary, or you can update the current user in Bubble with the id from the response received from Xano.
Since the Bubble platform leverages the current user, I would want to first make sure the Bubble user account can be created; if it can, then we create the Xano user.
Let me know if this makes sense or if I can clarify!
how can i define option sets in xano
Hey, great question! Options sets within Bubble are super powerful and can be reused throughout the app. If we are expecting to use the same set of options, we can implement something similar within Xano on the data table level. We'd create a new column of type 'enum' and then set the values that we want to use. Anytime we are writing to this table, we can supply a value as found in our enum list, and the record will update with that value. If we supply a value to our enum column that wasn't defined (that is, we didn't add it as an option within our enum column), then an error will be thrown. We may need to make a video on enums and option sets! Let me know if I can clarify!
Detailed step by step tutorial would be much better, this didn't covered every step and hard to understand for beginners.