Skip to content
Path naming convention
When using keys in directory or file name templates, you need to enclose the key in curly braces. For example, user becomes {user}.
Table 1
Soko key
Ayon key
Description
Soko key
Ayon key
Description
root[name]
root[name]
Path to root folder
studio[name]
studio[name]
Studio's full name
studio[code]
studio[code]
Studio's code
project[name]
project[name]
Project's full name
project[code]
project[code]
Project's code
parent[name]
folder[name]
Name of asset or shot
parent[type]
folder[type]
Folder type
parent[path]
folder[path]
Full folder path of asset or shot within a project
hierarchy
hierarchy
The folder path excluding the last folder name (you can use indexes in hierary e.g. hierarchy[0], hierarchy[1], hierarchy[-1] (like in python)
grandParent
parent
Name of hierarchical parent of the folder
task[name]
task[name]
Name of task
task[type]
task[type]
Type of task
task[short]
task[short]
Short name of task type (eg. Modeling ➜ mdl)
version
version
Version number
output[name]
product[name]
Product name
output[type]
product[type]
Product type
ext
ext
File extension
representation
Representation name
frame
frame
Frame number for sequence files.
app
app
Application Name
user
user
Username (can be overridden in settings-User Management
output
Extract review output profile name
comment
comment
Subversion string from workfiles tool (only relevant for workfiles template right now.)
colorspace
colorspace
Colorspace profile name
originalDirname
originalDirname
Original directory of published file
originalBasename
originalBasename
Original file name without extension
suffix
variant
There are no rows in this table
Publishing folder DD
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.