In the AE XML schema, the FolderStruct element allows one to specify the structure of a folder hierarchy and the locations of objects within that hierarchy. Below are my observations about how it works.
- When importing an XML file containing a
FolderStruct element, the AE will create any folders in the specified folder hierarchy that do not already exist.
- There is no way to hard-code an absolute path in the
FolderStruct element. Any folder hierarchy specified in the FolderStruct element is interpreted as being relative to the destination folder specified at import. If you want to import to a specific path, there are two ways to do this:
- Specify in the
FolderStruct element the folder structure relative to the lowest common folder of all objects in the XML file, and during import specify that lowest common folder as the destination folder.
- Specify in the
FolderStruct element the absolute folder structure (from the root of the folder tree), and during import specify "/" as the destination folder.
- It is possible to specify the
FolderStruct element by itself, without specifying any AE objects in the same XML file. The AE will create folders even if no objects appear in the XML file.
- The
id attribute of objects mentioned in the FolderStruct element is optional and can be safely omitted/removed.
See Importing/Exporting Objects and ImportObject, .
I have not yet tested the POST /{client_id}/folderobjects REST API to see whether it behaves in a similar way.