Forum Discussion
_anomDiebolt_
11 years agoQrew Elite
>Is there any way to get around this limit?
Use script and you will not hit these arbitrary limits.
Use script and you will not hit these arbitrary limits.
- PaulVorster19 years agoQrew CadetCan you provide some examples, or assist in how you processed scripts?
- _anomDiebolt_9 years agoQrew EliteAsk a new question and include a description of exactly what behavior you want irrespective of the limitation on the number of derived fields.
In a nutshell we would use jQuery to detect various events you want to respond to and in reaction to these events emulate in code the user clicking of the section to toggle the visibility:
$("#sect_s1Header span.sectionTitle").click();
This approach is the least invasive of the QuickBase code since we are not directly manipulating the visibility of DOM elements but rather emulating user input.
This approach can detect a much wider set of events then are hardcoded into the QuickBase form rules. - BenjaminLarrabe9 years agoQrew CadetHi Dan, I'm confident you can help me on a similar issue here :)
I have two fields on a form, that if changed, need to pop up a message (display message in form rules) and then require a specific field. This needs to happen if either or both fields change. Right now I'm using a webhook to push the current value of the field into another 'check' field, so that when the record is edited next time, the current and 'check' values won't match, causing the form rule to fire. However, I'm running into the max limit on derived fields due to all the other rules the client has in place. I'm happy to provide further info as needed. Thanks in advance Dan!