Bundle (obvpm):
The Bundle (obvpm) node is designed to efficiently pack multiple values into a single wire, allowing them to travel together through a workflow. This is particularly useful in scenarios where you need to pass a collection of data through a Lazy Case Switch, which only carries one value per branch. The node simplifies the process by naming each field after its connected input, and it provides a configuration dialog for renaming and reordering these fields. The node is designed to be dynamic, starting with one empty input and automatically adding more as each is filled, ensuring there is always a spare input available. This functionality allows for seamless integration and unpacking at the other end using the Unbundle node, preserving the laziness of the workflow by only executing when the branch is selected.
Bundle (obvpm) Input Parameters:
in
This parameter represents the packed value that you want to look inside. It is a required input that expects a bundle, which is essentially a dictionary mapping of names to values. The purpose of this parameter is to allow the node to access and report on the contents of the bundle without unpacking or converting it, ensuring that the process is efficient and cost-free in terms of computational resources. There are no specific minimum, maximum, or default values for this parameter, as it is dependent on the data you wish to pack into the bundle.
Bundle (obvpm) Output Parameters:
out
The output parameter out is the packed fields represented as one value. This output is crucial as it allows the bundled data to be transmitted through the workflow as a single entity. The packed bundle can then be unpacked at the destination using the Unbundle node, which reads the names off the bundle to separate the values back into individual wires. This output ensures that the data integrity and order are maintained throughout the workflow, facilitating complex data handling and processing tasks.
Bundle (obvpm) Usage Tips:
- Use the configuration dialog to rename and reorder fields within the bundle to match your workflow requirements, ensuring clarity and organization.
- Take advantage of the node's ability to dynamically add inputs by filling each available input, which will automatically create a new spare input for additional data.
Bundle (obvpm) Common Errors and Solutions:
ValueError: expected a bundle (a name/value mapping) but got <type>
- Explanation: This error occurs when the input provided to the node is not a valid bundle, meaning it is not a dictionary mapping of names to values.
- Solution: Ensure that the input connected to the node is a properly formatted bundle. Check that the data structure is a dictionary with appropriate key-value pairs before passing it to the node.