Forum Discussion
LauraThacker
5 years agoQrew Captain
Check that you do not have a Webhook, a QB Action or an Automation doing this. Your form rules only work when records are modified in the Form itself; not via an import. There must be another workflow process doing this.
- JamesTrory5 years agoQrew Assistant CaptainThat's what I had thought, that imports should not trigger form rules.
I have no Webhooks or Actions. I do have two Automations. One of them is set up to change a field called [Location Check-in] whenever the field [Location] is changed. This would include if [Location] was changed from "In Repair" to something else, which is also technically what the form rule is doing too in a very specific scenario. So there could be an overlap between the automation and form rule.
However, the automation is only set up to fire if a record is modified, not when it's added. I just did a new import of data and neither of the automations fired, but the imports did get the [Repair Check-in] field modified. It's so weird. - LauraThacker5 years agoQrew CaptainDisable your automation; and see if the import does the same thing. You may need to submit a support ticket if you are seeing data changes with no automations firing on new record imports.
- JamesTrory5 years agoQrew Assistant CaptainI was thinking the same. I disabled the two automations but the problem persists. I'll open a ticket with Quickbase. Thanks for your help.
- JamesTrory5 years agoQrew Assistant CaptainThe problem turned out to be that the [Repair Check-in] field, as a date field, had the box "today's date as default" checked in the field properties. This meant that new records automatically got today's date added into this field, even during import. The fix was just to uncheck this box. Problem solved.