Qrew LegendIn general you can use pipelines to automate functions but without knowing more about your app and it's purpose, on the surface I would have to question why you need to increment counters in another table.
For example if you wanted to know how many times a particular record was created where a certain look up field was chosen, you can easily run reports for that or create summary fields for that.
So I would just caution you that maybe you want to be using summary fields and not fancy automated processes using pipelines
Hello Mark,
Thank you for your insight. I'll take a look into pipelines more. The main purpose of the automation is to track the number of times a tool undergoes a cycle for our process.
I am using an existing record in the reference table to represent an "object" with its "fields" as properties of sorts. When a record in the operations table is modified, the reference/"object" table receives a trigger from operations to increment its [Cycle #] field depending on the reference field changed.
Let me provide a flow chart that can shed light on my line of thought.
Qrew LegendCan you tell me the names of your tables and their relationships? Which is the One side and which is the Many side?
For example one Machine has many Cycle records?
Above is the basic overview of what I'm trying to achieve. I've tried one-to-many and many-to-many relationships without using the pipelines feature yet. The tables pictured both have many-to-many relationships as I was testing reference field functionality and trying to use formulas/form rules to increment some numeric field to write to the Boat [Cycle #] field.
Please let me know if you need anything else.
