According to the docs at Folder Formats [Directory Opus Manual], if "the Expand aliases option is turned on then Opus will attempt to expand folder aliases and environment variables in the entered string before performing the pattern matching."
However, neither environment variables (e.g. %SHAREX_DIR%) nor aliases (e.g. /dopusdata) seem to work - the folder format is not applied in the respective folders. Also the syntax outlined in the docs (/$dopusdata; why is an $ needed here?) does not work.
However, neither environment variables (e.g. %SHAREX_DIR%) nor aliases (e.g. /dopusdata) seem to work - the folder format is not applied in the respective folders.
Also the syntax outlined in the docs (/$dopusdata; why is an $ needed here?) does not work.
"For example, /$Data (which is a folder alias for a drive called Data) would let you create a folder format that applies to a drive labeled Data no matter what drive letter it has."
Do you have a drive (not a folder) labeled as dopusdata?
My bad, I had a mis-configured wildcard folder format that was always applied and took precedence over the content type format - so it seemed like it doesn't work. Issue is resolved.
Thanks. Also for clarifying /$DRIVENAME, that's clear now as well.
The docs don't literally say /$dopusdata, but /$Data. I assumed the /$ is the needed notation to use an alias in the wildcard path (so I tried /$dopusdata just to test it), which was a misunderstanding from my side. So all good, docs are correct Thanks!
The manual page explains what /$Data is right after it uses it.
/$xyz is an alias that will take you to a drive whose label is xyz. It's useful for removable devices that might not always get the same drive letter, and works automatically without having to define the alias and path it points to each time it changes.
