Optinal fields

Pipeline Integrations
#1

Hello!

According to this guide - Integrations File System Reference – Shotgun Support - there is a way to utilize so called “optional” fields. But how? The example creates a folder with an optional field in use. If I try to utilize syntax with “” nothing works. Are there any in-depth guides on this topic, or any further information. The documentation is more confusing, than helping :confused:

Best regards,
Dietmar

#2

Optional fields work fine for filenames, but I wonder how they’d work for folders, given that they have to conform to your folder schema. You may have to provide branching paths (e.g. one with and one without the optional field) in your folder schema.
Someone with more experience in this should chime in.
Could you explain a bit more about “nothing works”? Were there errors?