Hi David, The data grid is useful to generate samples or to create a fixed, rarely changing, list of say states that you can then lookup.
You can both connect it to the data and the data will flow onwards. You can even inject the metadata into them. But I'm not sure this will what you are looking for. The intention for pipelines is that they become operational. changing the "code" is an expensive exercise for any enterprise. Therefore, I encourage you to break down what you need into distinct pipelines so that you get to the end result without modifying the pipeline. E.g. 1 A pipeline to process your adjustments into a table (e.g. load sales rebates) 2 Another pipeline to process the bulk of the data (e.g. load sales revenue) 3 A third pipeline to process the sales after rebates Your end user can add to the rebates register as often as needed. Your revenue after rebates works every time. I hope this helps. PS. join the chat. Its a lot easier to help you there [ https://www.bizcubed.com.au/ | ] Diego Mainou Product Manager M. +61 415 152 091 E. [ mailto:[email protected] | [email protected] ] [ https://www.bizcubed.com.au/ | www.bizcubed.com.au ] [ https://www.bizcubed.com.au/ | ] From: "David McNeill" <[email protected]> To: "users" <[email protected]> Sent: Friday, 22 March, 2024 8:58:57 AM Subject: Data Grid edit The data grid component gives a simple table. However it's not connected to the field flow, so it can't be fed with data, or continue data onwards that arrives in the flow. We have a use case where users would like to edit some data in a table passing from a database into the flow. So enable/disable check boxes on certain rows. Is this possible with any other transform? Or could Data Grid be wired into the field flow? Is there any other ways people pick up row-level data edits within the hop gui/wui? (not parameters or variables) David
