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? #numericfield ------------------------------ Ashleigh Wansbrough ------------------------------
Grid 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. ------------------------------Limiting 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 ------------------------------
Preventing date selection for dates before the current date
Hi, I have a date field that our users are selecting dates that are in the past and it should always be in the future/today. I didn't see any settings to prevent this from happening. Is there a formula or a setting to prevent a past date for just one field? Thanks! ------------------------------ Catelyn Atkinson ------------------------------Help with a custom data rule formula
I'm trying to add a custom data rule for a table that will come up with a message for the user. Can you help me figuring out whats wrong with this formula? If ( [Not available] = true, "Please check that your items are available during your event dates. Thank you!" ) The [Not available] field is a lookup field, so I'm trying to say that if it contains any dates, to show this message. However, I'm getting an error that says that on the left hand side of the operator "=" is of type textlist while the expression true on the right hand side is of type bool. The operator "=" cannot be used with these types of expressions. Thanks! ------------------------------ Megan Hardison ------------------------------
Set custom table rule to prevent deletion of a record if child record count is greater than 0
I have a Processes table (parent) and a Tasks table (child). In my Processes table, I have a count of completed child tasks that I'm keeping track of to display to users and for an automation I added. Is there a way to write a custom data rule for the Processes table where it looks for the count of tasks, if the number is greater than 0, show a warning message and do not allow the user to delete the record? Right now, I have a custom table rule that reads: If ( [Number of Completed Tasks] > 0, "There are currently " & [Number of Completed Tasks] & " completed tasks that belong to this process. If you'd like to delete this process, please delete all completed tasks for this process first." ) But I'm not sure how to get this system to stop the delete process if the Tasks condition is true. ------------------------------ AR ------------------------------Custom Data Rules and Lookup/Summary fields
Is there anyway to get around the limitations with custom data rules and summary and lookup fields? For example I have a Task table that has the projected number of hours a task should take. I then have an assignment table where actual assignment hours are billed against the projected. I was trying to have the system restrict users from assigning any hours that went over the projected hours. However the issue I am running into is since the projected hours is a lookup from the task table, the custom data rules are not firing correctly. Wondering if anyone else has run into this problem and figured out a work around? ------------------------------ Wallace (DHS) ------------------------------
