I have an RCDC with a number of minimum fields that are required to submit the form, i.e. dropdowns and textboxes and one UocIdentityPicker to pick another entity, but with this one it is possible to completely ignore the control and continue to the next tab and create the entity. Here is the XML: <my:Control my:Name="parentRef" my:TypeName="UocIdentityPicker" my:Caption="Discipline" my:Description="" my:RightsLevel="{Binding Source=rights, Path=parentRef}"><br/> <my:Properties><br/> <my:Property my:Name="ReadOnly" my:Value="false" /><br/> <my:Property my:Name="Required" my:Value="{Binding Source=schema, Path=parentRef.Required}" /><br/> <my:Property my:Name="ColumnsToDisplay" my:Value="DisplayName" /><br/> <my:Property my:Name="AttributesToSearch" my:Value="DisplayName" /><br/> <my:Property my:Name="Value" my:Value="{Binding Source=object, Path=parentRef, Mode=TwoWay}" /><br/> <my:Property my:Name="Mode" my:Value="SingleResult" /><br/> <my:Property my:Name="UsageKeywords" my:Value="Disciplines" /><br/> <my:Property my:Name="ListViewTitle" my:Value="Select Discipline" /><br/> <my:Property my:Name="ObjectTypes" my:Value="Discipline" /><br/> <my:Property my:Name="Hint" my:Value="{Binding Source=schema, Path=parentRef.Hint}" /><br/> <my:Property my:Name="MainSearchScreenText" my:Value="Select the parent discipline by searching above" /><br/> </my:Properties><br/> </my:Control> The Required property is clearly defined. Am I doing something wrong here? Any help appreciated.

I don't have <BR> elements in there, this site did that.

Have you try to modify the 4th line to <my:Property my:Name="Required" my:Value="true" /> That should force the field to be required. You can get the same control definition from the DisplayOwner in the Configuration for Group Creation RCDC

I tried that, but it didn't work, the field still isn't required. There's no red asterisk, and you can continue to the next tab.

Hi There, I haven't tried this particular control but I was also having that problem with "UocCheckBox" controls where the "Required" value being set to true wouldn't make the field mandatory. I got around it by using the "DefaultValue" to set the most common setting. However, referring to the RCDC guide, this option isn't available for the UocIdentityPicker. :( Thanks Blain

Thanks Blain. a work-around like that wouldn't be acceptable for us unfortunately. I need to have a look at DropDown lists as well, instead of an identity picker, but from what I've seen already, those are very limited as well. I'm at a loss as to why the UI is so difficult to configure and restrictive it is.

Are you sure you ran an IISRESET on your front-end servers after uploading the new RCDC? You won't actually see it take effect until either you do or your cache times out and the page reloads the schema and object definitions.Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com [If a post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]

Hi There (again!) :) I was playing within an RCDC yesterday and I was able to put my UocIdentityPicker as a required field. I had explicitly used the property value of: <my:Property my:Name="Required" my:Value="True"/> I even tried it with "true" and "True" with both values working okay. (I've seen some case sensitivity issues in a couple areas so I thought I'd try). If you're not getting any joy with the IISReset, perhaps you may want to try to reset the FIM Service itself (although this should have no effect but sometimes, you just have to try these things). :) Thanks B

Thanks Blain, I'll give that a go once we've got our new lab setup and everything working post-migration! OCG... Oxford? We've had Steve in here, he left last week. Very helpful chap. Saw you guys at the FIM London launch as well earlier this year.

Hi There, Yep, you tagged me, the low key OCG guy... :) I'm part of the North American subsidiary based out of California. Glad to be of help. B