Classifying keys that have special characters | Community
Skip to main content
Level 5
September 4, 2020
Solved

Classifying keys that have special characters

  • September 4, 2020
  • 3 replies
  • 2180 views

I am having trouble classifying keys for an s.eVar that contain special characters. For example, a key may look like this: Widget Makers, Inc. 

 

I've made sure that the classification template file uses "v:2.1" and not "v:2.0", as indicated in https://docs.adobe.com/content/help/en/analytics/components/classifications/faq.html, but still get a message that the classifications are not uploaded. I've tried placing quotation marks around the keys, but this also has had no effect. 

 

Any suggestions from the community?

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by vidurb80577666

While saving the file with special character for classification in excel save it as "Unicode Text" instead of tab delimited and try uploading the file. It should work.

3 replies

vidurb80577666Adobe EmployeeAccepted solution
Adobe Employee
September 4, 2020

While saving the file with special character for classification in excel save it as "Unicode Text" instead of tab delimited and try uploading the file. It should work.

Andrey_Osadchuk
Level 10
September 4, 2020

brentrad, could you share an extract with the header and the row with the mentioned value?

brentradAuthor
Level 5
September 4, 2020

Unfortunately I cannot provide the actual key values, but "Widget Makers, Inc." is a made-up value that has a similar format (i.e. commas and periods) that is currently not working in the classification file uploads. Nothing has been altered in the first four header rows of the classification template, and v:2.1 was the default version value. Note that the values being used to classify the key do not contain any special characters.

khurshid
Adobe Employee
Adobe Employee
September 4, 2020

Can you paste the screen shot of the message you are seeing? May be that could help identifying the issue.