Solved! Go to Solution.
Views
Replies
Total Likes
1. Ensure Permissions: Make sure the user executing the TagUI script has permissions to edit metadata in the DAM, including creating new properties. Check user roles (e.g., DAM Admin or Author).
2. Verify Metadata Schema: Confirm the custom metadata schema is applied to the asset types (e.g., images, documents) in the DAM. It must be associated correctly.
3. Create Metadata Node for New Assets: Ensure your script handles assets that don't have the metadata properties. You may need to use AEM's REST API to create the metadata nodes for new assets before modifying them. Example:
POST /bin/querybuilder.json
{
"path": "/content/dam/your-folder",
"type": "dam:Asset",
"p.limit": "-1"
}
4. TagUI Execution: Ensure the TagUI script is run with the correct user credentials and permissions. Simulate metadata field updates with set and click commands as needed.
Views
Replies
Total Likes
1. Ensure Permissions: Make sure the user executing the TagUI script has permissions to edit metadata in the DAM, including creating new properties. Check user roles (e.g., DAM Admin or Author).
2. Verify Metadata Schema: Confirm the custom metadata schema is applied to the asset types (e.g., images, documents) in the DAM. It must be associated correctly.
3. Create Metadata Node for New Assets: Ensure your script handles assets that don't have the metadata properties. You may need to use AEM's REST API to create the metadata nodes for new assets before modifying them. Example:
POST /bin/querybuilder.json
{
"path": "/content/dam/your-folder",
"type": "dam:Asset",
"p.limit": "-1"
}
4. TagUI Execution: Ensure the TagUI script is run with the correct user credentials and permissions. Simulate metadata field updates with set and click commands as needed.
Views
Replies
Total Likes