Commands

Yes, you can. Make a new command node, and use the command Insert Tana Paste with the following prompt:

- ${name} #note
  - Based on:: [[^${sys:nodeId}]]

The first line is the new node. It uses the name of the current node to inform the name of the new node by using the title expression ${name}. The supertag #note can be enough for Tana to find the right tag to use, but you can specify it more precisely by adding the ^nodeID to it. See the Tana Paste doc for more info on this convention. To retrieve the nodeID of a supertag, run the command Copy link (HTML formatted) on a supertag definition and paste the results. It will paste with the nodeID written out:

The second line is the field. After the name of the field and the double-colon :: is a reference to the current node that the command is being run on, which it is able to target by retrieving the nodeID of the current node using the title expression ${sys:nodeId}.

This is what the command node should look like:

Special thanks to Navigator Emmanuel Galanos for this clever solution!

Related docs:

• Commands
• Tana Paste
• Command nodes

Use Insert relative date command, here's an example:

Related docs:

• Commands
• Dates and Calendar nodes
• Command nodes

Currently, the easiest and most foolproof way to do this is to not share it but instead build the supertag, with its fields and anything else necessary for the supertag to work, from the ground up in the new space.

That said, if you still want to move a supertag over that exists only in your private workspace, the main work is to ensure that there's nothing in the supertag that references something in your private workspace, otherwise it will appear as broken to others once it's moved.

It's like packaging up a zip file. You can't just zip up a bunch of shortcuts, you need the real files in there or the recipient will only see broken shortcuts.

You'll also have to remember to move over other things like field options, commands, and ensure that no saved view options contain elements from your workspace. Basically, you must ensure that nothing you're moving over from your workspace contains references from your workspace.

To bring all nodes (except system nodes) into the supertags, fields and commands you want to move, use the command "Bring referenced node here". Alternatively, you can move each necessary node separately too if you foe example want the field definition to exist outside the supertag. But the key is that everything that is connected to what you're sending over gets sent over too, otherwise there will be missing pieces.

Related docs:

• Supertags
• Fields
• Commands
• Workspaces
• Command nodes

The Autofill command can generate a new node title and description based on the URL.

To set up the command

• Create a new command node
• Add the Autofill fields command
• Add and check off Autofill title and Autofill description parameters to change both
• Add Model to use to control which model you prefer. If left empty, Tana will pick the one that returns the answer with best quality and consistency

To run the command

• Run the command on a URL node using the command line
• Put this command node in the Commands section of a supertag you use for URLs. Press the button to run the command.

Related docs:

• Commands
• Command nodes

There is a command called Set view definition. It can set the Group, Sort and Display settings of a node view.

There is no good UX for this at the moment, so the instructions are not conventional nor friendly for beginners. But right now, this is one way of doing it:

• Mock up a node that will have sample child nodes representing the data you'll be applying this command on
• Then, create the exact view settings you want with Group, Sort and Display.
• Go Cmd/Ctrl+K > Debug Node on the parent node and look at Views for node:

• Clone the fields over to the command node so it looks like this:

When you run this command on a node, this should change the view settings according to your configuration.

Related docs:

• Views
• Commands
• Command nodes

Set [field] command only works on field types Option, Instance, User and Checkbox.

Related docs:

• Fields
• Commands
• Command nodes