Stupid SharePoint Delimiters

Company | Articles & Research | Services | Software |

Our Company

All SharePoint Articles

Security

Development

Accounting / Dynamics

AIS / Dynamics GP

Other

Consulting Services

Freeware / Experiments

Applications	WebParts	Security Components
SharePoint Field Diff And Copy Utility * Written In January, 2012 SharePoint Security Scanner * Written In January, 2012 SharePoint Kerberos Buddy * Written In Feburary, 2011 BioPoint: SharePoint Biometric Authentication * Written In September, 2007 SharePoint List Security Migrator * Written In August, 2007 SharePoint Anti-Keylogger™ * Written In April, 2006 S.M.A.R.T SharePoint™ * Written In May, 2006 SharePoint Sentinel™ * Written In June, 2006 SharePoint Scrubber™ * Written In July, 2006 SharePoint Safeguard™ * Written In August, 2006	SecureSilverlight For SharePoint * Written In January, 2010 Simple Rollup WebPart For SharePoint * Written In Novemember, 2009 SimpleChart For SharePoint * Written In December, 2009 SimpleSecurity For SharePoint * Written In June, 2009 CrytoCollaboration (Encryption) * Written In June, 2007 Sample AJAX Rotator WebPart * Written In July, 2007 Sample SharePoint Redirector WebPart * Written In August, 2006 WFE Server Name WebPart * Written In January, 2006	PDF IRM Protector * Written In December, 2010 ADAM Role Provider * Written In February, 2007 Universal Provider Framework * Written In April, 2007

Contact

I don't like SharePoint delimiters. They make me all sorts of mad. You really get into them when working with custom field types such as multi selection bound fields. They parse out as ";#". While that is all good for storage in SharePoint, sometimes programming against the field to pool values becomes a pain in the ass when writing WebParts or working on an arbitrary business application.

I needed a quick method to basically split on these this morning, so I threw this clunker together, which works fine. All it does is take the string parameter being passed in and use IndexOf against ";#" in order to return the first instance of the delimiter to get a starting point for the stripping. Once you have a the indexable numeric available to loop against, you can make two new strings that do the remove and replace functions, and then do all the returning.

PLAIN TEXT

C#:

public static string[] RemoveAndReplaceFieldValue(string strFieldValue)
{
if (strFieldValue == null)
throw new ArgumentNullException("strFieldValue");
int l_intIndex = strFieldValue.IndexOf(";#");
if (l_intIndex> -1)
{
string l_strRemove = strFieldValue.Remove(0, l_intIndex + 2);
string l_strReplace = strFieldValue.Replace(";#" + l_strRemove, "");
if (l_strRemove != null && l_strReplace != null)
{
return new string[] {l_strRemove, l_strReplace};
}
}
return new string[] { strFieldValue };
}

Probably not ideal, however it sure is functional.

Article Or Research Filed Under SharePoint Development.

1 Comment »

Why not use one of the value types for the SPFieldControls (SPFieldLookupValue/SPFieldMultiChoiceValue)? They account for the delimiters, and allow you to get the values out with ease.

SPFieldLookupValue splv = new SPFieldLookupValue(strFieldValue);
string value = splv.LookupValue;

Comment by Rich Finn — November 2, 2007 @ 10:55 am

RSS feed for comments on this post. TrackBack URL

Articles & Research

Latests SharePoint Development Posts

Latests SharePoint Security Posts

Stupid SharePoint Delimiters

1 Comment »

Leave a comment