Forum Discussion
BabiPanjikar
Qrew Assistant Captain
To add to Marks response, you can achieve this with enhancements to marks response. I do use these kind of scenarios many of the times to control my tables uniqueness
Follow these steps:
1) Create a text field, e.g. Reference Key, type Text and set this as unique unique.
2) Create a formula text field CF-Reference Key = ToText(UserToEmail(User())) & ":" & ToText(Today()). Replace today with date field. I used UserToEmail becase name can be duplicate but email address cannot.
3) Use the form rule to update the Reference Key field with CF-Reference Key on record save.
If you are uploading the data using import functionality, make sure that your excel or csv file is having the concatenated value.
Happy Quickbasing.
------------------------------
Babi Panjikar
------------------------------
Follow these steps:
1) Create a text field, e.g. Reference Key, type Text and set this as unique unique.
2) Create a formula text field CF-Reference Key = ToText(UserToEmail(User())) & ":" & ToText(Today()). Replace today with date field. I used UserToEmail becase name can be duplicate but email address cannot.
3) Use the form rule to update the Reference Key field with CF-Reference Key on record save.
If you are uploading the data using import functionality, make sure that your excel or csv file is having the concatenated value.
Happy Quickbasing.
------------------------------
Babi Panjikar
------------------------------
DavidHalter2
4 years agoQrew Member
Hi Babi and Mark;
This was exactly what I was looking for at this point. I have another question, however. Is there a way to modify the error message so that it will make sense to the user? In the example above, the error message would be something like "You have entered a duplicate value in "Reference Key." I can't imagine what a user is going to do with that information! I would need them to know something like "Each user can only make one entry per day - go review your prior entries and adjust as necessary."
Is that possible? -- Maybe it would be accomplished with a Table Rule?
Thanks
Dave
------------------------------
David Halter
------------------------------
This was exactly what I was looking for at this point. I have another question, however. Is there a way to modify the error message so that it will make sense to the user? In the example above, the error message would be something like "You have entered a duplicate value in "Reference Key." I can't imagine what a user is going to do with that information! I would need them to know something like "Each user can only make one entry per day - go review your prior entries and adjust as necessary."
Is that possible? -- Maybe it would be accomplished with a Table Rule?
Thanks
Dave
------------------------------
David Halter
------------------------------
- MarkShnier__You4 years agoQrew LegendWhat is do is stupid simple. Instead of calling my unique field [Reference Key], I contrive a longer field name which is descriptive to the user when integrated with the standard Quickbase message.
[Sorry, but this combination of blah blah blah is already taken].
Just iterate on the field name words until you like the error message.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------