Forum Discussion
JohnHarr
7 years agoQrew Trainee
I forgot that detail. It is a required field. Leaving it blank would cause an issue.
- ChuckGrigsby7 years agoQrew CadetIs it possible you could just require it after some other condition like if some field is not blank or some value? If quickbase doesn't register a new user until they actually login perhaps you could create a new user but never register then use that as the user? Not tested of course so not sure if it'll work.
- JohnHarr7 years agoQrew TraineeThis might actually work. I can create a user in the application called "unkown@url.com" When that is selected, it will indicate that the record needs to be properly assigned.
- ChuckGrigsby7 years agoQrew CadetLet me know if it works, good luck!
- RohitAgarwal7 years agoQrew CadetCreating unknown user it's like wasting your user licenses.
- ChuckGrigsby7 years agoQrew CadetThe theory is that it's not used until the person logins to the app for the first time. He could check his user count, add the fake user again to test that though.
- RohitAgarwal7 years agoQrew CadetI think we can approach in this way also.
What do you think?
1- make this field not required.
2- When you save a record without entering the value in this field at that time Fire a webhook and see if the field is blank. If it is blank fill it with the default value.