You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please note that the fix for the issue is to update the DataImporter class in the package com.adobe.acs.commons.mcp.impl.processes at line 61 setting the enableHeaderNameConversion to true
Alternative way would be to avoid passing it in the constructor since the Spreadsheet java constructor sets it to true in the class
Required Information
[6.4 ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: sp2
ACS AEM Commons Version: 3.18.3
Reproducible on Latest? yes/no- yes
Expected Behavior
I am using the data import feature to update asset's properties,
property names in the header of an excel, of the format propertyname@[] such as cq:tags@[] should be stored in aem as cq:tags and not cq:tags%5...
The value stored in aem is not cq:tags or any propertyname but a representation of(maybe creating a valid property name of @[]) "@[]"
Please note that the fix for the issue is to update the DataImporter class in the package com.adobe.acs.commons.mcp.impl.processes at line 61 setting the enableHeaderNameConversion to true
Alternative way would be to avoid passing it in the constructor since the Spreadsheet java constructor sets it to true in the class
Required Information
Expected Behavior
I am using the data import feature to update asset's properties,
property names in the header of an excel, of the format propertyname@[] such as cq:tags@[] should be stored in aem as cq:tags and not cq:tags%5...
The value stored in aem is not cq:tags or any propertyname but a representation of(maybe creating a valid property name of @[]) "@[]"
Links: https://adobe-consulting-services.github.io/acs-aem-commons/features/mcp-tools/data-importer/index.html
Actual Behavior
The aem property name should be stored as cq:tags without parsing the "@[]"
Steps to Reproduce
Attaching the sample excel sheet data
The text was updated successfully, but these errors were encountered: