So I am trying to come up with the right condtional statement here but I am having trouble.
going by what you said around 2:31 in the video,
maybe you should try adding a “created by <> current user” in the constraint
I’ll try that. I think I didn’t have a grasp on what “<>” does but I’ll give it a try.
the <> is almost equivalent to “not equal to” operator
For example saying “where current user 's age <> available ages list” will return ages that are not the current user’s age
I don’t know if I explained that right😂
I think bubble docs does the job better
Lol it’s make sense.
1 Like
@pelumioladipo312 and @geesonofgee yep it worked. Thanks!
@pelumioladipo312 @geesonofgee I did run into one problem. It is looking for the word to be the exact match. So just a simple lower case in the word “test” does not match what is in the data base “Test”.
I can make the first part of the condition “capitalized words” or upper case to try to match it. But I cannot control the list of words found and make them all capitalized or uppercase. Hopefully that made sense, I added photos below.
@geesonofgee @pelumioladipo312 Nvm I thought of the solution as soon as I sent this lol. Thank you both!
Just made a separate RG with the list of text and made it uppercase. Then had the input text uppercase and compared it to the RG list.
1 Like
You tried
But best practices, convert every input value to lower case before sending to the database and wherever it’ll be displayed, just use the operator to capitalize it on the frontend
of course except for cases where the value needs to remain the exact way
hmm you know that sounds better. making it all lower case before being saved.