We are in the process of building comma separated values calculated fields to map to AEM tags. Currently there are multiple fields from Workfront that need to be mapped to one AEM Tags.
Each of the fields we have above are multi-select dropdown fields. I am using the expression ,", ", between each fields to separate them by a comma and also a space.
After multiple tests, we found out that there is no issue faced if all options are selected. However, when not all options are selected, there will be commas and spaces in between the values for each fields that were not selected in the form. Here's an example of how the result of the calculated field looks like:
Please note that the above is only an example and I am not able to disclose our values due to data privacy. I believe the commas and spaces in between or at the end of the values are causing the whole data selected not to be mapped from WF to AEM.
I am sure that there is a way to correctly do this as the Workfront experience league article itself has advised us to use calculated fields. I am not sure how can I change my expression.
Is there anyone that has successfully mapped WF fields to AEM that can help us in building this? Any help is greatly appreciated. Thanks!
Topics
Topics help categorize Community content and increase your ability to discover relevant content.