Any way to automate firing of form rules?

I agree with your observations. I look at it as you have to work with the completely unknown ovoid shaped yellow object with a pleasant smell that burns if applied to paper cuts in order to create a pleasing substance that satisfies others.

You can leverage Webhooks to handle some form rule like functionality but you have to know how to write the code, which is easy once you learn how. You can also place controls on fields displayed in Grid Edit by making a separate field that is not "the" lookup field but a formula copy of "the" lookup field. This solution only allows the User to view data and cannot modify "the" field except in the form, I call it abstraction. Duplicates of the same data, shown in different locations. This gets tricky once permissions and Roles come into play. Then Webhooks, separate the permissions and a field you want to hide from input but still want to share the data in the field with the User.

Other options are to disable grid edit and create a path for the User only through forms. If there is a must have use case, separate the data entry/change for that data into a separate table and then do some creative relationship or Qunect with SSMS or PowerBI. Finally you can use something like Workato that on schedule searches a table for a change or boolean and triggers a recipe to do some logic.

Interesting, thing. Workato used to trigger based upon when a formula field updated without User intervention(edit). So if you had a check box formula field that became true 24 hours after Date created, it would trigger a recipe. I used it for about 1 year until more recently that functionality/bug was removed so now it has to be done on a schedule where Workato searches the table for certain boolean markers and then does something.

I see Quickbase as a database/software development environment. Use field properties as software logic, create more than one field based upon some logic and then show/hide different fields depending on which is true and what you want the User to do. Use Webhooks to move data around. Table Rules are also powerful but limited.

Ben's problem sounds like the Solution is a Workato recipe.

Jim

------------------------------
Jim Harrison
------------------------------