Tag From

This function block provides a named data anchor that participates in inter-block variable exchange. Give the block a unique tag name and use corresponding Tag To blocks elsewhere to send values into this anchor. The block accepts a generic value and makes it available under the chosen tag name for the running scenario.

📥 Inputs

Generic Accepts any kind of value (number, text, image, list, etc.) to be associated with the tag.

📤 Outputs

This function block does not have direct outputs.

🕹️ Controls

Tag Name Enter a short, unique string to identify this tag. This name is used by Tag To function blocks to route values to this anchor.

(hint) Make sure each Tag Name in your project is unique — duplicate tag names are detected and flagged by the block.

🎯 Features

• Named data anchor for passing values between different parts of your setup.

• Prevents duplicate tag names in the same project to avoid accidental overwrites.

• Guards against a Tag To block attempting to send data to the same block that defines the tag (self-send protection).

• Simple line-edit control for quick naming and identification.

📝 Usage Instructions

1. Drag a Tag From block into your workspace and enter a unique Tag Name.

2. Connect a data source (any block producing a generic value) to the Generic input if you want to provide an initial or fallback value.

3. Place a Tag To block elsewhere, set its target to the same Tag Name, and connect the value you want to transfer. The two blocks together exchange data using that name.

4. Use other referencing blocks such as Data Read Global or Data Read Local to read shared values in more complex setups.

📊 Evaluation

During run, the block participates in the scenario’s variable exchange. It ensures tag name uniqueness and validates cross-block tag operations before the scenario proceeds.

💡 Tips and Tricks

• Use Tag To together with this block to pass values between separate branches of your flow.

• Combine with Data Write Global / Data Read Global or Data Write Local / Data Read Local when you need persistent or cross-subsystem storage.

• Use Is None to check whether a tag currently holds a value before relying on it in downstream logic.

• Use Debug Input to log or inspect values being sent to a tag while developing your scenario.

• When exchanging structured data, consider Data to JSON to format multi-field data before sending it with Tag To.

• If you want to build tag names or messages dynamically, use String Merge to build the text fed into the Tag Name fields or the content sent by Tag To.

🛠️ Troubleshooting

• Duplicate tag error: Ensure no other Tag From block uses the same Tag Name. Rename one of the tags to resolve.

• Self-send warning: If a Tag To block appears to be sending to the same block that defines the tag, re-check your connections and tag names to avoid circular updates.

• Missing data: If the tag has no value, confirm the sending Tag To is active and that the source block actually produces data. Use Debug Input or Is None to help find where data is missing.