Required Lookup
Today I had a requirement to make a lookup field required and set the default value. For a lookup field this isn’t possible within the SharePoint 2010 interface.
My solution
Programmatically the SPFieldLookup also doesn’t have the options available. However casting the Lookup to an SPField does the trick.
public overridevoid FeatureActivated(SPFeatureReceiverProperties properties)
{
try
{
SPWeb web = (SPWeb)properties.Feature.Parent;
SPList list = web.Lists["MyList"];
SPField lookup = (SPField)list.Fields["My Lookup"];
lookup.DefaultValue = "1;#Value 1";
lookup.Required = true;
lookup.Update();
}
catch(Exception Ex)
{
// do what ever you want
}
}

Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There’s a better way — and I can show you exactly what it looks like.
I’m the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide.
For over 30 years I’ve been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions.
SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://staging.sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/
Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://staging.sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/
You can contact me using contact@staging.sharepains.com
Leave a Reply
You must be logged in to post a comment.