I've been playing with doing some recipe management via Ignition lately and while I can get simple recipe types to work fine with a standard transaction group I'm having a hard time wrapping my head around doing more complex forms of recipes. Mainly, recipes that can have varying numbers of steps. For example, some of our equipement has multiple steps (or rows) consisting of multiple functions (columns). Something like this:
So, the number of steps on a recipe can change and the information associated with that step can also change. This makes every recipe basically a table in the database. Depending on the equipment we can have many many recipes.
I’m not sure what the best way to handle this in Ignition would be? It doesn’t seem like something a normal transaction group would be able to handle (but I’m not very fluent with transaction groups so I may be wrong). Is there a transaction group that handles entire tables? I’m just wondering if anyone else has run into something similar and would be willing to give me some insight into what to do with this situation. Thanks!