Verify that there are no special Latin characters when importing asset metadata.
Select the UTF-8 Unicode type if the metadata is stored in Excel and you intend to save it as a CSV.
Consider exporting metadata for specific custom properties only.
Ensure that the custom namespace is correctly registered, as builds in CM will fail otherwise.
Make sure an index is created for the custom properties.
Always take a copy of the damAssetLucene index from the same version of production or the latest version to create a custom index; failing to do so will result in a build failure in CM.
Renaming is not supported in Azure Storage; assets must be recreated, so avoid modifying assets in Azure Storage.
Always enable duplicate detection, though it only applies to the first 100 assets.
Keep the number of search filters limited, as using too many fields in the request header can overflow it and cause the search to fail. Depending on the situation, exceeding the limit may lead to Fastly closing the client connection, or the client may receive either a 502 Gateway Error with an I/O error or a 503 Service Unavailable response with a header overflow error. For more details, refer to https://docs.fastly.com/products/network-services-resource-limits.
To create folders dynamically, add mixinType: mix:referenceable to generate a jcr:uuid, allowing folders to be referenced.
Always use a hyphen as a word separator, and ensure that asset names do not exceed 150 characters.
