Setting range limits on numeric field entries
Hello everyone, I am new to quickbase app development. I have a data entry form for users to fill out that contains numeric fields for Days Hours and Weeks. I would like a way to limit the entry for those fields. I.E the maximum entry for the hours field would be 23, maximum number for days field would be 6. Is there a way using a traditional numeric entry field or a formula to prevent a user from entering a number that falls outside of a desired range? #numeric field ------------------------------ Ashleigh Wansbrough ------------------------------126Views0likes1CommentCustom Data Rules to protect data import
I enjoyed Daniel Callahan's presentation on data validation using custom data rules during the Virtual Empower 2020. I have deployed some of the concepts he presented in a current project. The portion of the presentation that most intrigued me was brushed through but not covered in depth. Daniel mentioned using custom data rules to validate data before importing into the table. Has anyone used custom data rules to validate data before it is imported? I am comfortable with Quick Base formulas but am not sure how write a formula that will look at data during the import process. Does anyone have a suggestion for how best to accomplish this validation process? ------------------------------ Paul Peterson ------------------------------116Views0likes2CommentsRestrict data entry in numeric field to be less than a certain value
Without using a Multi-Choice text field, is there any way to limit the values entered by user to be whole numbers between 0-11. We have users who are entering total inches into a field that is meant for "remaining" inches (20 ft, 5 in some users are entering 245 in the inches field). I could set up rules that display message if entered incorrectly but some users use Grid Edit and not the Form. Or check if Ft is left blank but I am looking for something that prevents the error in the first place versus QCing data later. ------------------------------ Ruby Kapil [email protected] Wi-Finity, Inc ------------------------------100Views0likes4CommentsShare Table Permissions
I have a share table that displays and allows edits of the child records on a parent table. I would like to lock the field where a role can add but not modify. I have tried a number of different restriction by role but it still allow the role access to modify on the shared table. ------------------------------ Scott Talarico ------------------------------100Views0likes1CommentGrid Edit overriding Form Rules
Hi All, I have a form rule that basically shuts down all fields on a record once it has been checked, making it view only to the end user. Unfortunately, we have users that like to update and/or copy their records in Grid Edit, and as we all know, Grid Edit overrides form rules. Without excluding these checked records from a Grid Edit report, are there any workarounds for displaying records in Grid Edit but keeping them view only? ------------------------------ Urs. ------------------------------97Views0likes3CommentsPop-up or red-flag when a user incorrectly enters an email address; auto-corrections for   errors?
Hi hi folks, Two questions: One of our forms that staff input data into collects the email addresses of the people they communicate with so we can send them a survey at the end of the month. We're finding that periodically we get typos - someone rushes, or copies and pastes and accidentally includes spaces or special characters or forgets to complete the email address altogether. While the field "type" IS email - there doesn't seem to be any built in way to flag "hey - what you put in doesn't equal a valid email address". The field is used in a dozen different reports, forms, and I run pipelines off of it, so I don't know if replacing it with a different field would make sense. Is there a way to write a formula text field immediately after it that says - if Field ID 70 doesn't equal a valid email address, display warning? Also - we don't 'require' it to be populated every time a user completes the form, as we don't necessarily collect email addresses every time we speak to a person. Periodically a user will copy/paste into a form, or will input a special character and we get errors like (I believe that's for spaces, quotation marks I think are different?) - Is there any way to essentially search our Quickbase Realm for these errors and either delete the offending characters or change them to something acceptable (depending on the error code - I think there are different ones depending on the special character)? I'm thinking I could possibly write a Pipeline to do this, but I'm not quite sure if it's a reasonable thing to do or not. Any creative ideas on how to address these two things? Thank you! Jen ------------------------------ Jennifer Juhasz ------------------------------90Views0likes1CommentAny way to automate firing of form rules?
I know this is probably a no. But is there a way to push form rules to fire automatically without putting the record in edit. I am used to workflows in salesforce which fire in the background. Example would be. I have Accounts and Invoices. I have a field on accounts that shows how many days since last the last invoice. I have a form rule that is setup to change the status of the account to lapsed if the number of days is greater than 20. The change will not happen currently unless you click edit on the account. Any help would be greatly appreciated.89Views1like4CommentsWriting a input formula that only allows a specific format
Hello, I would like to write a formula for a input field that only allows input of an IP address. What is the best field type to use for this? Thanks! ------------------------------ Phil Heron ------------------------------88Views0likes1CommentLimiting the number of child records that can be created
I have a child table that a user is only meant to be able to make 1 record for each parent. Is there a way to limit the user's ability to create more than 1 child record? ------------------------------ Chris Swirtz ------------------------------85Views0likes2Comments