Enhanced rich text codes showing up in data that is exported, and after it was converted

%3CLINGO-SUB%20id%3D%22lingo-sub-2331730%22%20slang%3D%22en-US%22%3EEnhanced%20rich%20text%20codes%20showing%20up%20in%20data%20that%20is%20exported%2C%20and%20after%20it%20was%20converted%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2331730%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20had%20a%20manager%20of%20a%20large%20team%20come%20to%20us%20and%20ask%20us%20for%20direct%20access%20to%20the%20sql%20data%20for%20their%20site%20so%20they%20could%20export%20it%20into%20some%20other%20formats%20to%20be%20used%20in%20other%20applications.%26nbsp%3B%20Needless%20to%20say%2C%20we%20said%20no.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20in%20the%20ensuing%20discussions%20we%20thought%20we%20had%20a%20fix.%26nbsp%3B%20Export%20the%20data%20to%20csv%20and%20that%20would%20be%20good.%26nbsp%3B%20The%20only%20problem%20was%20that%20the%20data%20was%20in%20an%20Enhanced%20Rich%20Text%20multiline%20column%2C%20and%20when%20we%20exported%20it%20we%20got%20lots%20of%20html%20code%20mixed%20in%20the%20data.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20we%20thought%20we%20would%20convert%20the%20column%20to%20just%20regular%20Rich%20Text%2C%20since%20none%20of%20the%20business%20users%20ever%20uploaded%20pictures.%26nbsp%3B%20The%20only%20problem%20is%20that%20now%20we%20have%20those%20same%20kinds%20of%20codes%20mixed%20into%20all%20of%20their%20records%2C%20even%20before%20they%20are%20exported.%26nbsp%3B%20We%20converted%20the%20column%20back%20to%20enhanced%20rich%20text%2C%20but%20those%20characters%20are%20still%20showing%20up%20unfortunately.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20suggestions%20on%20what%20we%20can%20do%20about%20this%3F%26nbsp%3B%20%26nbsp%3BI'd%20love%20to%20find%20a%20way%20to%20convert%20this%20back%20to%20rich%20text%2C%20and%20then%20get%20rid%20of%20the%20codes%2C%20and%20then%20we%20could%20just%20export%20the%20data%20without%20the%20codes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20someone%20will%20suggest%20writing%20a%20powershell%20script%20to%20do%20that%2C%20but%20that%20is%20WAY%20beyond%20my%20scripting%20abilities.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3CP%3ETed%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EP.S.%20It's%20a%20large%20list.%26nbsp%3B%20Just%20dumping%20it%20to%20csv%20takes%20forever.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2331730%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Contributor

We had a manager of a large team come to us and ask us for direct access to the sql data for their site so they could export it into some other formats to be used in other applications.  Needless to say, we said no.

 

So in the ensuing discussions we thought we had a fix.  Export the data to csv and that would be good.  The only problem was that the data was in an Enhanced Rich Text multiline column, and when we exported it we got lots of html code mixed in the data.

 

So we thought we would convert the column to just regular Rich Text, since none of the business users ever uploaded pictures.  The only problem is that now we have those same kinds of codes mixed into all of their records, even before they are exported.  We converted the column back to enhanced rich text, but those characters are still showing up unfortunately.

 

Any suggestions on what we can do about this?   I'd love to find a way to convert this back to rich text, and then get rid of the codes, and then we could just export the data without the codes.

 

I know someone will suggest writing a powershell script to do that, but that is WAY beyond my scripting abilities.

 

Thanks.

Ted

 

P.S. It's a large list.  Just dumping it to csv takes forever.

0 Replies