AnsweredAssumed Answered

Tokenize to replace not append?

Question asked by Keith O'Toole Employee on Apr 26, 2017
Latest reply on Apr 27, 2017 by Ben Isherwood

Idiot playing in a lab, I apologize for how basic this question is:


I've got a Content Class that generates multiple returns on a pattern. The class will semicolon the multiple returns within one field. Then when I go into a basic/default index the index pukes on my semicolons, even in a multivalue field. Tokenize seems to be the right way to go, but tokenize will either append (leaving the semicolons) or make a new field, leaving the bad one too. If I tokenize into a new field, how do I drop the "bad" non-tokenized fields so they don't get indexed?