When you’re developing custom code for SharePoint, sometimes you’ll have a situation where you’re dynamically adding form field controls to your control or WebPart and the form context will not be automatically picked up by the controls. If you’re using them outside a new, display or edit form for example.<\/p>\n
It’s relatively simple to force the control(s) to the desired context but there’s something you should be aware of.<\/p>\n
Take a look the following code:
\n<\/p>\n
\r\nprivate void SetFormFieldContext(FieldMetadata formfield, Guid listId, int itemId)\r\n{\r\n formfield.ListId = listId;\r\n formfield.ControlMode = ControlMode;\r\n \r\n \/\/ Get the SPContext object based on the current web and specified list id and item id. \r\n SPContext context = SPContext.GetContext(HttpContext.Current, itemId < 0 ? 0 : itemId, listId, SPContext.Current.Web);\r\n formfield.RenderContext = context;\r\n formfield.ItemContext = context;\r\n \r\n if (ControlMode == SPControlMode.Display || ControlMode == SPControlMode.Edit)\r\n {\r\n formfield.ItemId = itemId;\r\n }\r\n}\r\n<\/pre>\nThe important part is to manually set the form field's ListId property, as this is not updated after setting RenderContext or ItemContext as you might expect.<\/p>\n
The same applies to the ItemId property.<\/p>\n","protected":false},"excerpt":{"rendered":"
When you’re developing custom code for SharePoint, sometimes you’ll have a situation where you’re dynamically adding form field controls to your control or WebPart and the form context will not be automatically picked up by the controls. If you’re using … Continue reading