Why does metadata export for a folder fail with “String is too long” exception?

When you export metadata for a folder from the Assets UI, the export job can fail with String is too long exception. This typically happens when the folder contains Experience Manager Guides specific properties that store non-string values, such as baselineObj.

Why does this happen?

Some properties stored under an asset’s metadata node are used internally by Experience Manager Guides and contain data, such as JSON objects, rather than plain string values. When exporting metadata for a folder, if Properties to be exported is set to All, the export job attempts to convert every property to a string, and it fails on properties that hold this kind of data.

How is this prevented?

To avoid this failure, the following properties are excluded from metadata export by default in the Asset Metadata Exporter Configuration:

Can I still export these properties?

Yes. If you need one or more of these properties in the export, you can edit the Asset Metadata Exporter Configuration and remove them from the exclusion list.

Removing a property from the exclusion list does not guarantee that the export will succeed. Depending on the size and content of the underlying data, the job may still fail with the same exception. If you run into this after re-enabling a property, add it back to the exclusion list to restore the default, reliable export behavior.